February 15, 2017 | Author: Zahirul Islam Onirban | Category: N/A
Download Atoll 3.1.2 User Manual Radio E1...
User Manual Radio
v e r s i o n 3.1.2
AT312_UM_E1
AT312_UM_E1
experts in radio network planning & optimisation software
Forsk USA Office
Forsk Head Office
Forsk China Office
200 South Wacker Drive
7 rue des Briquetiers
Suite 302, 3/F, West Tower,
Suite 3100
31700 Blagnac
Jiadu Commercial Building,
Chicago, IL 60606
France
No.66 Jianzhong Road,
USA
Tianhe Hi-Tech Industrial Zone, Guangzhou, 510665, People’s Republic of China
[email protected]
[email protected]
[email protected]
+1 312 674 4800
+33 (0) 562 747 210
+86 20 8553 8938
+1 312 674 4847
+33 (0) 562 747 211
+86 20 8553 8285
[email protected]
[email protected]
[email protected]
+1 888 GoAtoll (+1 888 462 8655)
+33 (0) 562 747 225
+86 20 8557 0016
8.00 am to 8.00 pm (EST)
9.00 am to 6.00 pm (CET)
9.00 am to 5.30 pm (GMT+8)
Monday - Friday
Monday - Friday
Monday - Friday
www.forsk.com
Atoll 3.1.2 User Manual
© Forsk
Atoll 3.1.2 User Manual Release AT312_UM_E1
© Copyright 1997 - 2012 by Forsk The software described in this document is provided under a licence agreement. The software may only be used or copied under the terms and conditions of the licence agreement. No part of this document may be copied, reproduced or distributed in any form without prior authorisation from Forsk. The product or brand names mentioned in this document are trademarks or registered trademarks of their respective registering parties. The Atoll user documentation is a guide and reference for users working with Atoll. Atoll is easy to use and offers a clear, self-explanatory user interface. The user documentation helps the user make effective and efficient use of all the features that Atoll offers. The user documentation aims to familiarise the user with the working environment of Atoll and enable him to use all of Atoll’s features and functions. The Atoll user documentation is technology-specific. For each Atoll radio technology, the Atoll user manual contains instructions and information specific to that technology as well as chapters describing the Atoll working environment and the tools available.
4
Atoll 3.1.2 User Manual Table of Contents
AT312_UM_E1
Table of Contents
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
5
The Working Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.1 1.1.1 1.1.1.1 1.1.1.2 1.1.1.3 1.1.2 1.1.2.1 1.1.2.2 1.1.2.3 1.1.2.4
The Atoll Work Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Selecting a Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Selecting a Window Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Selecting a Window from the Windows Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Using the Windows Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Organising the Atoll Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Creating a New Map Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Arranging Tool and Explorer Windows Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Using Tab Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Resetting the Workspace Layout to the Default View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.2 1.2.1 1.2.2 1.2.3 1.2.4 1.2.5
The Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Working with the Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Working with the Site Configuration Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Automatically Hiding Explorer Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Displaying or Hiding Objects on the Map Using the Explorer Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Working with Layers Using the Explorer Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.3 1.3.1 1.3.1.1 1.3.1.2 1.3.1.3 1.3.2 1.3.2.1 1.3.2.2 1.3.2.3 1.3.2.4 1.3.2.5 1.3.3 1.3.3.1 1.3.3.2
Working with Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Using the Object Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Renaming an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Deleting an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Displaying the Properties of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Modifying Sites and Transmitters Directly on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Selecting One of Several Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Moving a Site Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Moving a Site to a Higher Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Changing the Azimuth of the Antenna Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Changing the Antenna Position Relative to the Site Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Display Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Defining the Display Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Examples of Using the Display Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
1.4 1.4.1 1.4.1.1 1.4.1.2 1.4.1.3 1.4.1.4 1.4.2 1.4.3 1.4.4 1.4.5 1.4.6 1.4.7 1.4.8 1.4.9 1.4.10 1.4.11 1.4.12 1.4.12.1 1.4.12.2 1.4.12.3 1.4.12.4 1.4.12.5
Working with Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Changing the Map Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Zooming In and Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Zooming In on a Specific Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Choosing a Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Changing Between Previous Zoom Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Using Full Screen Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Moving the Map in the Document Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Using the Panoramic Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Centring the Map Window on an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Centring the Map Window on a Table Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Adjusting the Map Window to a Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Measuring Distances on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Displaying Rulers Around the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Displaying the Map Scale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Displaying the Map Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Using Zones in the Map Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Filtering Zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 The Computation Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 The Focus Zone and Hot Spots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Using Polygon Zone Editing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Using a Printing Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5
Atoll 3.1.2 User Manual Table of Contents
1.4.12.6 1.4.13 1.4.13.1 1.4.13.2 1.4.13.3 1.4.13.4 1.4.13.5 1.4.13.6 1.4.14 1.4.15
6
© Forsk 2012
Using a Geographic Export Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Editing Polygons, Lines, and Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Adding a Vector Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Creating Polygons, Lines, and Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Editing the Shape of Polygons and Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Combining or Cropping Polygons Using the Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Editing a Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Editing Contours, Lines, and Points Using the Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Copying the Content of a Zone into Another Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Map Window Pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
1.5 1.5.1 1.5.1.1 1.5.1.2 1.5.2 1.5.2.1 1.5.2.2 1.5.2.3
Working with Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Organising the Contents of the Predictions Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Creating a Predictions Sub-folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Moving a Coverage Prediction into a Sub-folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Exporting Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Exporting an Individual Coverage Prediction in Vector Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Exporting an Individual Coverage Prediction in Raster Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Exporting Multiple Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
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.6.5.1 1.6.5.2 1.6.5.3 1.6.6 1.6.7 1.6.8 1.6.9 1.6.10
Working with Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Opening a Data Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 Adding, Deleting, and Editing Data Table Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 Accessing an Object Type’s Table Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 Adding a Field to an Object Type’s Data Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Deleting a Field from an Object Type’s Data Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Opening an Object’s Record Properties Dialogue from a Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Defining the Table Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 Editing the Contents of a Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Editing Table Entries Directly in the Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Copying and Pasting in Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 Searching for and Replacing Text Entries in Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 Viewing a Statistical Analysis of Table Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Exporting Tables to Text Files and Spreadsheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Importing Tables from Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Exporting Tables to XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Importing Tables from XML Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
1.7 1.7.1 1.7.2 1.7.2.1 1.7.2.2 1.7.2.3 1.7.3 1.7.4 1.7.5
Printing in Atoll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Printing Data Tables and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Printing a Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Printing Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Defining the Printing Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Defining the Print Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 Previewing Your Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Printing a Docking Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Printing Antenna Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
1.8 1.8.1 1.8.1.1 1.8.1.2 1.8.1.3 1.8.1.4 1.8.2 1.8.2.1 1.8.2.2 1.8.3 1.8.3.1 1.8.3.2 1.8.3.3 1.8.3.4 1.8.4 1.8.4.1 1.8.4.2 1.8.5 1.8.5.1 1.8.5.2
Grouping, Sorting, and Filtering Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 Grouping Data Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 Grouping Data Objects by a Selected Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 Configuring the Group By Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Advanced Grouping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Examples of Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 Sorting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Sorting Data in Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Advanced Sorting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Filtering Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Filtering in Data Tables by Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Advanced Data Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Restoring All Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Advanced Filtering: Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 User Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Saving a User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Loading a User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Site and Transmitter Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Creating a Site or Transmitter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Adding a Site or Transmitter to a List in the Network Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
AT312_UM_E1
Atoll 3.1.2 User Manual Table of Contents
1.8.5.3 1.8.5.4 1.8.5.5 1.8.5.6 1.8.5.7 1.8.5.8 1.8.6 1.8.6.1 1.8.6.2 1.8.6.3 1.8.6.4 1.8.6.5 1.8.6.6 1.8.7 1.8.8
Adding a Site or Transmitter to a List from the Map Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Adding Sites or Transmitters to a List Using a Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Editing a Site or Transmitter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Importing a Site or Transmitter List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Exporting a Site or Transmitter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Filtering on a Site or Transmitter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Folder Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Creating a Folder Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Applying a Saved Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Reapplying the Current Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Saving a Folder Configuration in an External File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Loading a Folder Configuration from an External File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Deleting a Folder Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Creating and Comparing Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Filtering Data Using a Filtering Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
1.9 1.9.1 1.9.2 1.9.3 1.9.3.1 1.9.3.2 1.9.3.3 1.9.4 1.9.5 1.9.6 1.9.7
Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Undoing and Redoing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Refreshing Maps and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Searching for Objects on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Searching for a Map Object by Its Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Searching for a Map Object using Any Text Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Searching for a Point on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Using the Status Bar to Get Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Saving Information Displayed in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Using Icons from the Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Using Shortcuts in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2
Starting an Atoll Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
2.1
Before Starting a Radio-Planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
2.2 2.2.1 2.2.1.1 2.2.1.2 2.2.1.3 2.2.2 2.2.2.1 2.2.2.2 2.2.2.3 2.2.2.4 2.2.2.5
Creating an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Creating a New Atoll Document from a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Templates Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Creating a New Atoll Document from a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Defining a New Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Working in a Multi-User Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 The Atoll Multi-User Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Creating a New Atoll Document from a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Working With a Document on a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Refreshing an Atoll Document from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Archiving the Modifications of an Atoll Document in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
2.3 2.3.1 2.3.2
Making a Backup of Your Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Configuring Automatic Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Recovering a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
2.4
Making and Sharing Portable Atoll Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3
Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
3.1
Geographic Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
3.2
Supported Geographic Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.3 3.3.1 3.3.2 3.3.3 3.3.3.1 3.3.3.2 3.3.4 3.3.5 3.3.6 3.3.7
Importing Geo Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Importing a Raster-format Geo Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Importing a Vector-format Geo Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Importing MSI Planet® Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Importing One MSI Planet® Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Importing a MSI Planet® Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Importing a WMS Raster-format Geo Data File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Grouping Geo Data Files in Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Embedding Geographic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Repairing a Broken Link to a Geo Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
3.4
Digital Terrain Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
7
Atoll 3.1.2 User Manual Table of Contents
3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5
Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Names to Clutter Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Clutter Class Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Clutter Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Refreshing the List of Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Total Surface Area per Clutter Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6
Clutter Heights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
3.7 3.7.1 3.7.2 3.7.3
Contours, Lines, and Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing the Display of a Vector Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing the Properties of the Vector Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving a Vector Layer to the Network Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8 3.8.1 3.8.2
Scanned Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Importing Several Scanned Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Defining the Display Properties of Scanned Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
3.9 3.9.1 3.9.2
Population Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Managing the Display of Population Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Displaying Population Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
3.10 3.10.1 3.10.2 3.10.3 3.10.4 3.10.5
Custom Geo Data Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Custom Geo Data Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a File to a Custom Geo Data Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing the Properties of a Custom Geo Data Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Statistics on Custom Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrable Versus Non Integrable Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
152 152 153 154 154 154
3.11 3.11.1 3.11.2 3.11.2.1 3.11.2.2 3.11.2.3
Setting the Priority of Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Display Priority of Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Priority of Geo Data in Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 1: Two DTM Maps Representing Different Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 2: Clutter Classes and DTM Maps Representing the Same Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 3: Two Clutter Class Maps Representing a Common Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155 155 156 156 157 157
3.12
Displaying Information About Geo Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
3.13 3.13.1 3.13.2
Geographic Data Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Exporting a Geo Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Loading a Geo Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
3.14 3.14.1 3.14.1.1 3.14.1.2 3.14.1.3 3.14.1.4 3.14.2
Editing Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Clutter Class Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Clutter Polygon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Clutter Polygons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Coordinates of Clutter Polygons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Clutter Polygons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Population or Custom Data Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
160 160 160 160 161 161 161
3.15 3.15.1 3.15.1.1 3.15.1.2 3.15.2 3.15.3 3.15.4 3.15.5
Saving Geographic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving Modifications to an External File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting an Edited Clutter Class Map in a Raster-Format File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting an Edited Vector Layer in Vector-Format File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Source File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combining Several Raster Files into One File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting an Embedded File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New File from a Larger File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
162 163 163 164 164 165 165 166
4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6
8
© Forsk 2012
144 144 145 147 147 148
148 149 149 150
Antennas and Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Working With Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Antenna. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Planet-Format Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing 3-D Antenna Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Antenna Patterns With a Fixed Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Smoothing an Antenna Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing an Antenna Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
171 171 173 173 175 175 175
AT312_UM_E1
4.2 4.2.1 4.2.2 4.2.3 4.2.4
5
Atoll 3.1.2 User Manual Table of Contents
Working With Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Defining TMA Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Defining Feeder Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Defining Transmitter Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Updating the Values for Total Losses and the Transmitter Equipment Noise Figure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Working with Calculations in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
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 5.1.13 5.1.14
Working with Propagation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Propagation Model Characteristics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 The Standard Propagation Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Recommendations for Working with the Standard Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Calculating Diffraction With the SPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Sample Values for SPM Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Calculating f(clutter) with the Standard Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Modelling Fixed Receivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Defining the Parameters of the Standard Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 The Okumura-Hata Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Defining General Settings (Okumura-Hata) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Selecting an Environment Formula (Okumura-Hata). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Creating or Modifying Environment Formulas (Okumura-Hata) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 The Cost-Hata Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Defining General Settings (Cost-Hata) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Selecting an Environment Formula (Cost-Hata) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Creating or Modifying Environment Formulas (Cost-Hata). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 The ITU 529-3 Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Defining General Settings (ITU 529-3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Selecting an Environment Formula (ITU 529-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Creating or Modifying Environment Formulas (ITU 529-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 The ITU 370-7 Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 The Erceg-Greenstein Propagation Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Defining General Settings (Erceg-Greenstein (SUI)). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Selecting an Environment Formula (Erceg-Greenstein (SUI)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Creating or Modifying Environment Formulas (Erceg-Greenstein (SUI)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 The ITU 526-5 Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 The WLL Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 The Longley-Rice Propagation Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 The ITU 1546 Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 The Sakagami Extended Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 CrossWave Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Managing Propagation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5
Defining Calculation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Defining Calculation Parameters for One Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Defining the Same Calculation Parameters for a Group of Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Defining the Same Calculation Parameters for All Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Defining a Default Propagation Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Defining a Default Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.3.7 5.3.7.1 5.3.7.2 5.3.7.3 5.3.7.4 5.3.7.5 5.3.8
Managing Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Stopping Path Loss Matrix Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Setting the Storage Location of Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Using Centralised Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Checking the Validity of Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Optimising Path Loss Matrix Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Tuning Path Loss Matrices Using Measurement Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Defining the Area to be Tuned. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Defining Maximum Corrections and Thresholds on Path Loss Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Tuning Path Loss Matrices Using CW Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Tuning Path Loss Matrices Using Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Managing the Path Loss Tuning Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Exporting Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
5.4 5.4.1 5.4.1.1 5.4.1.2
Predictions Available in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Making Point Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Starting a Point Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 The Views of the Point Analysis Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
9
Atoll 3.1.2 User Manual Table of Contents
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 5.4.2.7
6
© Forsk 2012
Moving the Receiver on the Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Taking Indoor Losses into Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Taking Shadowing into Account in Point Analyses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Storage Location of Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting the Values per Pixel of a Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving Defined Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating Indoor Coverage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Taking Shadowing into Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214 214 214 215 215 216 217 219 219 221 221
Automatic Cell Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
6.1 6.1.1 6.1.2 6.1.2.1 6.1.2.2 6.1.2.3 6.1.3 6.1.4 6.1.5 6.1.5.1 6.1.5.2 6.1.6
The ACP Module and Atoll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Quality and Cost Objectives in the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Zones with ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Computation Zone and the Focus Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Custom Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Filtering Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Traffic Maps with ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shadowing Margin and Indoor Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACP and Antenna Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Native Propagation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-Native Propagation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMF Exposure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
225 226 226 226 226 227 227 227 227 228 228 229
6.2 6.2.1 6.2.2 6.2.3
Configuring the ACP Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Storage Location of ACP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Antenna Masking Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
229 230 230 231
6.3 6.3.1 6.3.1.1 6.3.1.2 6.3.1.3 6.3.2 6.3.2.1 6.3.2.2 6.3.2.3 6.3.2.4 6.3.2.5 6.3.2.6
Optimising Cell Planning with the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Optimisation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Optimisation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running an Existing Optimisation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicating an Existing Optimisation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Optimisation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Optimisation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Objective Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Network Reconfiguration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Site Selection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Antenna Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Comments to the Optimisation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
233 233 234 234 234 234 235 242 246 255 262 267
6.4
Running an Optimisation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
6.5
Working with Optimisations in the Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
6.6 6.6.1 6.6.1.1 6.6.1.2 6.6.1.3 6.6.1.4 6.6.1.5 6.6.1.6 6.6.2 6.6.3 6.6.3.1 6.6.3.2 6.6.3.3 6.6.3.4 6.6.3.5 6.6.3.6 6.6.4
Viewing Optimisation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Optimisation Results in the Properties Dialogue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Statistics Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Sectors Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Graph Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Quality Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Change Details Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Commit Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comparing Optimisations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Optimisation Results in the Map Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Objective Analysis Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Technology Layer Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The EMF Exposure Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comparing Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Display Properties of ACP Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting ACP Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Optimisation Results Using the Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
270 271 271 273 274 275 277 278 278 280 281 281 283 283 284 285 286
AT312_UM_E1
7
Atoll 3.1.2 User Manual Table of Contents
Multi-RAT Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
7.1
Designing a Multi-RAT Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.2.7 7.2.8 7.2.9 7.2.10 7.2.10.1 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.12 7.2.12.1 7.2.12.2 7.2.12.3
Planning and Optimising Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Creating a Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Creating a Group of Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Modifying Sites and Transmitters Directly on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Display Tips for Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Creating a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Creating a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Setting the Working Area of an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Studying a Single Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Studying Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Multi-RAT Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Making a Multi-RAT Effective Service Area Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Planning Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Importing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Planning Intra-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Planning Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Displaying Neighbours on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Allocating and Removing Neighbours on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Displaying Exceptional Pairs on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Adding and Removing Exceptional Pairs on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Allocating Resources in a Multi-RAT Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Allocating Resources in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Allocating Resources in UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Allocating Resources in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
7.3 7.3.1 7.3.2 7.3.3 7.3.3.1 7.3.3.2 7.3.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.5 7.3.6 7.3.7 7.3.8 7.3.8.1 7.3.8.2 7.3.8.3 7.3.8.4 7.3.8.5 7.3.8.6 7.3.8.7 7.3.8.8 7.3.9
Studying Network Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Importing OMC Traffic Data in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Defining Multi-service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Service and User Modelling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Modelling Multi-RAT Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Modelling Multi-RAT Mobility Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Modelling Multi-RAT Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Creating a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Creating a Sector Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Creating a User Profile Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Creating User Density Traffic Maps (No. Users/km2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Converting 2G Network Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Exporting Cumulated Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Exporting a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Calculating and Displaying a GSM Traffic Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Dimensioning a GSM/GPRS/EDGE Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Calculating and Displaying Traffic Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Search and Selection of Serving Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Radio Resource Management in GSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Creating Simulations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Displaying the Traffic Distribution on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Displaying the Results of a Single Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Displaying the Average Results of a Group of Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Updating Cell Values With Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Estimating a Traffic Increase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Analysing the Results of a Simulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
7.4 7.4.1 7.4.2 7.4.3
Optimising Network Parameters Using the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Optimisation Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 The Quality Analysis Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
7.5
Verifying Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
7.6
Displaying Elements of One Atoll Document in a Multi-RAT Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
7.7
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
11
Atoll 3.1.2 User Manual Table of Contents
8
© Forsk 2012
GSM/GPRS/EDGE Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
8.1
Designing a GSM/GPRS/EDGE Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
8.2 8.2.1 8.2.1.1 8.2.1.2 8.2.1.3 8.2.1.4 8.2.1.5 8.2.2 8.2.3 8.2.4 8.2.5 8.2.6 8.2.6.1 8.2.6.2 8.2.6.3 8.2.6.4 8.2.6.5 8.2.6.6 8.2.7 8.2.7.1 8.2.7.2 8.2.7.3 8.2.7.4 8.2.7.5 8.2.8 8.2.9 8.2.9.1 8.2.9.2 8.2.10 8.2.10.1 8.2.10.2 8.2.10.3 8.2.10.4 8.2.10.5 8.2.10.6 8.2.10.7 8.2.10.8 8.2.11 8.2.11.1 8.2.11.2 8.2.11.3 8.2.11.4 8.2.11.5 8.2.11.6 8.2.11.7 8.2.11.8 8.2.11.9
Planning and Optimising GSM/GPRS/EDGE Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a GSM/GPRS/EDGE Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of a Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating or Modifying a Base Station Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Placing a New Station Using a Station Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Station Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicating an Existing Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Group of Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Sites and Transmitters Directly on the Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Tips for Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modelling Packet-switched Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating and Modifying Repeater Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Placing a Repeater on the Map Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Several Repeaters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Properties of a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Updating Repeater Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Remote Antenna. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Remote Antennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Placing a Remote Antenna on the Map Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Several Remote Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Properties of a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Updating Remote Antenna Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Working Area of an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Studying a Single Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making a Point Analysis to Study the Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Studying Signal Level Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Studying Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning a Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Computation Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Transmitters as Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signal Level Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing a Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing and Exporting Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Neighbours. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Importance Factors for Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating Neighbours Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Automatic Allocation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating and Deleting Neighbours per Transmitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating the Importance of Existing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Consistency of the Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
364 364 365 374 377 378 382 384 384 384 385 385 386 386 386 387 387 389 390 390 390 391 391 392 392 393 393 395 397 398 399 402 402 403 404 413 422 422 423 423 424 424 427 431 433 434 435
8.3 8.3.1 8.3.2 8.3.3 8.3.3.1 8.3.3.2 8.3.3.3 8.3.3.4 8.3.3.5 8.3.4 8.3.5 8.3.5.1 8.3.5.2 8.3.5.3 8.3.5.4
Studying Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing OMC Traffic Data into the Subcells Table: Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Multi-service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Sector Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a User Profile Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating User Density Traffic Maps (No. Users/km2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting 2G Network Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Cumulated Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating and Displaying a Traffic Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites for a Traffic Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Traffic Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM/GPRS/EDGE Traffic Capture Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimating a Traffic Increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
436 436 437 437 438 439 444 445 446 446 447 447 447 449 449
12
AT312_UM_E1
Atoll 3.1.2 User Manual Table of Contents
8.3.5.5 8.3.6 8.3.6.1 8.3.6.2
Modifying a GSM/GPRS/EDGE Traffic Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Dimensioning a GSM/GPRS/EDGE Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Defining a GSM/GPRS/EDGE Dimensioning Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Dimensioning a GSM/GPRS/EDGE Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
8.4 8.4.1 8.4.1.1 8.4.1.2 8.4.1.3 8.4.2 8.4.2.1 8.4.2.2 8.4.2.3 8.4.2.4 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.4 8.4.4.1 8.4.4.2 8.4.4.3 8.4.4.4 8.4.4.5 8.4.4.6 8.4.4.7 8.4.4.8
Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 Defining Resource Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 Defining Frequency Bands, Domains, and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 Defining BSIC Domains and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 Defining HSN Domains and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 Allocating Frequencies and BSICs Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 Assigning BSIC Domains to Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 Assigning BSICs to Transmitters Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 Defining Frequency Domains for Transmitters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461 Assigning Frequencies to Subcells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 AFP Prerequisites (IM, Separations, Traffic, etc.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 Interference Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 Channel Separations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 Modelling Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 AFP-Related Parameters in the Subcells Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 Modelling Layers and Subcells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Automatic Resource Allocation Using an AFP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 The Scope of the AFP and the Scope of the Interference Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 The Network Validation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 The AFP's Target Computation Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Running an Automatic Frequency Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 The AFP Progress Dialogue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 The Results of the Automatic Frequency Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Committing and Exporting the Frequency Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 Allocating Frequencies Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
8.5 8.5.1 8.5.2 8.5.2.1 8.5.2.2 8.5.2.3 8.5.2.4 8.5.2.5 8.5.3 8.5.3.1 8.5.3.2 8.5.3.3 8.5.3.4 8.5.3.5
The Atoll AFP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507 Using the Atoll AFP at a Basic Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 Using the Atoll AFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 An Overview of the AFP Cost Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510 Setting the Parameters of the Atoll AFP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 Frequency Hopping Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527 Azimuth Oriented Assignments (Pattern Allocation, 1/1 1/3 1/x …) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 BSIC Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 Advanced AFP usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 Optimising the Number of Required TRXs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 Combining Interference Matrices According to Maximum Likelihood Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 The Storage of a frequency plan in Atoll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541 Various Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543 The Role of the AFP Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
8.6 8.6.1 8.6.2 8.6.2.1 8.6.2.2 8.6.2.3 8.6.2.4 8.6.3 8.6.3.1 8.6.3.2 8.6.3.3 8.6.4 8.6.5 8.6.6 8.6.7 8.6.8 8.6.9 8.6.9.1 8.6.9.2 8.6.9.3 8.6.9.4 8.6.10
Analysing Network Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 Evaluating the Quality of a Frequency Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 Interference Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 Making Quality Predic ons Based on C⁄I or C⁄(I+N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549 Studying Interference Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552 Analysing Interference Areas Using a Point Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 Example of Analysing Interference Using a Point Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556 Packet-Specific Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 Making a Coverage Prediction by GPRS/EDGE Coding Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 Making a Coverage Prediction by Packet Throughput. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 Making a BLER Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563 Making a Circuit Quality Indicator (BER, FER, or MOS) Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Making a Service Area Analysis Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 Studying Interference Between Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Auditing a GSM/GPRS/EDGE Frequency Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 Checking Consistency in Subcells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 Displaying the Frequency Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 Using Find on Map to Display Channel Reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 Displaying the Frequency Allocation Using Transmitter Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576 Grouping Transmitters by Frequencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577 Displaying the Channel Allocation Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577 Calculating Key Performance Indicators of a GSM/GPRS/EDGE Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
13
Atoll 3.1.2 User Manual Table of Contents
© Forsk 2012
8.7 8.7.1 8.7.2 8.7.3
Optimising Network Parameters Using the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM Optimisation Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The GSM Quality Analysis Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
581 581 582 582
8.8 8.8.1 8.8.2 8.8.3 8.8.4 8.8.4.1 8.8.4.2 8.8.4.3 8.8.4.4 8.8.4.5 8.8.4.6 8.8.5 8.8.6 8.8.7 8.8.8
Verifying Network Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Display of a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Incompatible Points Along Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predicting the Signal Level on Drive Test Data Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Coverage Predictions on Drive Test Data Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Statistics Over a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting a Field From a Drive Test Data Path for a Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Data Variations Along the Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting CW Measurements from Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating Interference Matrices from a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing and Exporting the Drive Test Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
583 583 586 586 587 587 589 590 591 592 592 594 594 595 595
8.9 8.9.1 8.9.2 8.9.3 8.9.3.1 8.9.3.2 8.9.3.3 8.9.4 8.9.4.1 8.9.5 8.9.5.1 8.9.5.2 8.9.5.3 8.9.5.4 8.9.5.5 8.9.6 8.9.6.1 8.9.6.2 8.9.6.3 8.9.6.4 8.9.6.5 8.9.7 8.9.7.1 8.9.8 8.9.8.1 8.9.8.2 8.9.9 8.9.9.1 8.9.9.2 8.9.9.3 8.9.10 8.9.11 8.9.12 8.9.12.1 8.9.13 8.9.14 8.9.14.1
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting HCS Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comparing Service Areas in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRX Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Cell Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of Cell Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRX Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating or Importing TRX Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Codec Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Codec Mode Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating or Modifying Codec Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Codec Mode Adaptation Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Codec Mode Quality Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Codec Configurations in Transmitters and Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Coding Schemes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating or Modifying a Coding Scheme Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Coding Scheme Configuration in Transmitters and Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adapting Coding Scheme Thresholds for a Maximum BLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Coding Scheme Throughput Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeslot Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating or Modifying a Timeslot Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Transmitter Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Extended Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Modelling of Multi-Band Transmitters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM/GPRS/EDGE Multi-Service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modelling GSM/GPRS/EDGE Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modelling GSM/GPRS/EDGE Mobility Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modelling GSM/GPRS/EDGE Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Interferer Reception Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Modelling of Hopping Gain in Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Shadowing Margins per Clutter Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modelling the Co-existence of Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modelling Inter-technology Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Inter-technology IRFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
595 596 596 600 601 601 602 604 604 605 605 606 606 607 608 608 608 609 610 610 611 611 612 612 612 613 616 616 618 618 620 620 621 622 622 623 623
9
UMTS HSPA Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
9.1
Designing a UMTS Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
9.2 9.2.1 9.2.1.1 9.2.1.2 9.2.1.3
Planning and Optimising UMTS Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a UMTS Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of a Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating or Modifying a Base Station Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Placing a New Station Using a Station Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
628 629 629 637 638
AT312_UM_E1
9.2.1.4 9.2.1.5 9.2.2 9.2.3 9.2.4 9.2.5 9.2.6 9.2.6.1 9.2.6.2 9.2.6.3 9.2.6.4 9.2.6.5 9.2.6.6 9.2.7 9.2.7.1 9.2.7.2 9.2.7.3 9.2.7.4 9.2.7.5 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.10.11 9.2.10.12 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.11.6 9.2.11.7 9.2.11.8 9.2.11.9 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.3 9.3.1 9.3.2 9.3.2.1 9.3.2.2 9.3.2.3 9.3.2.4 9.3.2.5 9.3.3 9.3.4 9.3.4.1 9.3.4.2 9.3.4.3
Atoll 3.1.2 User Manual Table of Contents
Managing Station Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639 Duplicating an Existing Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646 Creating a Group of Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 Modifying Sites and Transmitters Directly on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 Display Tips for Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648 Creating a Dual-Band UMTS Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648 Creating a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648 Opening the Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649 Creating and Modifying Repeater Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649 Placing a Repeater on the Map Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649 Creating Several Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650 Defining the Properties of a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650 Tips for Updating Repeater Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652 Creating a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653 Opening the Remote Antennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653 Placing a Remote Antenna on the Map Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653 Creating Several Remote Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654 Defining the Properties of a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654 Tips for Updating Remote Antenna Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655 Setting the Working Area of an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656 Studying a Single Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656 Making a Point Analysis to Study the Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656 Studying Signal Level Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658 Studying Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660 Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661 Assigning a Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 The Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665 Creating a Computation Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665 Setting Transmitters or Cells as Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666 Signal Level Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667 Analysing a Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671 UMTS-Specific Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681 HSDPA Quality and Throughput Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697 HSUPA Quality and Throughput Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700 Printing and Exporting Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701 Making a Multi-point Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701 Planning Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705 Importing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706 Defining Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706 Configuring Importance Factors for Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706 Allocating Neighbours Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707 Checking Automatic Allocation Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711 Allocating and Deleting Neighbours per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714 Calculating the Importance of Existing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 Checking the Consistency of the Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Exporting Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719 Planning Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720 Defining the Scrambling Code Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720 Creating Scrambling Code Domains and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 Defining Exceptional Pairs for Scrambling Code Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 Allocating Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722 Checking the Consistency of the Scrambling Code Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724 Displaying the Allocation of Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725 Studying Network Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729 Defining Multi-service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729 Creating a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729 Creating a Sector Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730 Creating a User Profile Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731 Creating User Density Traffic Maps (No. Users/km2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736 Converting 2G Network Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738 Exporting Cumulated Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738 Exporting a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739 Calculating and Displaying Traffic Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739 The Power Control Simulation Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740 Creating Simulations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745 Displaying the Traffic Distribution on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
15
Atoll 3.1.2 User Manual Table of Contents
9.3.4.4 9.3.4.5 9.3.4.6 9.3.4.7 9.3.4.8 9.3.4.9 9.3.5 9.3.5.1 9.3.5.2
© Forsk 2012
Displaying the User Active Set on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Results of a Single Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Average Results of a Group of Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Cell Values With Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding New Simulations to an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimating a Traffic Increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing the Results of a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making an AS Analysis of Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Coverage Predictions Using Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
748 748 754 757 758 760 760 760 761
9.4 9.4.1 9.4.2 9.4.3
Optimising Network Parameters Using the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UMTS Optimisation Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UMTS Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The UMTS Quality Analysis Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
762 762 762 763
9.5 9.5.1 9.5.2 9.5.3 9.5.4 9.5.4.1 9.5.4.2 9.5.4.3 9.5.4.4 9.5.4.5 9.5.4.6 9.5.5 9.5.6 9.5.7
Verifying Network Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Display of a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Incompatible Points Along Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predicting Signal Level on Drive Test Data Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Coverage Predictions on Drive Test Data Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Statistics Over a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting a Field From a Drive Test Data Path for a Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Data Variations Along the Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting CW Measurements from Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing and Exporting the Drive Test Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
764 764 767 767 768 768 770 771 772 773 773 775 775 775
9.6 9.6.1 9.6.2 9.6.2.1 9.6.2.2 9.6.3 9.6.3.1 9.6.3.2 9.6.3.3 9.6.3.4 9.6.3.5 9.6.3.6 9.6.3.7 9.6.3.8 9.6.3.9 9.6.4 9.6.5 9.6.5.1 9.6.5.2 9.6.6
Co-planning UMTS Networks with Other Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching to Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Coverage Predictions in a Co-Planning Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Inter-technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Inter-technology Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Inter-technology Exceptional Pairs on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding and Removing Inter-technology Exceptional Pairs on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Importance Factors for Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating Inter-technology Neighbours Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Inter-technology Neighbours on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating and Deleting Inter-technology Neighbours per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating the Importance of Existing Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Consistency of the Inter-technology Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a UMTS Sector From a Sector in the Other Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using ACP in a Co-planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Co-planning Optimisation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing the Other Network into the Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ending Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
776 776 778 778 779 782 782 783 783 784 784 786 787 790 792 793 794 794 794 795
9.7 9.7.1 9.7.2 9.7.3 9.7.3.1 9.7.3.2 9.7.4 9.7.4.1 9.7.4.2 9.7.4.3 9.7.5 9.7.5.1 9.7.5.2 9.7.5.3 9.7.6 9.7.6.1 9.7.6.2
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modelling Inter-Carrier Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Options of the Network Settings Properties Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining R99 Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining HSDPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining HSUPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Site Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Resource Consumption per UMTS Site Equipment and R99 Radio Bearer . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Resource Consumption per UMTS Site Equipment and HSUPA Radio Bearer . . . . . . . . . . . . . . . . . . . . . . . . . Receiver Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating or Modifying Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSDPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
795 795 796 796 796 797 798 798 798 799 799 800 801 801 801 801 803
16
AT312_UM_E1
Atoll 3.1.2 User Manual Table of Contents
9.7.6.3 9.7.7 9.7.8 9.7.9 9.7.9.1 9.7.10 9.7.10.1
HSUPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803 Multiple Input Multiple Output Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804 Conditions for Entering the Active Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805 Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805 Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805 Modelling Inter-technology Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806 Defining Inter-technology IRFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
10
CDMA2000 Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
10.1 10.1.1 10.1.1.1 10.1.1.2 10.1.1.3 10.1.1.4 10.1.1.5 10.1.2 10.1.3 10.1.4 10.1.5 10.1.6 10.1.6.1 10.1.6.2 10.1.6.3 10.1.6.4 10.1.6.5 10.1.6.6 10.1.7 10.1.7.1 10.1.7.2 10.1.7.3 10.1.7.4 10.1.7.5 10.1.8 10.1.9 10.1.9.1 10.1.9.2 10.1.10 10.1.10.1 10.1.10.2 10.1.10.3 10.1.10.4 10.1.10.5 10.1.10.6 10.1.10.7 10.1.10.8 10.1.10.9 10.1.11 10.1.11.1 10.1.11.2 10.1.11.3 10.1.11.4 10.1.11.5 10.1.11.6 10.1.11.7 10.1.11.8 10.1.11.9 10.1.12 10.1.12.1 10.1.12.2 10.1.12.3 10.1.12.4
Planning and Optimising CDMA Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811 Creating a CDMA Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812 Definition of a Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812 Creating or Modifying a Base Station Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818 Placing a New Station Using a Station Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820 Managing Station Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821 Duplicating of an Existing Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826 Creating a Group of Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828 Modifying Sites and Transmitters Directly on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828 Display Tips for Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829 Creating a Dual-Band CDMA Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829 Creating a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829 Opening the Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830 Creating and Modifying Repeater Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830 Placing a Repeater on the Map Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830 Creating Several Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831 Defining the Properties of a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831 Tips for Updating Repeater Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833 Creating a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833 Opening the Remote Antennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834 Placing a Remote Antenna on the Map Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834 Creating Several Remote Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834 Defining the Properties of a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835 Tips for Updating Remote Antenna Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836 Setting the Working Area of an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836 Studying a Single Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837 Making a Point Analysis to Study the Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837 Studying Signal Level Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838 Studying Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841 Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842 Assigning a Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843 The Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846 Creating a Computation Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846 Setting Transmitters or Cells as Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847 Signal Level Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848 Analysing a Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852 CDMA-Specific Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862 Printing and Exporting Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882 Planning Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882 Importing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882 Defining Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883 Configuring Importance Factors for Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883 Allocating Neighbours Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884 Checking Automatic Allocation Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887 Allocating and Deleting Neighbours per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891 Calculating the Importance of Existing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893 Checking the Consistency of the Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895 Exporting Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896 Planning PN Offsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896 Defining Exceptional Pairs for PN Offset Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897 Allocating PN Offsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897 Checking the Consistency of the PN Offset Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900 Displaying the Allocation of PN Offsets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
10.2 10.2.1
Studying Network Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904 Defining Multi-service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
17
Atoll 3.1.2 User Manual Table of Contents
10.2.2 10.2.2.1 10.2.2.2 10.2.2.3 10.2.2.4 10.2.2.5 10.2.3 10.2.4 10.2.4.1 10.2.4.2 10.2.4.3 10.2.4.4 10.2.4.5 10.2.4.6 10.2.4.7 10.2.4.8 10.2.4.9 10.2.5 10.2.5.1 10.2.5.2
© Forsk 2012
Creating a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Sector Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a User Profile Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating User Density Traffic Maps (No. Users/km2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting 2G Network Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Cumulated Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating and Displaying Traffic Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Power Control Simulation Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Traffic Distribution on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the User Active Set on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Results of a Single Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Average Results of a Group of Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Cell Values With Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding New Simulations to an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimating a Traffic Increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing the Results of a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making an AS Analysis of Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Coverage Predictions Using Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
904 905 906 911 913 913 914 914 915 917 919 921 921 927 929 929 931 931 932 932
10.3 10.3.1 10.3.2 10.3.3
Optimising Network Parameters Using the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDMA Optimisation Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDMA Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The CDMA Quality Analysis Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
933 933 934 935
10.4 10.4.1 10.4.2 10.4.3 10.4.4 10.4.4.1 10.4.4.2 10.4.4.3 10.4.4.4 10.4.4.5 10.4.4.6 10.4.4.7 10.4.5 10.4.6 10.4.7
Verifying Network Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Display of a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Incompatible Points Along Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predicting Signal Level on Drive Test Data Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Coverage Predictions on Drive Test Data Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Statistics Over a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting a Field From a Drive Test Data Path for a Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting a Field From a Drive Test Data Path for a Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Data Variations Along the Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting CW Measurements from Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing and Exporting the Drive Test Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
935 935 938 938 939 939 941 942 943 943 944 944 946 946 947
10.5 10.5.1 10.5.2 10.5.2.1 10.5.2.2 10.5.3 10.5.3.1 10.5.3.2 10.5.3.3 10.5.3.4 10.5.3.5 10.5.3.6 10.5.3.7 10.5.4 10.5.5 10.5.5.1 10.5.5.2 10.5.6
Co-planning CDMA Networks with Other Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching to Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Coverage Predictions in a Co-Planning Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Inter-technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Inter-technology Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Importance Factors for Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating Inter-technology Neighbours Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Inter-technology Neighbours on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating and Deleting Inter-technology Neighbours per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating the Importance of Existing Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Consistency of the Inter-technology Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a CDMA Sector From a Sector in the Other Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using ACP in a Co-planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Co-planning Optimisation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing the Other Network into the Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ending Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
947 948 949 949 950 952 953 955 955 957 958 961 962 963 964 964 964 965
10.6 10.6.1 10.6.2 10.6.3 10.6.3.1 10.6.3.2 10.6.4
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Inter-carrier Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Options of the Network Settings Properties Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Rates Available for Services in CDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
965 966 966 967 967 968 968
18
AT312_UM_E1
10.6.5 10.6.5.1 10.6.5.2 10.6.6 10.6.6.1 10.6.6.2 10.6.7 10.6.7.1 10.6.7.2 10.6.8 10.6.9 10.6.9.1 10.6.10 10.6.11 10.6.11.1
11
Atoll 3.1.2 User Manual Table of Contents
The 1xEV-DO Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969 Defining the Forward Link 1xEV-DO Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969 Defining the Reverse Link 1xEV-DO Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969 Site Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970 Creating Site Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970 Defining Channel Element Consumption per CDMA Site Equipment and Radio Configuration. . . . . . . . . . . . . . . . . . . . 970 Receiver Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971 Setting Receiver Height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971 Creating or Modifying Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971 Conditions for Entering the Active Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972 Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973 Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973 Creating PN Offset Domains and Groups for PN Offset Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974 Modelling Inter-technology Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975 Defining Inter-technology IRFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
TD-SCDMA Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
11.1
Designing a TD-SCDMA Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
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 11.2.2 11.2.3 11.2.4 11.2.5 11.2.6 11.2.6.1 11.2.6.2 11.2.6.3 11.2.6.4 11.2.6.5 11.2.6.6 11.2.7 11.2.7.1 11.2.7.2 11.2.7.3 11.2.7.4 11.2.7.5 11.2.8 11.2.9 11.2.9.1 11.2.9.2 11.2.10 11.2.10.1 11.2.10.2 11.2.10.3 11.2.10.4 11.2.10.5 11.2.10.6 11.2.10.7 11.2.10.8 11.2.10.9 11.2.10.10 11.2.11 11.2.11.1 11.2.11.2 11.2.11.3 11.2.11.4 11.2.11.5 11.2.12 11.2.12.1
Planning and Optimising TD-SCDMA Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980 Creating a TD-SCDMA Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980 Definition of a Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981 Creating or Modifying a Base Station Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988 Placing a New Base Station Using a Station Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989 Managing Station Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990 Duplicating an Existing Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995 Creating a Group of Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997 Modifying Sites and Transmitters Directly on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997 Display Tips for Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997 Creating a Dual-Band TD-SCDMA Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998 Creating a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998 Opening the Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999 Creating and Modifying Repeater Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999 Placing a Repeater on the Map Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999 Creating Several Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000 Defining the Properties of a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000 Tips for Updating Repeater Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002 Creating a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002 Opening the Remote Antennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003 Placing a Remote Antenna on the Map Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003 Creating Several Remote Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003 Defining the Properties of a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004 Tips for Updating Remote Antenna Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005 Setting the Working Area of an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005 Studying a Single Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006 Making a Point Analysis to Study the Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006 Studying Signal Level Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007 Studying Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010 Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011 Assigning a Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012 The Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014 Creating a Computation Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014 Setting Transmitters or Cells as Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015 Signal Level Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016 Analysing a Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024 Signal Quality Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032 HSDPA Quality and Throughput Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052 Printing and Exporting Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054 Planning Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054 Setting up N-Frequency Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055 Allocating Frequencies Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055 Checking Automatic Frequency Allocation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056 Allocating Carrier Types per Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056 Checking the Consistency of the Frequency Allocation Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057 Planning Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057 Importing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
19
Atoll 3.1.2 User Manual Table of Contents
11.2.12.2 11.2.12.3 11.2.12.4 11.2.12.5 11.2.12.6 11.2.12.7 11.2.12.8 11.2.12.9 11.2.13 11.2.13.1 11.2.13.2 11.2.13.3 11.2.13.4 11.2.13.5 11.2.13.6 11.2.13.7
© Forsk 2012
Defining Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Importance Factors for Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating Neighbours Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Automatic Allocation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating and Deleting Neighbours per Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating the Importance of Existing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Consistency of the Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Scrambling Code Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Scrambling Code Domains and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Exceptional Pairs for Scrambling Code Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Scrambling Code Relativity Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating Scrambling Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Consistency of the Scrambling Code Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Allocation of Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1058 1058 1059 1061 1064 1067 1068 1069 1069 1070 1070 1071 1071 1071 1074 1075
11.3 11.3.1 11.3.1.1 11.3.1.2 11.3.1.3 11.3.2 11.3.3 11.3.3.1 11.3.3.2 11.3.3.3 11.3.3.4 11.3.3.5 11.3.4 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.5.8 11.3.5.9 11.3.6
Studying Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating TD-SCDMA Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating Available Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating Required Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Network Capacity on the Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Multi-service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Sector Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a User Profile Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating User Density Traffic Maps (No. Users/km2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting 2G Network Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Cumulated Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating and Displaying Traffic Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Monte Carlo Simulation Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Traffic Distribution on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the User Best Server on the Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Results of a Single Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Average Results of a Group of Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Cell and Timeslot Values with Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding New Simulations to an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimating a Traffic Increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Coverage Predictions Using Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1078 1078 1079 1079 1080 1080 1081 1081 1083 1087 1089 1090 1090 1091 1091 1094 1095 1097 1098 1102 1104 1105 1107 1107
11.4 11.4.1 11.4.2 11.4.3 11.4.4 11.4.4.1 11.4.4.2 11.4.4.3 11.4.4.4 11.4.4.5 11.4.5 11.4.6 11.4.7
Verifying Network Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Display of a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Incompatible Points Along Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predicting the Signal Level on Drive Test Data Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Statistics Over a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting a Field From a Drive Test Data Path for a Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Data Variations Along the Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting CW Measurements from Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing and Exporting the Drive Test Data Analysis Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1108 1108 1110 1111 1111 1112 1112 1113 1114 1114 1116 1116 1117
11.5 11.5.1 11.5.2 11.5.2.1 11.5.2.2 11.5.3 11.5.3.1 11.5.3.2 11.5.3.3 11.5.3.4 11.5.3.5 11.5.3.6
Co-planning TD-SCDMA Networks with Other Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching to Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Coverage Predictions in a Co-Planning Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Inter-technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Inter-technology Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Importance Factors for Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating Inter-technology Neighbours Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Inter-technology Neighbours on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating and Deleting Inter-technology Neighbours per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating the Importance of Existing Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1117 1117 1119 1119 1120 1122 1122 1124 1125 1127 1127 1130
20
AT312_UM_E1
Atoll 3.1.2 User Manual Table of Contents
11.5.3.7 11.5.4 11.5.5
Checking the Consistency of the Inter-technology Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1132 Creating a TD-SCDMA Sector From a Sector in the Other Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133 Ending Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133
11.6 11.6.1 11.6.2 11.6.3 11.6.3.1 11.6.3.2 11.6.3.3 11.6.4 11.6.4.1 11.6.4.2 11.6.4.3 11.6.4.4 11.6.4.5 11.6.4.6 11.6.4.7 11.6.5 11.6.5.1 11.6.5.2 11.6.5.3 11.6.6 11.6.7 11.6.7.1 11.6.7.2 11.6.7.3 11.6.8 11.6.8.1
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134 Modelling Inter-carrier Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134 Defining Frequency Bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134 Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135 The Options on the Global Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135 The Options on the Calculation Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136 Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137 Smart Antenna Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137 Grid of Beams (GOB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138 Adaptive Beam Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139 Conventional Beamformer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140 Optimum Beamformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140 Statistical Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140 Third-Party Smart Antenna Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141 Smart Antenna Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141 Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142 Defining R99 Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142 Defining HSDPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143 Defining HSUPA Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143 Creating Site Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143 Receiver Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144 Creating or Modifying Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144 HSDPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145 HSUPA UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145 Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145 Displaying the Shadowing Margins per Clutter Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146
12
WiMAX BWA Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1149
12.1
Designing a WiMAX Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149
12.2 12.2.1 12.2.1.1 12.2.1.2 12.2.1.3 12.2.1.4 12.2.1.5 12.2.2 12.2.3 12.2.4 12.2.5 12.2.6 12.2.6.1 12.2.6.2 12.2.6.3 12.2.6.4 12.2.6.5 12.2.6.6 12.2.7 12.2.7.1 12.2.7.2 12.2.7.3 12.2.7.4 12.2.7.5 12.2.8 12.2.9 12.2.9.1 12.2.9.2 12.2.10 12.2.10.1 12.2.10.2 12.2.10.3
Planning and Optimising WiMAX Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1150 Creating a WiMAX Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151 Definition of a Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151 Creating or Modifying a Base Station Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157 Placing a New Base Station Using a Station Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159 Managing Station Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160 Duplicating an Existing Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164 Creating a Group of Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165 Modifying Sites and Transmitters Directly on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166 Display Tips for Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166 Creating a Multi-band WiMAX Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167 Creating a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167 Opening the Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167 Creating and Modifying Repeater Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168 Placing a Repeater on the Map Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168 Creating Several Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168 Defining the Properties of a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169 Tips for Updating Repeater Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171 Creating a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171 Opening the Remote Antennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172 Placing a Remote Antenna on the Map Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172 Creating Several Remote Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172 Defining the Properties of a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173 Tips for Updating Remote Antenna Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174 Setting the Working Area of an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174 Studying a Single Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175 Making a Point Analysis to Study the Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175 Studying Signal Level Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176 Studying Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1178 Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179 Assigning a Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181 The Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183
21
Atoll 3.1.2 User Manual Table of Contents
12.2.10.4 12.2.10.5 12.2.10.6 12.2.10.7 12.2.10.8 12.2.10.9 12.2.11 12.2.11.1 12.2.11.2 12.2.11.3 12.2.11.4 12.2.11.5 12.2.11.6 12.2.11.7 12.2.11.8 12.2.11.9
© Forsk 2012
Creating a Computation Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Transmitters or Cells as Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signal Level Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing a Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WiMAX Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing and Exporting Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Neighbours. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Importance Factors for Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating Neighbours Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Automatic Allocation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating and Deleting Neighbours per Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating the Importance of Existing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Consistency of the Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1183 1184 1185 1190 1199 1217 1217 1218 1218 1219 1219 1222 1225 1227 1228 1229
12.3 12.3.1 12.3.1.1 12.3.1.2 12.3.1.3 12.3.1.4 12.3.2 12.3.3 12.3.4 12.3.5 12.3.5.1 12.3.5.2 12.3.5.3 12.3.5.4 12.3.5.5 12.3.5.6
Configuring Network Parameters Using the AFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AFP Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interference Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbour Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Available for Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Constraint Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Preamble Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Permutation Zone PermBases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying and Analysing the AFP Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Find on Map to Display AFP Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying AFP Results Using Transmitter Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grouping Transmitters by Channels, Preamble Indexes, Zone PermBases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing the Frequency Allocation Using Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Consistency of the Preamble Index Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Preamble Index Allocation Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1230 1230 1230 1232 1232 1233 1233 1234 1236 1237 1237 1238 1239 1239 1240 1240
12.4 12.4.1 12.4.2 12.4.2.1 12.4.2.2 12.4.2.3 12.4.2.4 12.4.2.5 12.4.3 12.4.4 12.4.4.1 12.4.4.2 12.4.5 12.4.5.1 12.4.5.2 12.4.5.3 12.4.5.4 12.4.5.5 12.4.5.6 12.4.5.7 12.4.6
Studying Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Multi-service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Sector Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a User Profile Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating User Density Traffic Maps (No. Users/km2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting 2G Network Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Cumulated Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with a Subscriber Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Subscriber List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Calculations on Subscriber Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating and Displaying Traffic Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WiMAX Traffic Simulation Algorithm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Traffic Distribution on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Results of a Single Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Average Results of a Group of Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Cell Load Values With Simulation Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimating a Traffic Increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Coverage Predictions Using Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1240 1241 1241 1242 1243 1248 1250 1250 1251 1251 1251 1255 1255 1256 1257 1259 1262 1266 1268 1269 1269
12.5 12.5.1 12.5.2 12.5.3
Optimising Network Parameters Using the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WiMAX Optimisation Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WiMAX Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The WiMAX Quality Analysis Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1270 1270 1270 1272
12.6 12.6.1 12.6.2 12.6.3 12.6.4 12.6.4.1 12.6.4.2
Verifying Network Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Display of a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Measurement Points Along Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predicting Signal Level on Drive Test Data Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1272 1272 1275 1275 1276 1276 1277
22
AT312_UM_E1
Atoll 3.1.2 User Manual Table of Contents
12.6.4.3 12.6.4.4 12.6.4.5 12.6.4.6 12.6.5 12.6.6 12.6.7
Creating Coverage Predictions on Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279 Displaying Statistics Over a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279 Extracting a Field From a Drive Test Data Path for a Transmitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280 Analysing Measurement Variations Along the Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280 Exporting a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1282 Extracting CW Measurements from Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1282 Printing and Exporting the Drive Test Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1282
12.7 12.7.1 12.7.2 12.7.2.1 12.7.2.2 12.7.3 12.7.3.1 12.7.3.2 12.7.3.3 12.7.3.4 12.7.3.5 12.7.3.6 12.7.3.7 12.7.4 12.7.5 12.7.5.1 12.7.5.2 12.7.6
Co-planning WiMAX Networks with Other Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283 Switching to Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283 Working with Coverage Predictions in a Co-planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1285 Updating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1285 Analysing Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286 Performing Inter-technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288 Setting Inter-technology Exceptional Pairs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288 Configuring Importance Factors for Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1290 Allocating Inter-technology Neighbours Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1291 Displaying Inter-technology Neighbours on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292 Allocating and Deleting Inter-technology Neighbours per Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1293 Calculating the Importance of Existing Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1296 Checking the Consistency of the Inter-technology Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1297 Creating a WiMAX Sector From a Sector in the Other Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298 Using ACP in a Co-planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299 Creating a New Co-planning Optimisation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299 Importing the Other Network into the Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299 Ending Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300
12.8 12.8.1 12.8.2 12.8.2.1 12.8.2.2 12.8.2.3 12.8.3 12.8.4 12.8.5 12.8.6 12.8.7 12.8.8 12.8.8.1 12.8.8.2 12.8.8.3 12.8.9 12.8.10 12.8.10.1 12.8.11 12.8.11.1
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300 Defining Frequency Bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300 The Global Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301 The Options on the Global Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301 The Options on the Calculation Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1303 Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1303 Defining Frame Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304 Defining WiMAX Radio Bearers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306 Defining WiMAX Quality Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306 Defining WiMAX Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306 Defining WiMAX Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1309 Smart Antenna Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312 Optimum Beamformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312 Conventional Beamformer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313 Defining Smart Antenna Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313 Multiple Input Multiple Output Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315 Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1316 Displaying the Shadowing Margins per Clutter Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317 Modelling Inter-technology Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317 Defining Inter-technology IRFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318
12.9
Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319
12.10
Glossary of WiMAX Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327
13
Wi-Fi Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333
13.1
Designing a Wi-Fi Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333
13.2 13.2.1 13.2.1.1 13.2.1.2 13.2.1.3 13.2.1.4 13.2.1.5 13.2.2 13.2.3 13.2.4 13.2.5 13.2.6
Planning and Optimising Wi-Fi Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334 Creating a Wi-Fi Access Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334 Definition of an Access Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334 Creating or Modifying an Access Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337 Placing a New Access Point Using a Station Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339 Managing Station Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340 Duplicating an Existing Access Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344 Creating a Group of Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345 Modifying Sites and Transmitters Directly on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345 Display Tips for Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346 Creating a Multi-band Wi-Fi Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346 Setting the Working Area of an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346
23
Atoll 3.1.2 User Manual Table of Contents
© Forsk 2012
13.2.7 13.2.7.1 13.2.7.2 13.2.8 13.2.8.1 13.2.8.2 13.2.8.3 13.2.8.4 13.2.8.5 13.2.8.6 13.2.8.7 13.2.8.8 13.2.8.9
Studying a Single Access Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making a Point Analysis to Study the Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Studying Signal Level Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Studying Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning a Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Computation Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Transmitters or Cells as Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signal Level Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing a Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wi-Fi Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing and Exporting Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1347 1347 1348 1350 1351 1353 1355 1355 1356 1357 1361 1370 1382
13.3 13.3.1 13.3.2 13.3.2.1 13.3.2.2 13.3.2.3 13.3.2.4 13.3.3 13.3.4 13.3.4.1 13.3.4.2 13.3.5 13.3.5.1 13.3.5.2 13.3.5.3 13.3.5.4 13.3.5.5 13.3.5.6 13.3.5.7 13.3.6
Studying Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Multi-service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Sector Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a User Profile Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating User Density Traffic Maps (No. Users/km2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Cumulated Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with a Subscriber Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Subscriber List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Calculations on Subscriber Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating and Displaying Traffic Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wi-Fi Traffic Simulation Algorithm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Traffic Distribution on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Results of a Single Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Average Results of a Group of Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Cell Load Values With Simulation Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimating a Traffic Increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Coverage Predictions Using Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1383 1383 1383 1384 1385 1390 1392 1393 1393 1393 1397 1397 1397 1399 1400 1403 1406 1408 1409 1409
13.4 13.4.1 13.4.2 13.4.3 13.4.4 13.4.4.1 13.4.4.2 13.4.4.3 13.4.4.4 13.4.4.5 13.4.4.6 13.4.5 13.4.6 13.4.7
Verifying Network Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Display of a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Measurement Points Along Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predicting Signal Level on Drive Test Data Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Coverage Predictions on Drive Test Data Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Statistics Over a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting a Field From a Drive Test Data Path for a Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Measurement Variations Along the Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting CW Measurements from Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing and Exporting the Drive Test Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1410 1410 1412 1412 1413 1413 1414 1415 1415 1416 1416 1417 1417 1418
13.5 13.5.1 13.5.2 13.5.3
Co-planning Wi-Fi Networks with Other Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching to Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a Traffic Offload Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ending Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1418 1418 1420 1421
13.6 13.6.1 13.6.2 13.6.2.1 13.6.2.2 13.6.3 13.6.4 13.6.5 13.6.6 13.6.7 13.6.8 13.6.8.1
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Options on the Calculation Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wi-Fi Frame Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Wi-Fi Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Wi-Fi Quality Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Wi-Fi Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Input Multiple Output Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Shadowing Margins per Clutter Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1421 1421 1422 1422 1422 1422 1423 1423 1424 1426 1427 1428
24
AT312_UM_E1
Atoll 3.1.2 User Manual Table of Contents
13.6.9 13.6.9.1
Modelling Inter-technology Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428 Defining Inter-technology IRFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
13.7
14
Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1430
LTE Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1435
14.1
Designing an LTE Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1435
14.2 14.2.1 14.2.1.1 14.2.1.2 14.2.1.3 14.2.1.4 14.2.1.5 14.2.2 14.2.3 14.2.4 14.2.5 14.2.6 14.2.6.1 14.2.6.2 14.2.6.3 14.2.6.4 14.2.6.5 14.2.6.6 14.2.7 14.2.7.1 14.2.7.2 14.2.7.3 14.2.7.4 14.2.7.5 14.2.8 14.2.9 14.2.9.1 14.2.9.2 14.2.10 14.2.10.1 14.2.10.2 14.2.10.3 14.2.10.4 14.2.10.5 14.2.10.6 14.2.10.7 14.2.10.8 14.2.10.9 14.2.11 14.2.11.1 14.2.11.2 14.2.11.3 14.2.11.4 14.2.11.5 14.2.11.6 14.2.11.7 14.2.11.8 14.2.11.9
Planning and Optimising LTE Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1436 Creating an LTE Base Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437 Definition of a Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437 Creating or Modifying a Base Station Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444 Placing a New Base Station Using a Station Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1446 Managing Station Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1447 Duplicating an Existing Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451 Creating a Group of Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453 Modifying Sites and Transmitters Directly on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453 Display Tips for Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453 Creating a Multi-band LTE Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1454 Creating a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1454 Opening the Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455 Creating and Modifying Repeater Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455 Placing a Repeater on the Map Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455 Creating Several Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456 Defining the Properties of a Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456 Tips for Updating Repeater Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1458 Creating a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1458 Opening the Remote Antennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1459 Placing a Remote Antenna on the Map Using the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1459 Creating Several Remote Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1459 Defining the Properties of a Remote Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1460 Tips for Updating Remote Antenna Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461 Setting the Working Area of an Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461 Studying a Single Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1462 Making a Point Analysis to Study the Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1462 Studying Signal Level Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1463 Studying Base Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465 Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1466 Assigning a Propagation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468 The Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1470 Creating a Computation Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1470 Setting Transmitters or Cells as Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1471 Signal Level Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1472 Analysing a Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477 LTE Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486 Printing and Exporting Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504 Planning Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505 Importing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505 Defining Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505 Configuring Importance Factors for Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506 Allocating Neighbours Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506 Checking Automatic Allocation Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1509 Allocating and Deleting Neighbours per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1512 Calculating the Importance of Existing Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1514 Checking the Consistency of the Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1515 Exporting Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516
14.3 14.3.1 14.3.1.1 14.3.1.2 14.3.1.3 14.3.1.4 14.3.2 14.3.3 14.3.4 14.3.4.1
Configuring Network Parameters Using the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517 AFP Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517 Interference Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517 Neighbour Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1519 Resources Available for Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1519 Constraint Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1519 Planning Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1520 Planning Physical Cell IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521 Displaying and Analysing the AFP Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1523 Using the Find on Map Tool to Display AFP Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1523
25
Atoll 3.1.2 User Manual Table of Contents
© Forsk 2012
14.3.4.2 14.3.4.3 14.3.4.4 14.3.4.5 14.3.4.6
Displaying AFP Results Using Transmitter Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grouping Transmitters by Channels or Physical Cell IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing the Frequency Allocation Using Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Consistency of the Physical Cell ID Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Physical Cell ID Allocation Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1524 1524 1525 1525 1525
14.4 14.4.1 14.4.2 14.4.2.1 14.4.2.2 14.4.2.3 14.4.2.4 14.4.2.5 14.4.3 14.4.4 14.4.4.1 14.4.4.2 14.4.5 14.4.5.1 14.4.5.2 14.4.5.3 14.4.5.4 14.4.5.5 14.4.5.6 14.4.5.7 14.4.6
Studying Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Multi-service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Sector Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a User Profile Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating User Density Traffic Maps (No. Users/km2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting 2G Network Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Cumulated Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Traffic Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with a Subscriber Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Subscriber List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Calculations on Subscriber lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating and Displaying Traffic Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LTE Traffic Simulation Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Traffic Distribution on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Results of a Single Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the Average Results of a Group of Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Cell Load Values With Simulation Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimating a Traffic Increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Coverage Predictions Using Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1526 1526 1527 1527 1528 1533 1535 1535 1536 1536 1537 1540 1541 1541 1543 1544 1547 1552 1554 1555 1555
14.5 14.5.1 14.5.2 14.5.3
Optimising Network Parameters Using the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LTE Optimisation Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LTE Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The LTE Quality Analysis Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1555 1556 1556 1557
14.6 14.6.1 14.6.2 14.6.3 14.6.4 14.6.4.1 14.6.4.2 14.6.4.3 14.6.4.4 14.6.4.5 14.6.4.6 14.6.5 14.6.6 14.6.7
Verifying Network Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Display of a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Measurement Points Along Drive Test Data Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predicting the Signal Level on Drive Test Data Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Coverage Predictions on Drive Test Data Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Statistics Over a Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting a Field From a Drive Test Data Path for a Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Measurement Variations Along the Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting a Drive Test Data Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extracting CW Measurements from Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing and Exporting the Drive Test Data Analysis Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1558 1558 1561 1561 1562 1562 1563 1564 1564 1565 1565 1567 1567 1567
14.7 14.7.1 14.7.2 14.7.2.1 14.7.2.2 14.7.3 14.7.3.1 14.7.3.2 14.7.3.3 14.7.3.4 14.7.3.5 14.7.3.6 14.7.3.7 14.7.4 14.7.5 14.7.5.1 14.7.5.2 14.7.6
Co-planning LTE Networks with Other Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching to Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Coverage Predictions in an Co-Planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysing Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Inter-technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Inter-technology Exceptional Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Importance Factors for Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating Inter-technology Neighbours Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Inter-technology Neighbours on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating and Deleting Inter-technology Neighbours per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating the Importance of Existing Inter-technology Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Consistency of the Inter-technology Neighbour Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an LTE Sector From a Sector in the Other Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using ACP in a Co-planning Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Co-planning Optimisation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing the Other Network into the Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ending Co-planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1568 1568 1570 1570 1571 1573 1573 1575 1575 1578 1579 1582 1584 1585 1585 1586 1586 1586
26
AT312_UM_E1
Atoll 3.1.2 User Manual Table of Contents
14.8 14.8.1 14.8.2 14.8.2.1 14.8.2.2 14.8.2.3 14.8.3 14.8.4 14.8.5 14.8.6 14.8.7 14.8.8 14.8.8.1 14.8.9 14.8.10 14.8.11 14.8.11.1 14.8.12 14.8.12.1
Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1587 Defining Frequency Bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1587 The Global Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1588 The Options on the Global Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1588 The Options on the Calculation Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1590 Modifying Global Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1590 Defining LTE Radio Bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591 Defining LTE Quality Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1592 Defining LTE Reception Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1592 Defining LTE Schedulers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595 Defining LTE UE Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1596 Smart Antenna Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1597 Defining Smart Antenna Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1597 Multiple Input Multiple Output Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1599 Defining ICIC Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1600 Modelling Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1600 Displaying the Shadowing Margins per Clutter Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601 Modelling Inter-technology Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601 Defining Inter-technology IRFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602
14.9
Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1603
14.10
Glossary of LTE Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1608
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1611
27
Atoll 3.1.2 User Manual Table of Contents
28
© Forsk 2012
Chapter 1 The Working Environment This chapter presents the Atoll working environment and explains the tools and shortcuts available.
In this chapter, the following are explained: •
"The Atoll Work Area" on page 31
•
"The Explorer Window" on page 35
•
"Working with Objects" on page 39
•
"Working with Maps" on page 49
•
"Working with Coverage Predictions" on page 66
•
"Working with Data Tables" on page 69
•
"Printing in Atoll" on page 84
•
"Grouping, Sorting, and Filtering Data" on page 89
•
"Tips and Tricks" on page 108
Atoll 3.1.2 User Manual Chapter 1: Starting a Project
30
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
1 The Working Environment The Atoll working environment is both powerful and flexible. It provides a comprehensive and integrated set of tools and features that allow you to create and define your radio-planning project in a single application. Atoll includes advanced multitechnology network planning features (e.g., CDMA/LTE), and a combined single-RAN, multi-RAT GSM/UMTS/LTE Monte Carlo simulator and traffic model. You can save the entire project as a single file, or you can link your project to external files. The Atoll working environment uses familiar Windows interface elements, with the ability to have several document windows open at the same time, support for drag-and-drop, context menus, and support for standard Windows shortcuts, for example, for cutting and pasting. Atoll not only enables you to create and work on your planning project, but also offers you a wide range of options for creating and exporting results based on your project. The working environment provides a wide selection of tools to facilitate radio-planning, such as a search tool to locate either a site, a point on the map, or a vector. The Network explorer, the Geo explorer, and the Parameters explorer play a central role in Atoll. The explorers contain most of the objects in a document arranged in folders. Using the explorer windows, you can manage all objects in the Atoll document: sites, transmitters, calculations, etc., as well as geographic data such as the Digital Terrain Model (DTM), traffic maps, and clutter classes. You can, for example, define various coverage predictions or configure the parameters or display of data objects. The content of the folders in the explorer windows can be displayed in tables, allowing you to manage large amounts of data. You can sort and filter the data in a table, or change how the data is displayed. You can also enter large amounts of information into a table by importing data or by cutting and pasting the information from any Windows spreadsheet into the table. The map is the working area for your document and Atoll provides many tools for working with the map. You can change the view by moving or zooming in or out and you can choose which objects are displayed and how they are displayed. You can also export the current display definition, or configuration, to use it in other documents. This chapter provides an overview of the Atoll working environment. This chapter explains the following topics: • • • • • • • • •
"The Atoll Work Area" on page 31 "The Explorer Window" on page 35 "Working with Objects" on page 39 "Working with Maps" on page 49 "Working with Coverage Predictions" on page 66 "Working with Data Tables" on page 69 "Printing in Atoll" on page 84 "Grouping, Sorting, and Filtering Data" on page 89 "Tips and Tricks" on page 108.
1.1 The Atoll Work Area The Atoll work area, shown in Figure 1.1 on page 32, consists of the main window where the map window and data tables and reports are displayed and the explorer windows. The explorer windows contain the data, objects, and parameters of a document, arranged in folders. It is presented in detail in "The Explorer Window" on page 35.
31
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Toolbar
Document window (map) Workspace Geo explorer (docked)
Panoramic window (floating)
Find on Map window (docked) Figure 1.1: Atoll user interface Atoll offers a variety of tools to help you plan a network and enables you to keep all the tools you need open at the same time to simplify your work. Additionally, you can have several Atoll documents open at the same time or several different views of the same document open at the same time. Atoll enables you to manage the placement and appearance of these tools and windows in order to make using Atoll as efficient as possible. In this section, the following are explained: • •
"Selecting a Window" on page 32 "Organising the Atoll Workspace" on page 34.
1.1.1 Selecting a Window When working on a project, you usually have more than one window open. You might have several Atoll documents open, or you might have several windows open in one document, including data tables and more than one map window. Window tabs of different documents are displayed using a different colour. The tab title of the currently selected window is displayed in bold characters. In order to avoid very long window tabs, window tab titles longer than approximately 40 characters are truncated. However, the complete title is visible in tip text displayed when the mouse is placed over the window tab. The tip text also displays the path to the ATL file to which the window belongs. In Atoll you can move from one document window to another in several different ways: • • •
"Selecting a Window Tab" on page 32 "Selecting a Window from the Windows Menu" on page 33 "Using the Windows Dialogue" on page 33.
1.1.1.1 Selecting a Window Tab In Atoll, all open windows or data tables are identified by a tab at the top of the map window or tab group (see Figure 1.2). To select a window tab: •
32
Click the tab of the window you want to select.
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Figure 1.2: Window tabs If there are more windows open than can be displayed at the top of the map window, you can select the window you want, you can select the window you want from the Windows menu (for more information, see "Selecting a Window from the Windows Menu" on page 33) or using the Windows dialogue (for more information, see "Using the Windows Dialogue" on page 33). You can also rearrange the windows by clicking and dragging a tab horizontally to a new position.
1.1.1.2 Selecting a Window from the Windows Menu When you have several document windows, data tables, or map windows open, you can select a window using the Windows menu. To select a window using the Windows menu: 1. Click Windows. The Windows menu appears. 2. Select the window you want to work with from the list in the Windows menu.
You can also select a window by clicking the Active Files button ( ) to the right of the tabs in the map window and selecting the window from the list that appears.
1.1.1.3 Using the Windows Dialogue Atoll offers a Windows dialogue to simplify working with multiple windows. You can use the Windows dialogue to select a document window or data table that is already open, to close a document window, or to save the Atoll document associated with that window. To use the Windows dialogue: 1. Select Windows > Windows. The Windows dialogue appears. Selecting a window: a. Select the window from the Select list. b. Click Activate. The Windows dialogue closes and the selected window is made the active one. Saving one or more documents: a. Select the window or windows associated with the documents you want to save from the Select list. You can select contiguous windows by clicking the first window and dragging to the last window of the selection, or by clicking the first cell, pressing SHIFT and clicking the last window. You can select non-contiguous windows by pressing CTRL and clicking each window in the list separately. b. Click Save. Atoll saves the documents associated with the selected document windows. Closing one or more windows: a. Select the window or windows you want to close from the Select list. You can select contiguous windows by clicking the first window and dragging to the last window of the selection, or by clicking the first cell, pressing SHIFT and clicking the last window. You can select non-contiguous windows by pressing CTRL and clicking each window in the list separately. b. Click Close Window(s). Atoll closes the selected document windows. If one of the windows is the last document window open of a document and there are unsaved changes, Atoll asks you whether you want to save the changes before closing. 2. Click OK to close the Windows dialogue.
33
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.1.2 Organising the Atoll Workspace Atoll enables you to organise the workspace to best suit your needs. You can create several map windows of the same project, thereby simultaneously viewing several areas of the same project. You can also rearrange the windows of the workspace to suit your needs. You can move them to different areas of the workspace or group them. In this section, the following are explained: • • • •
"Creating a New Map Window" on page 34 "Arranging Tool and Explorer Windows Using the Mouse" on page 34 "Using Tab Groups" on page 35 "Resetting the Workspace Layout to the Default View" on page 35.
1.1.2.1 Creating a New Map Window When working on an Atoll project, especially when you are working on a larger, complex radio-planning project, you might want to be able to view a different part of the project without losing the focus on the original area. Atoll enables you to open several map windows of the same project. This permits you to verify data or to visually compare two separate areas of the project. To open a new map window: •
Select Window > New Map Window. Atoll creates a new map window of the current Atoll project. You can work with the new map window as you would with any Atoll map window.
1.1.2.2 Arranging Tool and Explorer Windows Using the Mouse While working on a radio-planning project, you will normally have several tool or explorer windows open at the same time. Atoll enables you to use the mouse to position tool and explorer windows to optimise your workspace. You can click the title of the tool or explorer that you want to reposition and drag it to a new position or float it over the workspace. To arrange tool and explorer windows using the mouse: 1. Click the title of the tool or explorer.
2. Drag the window icon towards the new position. A positioning icon appears over the Atoll workspace.
3. Place the window icon over the part of the positioning icon corresponding to the new position of window. An outline appears over the Atoll workspace to indicate the new position of the window.
If you release the window icon without placing it over positioning icon, you can float the tool or explorer window over the workspace.
34
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
4. Release the mouse. The window takes its new position.
1.1.2.3 Using Tab Groups When working with large numbers of documents or document windows, you can facilitate your work by arranging the windows in groups of tabbed windows. Only map windows data tables can be grouped in tab groups; tab groups do not apply to tools and explorer windows. To move a document window to a tab group: 1. Click the title of the document window.
2. Drag the window icon towards the centre of the map window.
3. Release the mouse. A context menu appears.
4. Select one of the following from the context menu: •
New Horizontal Tab Group: Atoll creates a new horizontal tab group and adds the selected document window to it.
•
New Vertical Tab Group: Atoll creates a new vertical tab group and adds the selected document window to it.
You can also add a document window to a new tab group by clicking its title and then selecting New Horizontal Tab Group or New Vertical Tab Group from the Windows menu. If you drag the window icon to the lower edge or right edge of an existing tab group even if there is only one tab group - an outline appears to indicate the tab group the window will automatically be added to when you release the mouse.
1.1.2.4 Resetting the Workspace Layout to the Default View Atoll offers a user interface that can be easily and quickly customised to suit your needs and your current task. However, you might want to quickly return the layout of the workspace to its default settings. To return the layout of the workspace to the default settings: •
Select Window > Reset Window Layout. Atoll resets the display of all windows and toolbars to their default positions and sizes.
1.2 The Explorer Window The explorer window plays a central role in Atoll. The tabs of the explorer window contain the data and objects of a document, arranged in folders. Each object and folder in the Network, Geo, and Parameters explorers has a context-specific menu that you can access by right-clicking. You can modify items at the folder level, with changes affecting all items in the folder, or you
35
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
can access and edit items individually. As well, most folder contents can also be accessed in a table, allowing you to manage large amounts of information. For information on working with tables, see "Working with Data Tables" on page 69. In this section, the following are described: • • • • •
"Working with the Explorer Window" on page 36 "Working with the Site Configuration Window" on page 37 "Automatically Hiding Explorer Windows" on page 37 "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38 "Working with Layers Using the Explorer Windows" on page 39.
1.2.1 Working with the Explorer Window There are three principal explorers: the Network explorer, the Geo explorer, and the Parameters explorer; each explorer has objects and folders containing objects. To move from one tab to another: •
Select the explorer at the left of the Atoll working environment.
You can open a folder in an explorer to view its contents. Each folder containing at least one object has an Expand ( ) or Contract button ( ) to the left of its name. To expand a folder to display its contents: •
Click the Expand button (
) to the left of its name.
The three explorers are: •
The Network Explorer: The Network explorer enables you to manage radio data and calculations. Depending on the modules installed with Atoll, the Network explorer has the following folders: • • • • • • • • • • • •
•
The Geo explorer: The Geo explorer enables 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 maps (GSM/GPRS/EDGE/TDMA, UMTS HSPA, CDMA2000, LTE, WiMAX, and Wi-Fi)
The Parameters explorer: The Parameters explorer enables you to manage the propagation models and additional modules. It contains: •
36
Sites Transmitters Predictions UMTS Simulations, CDMA2000 Simulations , WiMAX Simulations, Wi-Fi Simulations, or LTE Simulations Traffic analysis (GSM/GPRS/EDGE projects only) Interference matrices (GSM/GPRS/EDGE, LTE, and WiMAX projects only) Subscriber lists (LTE, WiMAX, and Wi-Fi projects only) Multi-point analyses Automatic cell planning results (GSM/GPRS/EDGE, UMTS, LTE, and WiMAX only) Hexagonal design Microwave links CW Measurements and drive test data
Propagation Models: The Parameters explorer has a Propagation Models folder with the following propagation models: • Cost-Hata • Erceg-Greenstein (SUI) • ITU 1546 • ITU 370-7 (Vienna 93) • ITU 526-5 • ITU 529 • Longley-Rice • Microwave ITU-R P.452 Model • Microwave Propagation Model • Okumura-Hata • Standard Propagation Model • WLL
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
• • • • • •
Radio Network Equipment: The Radio Network Equipment folder contains antenna models, transmitter models, repeater and smart antenna equipment, and waveguides, cables, and feeders. Traffic Parameters: The Traffic Parameters folder contains services, mobility types, terminals, user profiles, and environments. Network Settings: The Network Settings folder contains station templates, frequencies and frequency bands, bearers, reception equipment, quality indicators, etc. Microwave link network settings and equipment The AFP models available in your Atoll installation. Any additional module created using the API.
1.2.2 Working with the Site Configuration Window Using the Site Configuration window, you can view the transmitters that are on any site and then view the properties of any transmitter. The transmitters of the selected site are displayed in a hierarchical series of folders (see Figure 1.3). To display the Site Configuration window: •
Select View > Site Configuration Window. The Site Configuration window appears.
Figure 1.3: The Site Configuration window The Site Configuration window appears where it was last placed. If you reset the window layout, it appears as a tab along with the Network, Geo, and Parameters explorers. To display the transmitters on a site: 1. Select the site in the map window or in the Sites folder in the Network explorer. 2. Select the Site Configuration window. The site is displayed in the Site Configuration window. The transmitters located on that site are displayed in folders identifying their radio planning technology. 3. Click the Expand button (
) to the left of a folder to expand the folder and view the contents.
You can view the properties of a transmitter displayed in the Site Configuration window by double-clicking it.
1.2.3 Automatically Hiding Explorer Windows By having the explorers visible, you have immediate access to their data and objects. Sometimes, however, that you might want more of the map window to be displayed. Atoll enables you to auto-hide the explorers, thereby enabling you to see more of the map window. When auto-hide is activated on an explorer window, all three explorer windows are reduced to vertical tabs at the edge of the work area (see Figure 1.4). The hidden explorers reappears when you move the pointer over it.
37
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Figure 1.4: Auto-hide activated for the explorer windows and for Find on Map To auto-hide the explorer windows: •
In the right-hand corner of the explorer window title bar, beside the Close icon ( ), click the Auto-hide icon ( The explorer windows are reduced to vertical tabs at the edge of the work area (see Figure 1.4).
).
You can display the explorer window by resting the pointer over the name of the explorer window. To deactivate auto-hide: •
In the right-hand corner of the explorer title bar, beside the Close icon ( explorer windows are restored to their former positions.
), click the Auto-hide icon (
). The
You can display the explorer by resting the pointer over the name of the explorer. You can also auto-hide most tool windows, for example, the Find on Map window, the Legend window, the Drive Test Data window, etc.
1.2.4 Displaying or Hiding Objects on the Map Using the Explorer Windows You can use the explorer windows to display or hide objects on the map. By hiding one type of object, another type of object is more plainly visible. For example, you could hide all predictions but one, so that the results of that prediction are more clearly displayed. Hiding an object affects only its visibility in the map window; it will still be taken into consideration during calculations.
To hide an object on the map: 1. Select the explorer (the Network explorer or the Geo explorer) that contains that object. 2. Clear the check box ( ) immediately to the left of the object name. The check box appears cleared ( is no longer visible on the map.
38
) and the object
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
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.
1.2.5 Working with Layers Using the Explorer Windows In Atoll, the map is made of objects arranged in layers. The layers on the top (as arranged on the Network and Geo tabs) are the most visible on the screen and in print. The visibility of the lower layers depends on which layers are above and visible (see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38) and on the transparency of these layers (see "Defining the Transparency of Objects and Object Types" on page 45). To move a layer up or down: 1. Select the explorer (the Network explorer or the Geo explorer) that contains that object. 2. Click and drag the object to its new position. As you drag the object, a horizontal black line indicates where the object will remain when you release the mouse button (see Figure 1.5).
Figure 1.5: Moving a layer Before you print a map, you should pay attention to the arrangement of the layers. For more information, see "Printing Recommendations" on page 85.
1.3 Working with Objects In Atoll, the items found in the explorer (the Network explorer or the Geo explorer) and displayed on the map are referred to as objects. Most objects in Atoll belong to an object type. For example, a transmitter is an object of the type transmitter. Atoll enables you to carry out many operations on objects by clicking the object directly or by right-clicking the object and selecting the operation from the context menu. In this section, the following are explained: • • •
"Using the Object Context Menu" on page 39 "Modifying Sites and Transmitters Directly on the Map" on page 41 "Display Properties of Objects" on page 43.
1.3.1 Using the Object Context Menu In Atoll, an object’s context menu gives you access to commands specific to that object as well as to commands that are common to most objects. In this section, the following context menu commands common to all objects types are explained: • • •
Rename: "Renaming an Object" on page 40. Delete: "Deleting an Object" on page 40. Properties: "Displaying the Properties of an Object" on page 40.
39
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
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 on the map or in the explorer (the Network explorer or the Geo explorer). The context menu appears. 2. Select Rename from the context menu. 3. Enter the new name and press ENTER to change the name. 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 map or from the explorer (the Network explorer or the Geo explorer). To delete an object: 1. Right-click the object either on the map or in the explorer (the Network explorer or the Geo explorer). The context menu appears. 2. Select Delete from the context menu. The selected object is deleted.
1.3.1.3 Displaying the Properties of an Object You can modify the properties of an object in the Properties dialogue. To open the Properties dialogue of a data object: 1. Right-click the object either on the map or in the explorer (the Network explorer or the Geo explorer). The context menu appears. 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 41). 2. Select Properties from the context menu. The Properties dialogue appears. Switching Between Property Dialogues You can switch between the Properties dialogues of items (transmitters, antennas, sites, services, user profiles, etc.) in the same folder or defined view in the explorer (the Network explorer or the Geo explorer) by using the browse buttons (
) in the lower-left corner of each Properties dialogue: •
: jump to the first item in the list
•
: jump to the previous item in the list
•
: jump to the next item in the list
•
: jump to the last item in the list
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, for example, to access the properties of co-site transmitters without closing and reopening the Properties dialogue. Switching is performed within the folder or, if you have created a view, within the view. For example: • • •
40
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.
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
The browse buttons are not available: • • • •
When creating a new item. When opening an item’s Properties dialogue by double-clicking its record in a table. For repeater properties. For propagation model properties.
The Display tab of the Properties dialogue is explained in "Display Properties of Objects" on page 43.
1.3.2 Modifying Sites and Transmitters Directly on the Map In a complex radio-planning project, it can be difficult to find the data object in the Network explorer, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sitesand transmitters directly from the map. You can also change the position of a site by dragging it, or by letting Atoll find a higher location for it. In this section, the following are explained: • • • • •
"Selecting One of Several Transmitters" on page 41 "Moving a Site Using the Mouse" on page 41 "Moving a Site to a Higher Location" on page 42 "Changing the Azimuth of the Antenna Using the Mouse" on page 42 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42.
1.3.2.1 Selecting One of Several Transmitters If there is more than one transmitter with the same azimuth, Atoll enables you to select a specific transmitter. To select one of several transmitter with the same azimuth: 1. In the map window, click the transmitters. A context menu appears with a list of the transmitterswith the same azimuth (see Figure 1.6).
Figure 1.6: Selecting one transmitter 2. Select the transmitter from the context menu. •
When you select a transmitter, it appears with a green point at both ends of the icon (
).
1.3.2.2 Moving a Site Using the Mouse You can move a site by editing the coordinates on the General tab of the Site Properties dialogue, or by using the mouse. To move a site using the mouse: 1. Click and drag the site to the desired position. As you drag the site, the exact coordinates of the pointer’s current location are visible in the Status bar. 2. Release the site where you would like to place it. By default, Atoll locks the position of a site. When the position of a site is locked, Atoll asks you to confirm that you want to move the site. 3. Click Yes to confirm. While this method allows you to place a site quickly, you can adjust the location more precisely by editing the coordinates on the General tab of the Site Properties dialogue.
41
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.3.2.3 Moving a Site to a Higher Location If you want to improve the location of a site, in terms of reception and transmission, Atoll can find a higher location within a specified radius from the current location of the site. To have Atoll move a site to a higher location: 1. Right-click the site in the map window. The context menu appears. 2. Select Move to a Higher Location. 3. In the Move to a Higher Location dialogue, enter the radius of the area in which Atoll should search and click OK. Atoll moves the site to the highest point within the specified radius.
1.3.2.4 Changing the Azimuth of the Antenna Using the Mouse In Atoll, you can set the azimuth of a transmitter’s antenna by modifying it on the Transmitter tab of the Transmitter Properties dialogue, or you can modify it on the map, using the mouse. The azimuth is defined in degrees, with 0° indicating north. The precision of the change to the azimuth depends on the distance of the pointer from the transmitter symbol. Moving the pointer changes the azimuth by: • •
1 degree when the pointer is within a distance of 10 times the size of the transmitter symbol. 0.1 degree when the pointer is moved outside this area.
To modify the azimuth of the antenna using the mouse: 1. On the map, click the antenna whose azimuth you want to modify. 2. Move the pointer to the end of the antenna with a green circle ( ). An arc with an arrow appears under the pointer. 3. Click the green circle and drag it to change the antenna’s 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 antenna’s 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 antenna’s azimuth. The current azimuth of the antenna is displayed in the far left of the status bar. 4. Release the mouse when you have set the azimuth of the selected antenna to the desired angle. The azimuth of the selected antenna is modified on the Transmitter tab of the Transmitter Properties dialogue. The azimuth of the other antennas on the base station is offset by the same amount as the azimuth of the selected antenna. If you make a mistake when changing the azimuth, you can undo your changes by using Undo (by selecting Edit > Undo, by pressing CTRL+Z, or by clicking undo the changes made.
in the toolbar) to
1.3.2.5 Changing the Antenna Position Relative to the Site Using the Mouse By default, antennas are placed on the site. However, antennas are occasionally not located directly on the site, but a short distance away. In Atoll, you can change the position of the antenna relative to the site either by adjusting the Dx and Dy parameters or by entering the coordinates of the antenna position on the General tab of the Transmitter Property dialogue. Dx and Dy are the distance in metres of the antenna from the site position. You can also modify the position of the antenna on the map, using the mouse. To move a transmitter using the mouse:
42
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
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 antenna’s 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. If you make a mistake when changing the position of the transmitter, you can undo your changes by using Undo (by selecting Edit > Undo, by pressing CTRL+Z, or by clicking in the toolbar) to undo the changes made.
1.3.3 Display Properties of Objects In Atoll, most objects, such as sites or transmitters, belong to an object type. How an individual object appears on the map depends on the settings on the Display tab of the object type’s Properties dialogue. The Display tab is similar for all object types whose appearance can be configured. Options that are inapplicable for a particular object type are unavailable on the Display tab of its Properties dialogue (see Figure 1.7). In this section, the display options are explained, followed by a few examples of how you can use them while working on your Atoll document (see "Examples of Using the Display Properties of Objects" on page 48). In this section, the following are explained: • •
"Defining the Display Properties of Objects" on page 43 "Examples of Using the Display Properties of Objects" on page 48.
1.3.3.1 Defining the Display Properties of Objects When you access the Properties dialogue of a group of objects, for example, when you access the Properties dialogue of the Sites folder, the Display tab will show options applicable to all objects in that group (see Figure 1.7).
Figure 1.7: 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.8).
43
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Figure 1.8: The Display tab for an individual site To define the display properties of an object type: 1. Right-click the object type folder either on the map or in the explorer (the Network explorer or the Geo explorer). 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 44 "Defining the Transparency of Objects and Object Types" on page 45 "Defining the Visibility Scale" on page 46 "Defining the Object Type Label" on page 46 "Defining the Object Type Tip Text" on page 46 "Adding an Object Type to the Legend" on page 47
4. Set the display parameters. 5. Click OK. Defining the Display Type Depending on the object selected, you can choose from the following display types: unique, discrete values, value intervals, or automatic. To change the display type: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 43. 2. Select the display type from the Display Type list: •
Unique: defines the same symbol for all objects of this type. By defining a unique symbol for an object type, objects of different types, for example, sites or transmitters, are immediately identifiable. i.
To modify the appearance of the symbol, click the symbol in the table below. The Symbol Style dialogue appears.
ii. Modify the symbol as desired. iii. Click OK to close the Symbol Style dialogue. •
Discrete values: defines the display of each object according to the value of a selected field. This display type can be used to distinguish objects of the same type by one characteristic. For example, you could use this display type to distinguish transmitter by antenna type, or to distinguish inactive from active sites. i.
Select the name of the Field by which you want to display the objects.
ii. You can click the Actions button to access the Actions menu. For information on the commands available, see "Using the Actions Button" on page 45. iii. To modify the appearance of a symbol, click the symbol in the table below. The Display Parameters dialogue appears. iv. Modify the symbol as desired. v. Click OK to close the Display Parameters dialogue. •
44
Value intervals: defines the display of each object according to set ranges of the value of a selected field. This display type can be used, for example, to distinguish population density, signal strength, and the altitude of sites.
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
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.10 on page 47. 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 45. iv. To modify the appearance of a symbol, click the symbol in the table. The Display Parameters dialogue appears. v. Modify the symbol as desired. vi. Click OK to close the Display Parameters dialogue. •
Automatic: only available for transmitters; Atoll automatically assigns a colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding it. i.
Click the symbol in the table below. The Display Parameters dialogue appears.
ii. Modify the symbol as desired. iii. Click OK to close the Display Parameters dialogue. •
•
When you create a new map object, for example, a new site or a new transmitter, you must click the Refresh button ( ) for Atoll to assign a colour to newly created object according to the set display type. You can define the default symbol used for sites and how it is displayed by editing an option in the atoll.ini file. For more information, see the Administrator Manual.
Using the Actions Button The Actions button on the Display tab of the Properties dialogue allows you to modify the display type as defined in "Defining the Display Type" on page 44. To access the Actions menu: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 43. 2. Click the Actions button. The Actions menu gives you access to the following commands: • • • • • •
Properties: Atoll displays the Display Parameters dialogue, enabling you to define the appearance of the selected symbol in the table. Select all: Atoll selects all the values in the table. Delete: Atoll removes the selected value from the table. Insert before: When the selected display type is value intervals, Atoll inserts a new threshold in the table before the threshold selected in the table. Insert after: When the selected display type is value intervals, Atoll inserts a new threshold in the table after the threshold selected in the table. Shading: Atoll opens the Shading dialogue. When "Value Intervals" is the selected display type, you select Shading to define the number of value intervals and configure their colour. Enter the upper and lower limits of the value in the First Break and Last Break boxes respectively, and enter a value in the Interval box. Define the colour shading by choosing a Start Colour and an End Colour. The value intervals will be determined by the set values and coloured by a shade going from the set start colour to the set end colour. When "Discrete Values" is the selected display type, you select Shading to choose a Start Colour and an End Colour.
•
Display Configuration: Select Load if you want to import an existing display configuration. Select Save if you want to save the display settings of the current object in a display configuration file, so that you can share them with other users or use them in other documents.
Defining the Transparency of Objects and Object Types You can change the transparency of some objects, such as predictions, and some object types, such as clutter classes, to allow objects on lower layers to be visible on the map. To change the transparency: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 43. 2. Move the Transparency slider to the right to make the object or object type more transparent or to the left to make it less transparent.
45
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Defining the Visibility Scale You can define a visibility range for object types. An object is visible only if the scale, as displayed on the Map toolbar, is within this range. This can be used to, for example, prevent the map from being cluttered with symbols when you are at a certain scale. Visibility ranges are taken into account for screen display, and for printing and previewing printing. They do not affect which objects are considered during calculations. To define an object visibility range: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 43. 2. Enter a Visibility Scale minimum in the between 1: text box. 3. Enter a Visibility Scale maximum in the and 1: text box. Defining the Object Type Label For most object types, such as sites and transmitters, you can display information about each object in the form of a label that is displayed with the object. You can display information from every field in that object type’s data table, including from fields that you add. To define a label for an object type: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 43. 2. Click the Browse button (
) beside the Label box. The Field Selection dialogue appears (see Figure 1.9).
Figure 1.9: Defining a label 3. Select the fields which you want to display in the label: a. To select a field to be displayed in the label for the object type, select the field in the Available Fields list and click to move it to the Selected Fields list. b. To remove a field from the Selected Fields list, select the field in the Selected Fields list and click it.
to remove
c. To change the order of the fields, select a field and click or to move it up or down in the list. The objects will be grouped in the order of the fields in the Selected Fields list, from top to bottom. 4. Click OK to close the Field Selection dialogue and click OK to close the Properties dialogue. For most object types, you can also display object information in the form of tip text that is only visible when you move the pointer over the object. This option has the advantage of not filling the map window with text. For more information on tip text, see "Defining the Object Type Tip Text" on page 46. Defining the Object Type Tip Text For most object types, such as sites and transmitters, you can display information about each object in the form of tip text that is only visible when you move the pointer over the object. You can display information from every field in that object type’s data table, including from fields that you add.
46
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
In the explorer (the Network explorer or the Geo explorer), the tip text displays the total numbers of elements present in the Sites and Transmitters folders, and the view. To define tip text for an object type: 1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 43. 2. Click the Browse button (
) beside the Tip Text box. The Field Selection dialogue appears (see Figure 1.9).
3. Select the fields which you want to display in the tip text: a. To select a field to be displayed in the tip text for the object type, select the field in the Available Fields list and click
to move it to the Selected Fields list.
b. To remove a field from the Selected Fields list, select the field in the Selected Fields list and click it.
to remove
For most object types, you can also display object information in the form of a label that is displayed with the object. This option has the advantage of keep object-related information permanently visible. For more information on tip text, see "Defining the Object Type Label" on page 46. Once you have defined the tip text, you must activate the tip text function before it appears. To display tip text: •
Click the Display Tips button (
) on the toolbar. Tip text will now appear when the pointer is over the object.
If you have more than one coverage prediction displayed on the map, the tip text displays the tip text for all the coverage predictions available on a pixel up to a maximum of 30 lines. You can change this default maximum using an option in the atoll.ini file. For more information, see the Administrator Manual. Adding an Object Type to the Legend You can display the information defined by the display type (see "Defining the Display Type" on page 44) in your Atoll document’s legend. Only visible objects appear in the Legend window. For information on displaying or hiding objects, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In Figure 1.10, on the Display tab of a signal level prediction, the intervals defined are: • • •
Signal level >= -65 red -65 > Signal level >= -105 shading from red to blue (9 intervals) Signal level < -105 not shown in the coverage.
The entries in the Legend column will appear in the Legend window.
Figure 1.10: 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 43. 2. Select the Add to legend check box. The defined display will appear on the legend. To display the Legend window: •
Select View > Legend Window. The Legend window appears.
You can also display the comments defined in the properties of a coverage prediction in the Legend window by setting an option in the atoll.ini file. For more information about setting options in the atoll.ini file, see the Administrator Manual.
47
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.3.3.2 Examples of Using the Display Properties of Objects In this section are the following examples of how display properties of objects can be used: • •
"Automatic Display Type - Server Coverage Predictions" on page 48 "Shading - Signal Level Coverage Prediction" on page 48.
Automatic Display Type - Server Coverage Predictions When making a best server prediction, Atoll calculates, for each pixel on the map, which server is received the best. If the selected display type for transmitters is "Automatic," Atoll colours each pixel on the map according to the colour of the transmitter that is best received on that pixel. This way, you can identify immediately which transmitter is best received on each pixel. The following two figures show the results of the same best server area and handover margin coverage prediction. In Figure 1.11, the transmitter display type is "Discrete Values," with the site name as the chosen value. The difference in colour is insufficient to make clear which transmitter is best received on each pixel. In Figure 1.12, the transmitter display type is "Automatic." Because Atoll ensures that each transmitter has a different colour than the transmitters surrounding it, the prediction results are also immediately visible.
Figure 1.11: Value interval display type
Figure 1.12: Automatic display type
To display the results of a server coverage prediction with the transmitters set to the automatic display type: 1. Right-click the Transmitters folder in the Network explorer. 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 prediction results.
Shading - Signal Level Coverage Prediction Atoll displays the results of a signal level prediction as value intervals. On the map, these value intervals appear as differences of shading. You can use the Shading command to define the appearance of these value intervals to make the results easier to read or more relevant to your needs. For example, you can change the range of data displayed, the interval between each break, or you can change the colours to make the intervals more visible. In this example, Figure 1.13 shows the results of the best signal level plot from -60 dBm to -105 dBm. However, if you are more interested in reception from -80 dBm to -105 dBm, you can change the shading to display only those values. The result is visible in Figure 1.14.
48
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Figure 1.13: Shading from -60 dBm to -105 dBm
Figure 1.14: Shading from -80 dBm to -105 dBm
To change how the results of a signal level coverage prediction are displayed: 1. Expand the Predictions folder in the Network explorer and right-click the signal level prediction. The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Select the Display tab. 4. Click Actions to display the menu and select Shading. The Shading dialogue appears. 5. Change the value of the First Break to "-80". Leave the value of the Last Break at "-105." 6. Click OK to close the Shading dialogue. 7. Click OK to close the Properties dialogue and apply your changes.
1.4 Working with Maps Atoll has the following functions to help you work with maps: • • • • • • • • • • • • • • •
"Changing the Map Scale" on page 49 "Using Full Screen Mode" on page 50 "Moving the Map in the Document Window" on page 51 "Using the Panoramic Window" on page 51 "Centring the Map Window on an Object" on page 51 "Centring the Map Window on a Table Record" on page 52 "Adjusting the Map Window to a Selection" on page 52 "Measuring Distances on the Map" on page 52 "Displaying Rulers Around the Map" on page 53 "Displaying the Map Scale" on page 53 "Displaying the Map Legend" on page 53 "Using Zones in the Map Window" on page 54 "Editing Polygons, Lines, and Points" on page 61 "Copying the Content of a Zone into Another Application" on page 65. "Map Window Pointers" on page 65.
1.4.1 Changing the Map Scale You can change the scale of the map by zooming in or out, by zooming in on a specific area of the map, or by choosing a scale. Atoll also allows you to define a zoom range outside of which certain objects are not displayed (see "Defining the Visibility Scale" on page 46).
1.4.1.1 Zooming In and Out Atoll offers several tools for zooming in and out on the map. When you zoom in or out on the map, you do so based on the position of the cursor on the map.
49
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
To zoom in on the map: 1. Click the Zoom icon (
) on the Map toolbar (or press CTRL+Q).
2. Click the map where you want to zoom in. You can also zoom in by pressing CTRL++, by selecting Zoom > Zoom In from the View menu, or by holding down the CTRL key and rotating the mouse wheel button forward.
To zoom out on the map: 1. Click the Zoom icon (
) on the Map toolbar (or press CTRL+Q).
2. Right-click the map where you want to zoom out. You can also zoom out by pressing CTRL+–, by selecting Zoom > Zoom Out from the View menu, or holding down the CTRL key and rotating the mouse wheel button backward.
1.4.1.2 Zooming In on a Specific Area To zoom in on a specific area of the map: 1. Click the Zoom Area icon (
) on the Map toolbar (or press CTRL+W).
2. Click in the map on one of the four corners of the area you want to select. 3. Drag to the opposite corner. When you release the mouse button, Atoll zooms in on the selected area.
1.4.1.3 Choosing a Scale To choose a scale: 1. Click the arrow next to the scale box (
) on the Map toolbar.
2. Select the scale from the list. If the scale value you want is not in the list: 1. Click in the scale box (
) on the Map toolbar.
2. Enter the desired scale. 3. Press ENTER. Atoll zooms the map to the entered scale.
1.4.1.4 Changing Between Previous Zoom Levels Atoll saves the last five zoom levels, allowing you to move quickly between previous zoom levels and zoomed areas. To move between zoom levels: • •
Click the Previous Zoom button (
) to return to a zoom level you have already used (or press ALT + ←).
Once you have returned to a previous zoom level, click the Next Zoom button (
) to return to the latest zoom level
(or press ALT + →).
1.4.2 Using Full Screen Mode Atoll enables you to expand the map window to fill the entire computer screen, temporarily hiding the explorer windows and the toolbars. The menus remain visible and a Close Full Screen button appears, enabling you to quickly return to the normal view. To enable full screen mode: •
Select View > Full Screen. The map window expands to fill the computer screen. You can move the Close Full Screen button by clicking and dragging the Full Screen title bar above it. If you inadvertantly move the Close Full Screen button off screen, you can still return to the normal view by selecting View > Full Screen again or by pressing ESC.
50
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
With the toolbars and scrollbars hidden, you can still navigate around the map window using the keyboard shortcuts: •
CTRL++: Zoom in on the map
•
CTRL+–: Zoom out on the map
•
CTRL+Q: Select Zoom In/Out tool (left click to zoom in and right click to zoom out)
•
CTRL+D: Move the map in the map window
•
ALT+←: Previous zoom and location on the map
•
ALT+→: Next zoom and location on the map.
1.4.3 Moving the Map in the Document Window You can move the map in the document window using the mouse. To move the map in the document window: 1. Click the Move Map Window button (
) on the Map toolbar (or press CTRL + D).
2. Move the pointer over the map and drag the map in the desired direction. You can also move the map in the document window by placing the pointer over the map, pressing the mouse wheel, and dragging the map in the desired direction.
1.4.4 Using the Panoramic Window The Panoramic window displays the entire map with all of the imported geographic data. A dark rectangle indicates what part of the geographic data is presently displayed in a document window, helping you situate the displayed area in relation to the entire map. You can use the Panoramic window to: • • •
Zoom in on a specific area of the map Resize the displayed map area Move around the map.
To zoom in on a specific area of the map: 1. Click in the Panoramic window on one of the four corners of the area you want to zoom in on. 2. Drag to the opposite corner. When you release the mouse button, Atoll zooms in on the selected area. To resize the displayed map area: 1. Click in the Panoramic window on a corner or border of the zoom area (i.e., the dark rectangle). 2. Drag the border to its new position. To move around the map: 1. Click in the zoom area (i.e., the dark rectangle) in the Panoramic window. 2. Drag the rectangle to its new position.
1.4.5 Centring the Map Window on an Object You can centre the map on any selected object, for example, a transmitter, a site, one or all predictions, or on any zone in the Zones folder in the Geo explorer. When centring the map window on an object the current scale is kept. You can select the object in the map window or in the explorer. To centre the map window on a selected object: 1. Right-click the object in the map window or in the explorer. 2. Select Centre in Map Window from the context menu. If you want to quickly find an object, such as a site, on the map, you can select it in the explorer and then select the Centre in Map Window command.
51
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.4.6 Centring the Map Window on a Table Record You can centre the map on any record in the following tables: • • •
Sites table Transmitters table Any vector table.
When centring the map window on an object the current scale is kept. To centre the map window on a table record: 1. Open the table. 2. Right-click the record. The context menu appears. 3. Select Centre in Map Window from the context menu.
1.4.7 Adjusting the Map Window to a Selection You can adjust the map window to display the contents of the Sites folder (or of a view), or a set of measurement data points, or one or all predictions, or any object or zone in the Geo explorer. When you adjust the map window to display a selection, Atoll optimises the display by changing the scale and position so that the selection (for example, the sites) is completely displayed in the map window. To adjust the map window to a folder or object in the explorer: 1. Right-click the folder or object in the explorer. The context menu appears. 2. Select Adjust Map Window from the context menu. You can also adjust the map window to a record (polygon or line) in a vector table. The map window is then adjusted so that the polygon (or line) entirely occupies the displayed map.
1.4.8 Measuring Distances on the Map You can measure distances on the map by using the Distance Measurement tool. The Distance Measurement tool also gives you the azimuth of a line segment. You can also use the Distance Measurement tool to measure distance between several points along a polyline. As you measure, Atoll displays the following information: • • • •
Path: The total distance between the first point and the last point of a line segment or a polyline. Line: The distance between the first point and the pointer’s position (for a line segment), or distance between the last point and the pointer’s position (for a polyline). Total: The total distance between the first point and the pointer’s location. Azimuth: The azimuth of the pointer’s position with respect to the first point of a line segment, or with respect to the last point of a polyline. When the Distance Measurement tool is active, the information in the status bar changes from "Ready" to the following when you click the first point: "Path= 0 m, Line= 0 m; Total = 0 m; Azimuth = 0°"
To measure a distance on the map between two points: 1. Click the Distance Measurement button (
) on the toolbar.
2. Click the starting point on the map. As you move the pointer away from the first point, Atoll marks the initial position and connects it to the pointer with a line. The status bar displays the distance covered by the pointer thus far ("Path = 0 m" and "Line = Total"), and the azimuth of the pointer’s location with respect to the first point. As you move the pointer away from the first point, the measurement "Line" increases from 0 m to the distance covered by the pointer thus far. 3. Click the map where you want to end measurement. The status bar displays the same information as in step 2. (except that "Path = Total" and "Line = 0 m"). 4. Double-click anywhere on the map to exit distance measurement and clear the line segment from the map.
52
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
To measure a distance on the map between several points: 1. Click the Distance Measurement button (
) on the toolbar.
2. Click the first point on the map. As you move the pointer away from the first point, Atoll marks the initial position and connects it to the pointer with a line. The status bar displays the distance measured thus far ("Path = 0 m" and "Line = Total"), and the azimuth of the pointer’s location with respect to the first point. As you move the pointer away from the first point, the measurement "Line" increases from 0 m to the distance covered by the pointer thus far. 3. Click the next point on the map. The status bar displays the same information as in step 2. (except that "Path = Total" and "Line = 0 m"). 4. Continue clicking points until you have clicked the last point. In the example in Figure 1.15, "Site052" is the first point, "Site055" is the last point, the pointer’s location is 422 m away from the last point and its azimuth is 166° with respect to the last point. 5. Double-click anywhere on the map to exit distance measurement and clear the polyline from the map.
Figure 1.15: Measurement data in the status bar
1.4.9 Displaying Rulers Around the Map You can display rulers around the map in the document window. To display rulers: 1. Select Document > Preferences. The Preferences dialogue appears. 2. In the Preferences dialogue, click the Coordinates tab. 3. Under Display rulers and scale, select where you want the rulers to be displayed in the map window. 4. Click OK.
1.4.10 Displaying the Map Scale You can display the map scale in the map window. To display the map scale: 1. Select Document > Preferences. The Preferences dialogue appears. 2. In the Preferences dialogue, click the Coordinates tab. 3. Under Display rulers and scale, select the Scale on map check box. 4. Click OK.
1.4.11 Displaying the Map Legend You can display a map legend. The legend will contain the information on the object types that you have added to it. For information on adding object types to the legend, see "Adding an Object Type to the Legend" on page 47. To display the legend: •
Select View > Legend Window.
53
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.4.12 Using Zones in the Map Window In the Geo explorer, Atoll provides you with a set of tools called zones. The zones are a type of polygon, which can be created and modified in the same way as contours, lines, or points. Zones can be used to define areas of the map for the following purposes: •
Filtering Zone: The filtering zone is a graphical filter that restricts the objects displayed on the map and in the Network explorer to the objects inside the filtering zone. It also restricts which objects are used in calculations such as coverage predictions, etc. For more information on the filtering zone, see "Filtering Zones" on page 54.
•
Computation Zone: In radio--planning projects, the computation zone is used to define which base stations are to be taken into consideration in calculations and the area where Atoll calculates path loss matrices, coverage predictions, etc. For more information on the computation zone, see "The Computation Zone" on page 55.
•
Focus Zone and Hot Spots: With the focus zone and hot spots, you can select the areas of coverage predictions or other calculations on which you want to generate reports and results. For more information on the focus zone and hot spots, see "The Focus Zone and Hot Spots" on page 56.
•
Printing Zone: The printing zone allows you to define the area to be printed. For more information on printing using the printing zone, see "Using a Printing Zone" on page 59.
•
Geographic Export Zone: The geographic export zone is used to define part of the map to be exported as a bitmap. For more information on the geographic export zone, see "Using a Geographic Export Zone" on page 59. Zones are taken into account whether or not they are visible. In other words, if you have drawn a zone, it will be taken into account whether or not its visibility check box in the Zones folder of the Geo explorer is selected. For example, if you have filtered the sites using a filtering zone, the sites outside the filtering zone will not be taken into consideration in coverage predictions, even if you have cleared the filtering zone’s visibility check box. You will have to delete the zone if you no longer want to select sites using a filtering zone.
In this section, the following are explained: • • • • • •
"Filtering Zones" on page 54 "The Computation Zone" on page 55 "The Focus Zone and Hot Spots" on page 56 "Using Polygon Zone Editing Tools" on page 57 "Using a Printing Zone" on page 59 "Using a Geographic Export Zone" on page 59.
1.4.12.1 Filtering Zones The filtering zone is a graphical filter that restricts the objects displayed on the map and in the Network explorer to the objects inside the filtering zone. It also restricts which objects are used in calculations such as coverage predictions, etc. By limiting the number of sites, you can reduce the time and cost of calculations and make visualisation of data objects on the map clearer. The filtering zone is taken into account whether or not it is visible. In other words, if you have drawn a zone, it will be taken into account whether or not its visibility check box in the Zones folder of the Geo explorer is selected. You will have to delete the zone if you no longer want to select sites using a filtering zone. To create a filtering zone: 1. Select the Geo explorer. 2. Click the Expand button (
) to the left of Zones folder to expand the folder.
3. Right-click the Filtering Zone folder. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the zone.
ii. Click once on the map to define each point on the map where the border of the zone changes direction.
54
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
iii. Click twice to finish drawing and close the zone. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the filtering zone.
ii. Drag to the opposite corner of the rectangle that will define the filtering zone. When you release the mouse, the filtering zone will be created from the rectangle defined by the two corners. The filtering zone is delimited by a blue line. The data objects outside of the selected zone are filtered out. In the Network explorer, any folder whose content is affected by the filtering zone appears with a special icon ( cate that the folder contents have been filtered.
), to indi-
You can also create a filtering zone as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the filtering zone. Existing polygon: You can use any existing polygon as a filtering zone by right-clicking it on the map or in the Geo explorer and Use As > Filtering Zone from the context menu. You can also combine an existing filtering zone with any existing polygon by right-clicking it on the map or in the Geo explorer and selecting Add To > Filtering Zone from the context menu. Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an administrative area, you can import it and use it as a filtering zone. You can import it by right-clicking the Filtering Zone folder in the Geo explorer and selecting Import from the context menu.
Fit Zone to Map Window: You can create a filtering zone the size of the map window by right-clicking the Filtering Zone folder in the Geo explorer and selecting Fit Zone to Map Window from the context menu.
Once you have created a filtering zone, you can use Atoll’s polygon editing tools to edit it. For more information on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 57. You can save the filtering zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the filtering zone in the user configuration: For information on saving the fiiltering zone in a user configuration, see "Saving a User Configuration" on page 101. Exporting the filtering zone: You can export the filtering zone by right-clicking the Filtering Zone in the Geo explorer and selecting Export from the context menu.
1.4.12.2 The Computation Zone The computation zone is used to define the area where Atoll carries out calculations. When you create a computation zone, Atoll carries out the calculation for all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Therefore, it takes into consideration base stations inside and base stations outside the computation zone if they have an influence on the computation zone. In addition, the computation zone defines the area within which the coverage prediction results will be displayed. When working with a large network, the computation zone allows you to restrict your coverage predictions to the part of the network you are currently working on. By allowing you to reduce the number of base stations studied, Atoll reduces both the time and computer resources necessary for calculations. As well, by taking into consideration base stations within the computation zone and base stations outside the computation zone but which have an influence on the computation zone, Atoll gives you realistic results for base stations that are close to the border of the computation zone. If there is no computation zone defined, Atoll makes its calculations on all base stations that are active and filtered and for the entire extent of the geographical data available. The computation zone is taken into account whether or not it is visible. In other words, if you have drawn a computation zone, it will be taken into account whether or not its visibility check box in the Zones folder of the Geo explorer is selected. You will have to delete the computation zone if you no longer want to define an area for calculations. To create a computation zone: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Zones folder.
3. Right-click the Computation Zone. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the zone.
55
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
ii. Click once on the map to define each point on the map where the border of the zone changes direction. iii. Click twice to finish drawing and close the zone. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the computation zone.
ii. Drag to the opposite corner of the rectangle that will define the computation zone. When you release the mouse, the computation zone will be created from the rectangle defined by the two corners. The computation zone is delimited by a red line. You can also create a computation zone as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the computation zone. Existing polygon: You can use any existing polygon as a computation zone by right-clicking it on the map or in the Geo explorer and selecting Use As > Computation Zone from the context menu. You can also combine an existing computation zone with any existing polygon by right-clicking it on the map or in the Geo explorer and selecting Add To > 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 in the Geo explorer and selecting Import from the context menu. Fit Zone to Map Window: You can create a computation zone the size of the map window by right-clicking the Computation Zone in the Geo explorer and selecting Fit Zone to Map Window from the context menu.
Once you have created a computation zone, you can use Atoll’s polygon editing tools to edit it. For more information on the polygon editing tools, see"Using Polygon Zone Editing Tools" on page 57. You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the computation zone in the user configuration: For information on saving the computation zone in a user configuration, see "Saving a User Configuration" on page 101. Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone in the Geo explorer and selecting Export from the context menu.
1.4.12.3 The Focus Zone and Hot Spots Using the focus zone and hot spots, you can define an area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spots in addition to the focus zone. It is important not to confuse the computation zone and the focus zone and hot spots. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, etc., while the focus and hot spots are the areas taken into consideration when generating reports and results. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Atoll takes the focus zone and hot spots into account whether or not they are visible. In other words, if you have drawn a focus zone or hot spot, it will be taken into account whether or not its visibility check box in the Zones folder in the Geo explorer is selected. You will have to delete the zone if you no longer want to define an area for reports. A focus zone can consist of more than one polygon. The polygons of a focus zone must not intersect or overlap each other.
To define a focus zone or a hot spot: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spots folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. From the context menu, select one of the following: •
56
Draw Polygon
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
i.
Click once on the map to start drawing the focus zone or hot spot.
ii. Click once on the map to define each point on the map where the border of the focus zone or hot spot changes direction. iii. Click twice to finish drawing and close the focus zone or hot spot. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the focus zone or hot spot.
ii. Drag to the opposite corner of the rectangle that will define the focus zone or hot spot. When you release the mouse, the focus zone or hot spot will be created from the rectangle defined by the two corners. A focus zone is delimited by a green line; a hot spot is delimited by a heavy black line. If you clear the zone’s visibility check box in the Zones folder in the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a focus zone or hot spot in one of the following ways: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the focus zone or hot spot. Existing polygon: You can use any existing polygon as a focus zone or hot spot by right-clicking it on the map or in the Geo explorer and selecting Use As > Focus Zone or Use As > Hot Spot from the context menu. You can also combine an existing focus zone or hot spot with any existing polygon by right-clicking it on the map or in the Geo explorer and selecting Add To > Focus Zone or Add To > 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 zone or hot spot. You can import it by right-clicking the Focus Zone or Hot Spots folder in the Geo explorer and selecting Import from the context menu. When you import hot spots, you can import the name (in text format) given to each zone as well. Additionally, because you can have several hot spots, you can import more than one polygon into the Hot Spot folder, with each as a separate hot spot. Fit Zone to Map Window: You can create a focus zone or hot spot the size of the map window by right-clicking the Focus Zone or Hot Spots folder in the Geo explorer and selecting Fit Zone to Map Window from the context menu. You can save the focus zone or hot spot, so that you can use it in a different Atoll document, in the following ways: • •
Saving the focus zone in the user configuration: For information on saving the focus zone in a user configuration, see "Saving a User Configuration" on page 101. Exporting the focus zone or hot spots: You can export the focus zone or hot spots by right-clicking the Focus Zone or the Hot Spots folder in the Geo explorer and selecting Export from the context menu.
1.4.12.4 Using Polygon Zone Editing Tools Atoll provides you with several different ways of editing the computation zone, focus zone, hot spots, and filtering zones. You can edit these zones by editing the points that define them, by combining several polygons, or by deleting parts of the polygons that make up these zones. When you no longer need the zone, you can delete it from the map. The computation, focusand hot spot polygons can contain holes. The holes within polygonal areas are differentiated from overlaying polygons by the order of the coordinates of their vertices. The coordinates of the vertices of polygonal areas are in clockwise order, whereas the coordinates of the vertices of holes within polygonal areas are in counter-clockwise order. In this section, the following are explained: • •
1.4.12.4.1
"Editing Polygon Zones" on page 57 "Removing a Polygon Zone" on page 59.
Editing Polygon Zones Atoll enables you to edit a polygon zone in several different ways. The first step is to select it, either by: • • •
Selecting the polygon zone in the Zones folder in the Geo explorer Selecting the polygon zone by clicking it on the map, or Selecting the polygon zone from the list in the Vector Editor toolbar.
The second step is to put the zone in editing mode: • •
Right-click the zone you want to edit in the map window and select Edit Zone from the context menu, or Right-click the zone in the Zones folder in the Geo explorer and select Edit Zone from the context menu. If the zone has been selected from the list in the Vector Editor toolbar, it is automatically put in editing mode.
57
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Once you have the polygon zone in editing mode, you can edit it as explained in the following sections: • • •
"Editing the Points of a Polygon Zone" on page 58 "Editing Polygon Zones Using the Toolbar" on page 58 "Editing Polygon Zones Using the Context Menu" on page 59.
Editing the Points of a Polygon Zone To edit a point of a polygon zone: 1. Put the polygon zone in editing mode as explained in "Editing Polygon Zones" on page 57. 2. Select the polygon zone. You can now edit it by: •
Moving a point: i.
Position the pointer over the point you want to move. The pointer changes (
).
ii. Drag the point to its new position. •
Adding a point to the polygon zone: i.
Position the pointer over the polygon zone border where you want to add a point. The pointer changes (
).
ii. Right-click and select Insert Point from the context menu. A point is added to the polygon zone border at the position of the pointer. •
Deleting a point from a polygon zone: i.
Position the pointer over the point you want to delete. The pointer changes (
).
ii. Right-click and select Delete Point from the context menu. The point is deleted. Editing Polygon Zones Using the Toolbar In Atoll, you can create complex polygon zones by using the tools on the Vector Editor toolbar. The filtering, computation, and focus zone polygons can contain holes. The holes within polygonal areas are differentiated from overlaying polygons by the order of the coordinates of their vertices. The coordinates of the vertices of polygonal areas are in clockwise order, whereas the coordinates of the vertices of holes within polygonal areas are in counter-clockwise order. To edit a polygon zone using the icons on the Vector Editor toolbar: 1. Put the polygon zone in editing mode as explained in "Editing Polygon Zones" on page 57. 2. Click the contour to edit. The Vector Editor toolbar has the following buttons: •
: To combine several polygon zones: i.
In the Vector Editor toolbar, click the Combine button (
).
ii. Click once on the map where you want to begin drawing the new polygon zone. iii. Click each time you change angles on the border defining the outside of the polygon zone. iv. Double-click to close the polygon zone. v. Draw more polygon zones if desired. Atoll creates a group of polygons of the selected and new contours. If polygon zones overlap, Atoll merges them. •
: To delete part of the selected polygon zone: i.
In the Vector Editor toolbar, click the Delete button (
).
ii. Draw the area you want to delete from the selected polygon zone by clicking once on the map where you want to begin drawing the area to delete. iii. Click each time you change angles on the border defining the outside of the area. iv. Double-click to close the area. Atoll deletes the area from the selected contour. •
: To create a polygon out of the overlapping area of two polygons: i.
In the Vector Editor toolbar, click the Intersection button (
).
ii. Click once on the map where you want to begin drawing the polygon that will overlap the selected one. iii. Click each time you change angles on the border defining the outside of the polygon. iv. Double-click to close the polygon. Atoll creates a new polygon of the overlapping area of the two polygons and deletes the parts of the polygons that do not overlap.
58
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
•
: To split the selected polygon into several polygons: i.
In the Vector Editor toolbar, click the Split button (
).
ii. Click once on the map where you want to begin drawing the polygon that will split the selected one. iii. Click each time you change angles on the border defining the outside of the polygon. iv. Double-click to close the polygon. Atoll separates the area covered by the polygon from the selected polygon and creates a new polygon. Editing Polygon Zones Using the Context Menu When you are editing polygon zones, you can access certain commands using the context menu. To edit a polygon zone using the context menu: 1. Click the polygon zone you want to edit. 2. Right-click the polygon zone to display the context menu and select one of the following: • • •
Properties: Select Properties to open the Properties dialogue of the selected polygon zone. The Properties dialogue gives the coordinates of each point that defines the position and shape of the polygon zone. Insert Point: Select Insert Point to add a point to the border of the contour at the position of the pointer. Move: i.
Select Move from the context menu to move the contour, line, or point on the map.
ii. Move the contour, line, or point. iii. Click to place the contour, line, or point.
1.4.12.4.2
•
Quit edition: Select Quit Edition to exit editing mode.
•
Delete: Select Delete to remove the selected contour, line, or point from the map.
Removing a Polygon Zone When you no longer need a polygon zone, you can remove the zone and redisplay all data objects. To remove a polygon zone: 1. Select the Geo explorer. 2. Click the Expand button (
) to the left of Zones folder to expand the folder.
3. Right-click the folder containing the zone you want to remove. 4. From the context menu, select Delete Zone. The polygon zone is removed and all document data are now displayed. You can also delete it by right-clicking its border on the map and selecting Delete from the context menu.
1.4.12.5 Using a Printing Zone The printing zone allows you to define the area to be printed. For information on using the printing zone, see "Defining the Printing Zone" on page 85.
1.4.12.6 Using a Geographic Export Zone If you want to export part of the map as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, Atoll offers you the option of exporting only the area covered by the zone if you export the map as a raster image. To define a geographic export zone and export the map: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Zones folder.
3. Right-click the Geographic Export Zone folder. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the zone.
59
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
ii. Click once on the map to define each point on the map where the border of the zone changes direction. iii. Click twice to finish drawing and close the zone. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the zone.
ii. Drag to the opposite corner of the rectangle that will define the zone. When you release the mouse, the zone will be created from the rectangle defined by the two corners. •
Fit Zone to Map Window Atoll creates a geographic export zone that fits the map window.
The geographic export zone is delimited by a light purple line . If you clear the geographic export zone’s visibility check box in the Zones folder in the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a geographic export zone as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the geogaphic export zone. Existing polygon: You can use any existing polygon as a geographic export zone by right-clicking it on the map or in the Geo explorer and selecting Use As > Geographic Export Zone from the context menu. You can also combine an existing geographic export zone with any existing polygon by right-clicking it on the map or in the Geo explorer and selecting Add To > Geographic Export Zone from the context menu. The "effective" geographic export zone will be the rectangle encompassing the several polygons composing the geographic export zone. Importing a polygon: If you have a file with an existing polygon, you can import it and use it as a geographic export zone. You can import it by right-clicking the Geographic Export Zone folder in the Geo explorer and selecting Import from the context menu. Fit Zone to Map Window: You can create a geographic export zone the size of the map window by right-clicking it on the map or in the Geo explorer and selecting Fit Zone to Map Window from the context menu.
Once you have created a geographic export zone, you can use Atoll’s polygon editing tools to edit it. For more information on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 57. You can save the geographic export zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the geographic export zone in the user configuration: For information on saving the geographic export zone in a user configuration, see "Saving a User Configuration" on page 101. Exporting the geographic export zone: You can export the geographic export zone by right-clicking the Geographic Export Zone in the Geo explorer and selecting Export from the context menu.
The geographic export zone can only export in raster format. You can not export in raster format if the coverage prediction was made per transmitter (for example, coverage predictions with the display type set by transmitter, by a transmitter attribute, by signal level, by path loss, or by total losses). Only the coverage area of a single transmitter can be exported in raster format. 5. Select File > Save Image As. The Map Export dialogue appears, with the option Geographic export zone selected. 6. Click Export. The Save As dialogue appears. 7. 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: BMP, PNG, ArcView Grid (TXT), TIFF, BIL, JPEG 2000, and JPG. If you want to use the saved file as a digital terrain model, you should select the TIF, BIL, or TXT format. When saving in BIL format, Atoll allows you to save files larger than 2 Gb. 8. Click Save. The Exported Image Size dialogue appears. 9. You can define the size of the exported image in one of two ways: • •
60
Scale: If you want to define the size by scale, select Scale, enter a scale in the text box and a resolution. If you want to export the image with rulers, select Include Rulers. Pixel size: If you want to define the size by pixel size, select Pixel size, and enter a pixel size in the text box.
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
If you want to use the exported file as a digital terrain model, you must define the size of the exported image by pixel size. Atoll then creates a geo-reference file for the exported image. 10. Click OK.
1.4.13 Editing Polygons, Lines, and Points Atoll uses different types of polygons, lines, and points in the map window. For example, the zones such as the computation, focus zone and hot spot, described in "Using Zones in the Map Window" on page 54, are specific types of polygons. Another type of polygon, called contours, can along with lines and points, be used to add additional information to geographic data. Atoll provides you with several different ways of editing the polygons, lines, and points. You can move or delete the points that define polygons, lines, and points. You can edit polygons by editing the points that define them, by combining several polygons, or by deleting parts of the polygons. Polygons, including the computation, focus zone and hot spot polygons can contain holes. The holes within polygonal areas are differentiated from overlaying polygons by the order of the coordinates of their vertices. The coordinates of the vertices of polygonal areas are in clockwise order, whereas the coordinates of the vertices of holes within polygonal areas are in counter-clockwise order. When you no longer need the polygon, line, or point, you can delete it from the map. In this section, the different ways of editing polygons, lines, and points are explained: • • • • • •
"Adding a Vector Layer" on page 61 "Creating Polygons, Lines, and Points" on page 61 "Editing the Shape of Polygons and Lines" on page 62 "Combining or Cropping Polygons Using the Toolbar" on page 62 "Editing a Point" on page 64 "Editing Contours, Lines, and Points Using the Context Menu" on page 64.
1.4.13.1 Adding a Vector Layer You can add vector objects such as polygons, lines or points to geographical map information in a project by first creating a vector layer. You can also modify certain geographic data maps, for example, population maps, and custom data, by adding a vector layer to them and afterwards adding polygons, lines and points. For information on modifying certain geographic data maps by adding a vector layer, see "Editing Population or Custom Data Maps" on page 161. To add a vector layer to the Geo explorer: •
Click the New Vector Layer button (
) on the Vector Editor toolbar.
Atoll creates a folder called "Vectors" in the Geo explorer. For information on adding vector objects such as contours, lines, and points to the vector layer, see "Creating Polygons, Lines, and Points" on page 61.
1.4.13.2 Creating Polygons, Lines, and Points Once you have created a vector layer, as explained in "Adding a Vector Layer" on page 61, you can add polygons, lines, and points to it. To add a polygon, line, or point to a vector layer: 1. Right-click the vector layer in the Geo explorer. The context menu appears. 2. Select Edit from the context menu. The tools on the Vector Editor toolbar are available. You can also make the vector tools available by selecting the vector layer to edit from the Vector Editor toolbar list. Because Atoll names all new vector layers "Vectors" by default, it might be difficult to know which Vectors folder you are selecting. By renaming each vectors folder, you can ensure that you select the correct folder. For information on renaming objects, see "Renaming an Object" on page 40. If the Vector Editor toolbar is not visible, select View > Toolbars > Vector Editor. 3. Click one of the following buttons on the Vector Editor toolbar:
61
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
New Polygon: a. Click once on the map where you want to begin drawing the contour. b. Click each time you change angles on the border defining the outside of the contour. c. Double-click to close the contour. New Rectangle: a. Click the point on the map that will be one corner of the rectangle. b. Drag to the opposite corner of the rectangle. c. Release the mouse to create the rectangle defined by the two corners. If the polygon or rectangle is on the vector layer of a population map, or custom data, you must define the value the polygon or rectangle represents and map the vector layer. For more information, see "Editing Population or Custom Data Maps" on page 161. New Line: a. Click once on the map where you want to begin the line. b. Click each time you change angles on the line. c. Double-click to end the line. New Point: Click once on the map where you want to place the point. 4. Press ESC to deselect the currently selected button on the Vector Editor toolbar.
1.4.13.3 Editing the Shape of Polygons and Lines You can edit the shape of polygons and lines on the vector layer. To edit the shape of polygons and lines: 1. In the explorer (the Network explorer or the Geo explorer) containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Draw from the context menu. The vector tools on the Vector Editor toolbar are activated. You can also activate the vector tools by selecting the vector layer to edit from the Vector Editor toolbar list.
3. Select the contour or line. You can now edit by: •
Moving a point: i.
Position the pointer over the point you want to move. The pointer changes (
).
ii. Drag the point to its new position. If you are editing a rectangle, the adjacent points on the rectangle change position as well, in order for the rectangle to retain its shape. •
Adding a point to a contour or a line: i.
Position the pointer over the contour border or line where you want to add a point. The pointer changes (
).
ii. Right-click and select Insert Point from the context menu. A point is added to the contour border or line at the position of the pointer. •
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.13.4 Combining or Cropping Polygons Using the Toolbar In Atoll, you can create complex contours by using the tools on the Vector Editor toolbar.
62
).
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
To edit a vector object using the icons on the Vector Editor toolbar: 1. In the explorer (the Network explorer or the Geo explorer) containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Draw from the context menu. The vector tools on the Vector Editor toolbar are activated. You can also activate the vector tools by selecting the vector layer to edit from the Vector Editor toolbar list.
3. Click the contour to edit. The Vector Editor toolbar enables you to perform the following functions: •
: To combine an existing contour with a new one: i.
On the Vector Editor toolbar, click the Combine button (
).
ii. Click once on the map where you want to begin drawing the new contour. iii. Click each time you change angles on the border defining the outside of the contour. iv. Double-click to close the contour. v. Draw more contours if desired. Atoll creates a group of polygons of the selected and new contours. If contours overlap, Atoll merges them. •
: To combine two existing contours: i.
In the Vector Editor toolbar, click the Combine button (
).
ii. Click the contour that you want to combine with the selected one. Atoll combines the two selected contours into a single object, merging them if they overlap. •
: To draw a hole in the selected contour: i.
In the Vector Editor toolbar, click the Delete button (
).
ii. Draw the area you want to delete from the selected contour by clicking once in the contour where you want to begin drawing the area to delete. iii. Click each time you change angles on the border defining the outside of the area. iv. Double-click to close the area. Atoll deletes the area from the selected contour. •
: To delete an area of the selected contour that is overlapped by another contour: i.
In the Vector Editor toolbar, click the Delete button (
).
ii. Click the contour (which overlaps the selected contour) to delete the overlapping area from the first selected contour. Atoll deletes the area covered by the second contour from the first contour. •
: To create a contour out of the overlapping area of an existing contour and a new one: i.
In the Vector Editor toolbar, click the Intersection button (
).
ii. Click once on the map where you want to begin drawing the contour that will overlap the selected one. 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. •
: To create a contour out of the overlapping area of two existing contours: i.
In the Vector Editor toolbar, click the Intersection button (
).
ii. Click the contour (which overlaps the selected contour) that you want to intersect with the first selected contour. Atoll creates a new contour from the area of the two contours that overlaps and deletes the parts of the contours that do not overlap. •
: To split the selected contour into two contours: i.
In the Vector Editor toolbar, click the Split button (
).
ii. Click once on the map where you want to begin drawing the contour that will split the selected contour.
63
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
iii. Click each time you change angles on the border defining the outside of the contour. iv. Double-click to close the contour. Atoll deletes the area defined by the newly drawn contour from the selected contour, thereby creating two new contours. •
: To split overlapping contours into three contours: i.
In the Vector Editor toolbar, click the Split button (
).
ii. Click the contour (which overlaps the selected contour) that you want to use to crop the first selected contour. Atoll separates the overlapping area from the first selected contour, thereby creating three contours: the first contour minus the area overlapped by the second, the second contour (which remains unchanged, and a third contour created from the area deleted from the first selected contour.
1.4.13.5 Editing a Point To edit a point: 1. In the explorer (the Network explorer or the Geo explorer) containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Draw from the context menu. The vector tools on the Vector Editor toolbar are activated. You can also activate the vector tools by selecting the vector layer to edit from the Vector Editor toolbar list.
3. Select the 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.13.6 Editing Contours, Lines, and Points Using the Context Menu When you are editing contours, lines, and points, you can access certain commands using the context menu. To edit a vector object using the context menu: 1. Click the vector object you want to edit. 2. Right-click the vector object to display the context menu and select one of the following: • • • • • • •
Delete: Select Delete to remove the selected contour, line, or point from the map. Convert to Line: Select Convert to Line to convert the selected contour to a line. Convert to Polygon: Select Convert to Polygon to convert the selected line to a contour. Open Line: Select Open Line to remove the segment between the last and the first point. Close Line: Select Close Line to add a segment between the last and the first point of the line. Insert Point: Select Insert Point to add a point to the border of the contour at the position of the pointer. Move: i.
Select Move from the context menu to move the contour, line, or point on the map.
ii. Move the contour, line, or point. iii. Click to place the contour, line, or point. • •
Quit edition: Select Quit Edition to exit editing mode. Properties: Select Properties to open the Properties dialogue of the selected contour, line, or point. The Properties dialogue has two tabs: • •
64
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.
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Only the commands relevant to the selected contour, line, or point are displayed in the context menu.
1.4.14 Copying the Content of a Zone into Another Application You can copy the content of one of the following zones of the map window into a document created using another application: • • • • • •
Filtering zone Focus zone Computation zone Hot spot Printing zone Geographical export zone
To copy the content of a zone into a document created using another application: 1. Select the zone in the map window, or expand the Zones folder in the Geo explorer and select the zone. You can copy the contents of the zone in the following ways: •
Select Edit > Copy (or press Ctrl+C) to copy a bitmap image of the selected zone, or
a. Select Edit > Advanced Copy. The Advanced Copy dialogue appears. b. Select one of the following: •
• •
Bitmap image: Select Bitmap Image to copy the contents of the zone as a bitmap and then select either Screen resolution or Custom resolution and enter the custom resolution in the text box. The default custom resolution is 50 m. Metafile Image: Select Metafile Image to copy the contents of the zone as a Windows metafile. Georeference Coordinates: Select Georeference Coordinates to copy the georeference coordinates to the clipboard. They will be pasted as the coordinates.
2. Open the application into which you want to paste the image and select Edit > Paste (or press Ctrl+V). The zone of the map is pasted as an image (or as georeference coordinates) into the new document.
1.4.15 Map Window Pointers In Atoll, the pointer appears in different forms according to its function. Each pointer is described below: Appearance
Description
Meaning
Selection arrow
The zone selection pointer indicates that, on the map, you can define a zone to print or copy and, in the Panoramic window, you can define the zone to be displayed on the map. To define a zone, click and drag diagonally.
Polygon drawing pointer
The polygon drawing pointer indicates you can draw a zone to filter either sites or transmitters, draw computation/focus/hot spot/filtering/printing/ geographic export zones, or draw vector or raster polygons on the map. To draw a polygon, click once to start, and each time you change angles on the border defining the outside of the polygon. Close the polygon by clicking twice.
The rectangle drawing pointer indicates you can draw computation/focus/hot spot/ Rectangle drawing filtering/printing/geographic export zones, or draw vector or raster rectangles on pointer the map. To define a zone, click and drag diagonally. Hand
The hand pointer indicates you can move the visible part of the displayed map.
Zoom tool
The zoom pointer indicates you can click to zoom in and right-click to zoom out at the location of the mouse pointer
Zoom area
The zoom area pointer indicates you can zoom in on an area of the by clicking and dragging to define the area.
New transmitter Point analysis
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.
65
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
Appearance
© Forsk 2012
Description Point placed (Receiver)
Meaning The point placed pointer indicates the position of the receiver on the map that is used for the point-to-point analysis. The results are displayed in the CW Measurements or Point Analysis window.
Pencil
The pencil pointer indicates you can create a polygonal clutter zone, by clicking once to start the polygon, once to create each corner, and by double-clicking to close the polygon.
Deletion
The deletion pointer indicates that you can delete a newly created polygonal clutter zone by clicking its border.
Position indicator
The position indicator pointer indicates you can select the border of a polygon. Right-clicking the polygon border opens a context menu allowing you to add a point, delete the polygon, or centre the map on the polygon.
Select/create points
The select/create points pointer indicates you can modify the polygon in the map window. You can add a new point and modify the polygon contour by clicking on one of the edges and dragging. You can move an existing point by clicking and dragging an existing point. You can right-click to open a context menu to delete a point, delete the polygon, or centre the map on the polygon.
Placing a CW measurement point
The first CW measurement point pointer indicates you can click a point on the map to create the first point of a CW measurement path.
Placing points in a The next CW measurement point pointer indicates the first CW measurement point CW measurement has been set and you can now click other points on the map. Double-click to end the path CW measurement path. The measurement pointer indicates you can click on the map to set the start point of Measurements on your measurement. As you move the pointer, the distance between the first point the map and the pointer is displayed in the status bar.
Terrain section
The terrain section pointer indicates that you can create a terrain section by clicking once on the map to create the first point and once more to create the second point. The terrain profile between the two points is displayed in the Point Analysis window and stored under Terrain Sections in the Geo explorer.
1.5 Working with Coverage Predictions When working with coverage predictions, Atoll has the following functions to help you organise them and to export them to other formats: • •
"Organising the Contents of the Predictions Folder" on page 66 "Exporting Coverage Prediction Results" on page 67.
1.5.1 Organising the Contents of the Predictions Folder When you create a coverage prediction in Atoll, it is stored in the Predictions folder in the Network explorer. Atoll enables you to organise the predictions created in a series of sub-folders that you can give descriptive names to. In this section, the following are explained: • •
"Creating a Predictions Sub-folder" on page 66 "Moving a Coverage Prediction into a Sub-folder" on page 67.
1.5.1.1 Creating a Predictions Sub-folder Atoll enables you to create sub-folders in the Predictions folder in the Network explorer. Atoll only permits one level of subfolders. In other words, you can create a sub-folder in the Predictions folder, but you can not create a sub-folder within a subfolder. Once you have created a sub-folder, you can move coverage predictions into it. For more information, see "Moving a Coverage Prediction into a Sub-folder" on page 67
66
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
To create a sub-folder in the Predictions folder: 1. Click the Network explorer. 2. Right-click the Predictions folder in the Network explorer. The context menu appears. 3. Select New Folder from the context menu. Atoll creates a new sub-folder named "Folderx" in the Predictions folder, where "x" is a number assigned by Atoll sequentially according to the number of sub-folders with default names in the Predictions folder. You can change the name of the sub-folder to give it a more descriptive name.
1.5.1.2 Moving a Coverage Prediction into a Sub-folder Once you have created sub-folders in the Predictions folder in the Network explorer as explained in "Creating a Predictions Sub-folder" on page 66, you can organise the coverage predictions by moving them into the sub-folders. Atoll also permits you to move them from one sub-folder to another or from a sub-folder directly to the Predictions folder. To move a coverage prediction from the Predictions folder to a sub-folder: 1. Click the Network explorer. 2. Click the Expand button (
) to the left of Predictions folder to expand the folder.
3. Right-click the coverage prediction you want to move to a sub-folder. The context menu appears. 4. Select Move To from the context menu. The Move to Folder dialogue appears. 5. Select the name of the sub-folder in the Move to Folder dialogue and click Okay. The coverage prediction is moved to the selected sub-folder. The same procedure can be used to move a coverage prediction from one sub-folder to another or from a sub-folder to the Predictions folder.
You can also use drag-and-drop to move any coverage prediction to the Predictions folder or any of its sub-folders by dragging the coverage prediction over the Predictions folder or over the name of the destination sub-folder and dropping it. You can only drop a coverage prediction in a destination folder when this folder is highlighted, as shown in Figure 1.16.
Figure 1.16: Using drag-and-drop to move a coverage prediction to a Predictions sub-folder
1.5.2 Exporting Coverage Prediction Results In Atoll, you can export the coverage areas of a coverage prediction in raster or vector formats. In raster formats, you can export in BMP, TIF, JPEG 2000, ArcView© grid, or Vertical Mapper (GRD and GRC) formats. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 GB. In vector formats, you can export in ArcView©, MapInfo©, or AGD formats. The file exported can then be imported as a vector or raster object in Atoll or in another application. When you export a coverage prediction in vector format, the exported zone is delimited by the rectangle encompassing the coverage. When you export a coverage prediction in vector format, you can export the entire coverage prediction, or you can export a defined area of the coverage prediction. All coverage types can be exported, however, you can not export a coverage prediction in raster format if the coverage prediction was made per transmitter (for example, coverage predictions with the display type set by transmitter, by a transmitter attribute, by signal level, by path loss, or by total losses). In this case, only the coverage area of a single transmitter can be exported in raster format.
67
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
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 68 "Exporting an Individual Coverage Prediction in Raster Format" on page 68 "Exporting Multiple Coverage Predictions" on page 69.
1.5.2.1 Exporting an Individual Coverage Prediction in Vector Format To export a coverage prediction in vector format: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Predictions folder.
The coverage prediction must be displayed in the map window before it can be exported. For information on displaying objects in the map window, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. 3. Select Export the Coverage from the context menu. The Save As dialogue appears. 4. In the Save As dialogue, select a destination folder, enter a File name, and select the vector format from the Save as type list. 5. Click Save to export the coverage prediction results. If you have chosen to export the prediction coverage in a vector format other than AGD, the Vector Export dialogue is displayed in which you can modify the following export settings: a. Coordinate Systems: You can change the reference coordinate system for the file being exported. b. Resolution: You can change the Resolution of the exported coverage. The default resolution is the resolution of the coverage prediction results (as set in the coverage prediction Properties dialogue). c. Filtering: You can apply a filter to the coverage prediction export to fill empty pixels with a value averaged from surrounding pixels. Define the level of filtering by moving the Filtering slider, or entering the percentage in the text box. d. Smoothing: You can smooth the vectors exported by a set percentage by moving the Smoothing slider, or entering the percentage in the text box. When exporting a prediction coverage in MIF format, the tip text will be exported with it and will be visible as tip text when you re-import the MIF file in another Atoll project. For information on defining tip text, see "Defining the Object Type Tip Text" on page 46.
1.5.2.2 Exporting an Individual Coverage Prediction in Raster Format To export a coverage prediction in raster format: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Predictions folder.
The coverage prediction must be displayed in the map window before it can be exported. For information on displaying objects in the map window, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. 3. 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: a. Define the geographic export zone as explained in "Using a Geographic Export Zone" on page 59. b. Right-click the coverage prediction you want to export.
68
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
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. 5. In the Save As dialogue, select a destination folder, enter a File name and select the raster format from the Save as type list. 6. Click Save to export the coverage prediction results. The Raster Export dialogue appears. a. Under Region, select the area to export: • • •
Entire covered area: to export a rectangle containing only the area covered by the study, Computation zone: to export a rectangle containing the entire computation zone, or Geographic export zone: to export the rectangle defined by the geographic export zone.
b. Define the level of filtering by moving the Filtering slider, or entering the percentage in the text box, if you want to apply a filter to the coverage prediction export to fill empty pixels with a value averaged from surrounding pixels. c. Click OK to finish exporting the coverage prediction results. You can not export in raster format if the coverage prediction was made per transmitter (for example, coverage predictions with the display type set by transmitter, by a transmitter attribute, by signal level, by path loss, or by total losses). Only the coverage area of a single transmitter can be exported in raster format.
1.5.2.3 Exporting Multiple Coverage Predictions If you have several coverage predictions that you want to export, you can export them at the same time. To export several coverage predictions at the same time: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Export Coverages from the context menu. The Coverage Export dialogue appears. 4. In the Coverage Export dialogue, select the check boxes corresponding to the coverage predictions you want to export. By default, Atoll selects the check boxes of all coverage predictions whose visibility check box is selected in the Network explorer. 5. Under Options, you can define the following parameters: • • • •
Folder: Enter the folder you want to store the exported coverage predictions in or click the Browse button ( ) to navigate to it. Format: Select the vector file format you want Atoll to export the coverage predictions in. Time stamp: If you select the Time stamp check box, Atoll will add the date and time to the file name of each exported coverage prediction. Resolution in metres: You can define a resolution for the exported coverage predictions.
6. Click Export to export the selected coverage predictions. The selected coverage predictions are saved in the selected folder. When you export several coverage predictions at the same time, Atoll does not take the geographic export zone into consideration. The geographic export zone is only taken into consideration for raster file formats.
1.6 Working with Data Tables Atoll stores object data (sites, transmitters, repeaters, antennas, UMTS or CDMA2000 cells, UMTS or CDMA2000 parameters, etc.) in the form of tables, containing all their parameters and characteristics. The data contained in prediction reports are also stored in the form of tables. You can add columns to the data table and you can delete certain columns. When you create a new column, you can create a default value for a field you create. You can also create a list of options (for text fields) from which the user can choose when filling in the field.
69
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
You can filter, sort, and group the data contained in these tables, and view a statistical analysis of the data. You can also export the data or import data into the Atoll data tables. The options for working with data tables are available from the context menu or from the Table toolbar displayed above the table. Atoll allows you to navigate through the data in tables by either using the vertical or horizontal scroll bars, the mouse wheel, or by moving through the table cell by cell using the cursor keys or the tab key. In this section, the following are explained: • • • • • • • • • • •
"Opening a Data Table" on page 70 "Adding, Deleting, and Editing Data Table Fields" on page 70 "Editing the Contents of a Table" on page 76 "Opening an Object’s Record Properties Dialogue from a Table" on page 72 "Defining the Table Format" on page 73 "Copying and Pasting in Tables" on page 77 "Viewing a Statistical Analysis of Table Contents" on page 80 "Exporting Tables to Text Files and Spreadsheets" on page 80 "Importing Tables from Text Files" on page 82 "Exporting Tables to XML Files" on page 83 "Importing Tables from XML Files" on page 83.
1.6.1 Opening a Data Table To open a data table: 1. Select the Network or Parameters explorer. 2. Right-click the data folder of which you want to display the data table. 3. Select Open Table from the context menu.
If the Remove Filter button (
) in the Table toolbar is active, a filter has already been
applied on the table. You can click the Advanced Filter button ( ) in the toolbar to see the details of the current filter (unless the filter was applied using a filtering zone, or using a site or transmitter list).
1.6.2 Adding, Deleting, and Editing Data Table Fields The data for each object type is stored in the form of a data table. Every data table in Atoll is created with a default set of columns, each corresponding to a field. In this section, the following functions are explained: • • •
"Accessing an Object Type’s Table Fields" on page 70 "Adding a Field to an Object Type’s Data Table" on page 71 "Deleting a Field from an Object Type’s Data Table" on page 72
1.6.2.1 Accessing an Object Type’s Table Fields The fields contained in an object type’s table are defined in a dialogue. To access an object type’s table fields: 1. In the Network or Parameters explorer, open the data table as described in "Opening a Data Table" on page 70. 2. Right-click the table in the map window. The context menu appears. 3. Select Table Fields from the context menu. A dialogue appears where you can view the existing fields and add or delete new ones. The dialogue displays the following information for each type of data (see Figure 1.17): • • • • • •
70
The name of the field in the database (Name). The name of the field as it appears in the ATL file (Legend). The Type of the field. The maximum Size of the field. The Default value of the field. The Group to which the field belongs. When opening an Atoll document from a database, you can select a group of custom fields to be loaded from the database, instead of loading all custom fields.
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Figure 1.17: The Table tab Some fields listed under Legend on the Table tab of Properties dialogues are followed by: • •
"(NOT USED)" to indicate that the field is not used in the current release of Atoll. The corresponding column is hidden by default when Open Table is used. "(OBSOLETE)" to indicate that the field is not available and will be removed in a future release of Atoll. The corresponding column does not appear in the table.
1.6.2.2 Adding a Field to an Object Type’s Data Table You can add a custom field to any object type’s data table. To add a custom field to an object type’s data table: 1. Access the object type’s table fields as explained in "Accessing an Object Type’s Table Fields" on page 70. 2. Click Add. The Field Definition dialogue appears (see Figure 1.18). 3. The Field Definition dialogue has the following text boxes: • •
• • • • •
Name: Enter the Name for the field that will appear in the database Group: If desired, you can define a Group that this custom field will belong to. When you open an Atoll document from a database, you can then select a specific group of custom fields to be loaded from the database, instead of loading all custom fields. Legend: Enter the name for the field that will appear in the Atoll document. Type: Select a type for the field (text, short integer, long integer, single, double, true/false, date/time, or currency) Size: The Size field is only available if you have selected "text" as the Type. Enter a size in characters. Default value: If you want, enter a default value that will appear each time you create a new record of this object type. Choice list: The Choice list field is only available if you have selected "text" as the Type. You can create a choice list by entering the list items in the Choice list text box, and pressing ENTER after each list item, if you want, keeping each on a separate line. Select the Restricted check box, if you want the custom field to only accept values listed in the Choise list text box. Clear the Restricted check box, if you want to allow users to enter values other than those in the choice list.
4. Click OK to return to the object type table. User or custom fields are for information only and are not taken into account in any calculation. You can find these fields on the Other Properties tab of an object type’s Properties dialogue.
71
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Figure 1.18: The Field Definition dialogue
1.6.2.3 Deleting a Field from an Object Type’s Data Table You can delete custom fields from an object type’s data table. Custom fields are the fields that the user adds to an object type’s data table, as explained in "Adding a Field to an Object Type’s Data Table" on page 71. To delete a custom field from an object type’s data table: All data stored in the field will be lost when you delete the field itself. Make sure that you are not deleting important information.
1. Access the object type’s table fields as explained in "Accessing an Object Type’s Table Fields" on page 70. 2. Select the custom field that you want to delete. Some fields can not be deleted. If you select a field and the Delete button remains unavailable, the selected field is not a custom field and can not be deleted.
3. Click Delete. The field is deleted from the object type’s data table.
1.6.3 Opening an Object’s Record Properties Dialogue from a Table You can open the Record Properties dialogue of an object, for example, a site, antenna, transmitter, or cell, from its data table. To open the Record Properties dialogue of an object: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Right-click the record whose properties you want to see. 3. Select Record Properties from the context menu. You can also open the Record Properties dialogue by double-clicking the record. To avoid editing the record when you double-click, double-click the left margin of the record instead of the record itself. You can also select the record and click the Record Properties button (
72
) in the Table toolbar.
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
1.6.4 Defining the Table Format Atoll lets you format the data tables so that the data presented is more legible or better presented. You can change the format of the data table by: • • • • • •
"Formatting the Column Headers" on page 73 "Formatting Table Cells" on page 73 "Changing Column Width or Row Height" on page 73 "Displaying or Hiding a Column" on page 74 "Freezing or Unfreezing a Column" on page 75 "Moving Columns" on page 75
Formatting the Column Headers To define the format of the column headers: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Right-click the table. The context menu appears. 3. Select Format > Header Format from the context menu. The Format dialogue appears. 4. The Format dialogue has the following tabs: • • • •
Font: You can select the Font, Outline (the font style), font Size, Effects, and Text colour. Colour: You can select the colour of the column headers by selecting a Foreground colour, a Background colour, and a pattern from the list box. You can also select a 3D Effect for the header. Borders: You can select the Border, the Type, and the Colour for each column header. Alignment: You can select both the Horizontal and Vertical alignment of the column header text. The Alignment tab has additional options as well, allowing you to enable Wrap text, Auto-size, and Allow enter.
5. Click OK. Formatting Table Cells To define the format of the table cells: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Right-click the table. The context menu appears. 3. Select Format > Cell Format from the context menu. The Format dialogue appears. 4. The Format dialogue has the following tabs: • • • •
Font: You can select the Font, Outline (the font style), font Size, Effects, and Text Colour. Colour: You can select the background colour (Interior) of the column headers, by selecting a Foreground colour, a Background colour, and a pattern from the list box. You can also select a 3D Effect for the header. Borders: You can select the Border, the Type, and the Colour for each column header. Alignment: You can select both the Horizontal and Vertical alignment of the column header text. The Alignment tab has additional options as well, allowing you to enable Wrap text, Auto-size, and Allow enter.
5. Click OK. Changing Column Width or Row Height You can change the column width and row height in a data table. When you change the column width, you change the width only for the selected column. When you change the row height, however, you change the row height for every row in the table. To change the column width: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Click the border separating two column headers and drag to change the column width (see Figure 1.19). To change the row height: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Click the border separating two rows and drag to change the row height (see Figure 1.20). The width or height of the columns or rows change once you release the mouse.
73
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Figure 1.19: Changing column width
Figure 1.20: Changing row height Displaying or Hiding a Column You can choose which columns in data tables to display or hide. To display or hide a column: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Right-click the table. The context menu appears. 3. Select Display Columns from the context menu or click the Display Columns button ( Columns to Be Displayed dialogue appears (see Figure 1.21).
) in the Table toolbar. The
4. To display a column, select its check box. 5. To hide a column, clear its check box. You can also hide a column by right-clicking on its header and selecting Hide Columns from the context menu or by clicking the Hide Columns button ( ) in the Table toolbar. You can hide more than one column by pressing CTRL while selecting the columns and then clicking the Hide Columns button ( 6. Click Close.
74
).
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Figure 1.21: The Columns to Be Displayed dialogue Freezing or Unfreezing a Column In Atoll, you can freeze one or more columns of a data table so that they always remain visible as you scroll horizontally through the table. For example, while scrolling through the Sites table, you might want to have the Name column always visible. You can keep this column, or any other column visible, by freezing it. To freeze a column: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Select the header of the column you want to freeze. Click and drag over several headers to select more than one column to freeze. You can only freeze adjacent columns.
3. Right-click the selected header or headers and select Freeze Columns from the context menu or click the Freeze Columns button ( ) in the Table toolbar. Frozen columns are grouped to the left of the table and separated from other columns with a vertical red line. You can not freeze a column in a report table.
To unfreeze columns: •
Right-click the table and select Unfreeze All Columns from the context menu or click the Unfreeze All Columns button (
) in the Table toolbar.
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 70. 2. Select the header of the column you want to move. Click and drag over several headers to select more than one column to move. You can only move several columns at the same time when they are adjacent.
3. Click again on the selected column and drag to the desired area. As you drag the column, the position the column will occupy is indicated by a red line (see Figure 1.22).
75
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Figure 1.22: Moving columns 4. Release the mouse column to place the column.
It might be necessary to click Refresh
in the Map toolbar for your changes to appear.
1.6.5 Editing the Contents of a Table You can edit the content of a table in Atoll in several different ways: • • •
"Editing Table Entries Directly in the Table" on page 76 "Copying and Pasting in Tables" on page 77 "Searching for and Replacing Text Entries in Tables" on page 79.
1.6.5.1 Editing Table Entries Directly in the Table To edit table entries directly in the table: 1. Click the Network or Parameters explorer. 2. Right-click the data folder of which you want to display the data table. 3. Select Open Table from the context menu. 4. Edit the content of the table by entering the value directly in the field (see Figure 1.23). 5. Click elsewhere in the table when you have finished updating the table. Your changes are automatically saved. If a list of options has been defined for a field, you can select a value from the list (see Figure 1.24) or enter a new value.
76
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Figure 1.23: Editing data in the transmitters data tables
Figure 1.24: Choosing data in the transmitters data tables
1.6.5.2 Copying and Pasting in Tables In Atoll, you can copy and paste data in tables using the Copy (CTRL+C), Cut (CTRL+X), and Paste (CTRL+V) commands on the Edit menu. You can copy and paste data to create new elements or you can copy and paste the same data into several cells. In this section, the following is explained: • •
1.6.5.2.1
"Copying and Pasting a Table Element" on page 77 "Pasting the Same Data into Several Cells" on page 78.
Copying and Pasting a Table Element You can create a new element in tables by copying an existing element, pasting it into a new row and editing the details that are different. Each element in a table must have a unique Name.
To create a new element by copying and pasting: 1. Open the data table as explained in "Opening a Data Table" on page 70. 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.
77
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
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.6.5.2.2
Pasting the Same Data into Several Cells You can paste the same data into several cells, using Fill Up or Fill Down. To paste the same data into several cells: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Click on the cell with the data you want to copy and drag to select the cells into which you want to copy the data (see Figure 1.25).
Figure 1.25: Selecting the cells 3. Copy into the selected cells: •
To copy the contents of the top cell of the selection into the other cells, right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button (
) in the Table toolbar (see Figure 1.26).
Figure 1.26: Copying the contents of the top cell •
To copy the contents of the bottom cell of the selection into the other cells, right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button (
78
) in the Table toolbar (see Figure 1.27).
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Figure 1.27: Copying the contents of the bottom cell
1.6.5.3 Searching for and Replacing Text Entries in Tables In Atoll, you can search for and replace text strings in the table entries: • •
1.6.5.3.1
"Searching for Text Entries in Tables" on page 79 "Replacing Text Entries in Tables" on page 79
Searching for Text Entries in Tables In Atoll, you can search for text strings in the table entries. To search for text strings in a table: 1. Press CTRL+SHIFT+F. The Find dialogue appears. You can also click the Find button (
) in the table toolbar.
2. In the Find button, define what you want to find: a. Enter the text you want to find in the Find what box. b. Select whether you want to search Up or Down from your current position in the table. c. If desired, select the Match case check box. 3. Click Find Next.
1.6.5.3.2
Replacing Text Entries in Tables In Atoll, you can search for and replace text strings in the table entries. To search for and replace text strings in a table: 1. Press CTRL+SHIFT+R. The Replace dialogue appears. You can also click the Replace button (
) in the table toolbar.
2. In the Replace button, define the text you want to find and replace: a. Enter the text you want to find in the Find what box. b. Enter the text you want to replace the text in the Find what box in the Replace with box. c. If desired, select the Match case check box. 3. Click Find Next. Atoll proceeds to the next entry of the text entered in the Find what box. You can replace the text found: •
Replace: Atoll replaces the selected text with the entry in the Replace with box.
•
Replace All: Atoll replaces all occurences of the text in the Find what box with the entry in the Replace with box.
79
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.6.6 Viewing a Statistical Analysis of Table Contents You can view a statistical analysis of the contents of an entire column in a table or of the contents of a selection of cells. To view a statistical analysis of table contents: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Select the column data you want to analyse: To view a statistical analysis of an entire column: •
Click the column title. The entire column is selected.
To view a statistical analysis of a selection of cells in one column: •
Select the cells you want to analyse. You can select contiguous cells by clicking the first cell and dragging to the last cell of the selection you want to analyse, or by clicking the first cell, pressing SHIFT and clicking the last cell. You can select non-contiguous cells by pressing CTRL and clicking each cell in the column separately. In Atoll you can organise data in several different ways, allowing you to select only certain data. For more information, see "Grouping, Sorting, and Filtering Data" on page 89.
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.28).
Figure 1.28: 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.6.7 Exporting Tables to Text Files and Spreadsheets You can export entire Atoll data tables, or selected columns, to ASCII text files (in text and comma-separated value formats), MS Excel files (XLS), and XML Spreadsheet 2003 files (XML). You can open XML Spreadsheet 2003 files in MS Excel 2003 and later. Unlike XLS files, XML Spreadsheet files are not limited to 65,536 rows and 256 columns. To export a table: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Right-click the table. The context menu appears. 3. Select Export from the context menu. The Export dialogue appears. You can see how the exported table will appear in the Preview pane (see Figure 1.29).
80
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Figure 1.29: 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 field separately. a. To select a field to be exported, select the field in the Available Fields box and click ported Fields list. All fields in the Exported Fields list will be exported.
to move it to the Ex-
b. To remove a field from the list of Exported Fields, select the field in the Exported Fields list and click move it.
to re-
c. To change the order of the fields, select a field and click or to move it up or down in the list. The fields at the top of the Exported Fields appear at the left of the exported table. You can save the choices you have made in the Export dialogue as a configuration file by clicking the Save button at the top of the dialogue and entering a name for the file in the Save As dialogue that appears. The next time you export a data table, you can click Load in the Export dialogue to open your configuration file with the same settings you used this time. 8. Click Export. The Save As dialogue appears. 9. In the Save As dialogue, enter the File name and select the format from the Save as type list. 10. Click Save to export the table. You can export the Sites and Transmitters tables to text files by selecting the folder or view in the Network explorer and pressing CTRL+E. For information on importing data into a data table, see "Importing Tables from Text Files" on page 82.
81
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.6.8 Importing Tables from Text Files You can import data in the form of ASCII text files (in TXT and CSV formats) into Atoll data tables. To import a table: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Right-click the table. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the ASCII text file you want to open and click Open. The Import dialogue appears (see Figure 1.30).
Figure 1.30: Importing information into a data table 5. If the file was created using a different Coordinate system, click the Browse button ( ) to select the coordinate system the file was created with. Atoll will convert the coordinates in the imported file to match the coordinate system used in the Atoll document. 6. Enter the number of the first line of data in the 1st Data Line box. 7. Select a Decimal Symbol from the list. 8. Select a Field Separator from the list. 9. Select the Update Records check box if you want to replace the data of records already existing in the table. Atoll compares the values in the left-most column of the data to be imported with the values in the same column of the data table to see if records already exist. The values of these records are replaced when the Update Records check box is selected. If the Update Records check box is not selected, these records are not imported. 10. Under Field Mapping, there are two header rows: • •
Source: The column headers from the text file you are importing. Destination: The column headers from the Atoll data table.
Align the content of the source file with the content of the destination file by clicking the column header in the Destination row and selecting the corresponding column from the Atoll data file (see Figure 1.30). Select for source file columns that you do not want to import.
82
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
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 73.
You can save the choices you have made in the Import dialogue as a configuration file by clicking the Save button at the top of the dialogue and entering a name for the file in the Save As dialogue that appears. The next time you export a data table, you can click Load in the Import dialogue to open your configuration file with the same settings you used this time. 11. Click Import. The contents are imported in the current Atoll data table. You can import data from text files into the Sites and Transmitters tables by selecting the folder or view in the Network explorer and pressing CTRL+I. For information on exporting the information in a data table into a text file, see "Exporting Tables to Text Files and Spreadsheets" on page 80.
1.6.9 Exporting Tables to XML Files You can export the data tables in your Atoll document to XML files. You can use XML to exchange information between Atoll and the OMC. Atoll creates one XML file for each exported data table, and an index.xml file that contains the mapping between the tables that were exported and the XML files corresponding to each data table. The index.xml file also stores the information on the system (GSM, UMTS, etc.), the technology (TDMA, CDMA, TD-SCDMA, etc.), and the version of Atoll with which the XML files were created. For more information about the formats of the XML files, see the Technical Reference Guide. To export all the data tables in your document to XML files: 1. Select Document > Data Exchange > XML Export. The Browse for Folder dialogue appears. 2. Select the folder where the XML files are to be stored. Click the Make New Folder button if you want to create a new folder to store the XML files. 3. Click OK. All the data tables in the document are exported to XML files. For information on importing the data tables from XML files into your document, see "Importing Tables from XML Files" on page 83.
1.6.10 Importing Tables from XML Files You can import data tables into your Atoll document from XML files. You can use XML to exchange information between Atoll and the OMC. In order for Atoll to be able to correctly import the data tables from XML files, the XML files and the current Atoll document must use the same system (GSM, UMTS, etc.), the technology (TDMA, CDMA, TD-SCDMA, etc.), and the Atoll version used to create the XML files must be the same as the version used to import the data. For more information about the formats of the XML files, see the Technical Reference Guide. To import data tables into your document from XML files: 1. Select Document > Data Exchange > XML Import. The Browse for Folder dialogue appears. 2. Select the folder where the index.xml file is located. 3. Click OK. The data tables from the XML files listed in the index.xml file are imported in the document . Tables are imported in the same order they appear in the index.xml file. Do not modify the order of tables in the index.xml file because the order in which the data is imported is very important; some data must be imported before other data. For example, antennas used by transmitters must be imported before the transmitters themselves. When the data tables are imported: • • •
Data that exist both in the tables and in the XML files are overwritten by the data from the XML files. Data that exist only in the tables and not in the XML files are not deleted from the tables. Data that only exist in the XML files and not in the tables are imported from the XML files as new records in the tables.
83
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
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 83.
1.7 Printing in Atoll In Atoll, you can print any part of your document, including maps, data tables, document reports, and antenna patterns. When printing a map, Atoll enables you to define the area to be printed. Additionally, you can define the layout, for example, you can add a logo or graphic element, or a legend. In this section, the following are explained: • • • •
"Printing Data Tables and Reports" on page 84 "Printing a Map" on page 84 "Printing a Docking Window" on page 88 "Printing Antenna Patterns" on page 88.
1.7.1 Printing Data Tables and Reports Data tables and reports are both presented in tabular format in Atoll and can, therefore, be printed in the same way. If you want to see how the table will appear once printed, see "Previewing Your Printing" on page 88. To print a table: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. If you want to print an area of the table, select it by clicking in one corner of the area and dragging diagonally to the opposite corner. 3. Select File > Print. 4. If you want to print only a selected area, choose Selected in the Print dialogue. 5. Click OK to print.
1.7.2 Printing a Map You can print a map in Atoll and create a paper copy of coverage predictions, etc. Atoll offers several options allowing you to customise and optimise the printed map. Atoll supports printing to a variety of paper sizes, including A4 and A0. Before you print a map, you have the following options: •
You can define an area of the map to be printed in one of the following ways: • •
• •
By selecting the print area (see "Defining the Printing Zone" on page 85). By creating a focus zone (see "The Focus Zone and Hot Spots" on page 56) and then opting to print only the contents of the focus zone (see "Defining the Print Layout" on page 86).
You can accept the default layout or you can modify the print layout (see "Defining the Print Layout" on page 86). You can see how the map will appear once printed (see "Previewing Your Printing" on page 88). 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 85 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 define an area of the map to print with a printing zone (see "Defining the Printing Zone" on page 85) or with a focus zone (see "The Focus Zone and Hot Spots" on page 56). You can modify the print layout ("Defining the Print Layout" on page 86). You can see how the map will appear once printed (see "Previewing Your Printing" on page 88).
3. Select File > Print. 4. Click OK.
84
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
1.7.2.1 Printing Recommendations The appearance of the map is determined by the arrangement and properties of the objects the map contains. Objects in Atoll are arranged in layers. The layers on the top (as arranged on the Network and Geo tabs) are the most visible on the screen and in print. The visibility of the lower layers depends on which layers are above it and on the transparency of these layers (for information on transparency, see "Defining the Transparency of Objects and Object Types" on page 45). 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, 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 in the Network explorer, for example, sites, transmitters, and predictions, are displayed above objects in the Geo explorer. 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 in the Geo explorer over predictions: 1. Select the Geo explorer. 2. Right-click the vector layer you want to move to the Network explorer. The context menu appears. 3. Select Move to Network from the context menu. 4. Select the Network explorer. 5. Drag the vector layer to a position above Predictions but below Sites, Antennas, and Transmitters.
1.7.2.2 Defining the Printing Zone You can define the area of the map to be printed by creating a printing zone. To create a printing zone: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Zones folder.
3. Right-click the Printing Zone folder. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the zone.
ii. Click once on the map to define each point on the map where the border of the zone changes direction. iii. Click twice to finish drawing and close the zone. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the printing zone.
ii. 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.31). If you clear the printing zone’s visibility check box in the Zones folder in the Geo explorer, it will no longer be displayed but will still be taken into account.
85
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Figure 1.31: Printing zone You can also create a printing zone as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the printing zone. Existing polygon: You can use any existing polygon as a printing zone by right-clicking it on the map or in the Geo explorer and selecting Use As > Printing Zone from the context menu. You can also combine an existing printing zone with any existing polygon by right-clicking it on the map or in the Geo explorer and selecting Add To > Printing Zone from the context menu. The "effective" resulting printing zone will be the rectangle encompassing the several polygons composing the printing zone. Importing a polygon: If you have a file with an existing polygon, you can import it and use it as a printing zone. You can import it by right-clicking the Printing Zone folder in the Geo explorer and selecting Import from the context menu. Fit Zone to Map Window: You can create a printing zone the size of the map window by right-clicking the Printing Zone folder and selecting Fit Zone 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 Atoll’s polygon editing tools to edit the printing zone. For more information on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 57. You can save the printing zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the printing zone in the user configuration: For information on saving the printing zone in a user configuration, see "Saving a User Configuration" on page 101. Exporting the printing zone: You can export the geographic export zone by rightclicking the Printing Zone in the Geo explorer and selecting Export from the context menu.
1.7.2.3 Defining the Print Layout You can use the Print Setup dialogue to define how your map will appear when you print it. On the Print Setup dialogue, you can: • • • • • •
Set the scale of the map. Choose to print the rulers with the map. Choose to print the area outside the focus zone. Choose to print the legend. Add a title, comment, logo, header, or footer. Select paper size and source, as well as the page orientation and the margins.
These settings can be saved as a configuration, allowing you to define a standard appearance which you can then load and use the next time you print a similar document.
86
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
To define the appearance of the map when it is printed: 1. Select File > Print Setup. The Print Setup dialogue appears. You define the print setup on the Page tab, the Components tab, and the Header/Footer tab. You can see any changes you make in the schematic preview on the right side of the Print Setup dialogue. If you have previously defined a configuration file containing all the necessary settings, you can click the Load button under Configuration file to import those settings.
2. Click the Page tab. On the Page tab, you can define the page size, margins, and orientation and the scale of the printed map: a. Under Orientation, select whether the page should be printed in Portrait or Landscape. b. Under Paper, select the Size of the paper and, optionally, the Source of the paper. c. Under Scaling, define the scale of the printed image either by selecting Fit to page, or by selecting Scale and defining the scale. d. Under Margins, set the margins of the page in millimetres. 3. Click the Components tab. a. Under Map, you can define the appearance of the printed map: • •
Select the Rulers check box if you want to print the map with a scale around it. Select the Area inside focus zone only check box if you only want to print the part of the map inside the focus zone.
b. Under Legend, you can define the placement of the legend. •
Select the Legend check box if you want to print a legend with the map.
•
Click a button to set the Position of the legend. The buttons inside the square will place the legend on top of the map. The buttons outside of the square will place the legend outside of the map.
•
Click the Font button to open the Font dialogue to define the font of the legend.
c. Select the Comments check box if you want to print a comment with the map and set its Position. Clicking the Properties button opens a dialogue where you can enter text and set variables such as the current time and date. If you want the comment to appear on the map (and not outside of it), select the On the map check box. 4. Click the Header/Footer tab. On the Header/Footer tab, you can set the position of graphic elements. a. Select the Map title check box if you want to define a title for the map and set its Position. Clicking the Properties button opens a dialogue where you can enter text and set variables such as the current time and date. If you want the title to appear on the map (and not outside of it), select the On the map check box. b. Under Logo 1 and Logo 2, you can define graphics that appear for the map. The graphics can be a company logo or other information, such as copyright information, in the form of a BMP graphic. i.
For the selected logo check box, click the Properties button. The Logo dialogue appears. By default, Atoll searches for the logo files in the Atoll’s 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. In the Logo dialogue, click File. The Open dialogue appears. iii. Select the your graphic in BMP format and click Open. Only BMP graphics can be used as logos. If your logo is in a different format, you must first convert it using a graphics programme to the BMP format.
iv. Select the correct Width and Height (in pixels). v. Click OK.
87
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
c. Select the Header/Footer Note check box if you want to define a header or footer for the map and set its Position. Clicking the Properties button opens a dialogue where you can enter text and set variables such as the current time and date. If you want the header or footer to appear on the map (and not outside of it), select the On the map check box. 5. Once you have made your settings, click OK to close the Print Setup dialogue, or click Print to print the document. You can save the current settings as a configuration file by clicking the Save button under Configuration file. This enables you to re-use the same settings the next time by loading them.
1.7.3 Previewing Your Printing When you want to print maps, data tables, or reports, you can preview your printing. To preview your printing: 1. Select the map or table you want to print. 2. Select File > Print Preview. The Print Preview window appears. At the top of the Print Preview window, you can click one of the following buttons: • • •
Click the Print button ( ) to open the Print dialogue. Click the Next Page button ( ) to display the following page Click the Previous Page button ( ) to display the previous page.
•
Click the Zoom In button (
•
Click the Zoom Out button (
) to zoom in on the print preview.
• •
Click the Toggle One/Two Pages Display button ( Click Close to close the print preview.
) to zoom out on the print preview. ) to switch display from one to two pages side by side
1.7.4 Printing a Docking Window You can print the content of many docking windows using the context menu; selecting File > Print only prints the contents of a document window, as explained in "Printing a Map" on page 84. The docking windows whose contents you can print are: • • • •
Legend Window (for more information on this tool, see "Adding an Object Type to the Legend" on page 47) Point Analysis Tool CW Measurement Analysis Tool (for more information on this tool, see the Measurements and Model Calibration Guide. Drive Test Data Analysis Tool
To print the content of a docking window: 1. Open the docking window you want to print. •
If you want to print a Point Analysis window, click the tab you want to print.
2. Right-click the window you want to print. 3. Select Print from the context menu. The Print dialogue appears. 4. Click OK to print.
1.7.5 Printing Antenna Patterns You can print the horizontal or vertical pattern of an antenna. To print an antenna pattern: 1. Click the Parameters explorer. 2. Open the Antennas table: To open the RF Antennas table: a. Click the Expand button (
) to the left of the Radio Network Equipment folder.
b. Right-click the Antennas folder. c. Select Open Table from the context menu. 3. Right-click the antenna whose pattern you want to print.
88
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
4. Select Record Properties from the context menu. The Properties dialogue appears. 5. Select the Horizontal Pattern tab or the Vertical Pattern tab. 6. Right-click the antenna pattern and select Linear or Logarithmic from the context menu. 7. Right-click the antenna pattern and select Print from the context menu.
1.8 Grouping, Sorting, and Filtering Data In Atoll you can organise data in several different ways, allowing you to select only certain data and then, for example, modify only selected data or run calculations on the selected data. Atoll allows you to group, sort, or filter data quickly by one criterion, or by several. After you have defined how you will group, sort, or filter data, you can save this information as a folder configuration. In this section the following will be explained: • • • • •
"Grouping Data Objects" on page 89 "Sorting Data" on page 93 "Filtering Data" on page 95 "Folder Configurations" on page 105 "Creating and Comparing Views" on page 107
1.8.1 Grouping Data Objects You can group objects according to a selected property in the Network explorer. The objects to be grouped can be in a data folder or in a view (see "Creating and Comparing Views" on page 107). You can also define the properties by which you can group objects. Grouping objects in the Network explorer is similar to sorting data in the data table because it puts all records with the selected property together. Once you have grouped data objects, you can access their Properties dialogue from the context menu to edit properties on all grouped objects. You can save the grouping parameters as a folder configuration. For information, see "Folder Configurations" on page 105. This section explains: • • •
"Grouping Data Objects by a Selected Property" on page 89 "Configuring the Group By Submenu" on page 90 "Advanced Grouping" on page 90.
For examples of grouping data objects, see "Examples of Grouping" on page 91.
1.8.1.1 Grouping Data Objects by a Selected Property You can group data objects by a selected property using the Group By command on the context menu. To group data objects by a selected property: 1. Select the Network explorer. 2. Right-click the folder or view whose objects you want to group. The context menu appears. 3. From the Group By submenu, select the property by which you want to group the objects. The objects in the folder are grouped by that property. If the range of properties available in the Group By submenu has been configured as explained in "Configuring the Group By Submenu" on page 90, you can select additional properties by selecting More Fields from the Group By submenu. For information on using the dialogue that appears, see "Configuring the Group By Submenu" on page 90. To undo the grouping: 1. Select the Network explorer. 2. Right-click the folder or view whose objects you have grouped. 3. From the context menu, select from the Group By > None. See "Examples of Grouping" on page 91.
89
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.8.1.2 Configuring the Group By Submenu Some data objects, such as transmitters, have a large number of properties that will appear by default in the Group By submenu. You can make it easier to group data objects by configuring the Group By submenu to display only the properties that are relevant for grouping. To configure the Group By submenu: 1. Select the Network explorer. 2. Right-click the folder whose Group By submenu you want to configure. The context menu appears. 3. Select Properties from the context menu. 4. Select the General tab of the Properties dialogue. 5. Click the Configure Menu button next to the Group By field that shows how the data objects are presently grouped. The Menu Configuration dialogue appears (see Figure 1.32).
Figure 1.32: The Menu Configuration dialogue 6. Select the fields you want to appear in the Group By submenu. You can display all the fields belonging to a table by clicking the Expand button ( ) to the left of the table name. You can select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking each field separately. •
To select a field to appear in the Group By submenu, select the field in the Available fields list and click move it to the Grouping Fields list.
to
•
To remove a field from the list of Grouping Fields, select the field in the Grouping fields list and click remove it.
to
•
To change the order of the fields, select a field and click or to move it up or down in the list. The objects will be grouped in the order of the fields in the Grouping fields list, from top to bottom.
7. Click OK to close the Menu Configuration dialogue and click OK to close the Properties dialogue. The Group By submenu will now contain only the fields you selected.
1.8.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. Select the Network explorer. 2. Right-click the folder or view 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.33).
90
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Figure 1.33: 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 field separately. •
To select a field to be used to group the objects, select the field in the Available Fields list and click it to the Grouping Fields list.
to move
•
To remove a field from the list of Grouping Fields, select the field in the Grouping Fields list and click remove it.
•
To change the order of the fields, select a field and click or to move it up or down in the list. The objects will be grouped in the order of the fields in the Grouping Fields list, from top to bottom.
to
7. Click OK to close the Group dialogue and click OK to close the Properties dialogue and group the objects. To undo the grouping: 1. Select the Network explorer. 2. Right-click the folder or view whose objects you have grouped. 3. From the context menu, select from the Group By > None.
1.8.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 Network explorer, 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.34), you can group the transmitters by the site they are located on.
91
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Figure 1.34: Grouping transmitters by site The result of grouping can be seen in Figure 1.35.
Figure 1.35: 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.34), you can group the transmitters in the focus zone together.
92
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Figure 1.36: Grouping transmitters by zone The result of grouping can be seen in Figure 1.35. The transmitters are now in two groups: those inside the focus zone and those outside the focus zone.
Figure 1.37: Transmitters grouped by site
1.8.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 105. This section explains the following: • •
"Sorting Data in Tables" on page 93 "Advanced Sorting" on page 94
1.8.2.1 Sorting Data in Tables When sorting data in tables, you can sort by one column or by several columns: • •
"Sorting by One Column" on page 94 "Sorting by Several Columns" on page 94.
93
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Sorting by One Column To sort data in a table by one column: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Select the header of the column that you want to sort on. The entire column is selected. 3. Right-click the column header. The context menu appears. 4. From the context menu, select how you want to sort: •
Sort Ascending: sort the data table records from the lowest value in the reference column to the highest value.
•
Sort Descending: sort the data table records from the highest value in the reference column to the lowest value. You can also sort data in a table by selecting the column as described and then clicking either the Sort Ascending (
) or Sort Descending (
) buttons in the Table toolbar.
Sorting by Several Columns You can only sort in a table by adjacent columns. If you want to sort by columns that are not adjacent, you can move the columns first as explained in "Moving Columns" on page 75. 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 94. To sort data in a table by several columns: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Click the header of the first column and drag over the adjacent columns that will be your sort references. The entire column is selected. 3. Right-click the column headers. The context menu appears. 4. From the context menu, select how you want to sort: •
Sort Ascending: sort the data table records from the lowest value in the first reference column to the highest value.
•
Sort Descending: sort the data table records from the highest value in the first reference column to the lowest value. You can also sort data in a table by selecting the column as described and then clicking either the Sort Ascending (
) or Sort Descending (
) buttons in the Table toolbar.
1.8.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. Select the Network explorer. 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.38). 6. For the first column you want to sort on: a. Select the column name from the Sort by list. b. Choose whether you want to sort in ascending or descending order. 7. For each other column you want to sort on: a. Select the column name from the And by list. b. Choose whether you want to sort in ascending or descending order.
94
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
8. Click OK.
Figure 1.38: The Sort dialogue
1.8.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 105. This section explains the following: • • • •
"Filtering in Data Tables by Selection" on page 95 "Advanced Data Filtering" on page 96 "Restoring All Records" on page 97 "Advanced Filtering: Examples" on page 98.
1.8.3.1 Filtering in Data Tables by Selection You can filter a data table by selecting one or more values. Once you have selected one or more values, you can choose to view only records that have the same value or only records that do not have that value. To filter a data table on one or more fields: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Select the value to filter on. You can select multiple values by pressing CTRL as you click the other values. 3. Right-click the selected value or values and select one of the following from the table’s context menu: •
Filter by Selection: All records with the selected value or values are displayed. You can now modify these records or make calculations on them as you would normally do with the entire data table (see Figure 1.39 on page 96).
•
Filter Excluding Selection: All records without the selected value or values are displayed. You can now modify these records or make calculations on them as you would normally do with the entire data table (see Figure 1.40 on page 96).
When the data in a table are filtered, a filter funnel icon ( ) appears in the corresponding column header, as shown on the right-hand side of Figure 1.39 and Figure 1.40.
95
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Figure 1.39: Filtering by selection
Figure 1.40: Filtering excluding selection You can also filter data in a table by selecting the values as described and then clicking either the Filter by Selection ( toolbar.
) or Filter Excluding Selection (
) buttons in the Table
1.8.3.2 Advanced Data Filtering You can use advanced data filtering to combine several criteria in different fields to create complex filters. To create an advanced filter: 1. Open the data table as explained in "Opening a Data Table" on page 70. 2. Click the Advanced Filter button (
) in the Table toolbar. The Filter dialogue appears.
You can also access the Filter dialogue by clicking the Filter button of the table’s Properties dialogue.
96
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
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. 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 95.
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.41).
Figure 1.41: The Filter dialogue - Advanced tab b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the following table: Formula
Data are kept in the table only if
=X
value equal to X (X can be a number or characters)
X
value not equal to X (X can be a number or characters)
X
numerical value is greater than X
=X
numerical value is greater than or equal to X
*X*
text objects which contain X
X*
text objects which start with X
5. Click OK to filter the data according to the criteria you have defined. Filters are combined first horizontally, then vertically. See "Advanced Filtering: Examples" on page 98.
1.8.3.3 Restoring All Records After you have applied filter criteria to records, you may want to cancel the filter criteria and display all the records again. To restore all records: •
Click the Remove Filter button (
) in the Table toolbar.
97
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.8.3.4 Advanced Filtering: Examples In this section, you will find a few examples of advanced filtering: • • •
1.8.3.4.1
"Advanced Filtering: Example 1" on page 98 "Advanced Filtering: Example 2" on page 99 "Advanced Filtering: Example 3" on page 99.
Advanced Filtering: Example 1 In this example, there is an Atoll document with antennas from two manufacturers and with different characteristics.
Figure 1.42: Initial table The objective of this example is to use filter criteria to find antennas manufactured by Kathrein with a beamwidth between 50 and 100°. To do this, the following filter syntax is entered on the Advanced tab of the Filter dialogue (for information on the Advanced tab, see "Advanced Data Filtering" on page 96): •
• •
The first criterion, as shown in Figure 1.43, 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.43.
Figure 1.43: Advanced filtering
98
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
1.8.3.4.2
Advanced Filtering: Example 2 In this example, the document is the same as in "Advanced Filtering: Example 1" on page 98. The objective of this example is the same as well: to use filter criteria to find antennas manufactured by Kathrein with a beamwidth between 50 and 100°. The filter syntax is entered on the Advanced tab of the Filter dialogue (for information on the Advanced tab, see "Advanced Data Filtering" on page 96), in this case, however, the entered filter syntax contains errors: • •
As shown in Figure 1.44, the first criterion is all antennas made by a manufacturer with a name beginning with a "K" ("=K*"). The second criterion is all antennas with a beamwidth under 100° and over 50°.
The result of this advanced filter can be seen in the second pane of Figure 1.43.
Figure 1.44: 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.8.3.4.3
Advanced Filtering: Example 3 In this example, the document is the same as in "Advanced Filtering: Example 1" on page 98. The objective of this example is the same as well: to use filter criteria to find antennas manufactured by Kathrein with a beamwidth between 50 and 100°. The filter syntax is entered on the Advanced tab of the Filter dialogue (for information on the Advanced tab, see "Advanced Data Filtering" on page 96), in this case, however, the entered filter syntax contains errors: • •
As shown in Figure 1.45, the first criterion is all antennas made by a manufacturer with a name beginning with a "K" ("=K*"). The second criterion is all antennas with a beamwidth under 100° and over 50°.
The result of this advanced filter can be seen in the second pane of Figure 1.43.
Figure 1.45: Errors in filtering
99
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
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.8.4 User Configurations In Atoll, you can save many parameters and settings in user configurations and then load them in other documents. User configurations are used to store parameters and settings that are not stored in databases. User configuration files enable you to ensure that all users in a multi-user environment use the same settings. The file extension of user configuration files is CFG. The file extension GEO is, however, used if only the geographic data set or zones are being saved in a user configuration file. User configuration files are XML files and can be opened in text and XML editors. You can save the following information in user configuration files: •
Geographic data set: Full paths of imported geographic maps, map display settings (such as, the visibility scale, transparency, tip text, etc.), clutter description (code, name, height, standard deviations, etc.), and raster or user profile traffic map description. When you save the geographic data set in a user configuration file, the coordinate system of all vector geographic data must be the same as that of the raster geographic data.
• • •
• • • • • •
Map centre and zoom level: X and Y coordinates of the centre of the map window and the zoom level. Zones: Filtering, focus, computation, printing, and geographic export zones in the current document. Folder configurations: Sort, group, and filter settings (the current folder configuration, even if not saved, and other defined configurations for the folders), the filtering zone, the display settings of network data folders (including measurement display settings), and LTE and WiMAX AFP parameters (including constraint weights for frequency planning, physical cell ID planning, and preamble index planning). Automatic Neighbour Allocation Parameters: The input parameters of the automatic neighbour allocation. Automatic Scrambling Code Allocation Parameters: The parameters of the automatic scrambling code allocation. Automatic PN Offset Allocation Parameters: The parameters of the automatic PN offset allocation. Prediction List: The list of predictions in the Predictions folder and their settings (general, coverage conditions, and display). GSM Automatic Frequency Planning Parameters: Calculation options selected when starting a GSM AFP session as well as calculation parameters used for interference histograms. Macros: Full paths of any macros. Macros are loaded for entire Atoll sessions and not for a specific Atoll document. You can export the macros to a user configuration even if you do not have an Atoll document open.
For a detailed description of the user configuration file, see the Administrator Manual. In this section, the following are explained: • •
100
"Saving a User Configuration" on page 101 "Loading a User Configuration" on page 101.
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
1.8.4.1 Saving a User Configuration You create a user configuration by saving the selected settings to an external file. To save a user configuration: 1. Select Tools > User Configuration > Save. The User Configuration dialogue appears (see Figure 1.46).
Figure 1.46: Saving 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.8.4.2 Loading a User Configuration You can load a user configuration that you or another user has created, as explained in "Saving a User Configuration" on page 101, into your current Atoll document. If the user configuration you load contains macro information, it will only be loaded if no document is currently open. When there is no Atoll document open, only macro information is loaded from the user configuration. To load a user configuration: 1. Select Tools > User Configuration > Load. The Open dialogue appears. 2. Select the user configuration file with the data you want to use in your current document. 3. Click Open. The User Configuration dialogue appears (see Figure 1.47).
Figure 1.47: Loading a user configuration 4. Select the check boxes of the information you want to load. 5. Click OK. The user configuration is loaded into your current document.
101
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.8.5 Site and Transmitter Lists In Atoll, you can create lists of sites and transmitters. Once you have created a site or transmitter list, you can modify the list and use it to filter data to be able to work with a subset of data, or to facilitate working with large documents by reducing the number of records displayed. In a multi-user environment, site lists can be stored in the database. When you open a document from a database, you can select the sites to load according to any defined site lists. In a large radio-planning project, this allows you to more effectively manage your resources by reducing the unnecessary data you retrieve from the database. In this section, the following are explained: • • • • • • • •
"Creating a Site or Transmitter List" on page 102 "Adding a Site or Transmitter to a List in the Network Explorer" on page 102 "Adding a Site or Transmitter to a List from the Map Window" on page 103 "Adding Sites or Transmitters to a List Using a Zone" on page 103 "Editing a Site or Transmitter List" on page 103 "Importing a Site or Transmitter List" on page 104 "Exporting a Site or Transmitter List" on page 104 "Filtering on a Site or Transmitter List" on page 105.
1.8.5.1 Creating a Site or Transmitter List You can create lists of sites or transmitters that you can then use to filter the data displayed. To create a site or transmitter list: 1. Select the Network explorer. 2. Right-click the folder where you want to create the list: Site list: if you want to create a site list: a. Right-click the Sites folder. The context menu appears. b. Select Site Lists > Open Table from the context menu. The Site Lists table appears. Transmitter list: if you want to create a transmitter list: a. Right-click the Transmitters folder. The context menu appears. b. Select Transmitter Lists > Open Table from the context menu. The Transmitter Lists table appears. 3. Enter the name of the new list in the row marked with the New Row icon (
).
You can create a series of blank site or transmitter lists by importing a text file with the names of the new lists. You can import the text file by clicking the Actions button on the Site Lists or Transmitter Lists dialogue and then selecting Import from the menu that appears. You can also export the names of all existing site or transmitter lists by selecting Export from the same menu.
1.8.5.2 Adding a Site or Transmitter to a List in the Network Explorer You can add a site or transmitter to a list by selecting it from the Network explorer. To add a site or transmitter to a list: 1. Select the Network explorer. 2. Click the Expand button (
) to the left of Sites or Transmitters folder to expand the folder.
3. Right-click the site or transmitter you want to add to the list. The context menu appears. Site list: if you want to add a site to a list: •
Select Add Site to a List from the context menu. A dialogue appears.
Transmitter list: if you want to add a transmitter to a list. •
Select Add Transmitter to a List from the context menu. A dialogue appears.
4. Select the name of the list from the dialogue.
102
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
You can create a new list by entering a name in the list instead of selecting the name from the list. The selected site or transmitter will be added to the new list.
5. Click OK. The site or transmitter is added to the selected list. You can quickly create a complete list by first filtering the contents of the Sites or Transmitters folder as explained in "Filtering Data" on page 95. 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.8.5.3 Adding a Site or Transmitter to a List from the Map Window You can add a site or transmitter to a list by selecting it from the map window. To add a site or transmitter to a list: 1. In the map window, right-click the site or transmitter you want to add to a list. Site list: if you want to add a site to a list: •
Select Add Site to a List from the context menu. A dialogue appears.
Transmitter list: if you want to add a transmitter to a list. •
Select Add Transmitter to a List from the context menu. A dialogue appears.
2. Select the name of the list from the dialogue. You can create a new list by entering a name in the list instead of selecting the name from the list. The selected site or transmitter will be added to the new list.
3. Click OK. The site or transmitter is added to the selected list.
1.8.5.4 Adding Sites or Transmitters to a List Using a Zone You can add the sites or transmitters contained in a zone to a site or transmitter list. To add the sites or transmitters contained in a zone to a list: 1. Create a zone as explained in "Using Zones in the Map Window" on page 54 that contains the sites or transmitters you want to add to a list. You can use a filtering, computation, focus, hot spot, printing, or geographic export zone. 2. In the Geo explorer, right-click the zone and select one of the following from the context menu: • •
Add Sites to a List: Select Add Sites to a List to add the sites in the zone to a site list. A dialogue appears. Add Transmitters to a List: Select Add Transmitters to a List to add the sites in the zone to a site list. A dialogue appears.
3. Select the name of the list from the dialogue. 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.8.5.5 Editing a Site or Transmitter List You can edit a site or transmitter list using the Site List or Transmitter List table. To edit a site or transmitter list: 1. Select the Network explorer. 2. Right-click the folder where you want to edit the list:
103
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
Site list: if you want to edit a site list: a. Right-click the Sites folder. The context menu appears. b. Select Site Lists > Open Table from the context menu. The Site Lists table appears. Transmitter list: if you want to edit a transmitter list: a. Right-click the Transmitters folder. The context menu appears. b. Select Transmitter Lists > Open Table from the context menu. The Transmitter Lists table appears. 3. Select the name of the list you want to edit and click Properties. The Properties dialogue appears. 4. You can now edit the list: To add a site or transmitter to the list: •
Select the name of the site or transmitter in the row marked with the New Row icon (
).
To delete a site or transmitter from the list: a. Click in the left margin of the row containing the site or transmitter to select it. b. Press DEL to delete the site or transmitter from the list. 5. Click OK when you have finished editing the site or transmitter list.
1.8.5.6 Importing a Site or Transmitter List You can import a site or transmitter list from a text file using the Site List or Transmitter List table. To import a site or transmitter list: 1. Select the Network explorer. 2. Right-click the folder where you want to import the list: Site list: if you want to import a site list: a. Right-click the Sites folder. The context menu appears. b. Select Site Lists > Open Table from the context menu. The Site Lists table appears. Transmitter list: if you want to import a transmitter list: a. Right-click the Transmitters folder. The context menu appears. b. Select Transmitter Lists > Open Table from the context menu. The Transmitter Lists table appears. 3. Select the name of the list into which you want to import entries and click Properties. The Properties dialogue appears. 4. In the Properties dialogue, click the Import button. The Open dialogue appears. 5. Select the text file with the site or transmitter names you want to import and click Open. The contents of the text file are added to the list. 6. Click OK in the Properties dialogue when you have finished importing the file.
1.8.5.7 Exporting a Site or Transmitter List You can export a site or transmitter list to a text file using the Site List or Transmitter List table. To export a site or transmitter list: 1. Select the Network explorer. 2. Right-click the folder where you want to export the list: Site list: if you want to export a site list: a. Right-click the Sites folder. The context menu appears. b. Select Site Lists > Open Table from the context menu. The Site Lists table appears. Transmitter list: if you want to export a transmitter list: a. Right-click the Transmitters folder. The context menu appears. b. Select Transmitter Lists > Open Table from the context menu. The Transmitter Lists table appears. 3. Select the name of the list you want to export and click Properties. The Properties dialogue appears. 4. In the Properties dialogue, click the Export button. The Save As dialogue appears. 5. Enter a file name and click Save. The site or transmitter list is saved as a text file.
104
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
1.8.5.8 Filtering on a Site or Transmitter List You can use site or transmitter lists to filter the contents of the Sites and Transmitters folders. To filter folder contents using a site or transmitter list: 1. Select the Network explorer. 2. Right-click the folder whose contents you want to filter. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab of the Properties dialogue, click the Filter button. The Filter dialogue appears. 5. If you have created a list, there will be an additional tab: • •
Sites: Click the Site Lists tab. Transmitters: Click the Transmitter Lists tab.
6. Select the check box of the list or lists that you want to display. 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 Network explorer and in the map window.
1.8.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 105 "Applying a Saved Folder Configuration" on page 105 "Reapplying the Current Folder Configuration" on page 106 "Saving a Folder Configuration in an External File" on page 106 "Loading a Folder Configuration from an External File" on page 106 "Deleting a Folder Configuration" on page 106. 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.8.6.1 Creating a Folder Configuration In Atoll, you can save the parameters defining how data contained in a folder are grouped, filtered, or sorted as a folder configuration. To create a configuration: 1. Select the Network explorer. 2. Right-click the folder whose settings you want to save. 3. Select Properties from the context menu. 4. Select the General tab in the Properties dialogue. 5. If you have not yet done so, set the following parameters as desired: • • •
Group By (see "Grouping Data Objects" on page 89) Sort (see "Sorting Data" on page 93) Filter (see "Filtering Data" on page 95).
6. Under Folder configuration, click Save. 7. Enter the name of the configuration in the Save Configuration dialogue. 8. Click OK to save the configuration and click OK to close the Properties dialogue. The saved folder configuration is only available for the current folder and can be reapplied to the folder by selecting it from the Folder Configuration submenu on the folder’s context menu.
1.8.6.2 Applying a Saved Folder Configuration You can apply a folder configuration that has been created and saved for the present folder.
105
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
To apply a saved folder configuration: 1. Select the Network explorer. 2. Right-click the folder to which you want to apply a folder configuration. The context menu appears. 3. On the Folder Configuration submenu, select the name of the folder configuration you want to apply. The folder configuration is applied to the current folder.
1.8.6.3 Reapplying the Current Folder Configuration If you have grouped, filtered, or sorted a data folder, you have created and applied a folder configuration. If you then add or modify data, the properties of these may not match the folder configuration you previously made on the data folder. In this case, you can reapply the same filter or sort settings to the new or modified data. To reapply the folder configuration: 1. Select the Network explorer. 2. Right-click the folder whose folder configuration you want to reapply. 3. Select Update Folder Configuration from the context menu. The previously configured folder configuration is reapplied to the data.
1.8.6.4 Saving a Folder Configuration in an External File When you create a folder configuration, you save it in the current ATL document. However, you can save it as part of a user configuration in an external file, so that it can be used in other documents. To save a folder configuration in an external file: 1. Select Tools > User Configuration > Save. The User Configuration dialogue appears (see Figure 1.46 on page 101). 2. Select the Folder Configuration check box. If you want to export other configurations at the same time, select those check boxes as well. 3. Click OK. The Save As dialogue appears. 4. Enter a File name for the CFG file and click Save. The folder configuration has been saved.
1.8.6.5 Loading a Folder Configuration from an External File Once you have saved a folder configuration as explained in "Saving a Folder Configuration in an External File" on page 106, you can load it into your current document. To load a folder configuration: 1. Select Tools > User Configuration > Load. The Open dialogue appears. 2. Select the CFG file with the folder configuration you want to import. 3. Click Open. The User Configuration dialogue appears (see Figure 1.47 on page 101). 4. Select the Folder Configuration check box. If you want to import other configurations at the same time, select those check boxes as well. 5. Click OK. The folder configuration is imported.
1.8.6.6 Deleting a Folder Configuration You can delete a folder configuration from the Atoll document when you no longer need it. To delete a folder configuration: 1. Select the Network explorer. 2. Right-click the folder with the folder configuration you want to delete. 3. Select Properties from the context menu. 4. Select the General tab in the Properties dialogue. 5. Under Folder configuration, select the name of the configuration from the list. 6. Click Delete. The folder configuration is deleted. When you delete a folder configuration, Atoll will not ask for confirmation; it is deleted immediately.
106
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
1.8.7 Creating and Comparing Views You can compare the effects of different grouping, sorting, or filtering settings by creating views of object folders in the Network explorer and applying different settings to each view. Each view contains a copy of the data in the object folder in which it was created. To create a view of a folder: 1. In the Network explorer, right-click the folder you want to create a view of. 2. Select Create View from the context menu. A view is created containing a copy of the original folder content. You can now perform the following actions on the view: • • •
Grouping (see "Grouping Data Objects" on page 89) Sorting (see "Sorting Data" on page 93) Filtering (see "Filtering Data" on page 95). If you have created several views, you can rename each one to give it a more descriptive name. For information on renaming an object, see "Renaming an Object" on page 40.
Once you have performed the actions on each view, you can compare the differences, by displaying in turn each view, with its grouping, sorting, or filtering settings, on the map. For more information on display properties, see "Display Properties of Objects" on page 43. To compare views: 1. In the Network explorer, clear the check boxes to the left of each view. The data objects are not displayed on the map. 2. Select the check box of one of the views, leaving the check boxes of the other views cleared. The data objects of the selected view, with its associated grouping, sorting, or filtering settings, are displayed on the map. 3. Clear this check box and select the check box of a different view. How the objects are displayed on the map will change, depending on the different grouping, sorting, or filtering settings of the selected view. You can remove views by deleting them. When you delete a view, the data contained are not deleted. When you delete the last view, the data reappear under the initial folder. To delete a view: •
Select the view to be deleted and press DEL. If, after deleting the last view, the data do not reappear under the initial folder, you can refresh the display by right-clicking the folder and selecting Group By > None from the context menu.
1.8.8 Filtering Data Using a Filtering Zone In Atoll, you can simplify your calculations by using a polygon on the map to limit the amount of data considered in calculations. By limiting the number of sites, you can reduce the time and cost of calculations and make the display of data objects on the map clearer. You can select a pre-existing computation or focus zone as a filter zone or you can draw a new filtering zone. The data objects filtered by the polygon are reflected on the map and in the data tables. In the Network explorer, any folder whose content is affected by the filtering zone appears with a special icon ( been filtered.
), to indicate that the folder contents have
When you have applied a polygon filter, you can perform the following actions on the filtered data: • • •
Grouping (see "Grouping Data Objects" on page 89) Sorting (see "Sorting Data" on page 93) Filtering (see "Filtering Data" on page 95).
For more information on creating and editing a filtering zone, see "Filtering Zones" on page 54.
107
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
1.9 Tips and Tricks In this section, you will learn a few shortcuts and tricks to help you work more efficiently with Atoll: • • • • • • •
"Undoing and Redoing" on page 108 "Refreshing Maps and Folders" on page 108 "Searching for Objects on the Map" on page 108 "Using the Status Bar to Get Information" on page 109 "Saving Information Displayed in the Event Viewer" on page 110 "Using Icons from the Toolbar" on page 110 "Using Shortcuts in Atoll" on page 113.
1.9.1 Undoing and Redoing You can undo or redo most actions in Atoll, up to a maximum of 10 actions. If you perform an action that can not be undone, for example, a simulation, the Undo and Redo histories are erased. For example, you can undo or redo: • •
•
Most modifications in the workspace: such as creating, deleting, and moving a site, a station or a group of stations, modifying the antenna azimuth, moving a transmitter, or deleting a transmitter, Tasks performed in the Explorer: such as creating and deleting objects (sites, transmitters, antennas, repeaters or remote antennas, links, groups of hexagons, measurement paths, coverage predictions, maps, propagation models, etc.). Tasks performed in tables: such as adding or deleting records, pasting in tables.
To undo an action: •
Select Edit > Undo.
To redo an action that you have undone: •
Select Edit > Redo.
1.9.2 Refreshing Maps and Folders Under certain circumstances, for example, when you add data that is inconsistent with an applied filter, the data displayed on the map or in the Network explorer may not be actual. You can refresh the display to get Atoll to reload the data and reapply the current folder configurations. To refresh the display of the Network explorer and the map: •
Click the Refresh button (
) on the toolbar or press F5.
1.9.3 Searching for Objects on the Map Atoll provides the Find on Map tool for finding data objects on the map. You can search for some objects (sites, vectors, transmitters, repeaters) by their name or by any text field, using Find on Map. You can also use Find on Map to search for a point on the map by its X and Y coordinates. Additionally, Find on Map enables you to find technology-specific attributes such as a BSIC-BCCH pair in GSM. Using Find on Map to find technology-specific attributes is covered in the chapter for that technology. This section explains: • • •
"Searching for a Map Object by Its Name" on page 108 "Searching for a Map Object using Any Text Property" on page 109 "Searching for a Point on the Map" on page 109.
1.9.3.1 Searching for a Map Object by Its Name You can use Find on Map to search for the following map objects by name: • • • • •
sites transmitters repeaters remote antennas vectors
To search for a map object by name using the Find on Map tool: 1. Select Tools > Find on Map. The Find on Map window appears. 2. From the Find list, choose the map object you are searching for:
108
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
• • • •
Vector Site Transmitter Repeater/Rem. Antenna
The map object you select appears in the Field box. 3. Enter the name of the object in the text box marked with an equal sign ("="). You can use an asterisk ("*") as a wild card by entering it as the first character. For example, entering "*X*" will find all names which contain "X". Atoll automatically begins searching and displays the results in the Find on Map window. 4. Select the object from the list. Atoll centres it in the map window.
1.9.3.2 Searching for a Map Object using Any Text Property You can use Find on Map to search for the following map object using any text (i.e., non-numeric) property: • • • • •
sites transmitters repeaters remote antennas vectors.
To search for a map object by a text property using the Find on Map tool: 1. Select Tools > Find on Map. The Find on Map window appears. 2. From the Find list, choose the map object you are searching for: • • • •
Site Transmitter Repeater/Rem. Antenna Vector
3. From the Field list, select the text property on which you want to search, for example, "Antenna," or "Main Propagation Model." 4. Enter the name of the object in the text box marked with an equal sign ("="). You can use an asterisk ("*") as a wild card by entering it as the first character. For example, entering "*X*" will find all names which contain "X". Atoll automatically begins searching and displays the results in the Find on Map window. 5. Select the object from the list. Atoll centres it in the map window.
1.9.3.3 Searching for a Point on the Map You can can use Find on Map to search for a point by its x and y coordinate. To search on the map for a point using Find on Map: 1. Select Tools > Find on Map. The Find on Map window appears. 2. From the Find list, choose Position. 3. Enter the X and Y coordinates of the point, using the same units as defined under Display on the Coordinates tab of the Preferences dialogue (see "Projection and Display Coordinate Systems" on page 120). 4. Click Find. Atoll centres the point in the map window.
1.9.4 Using the Status Bar to Get Information Atoll displays the following information, if available, about the current position of the mouse pointer in right side of the status bar (see Figure 1.48): • • • •
the current X-Y coordinates (according to the defined display coordinate system) the altitude (as defined in the DTM) the clutter class (as defined in the clutter classes properties) the clutter height (as defined in the clutter height file, or in the clutter classes).
109
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
© Forsk 2012
X-Y coordinates
Altitude
Clutter class
Figure 1.48: Information displayed in the status bar
1.9.5 Saving Information Displayed in the Event Viewer Atoll displays information about the current document in the Event Viewer. The Event Viewer displays information ( ), warning ( ), and error ( ) messages, as well as the progress of calculations. You can save the information displayed in the Event Viewer in a log file. To save events in the Event Viewer in a log file: 1. If the Event Viewer is not displayed, select View > Event Viewer to display it. 2. Click the event in the Event Viewer to select it. Click and drag to select several events. 3. Right-click the select event(s). The context menu appears. 4. Select Save As. The Save As dialogue appears. 5. In the Save As dialogue, select a destination folder, enter a File name, and select a file type from the Save as type list. 6. Click OK. The selected events are saved in the text file. You can also automatically generate log files for each Atoll session and select the level of information displayed in the Event viewer. For more information about these settings, see the Administrator Manual.
1.9.6 Using Icons from the Toolbar You can access many commands in Atoll by clicking its icon on the toolbar. Some of them are also linked to shortcut keys (see "Using Shortcuts in Atoll" on page 113). The different icons located in the toolbar are listed below: •
In the Standard toolbar Open the Project Templates dialogue (CTRL+N) Open the Open dialogue (CTRL+O) Save the current document (CTRL+S) New from an existing database Refresh from database Save pending changes in database Import a file Load a user configuration Save a user configuration Cut the selected data (CTRL+X) Copy the selected data (CTRL+C) Paste the content of the clipboard (CTRL+V) Undo the last modification (CTRL+Z)
110
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Redo the previous undone modification (CTRL+Y) Print the current window (table or map) (CTRL+P) Preview the current window before printing (table or map) Open the Atoll Help •
In the Radio Planning toolbar Station template currently selected Create a new transmitter or station based on the currently selected model Create a new group of hexagons based on the currently selected station template A new hexagon group is created in the Hexagonal Design folder if the check box to the left of this folder is selected when you create a new station or a group of stations. If the check box is not selected, you can create a new station without creating a corresponding hexagon group. Create a new repeater or remote antenna for the currently selected transmitter Graphically manage neighbours for the selected transmitter Open the Point Analysis window Calculate only invalid matrices, unlocked coverages, and pending simulations (F7) Force the calculation of all matrices, unlocked coverages, and pending simulations (CTRL+F7) Stop the calculation of all matrices, unlocked coverages, and pending simulations (ESC)
•
In the Map toolbar Refresh display of map and folders (F5) Select an object and disable zooming and panning tools. Move the map (CTRL+D) Map scale currently used Previous view (zoom and location) (Alt+left arrow) Next view (zoom and location) (Alt+right arrow) Zoom in or out on the map and centre on the cursor location (CTRL+Q) Define a zoom area on the map (CTRL+W) Display a height profile Measure distances on the map Turn on tip text Find on the map
•
In the Vector Editor toolbar Create a new vector layer (in either the Geo or the Network explorer) Select the vector layer to edit Draw a new polygon
111
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
Draw a new rectangle Draw a new line Draw points Combine several vector polygons Cut out areas in polygons Create new polygon from overlapping areas Split one polygon along the drawn lines. •
In the Windows toolbar Display the Network explorer Display the Geo explorer Display the Parameters explorer Display the Event Viewer Display the Legend Window Display the Panoramic Window
•
In the Table toolbar Import data from a file into the table Export data from the table to a file Display the properties of the current record Centre the current record on the map Define which columns should be displayed Hide the selected columns Freeze the selected columns Unfreeze all frozen columns Filter by the selected fields Filter excluding all records with the selected values Define an advanced filter Remove the filter Sort the selected columns in ascending order Sort the selected columns in descending order Display statistics Copy the contents of the top selected row into the rows below Copy the contents of the bottom selected row into the rows above Select the entire table Align the contents of the selected columns to the left
112
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
AT312_UM_E1
Centre the contents of the selected columns Align the contents of the selected columns to the right Display the selected columns in bold Display the selected columns in italics Find specified text in the table Replace specified text in the table When you place the cursor over an icon, tip text appears, giving a short description.
1.9.7 Using Shortcuts in Atoll Atoll provides many shortcuts that enable you to access commonly used tools and commands more quickly. The shortcuts available are listed below (some of the same commands can be accessed using a toolbar icon; see "Using Icons from the Toolbar" on page 110): •
Using the CTRL key: •
CTRL++: Zoom in on the map (in the toolbar, click
•
CTRL+–: Zoom out on the map (in the toolbar, click
•
CTRL+A: Select all records in a table
•
CTRL+C: Copy the selected data (in the toolbar, click
•
CTRL+D:
and click the map) and right-click the map)
)
•
In tables: Copy the first cell of a selection down into all selected cells
•
In the map window: Move the map in the map window (in the toolbar, click
)
•
CTRL+E: Export the table of the selected Sites or Transmitters folder or view to a text file. For more information, see "Exporting Tables to Text Files and Spreadsheets" on page 80.
•
CTRL+F: Open the Find on Map dialogue when the map is active. Find specified text in a table when a table is active (in the toolbar, click
).
•
CTRL+H: Replace specified text in a table (in the toolbar, click
)
•
CTRL+I: Import the table of the selected Sites or Transmitters folder or view from a text file. For more information, see "Importing Tables from Text Files" on page 82.
•
CTRL+N: Open the Project Templates dialogue (in the toolbar, click
•
CTRL+SHIFT+N: Create a new document from an existing database
•
CTRL+O: Open the Open dialogue (in the toolbar, click
)
•
CTRL+P: Print the current window (in the toolbar, click
)
•
CTRL+Q: Select Zoom In/Out tool (in the toolbar, click
)
)
•
CTRL+S: Save the current active document (in the toolbar, click
•
CTRL+U: Copy the last cell of a selection up into all selected cells
)
• CTRL+V: Paste the content of the clipboard (in the toolbar, click
)
•
CTRL+W: Define a zoom area on the map (in the toolbar, click
)
•
CTRL+X: Cut the selected data (in the toolbar, click
•
CTRL+Y: Redo the previous undone modification (in the toolbar, click
) )
113
Atoll 3.1.2 User Manual Chapter 1: The Working Environment
• •
•
© Forsk 2012
CTRL+Z: Undo the last modification (in the toolbar, click
)
Using the ALT key: •
ALT+←: Previous zoom and location on the map (in the toolbar, click
•
ALT+→: Next zoom and location on the map (in the toolbar, click
•
ALT+F8: Open the Add-ins and Macros dialogue
) )
Using the Function Keys •
F5: Refresh display of map and folders (toolbar: select
)
•
F7: Calculate only invalid matrices, unlocked coverages, and pending simulations (in the toolbar, click
•
CTRL+F7: Force the calculation of all matrices, unlocked coverages, and pending simulations (in the toolbar, click ) You can also access menus and commands by pressing the ALT key and typing the underlined letter in the menu or command name.
114
)
Chapter 2 Starting a Project This chapter explains how to start a new Atoll project.
In this chapter, the following are explained: •
"Before Starting a Radio-Planning Project" on page 117
•
"Creating an Atoll Document" on page 117
•
"Making a Backup of Your Document" on page 129
•
"Making and Sharing Portable Atoll Projects" on page 131
Atoll 3.1.2 User Manual Chapter 2: Starting a Project
116
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
AT312_UM_E1
2 Starting an Atoll Project When you want to start a new project, you base it on a template that has the data and folder structure necessary for the technology you are using. Once you have started your new Atoll project, you can modify the network parameters to meet your particular needs. Several templates are supplied with Atoll: GSM GPRS EDGE, CDMA200 1xRTT 1xEV-DO, microwave radio links, UMTS HSPA, WiMAX, Wi-Fi, and LTE. The actual templates supplied depend on the modules included with your Atoll installation. You can also create your own templates by opening an existing template, making the changes necessary to meet your own needs and then saving it as a new template. When you open an existing project, you can select it from the File menu if it is one of the last projects you have worked on, or you can open it from the Open dialogue. Because Atoll can work with linked geographic data files, it may happen that one of the linked files was moved or renamed since the last time you worked on that project. Atoll enables you to find the file and repair the link. In this chapter, the following are explained: • •
"Before Starting a Radio-Planning Project" on page 117 "Creating an Atoll Document" on page 117.
2.1 Before Starting a Radio-Planning Project For every radio-planning project you must assemble the information necessary: • • •
Radio equipment: sites, transmitters, antennas, repeaters, and other equipment. For more information on radio equipment, see the technology-specific chapters. Radio data: frequency bands, technology-specific parameters, coordinate systems, etc. For more information on radio data, see the technology-specific chapters. Geographic data: clutter classes, clutter heights, DTM, population maps, etc. For more information on geographic data, see Chapter 3: Geographic Data.
Once the necessary data have been assembled, you can create the Atoll document.
2.2 Creating an Atoll Document Whatever the radio technology you will be modelling, you create an Atoll document in one of two ways: •
From a document template: You can create a new Atoll document, including a multi-RAT document, from a template. Atoll is delivered with a template for each technology you will be planning for. For information on creating a document from a template, see "Creating a New Atoll Document from a Template" on page 117. You can also create your own template by basing it on an existing document that you have already customised with, for example, certain geo data or antennas.
•
From an existing database: When you create a new Atoll document from a database, the database you connect to has been created with the technology or technologies, in the case of a multi-RAT document, and data you need. Working with a database allows several users to share the same data while at the same time managing data consistency. The exact procedure for creating a new Atoll document from a database differs, depending on the database containing the data. Atoll can work with several common databases. For information on starting a document from a database, see "Creating a New Atoll Document from a Database" on page 123.
2.2.1 Creating a New Atoll Document from a Template You can create a new Atoll document from a template. Atoll has a template for each technology you will be planning for. Each template provides data and a data structure suitable for the technology. For example, the tables and fields for transmitters as well as the radio parameters available differ according to the project. As well, the objects that are available are appropriate for the technology. For example, UMTS cells are only available in UMTS documents and TRX are only available in GSM-TDMA documents. If you create a multi-RAT document, Atoll enables you to select the multiple radio technologies you will be planning for. In a multi-RAT document, the data and data structures for each radio technology planned for are made available in the new Atoll document. Once you have selected the appropriate template for your radio-planning project, you configure the basic parameters of the Atoll document (see "Defining a New Atoll Document" on page 120). In this section, the following are explained: • •
"Templates Available" on page 118 "Creating a New Atoll Document from a Template" on page 118
117
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
•
© Forsk 2012
"Defining a New Atoll Document" on page 120
2.2.1.1 Templates Available Depending on your configuration of Atoll, the following templates are available: •
•
GSM GPRS EDGE: This template can be used to model second generation (2G) mobile telecommunications using TDMA (Time Division Multiple Access) technology. This template can be used to model the following technologies: •
GSM (Global System for Mobile Communication): GSM is a 2G technology based on TDMA.
•
GPRS (General Packet Radio Service): GPRS is a packet-switched technology that enables data applications on GSM networks. It is considered a 2.5G technology.
•
EDGE (Enhanced Data for Global Evolution): EDGE is an advancement for GSM/GPRS networks that triples data rates. Because it is based on existing GSM technology, it allows for a smooth upgrade for GSM operators, giving them capabilities approaching those of a 3G network, while remaining with the existing 2G system. Two types of EDGE are considered: standard EDGE (also called EGPRS) and EDGE Evolution (EGPRS2).
CDMA2000 1xRTT 1xEV-DO: This template can be used to model third generation (3G) mobile telecommunications based on CDMA2000 technology. CDMA2000 is an evolution of CDMA, or code division multiple access. This template can be used to model the following technologies: •
•
1xRTT (1x Radio Transmission Technology): 1xRTT is sometimes considered not as 3G but as 2.5G in terms of mobile telecommunications. It offers increased voice capacity as compared to 2G technologies, but not as much as pure 3G solutions. 1xEV-DO (1x Evolution - Data Only): 1xEV-DO is an evolution of CDMA2000 that provides data transfer rates of over 10 times those of 1xRTT. It is considered a 3G solution and addresses, as its name suggests, data only.
•
UMTS HSPA: UMTS (Universal Mobile Telecommunications System) and HSDPA (High Speed Downlink Packet Access) and HSUPA (High Speed Uplink Packet Access), collectively referred to as HSPA, are third generation (3G) mobile telecommunication systems based on WCDMA (Wideband Code Division Multiple Access) technology. Although WCDMA is similar in implementation to CDMA, the two technologies are incompatible. UMTS and HSPA are usually implemented in place and over GSM networks.
•
TD-SCDMA: TD-SCDMA (Time Division Synchronous CDMA) is a 3G mobile telecommunication system based on Time Division Duplex (TDD) mode. TD-SCDMA transmits uplink and downlink traffic in the same frame in different time slots.
•
WiMAX: Atoll WiMAX is a state-of-the-art WiMAX and Broadband Wireless Access (BWA) network planning tool developed in cooperation with world-leading WiMAX equipment suppliers. Atoll WiMAX supports IEEE 802.16e.
•
Wi-Fi: Atoll Wi-Fi enables modelling of IEEE 802.11 wireless local area networks (WLAN) and to study mobile traffic offloading to Wi-Fi networks.
•
LTE: This template can be used to model the new fourth generation (4G) networks based on the UTRAN LTE (UMTS Terrestrial Radio Access Networks’ Long Term Evolution) specifications proposed by the 3GPP. Atoll LTE strictly follows the latest 3GPP LTE specifications, and has been developed in collaboration with the market-leading equipment manufacturers. Atoll LTE is the first and most comprehensive LTE network planning tool available on the market.
•
3GPP Multi-RAT: This template can be used to model the most common multi-technology projects. When starting a new 3GPP multi-RAT project, Atoll allows you to select which radio technologies will be modelled in the same project: GSM, UMTS, and LTE. The multi-RAT template can also be used to create a GSM, UMTS, or LTE single-RAT document. By using the multi-RAT template to create a single-RAT document, you will have the flexibility of being able to add additional technologies to the document in the future.
2.2.1.2 Creating a New Atoll Document from a Template To create a new document from a template: 1. Select File > New > From a Document Template. The Project Templates dialogue appears. 2. Select the template on which you want to base your document and click OK. Atoll creates a new document based on the template selected. •
If the template you selected was "Multi-RAT," Atoll displays a dialogue enabling you to select the radio technologies you want to model in the new document: GSM, UMTS, or LTE.
Figure 2.1 shows a new Atoll document based on the UMTS HSPA template. The Network explorer now has a folder structure suitable for a UMTS HSPA radio-planning project, with, among other UMTS-specific elements, UMTS HSPA HSPA simulations. Figure 2.2 shows the contents of the Geo explorer of the new document. Figure 2.3 shows the contents of the Parameters
118
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
AT312_UM_E1
explorer, with other UMTS HSPA parameters. The Antennas folder is expanded to show the UMTS-compatible antennas suggested by Atoll. These can be modified or replaced.
Figure 2.1: New Atoll document based on a template
Figure 2.2: New Atoll document — Geo explorer
Figure 2.3: New Atoll document — Parameters explorer
When you create an Atoll document from a template, the document is not connected to a database. To verify whether the document is connected to a database: •
Select Document > Database > Connection Properties. The dialogue in Figure 2.4 appears.
Figure 2.4: An Atoll document based on a template is not connected to a database
119
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
© Forsk 2012
2.2.1.3 Defining a New Atoll Document Once you have created a new Atoll document as explained in "Creating a New Atoll Document from a Template" on page 118, you configure the basic parameters of the Atoll document. You can accept the default values for some parameters, such as basic measurement units, but you must set projection and display coordinate systems. In this section, the following are explained: • • • •
2.2.1.3.1
"Projection and Display Coordinate Systems" on page 120 "Setting a Coordinate System" on page 121 "Selecting the Degree Display Format" on page 121 "Setting Measurement Units" on page 122
Projection and Display Coordinate Systems In Atoll, you define the two coordinate systems for each Atoll document: the projection coordinate system and the display coordinate system. By default, the same coordinate system is used for both. A projection is a method for producing all or part of a round body on a flat sheet. This projection cannot be done without distortion, thus the cartographer must choose the characteristic (distance, direction, scale, area or shape) which is to be shown appropriately at the expense of the other characteristics, or he must compromise on several characteristics1. The projected zones are referenced using cartographic coordinates (meter, yard, etc.). Two projection systems are widely used: •
•
The Lambert Conformal-Conic projection: a portion of the earth is mathematically projected on a cone conceptually secant at one or two standard parallels. This projection type is useful for representing countries or regions that lay primarily east to west. The Universal Transverse Mercator projection (UTM): a portion of the earth is mathematically projected on a cylinder tangent to a meridian (which is transverse or crosswise to the equator). This projection type is useful for mapping large areas that are oriented north-south.
A geographic system is not a projection, but a representation of a location on the earth's surface from geographic coordinates (degree-minute-second or grade) giving the latitude and longitude in relation to the origin meridian (Paris for the NTF system and Greenwich for the ED50 system). The locations in the geographic system can be converted into other projections. Atoll has databases including more than 980 international coordinate system references, a database based on the European Petroleum Survey Group and another one regrouping only France's coordinate systems. Atoll uses the cartographic coordinate systems for projection and either cartographic or geographic coordinate systems for display. The maps displayed in the workspace are referenced with the same projection system as the imported geographic data files; thus, the projection system depends on the imported geographic file. By choosing a specific display system, you can see (using the rulers or status bars) the location of sites on the map in a coordinate system different from the projection coordinate system. You can also position on the map sites referenced in the display system: the coordinates are automatically converted from the projection system to the display system and the site is displayed on the map. In Figure 2.5, the Brussels geographic data file has been imported. The map shows Brussels projected using the cartographic UTM system (coordinates in metres). On the other hand, site coordinates are stated in the geographic WGS 84 system (coordinates in degrees-minutes-seconds).
1. Snyder, John. P., Map Projections Used by the US Geological Survey, 2nd Edition, United States Government Printing Office, Washington, D.C., 313 pages, 1982.
120
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
AT312_UM_E1
Figure 2.5: UTM system used with WGS 84 system All imported raster geographic files must be use the same cartographic system. If not, you must convert them to a single cartographic system.
2.2.1.3.2
Setting a Coordinate System Because you are working with maps, you must set a coordinate system for your Atoll document. By default, projection and display coordinate systems are the same, but you can choose a different display coordinate system if you want. To define the coordinate system: 1. Select Document > Properties. The Properties dialogue appears. 2. On the Coordinates tab, click the Browse button ( dialogue appears.
) to the right of the Projection field. The Coordinate Systems
3. In the Coordinate Systems dialogue, select a catalogue from the Find in list. For the projection system, only cartographic systems ( ) are available. 4. Select a coordinate system from the list. If you frequently use a particular coordinate system you can add it to a catalogue of favourites by clicking Add to Favourites.
5. Click OK. The selected coordinate system appears in the Projection field and, by default, in the Display field as well. 6. If you wish to set a different coordinate system for the display, click the Browse button (
) to the right of the
Display field and repeat step 3. to step 5. For the display system, both cartographic systems (identified by the symbol) and geographic systems (
2.2.1.3.3
) are available.
Selecting the Degree Display Format Atoll can display longitude and latitude in four different formats. For example: • • • •
26°56’29.9’’N 26d56m29.9sN 26.93914N +26.93914
To change the degree display format: 1. Select Document > Properties. The Properties dialogue appears. 2. On the Coordinates tab, select the format from the Degree Format list. 3. Click OK.
121
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
© Forsk 2012
The degree format options apply only to the geographic coordinate systems.
2.2.1.3.4
Setting Measurement Units When you create a new Atoll document, Atoll sets certain measurement units for reception, transmission, antenna gain, distance, height and offset to internal defaults. You can accept these default measurement units, or you can change them using the Properties dialogue. To set the measurement units: 1. Select Document > Properties. The Properties dialogue appears. 2. On the Units tab, select the desired unit for the following measurements: •
Radio: • • • •
•
Geo: • •
•
Radiated power: Select either "EIRP" (Effective Isotropically Radiated Power) or "ERP" () Antenna gain: Select either "dBi" (decibel (isotropic)) or "dBd" (decibel (dipole)) Transmission: Select either "dBm" (decibel (milliWatt)), "W" (Watt), or "kW" (kiloWatt) Reception: Select either "dBm" (decibel (milliWatt)), "dBµV" (decibel (microvolt)), "dBµV/M" (decibel (microvolt per metre)), or "V/M" (volts per metre) Distance: Select either "m" (metres), "Km" (kilometres), or "mi" (miles) Height and offset: Select either "m" (metres) or "ft" (feet)
Climate: •
Temperature: Select either "°C" (Celsius) or "°F" (Fahrenheit)
3. Click OK.
2.2.2 Working in a Multi-User Environment A multi-user environment is one where a number of users, or groups of users, work simultaneously on given parts of a single, large (perhaps nation-wide) network. Different user groups might be working on regional or smaller sections of the network. This section describes the different components of multi-user environments and outlines their purpose. When you create a new Atoll document from a database, Atoll loads the data to which you have rights from database into your new document and then disconnects it from the database. The connection to the reference database is reactivated only when necessary, thus ensuring access to the database by other users. When you work on a document created from a database, you are working on data that you are sharing with other users. Consequently, there are issues related to sharing data that do not arise when you are working on a stand-alone document. For example, when you archive your changes to the database, the changes you have made may occasionally interfere with changes other users have made and you will need to resolve this conflict. In this section, the following are explained: • • • • •
"The Atoll Multi-User Environment" on page 122 "Creating a New Atoll Document from a Database" on page 123 "Working With a Document on a Database" on page 124 "Refreshing an Atoll Document from the Database" on page 126 "Archiving the Modifications of an Atoll Document in the Database" on page 126.
2.2.2.1 The Atoll Multi-User Environment An Atoll multi-user environment consists of the following elements, connected over a network: •
A central Atoll project: The central Atoll project can only be accessed, modified, and updated by the Atoll administrator. Through this central Atoll project, the Atoll administrator can manage all the data shared by all the individual Atoll users or groups of users.
•
Shared data: Shared data are initially set up by the administrator using the central Atoll project and are then accessed, modified, worked on, and updated by the Atoll users and the administrator. The shared data are mainly of the following three types: •
122
The central database: The central database stores all the radio data of all the Atoll user documents. It is initiated through the central Atoll project by the administrator, and is then subdivided into sections on which users or groups of users can work simultaneously. Once the database is in place, users can modify their projects, refresh their projects from the data stored in the database, and archive their modifications in the database. The use of a database means that potential data conflicts due to modifications from other users, modified or deleted records, for example, can be detected and resolved.
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
AT312_UM_E1
•
Shared geographic data: Shared geographic data files are usually stored on a common file server with a fast access connection. Since geographic data files are usually large, they are usually linked to an Atoll file, i.e., they are stored externally, so as to minimise the size of the Atoll file. Users who modify geographic data locally, for example, editing edit clutter or traffic in their respective projects, usually store these modifications locally, since these modifications rarely have an impact on other users.
•
Path loss matrices: The path loss matrices are calculated through the central Atoll project by the administrator and can be updated only by the administrator. Each user can read these path loss data but cannot modify them. If users modify their Atoll documents in such a way that the path loss data becomes invalid for their document, any path loss matrices calculated by these users are stored locally, either embedded in the ATL file or linked to an external file. The shared path loss data are not modified. Shared path loss matrices are updated when the calculation administrator performs an update, taking into account the modifications made by other users which have been stored and updated in the central database. Shared path loss matrices enable a number of users to work with a centralised path loss matrices folder, containing path loss matrices corresponding to the central Atoll project.
•
User Documents: Individual user documents are initialised by the administrator but are later worked upon and managed by each user. User documents are Atoll files which are connected to the central database, load only the required part of the geographic data (as defined by the CFG file, for example), and have access to the shared path loss matrices folder.
Figure 2.6: Components of Multi-user Environments For information on creating and maintaining the database, see the Administrator Manual.
2.2.2.2 Creating a New Atoll Document from a Database When you create a new document from a database, you must connect to the database. Once connected, Atoll loads the database into a new Atoll document. Then the connected is interrupted. A new connection with the database will be created only when necessary, in order to allow other users access to the database. The exact procedure of connecting with the database differs from one database to another. Atoll can work with the following databases: • • •
Microsoft Access Microsoft SQL Server Oracle
123
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
• •
© Forsk 2012
Sybase Microsoft Data Link files
The following sections give examples of connecting to two different databases and loading data: • •
"Connecting to a Database" on page 124. "Selecting the Data to Load From the Database" on page 124.
An example of a new Atoll document created from a database is shown in: •
2.2.2.2.1
"Working With a Document on a Database" on page 124
Connecting to a Database To create a new document from a database: 1. Select File > New > From an Existing Database. The Open from a Database dialogue appears. 2. In the Files of type list, select the option corresponding to the type of your database. Depending on the type of the database, a dialogue may appear where you can enter your User Name, Password, and Server. •
•
By setting an option in the atoll.ini file, you can instruct Atoll to always use a defined database type (MS Access, SQL Server, or Oracle). The Open from a Database dialogue will not appear. Instead the database-specific authentication dialogue will appear immediately. For more information, see the Administrator Manual. Additional dialogues might open asking you to choose which project in the database to load or which site list to load.
3. Click OK. The Data to Load 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 124).
2.2.2.2.2
Selecting the Data to Load From the Database When you create a new document from a database, you can select the data to be loaded from the database to create the document in the Data to load dialogue. You can select which Project, Site List, Custom Fields Groups, and Neighbours to load. If you load the intra-technology or the inter-technology neighbour list, Atoll will also load the associated exceptional pairs table.
Figure 2.7: Selecting the data to load
2.2.2.3 Working With a Document on a Database Figure 2.8 shows a new Atoll document based created from a database. The Network explorer now has a folder structure suitable for a UMTS radio-planning project. The Sites folder is expanded to show that a document created from a database can have additional data, such as sites, unlike a document created from a template. These can be modified or replaced. Figure 2.9 and Figure 2.10 show the contents of the Geo and Parameters tabs of the new document, respectively.
124
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
AT312_UM_E1
Figure 2.8: New Atoll document opened from a database The new document might open with no site displayed in the map window. This is because the north-west point of the project is by default the axis origin. You can re-centre the document on the data displayed in the Network explorer by expanding the Sites folder, rightclicking any site, and selecting Centre in Map Window from the context menu.
Figure 2.9: New Atoll document — Geo explorer
Figure 2.10: New Atoll document — Parameters explorer
When you create an Atoll document from a database, you can view the characteristics of the database connection. To view the characteristics of the database connection: 1. Select Document > Database > Connection Properties. The Database Connection dialogue appears (see Figure 2.11). 2. You can now: •
Disconnect your document from the database. If you disconnect your document from the database, it will be become a stand-alone document and you will not be able to reconnect it to the database.
•
Modify your connection to the database.
125
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
© Forsk 2012
Figure 2.11: The Database Connection dialogue
2.2.2.4 Refreshing an Atoll Document from the Database As you are working on your document, other users who have access to the database may have modified some of the data. You can ensure that you have the most recent data in your document by refreshing the information from the database. How frequently you refresh the document depends on how frequently the database is updated. If the database is updated frequently, you should refresh your document frequently as well, in order to continue working with the most up-to-date data. To refresh an Atoll document from the database: 1. Select Document > Database > Refresh From the Database. The Refresh dialogue appears. 2. In the dialogue, you can do one of the following if you have modified your document but have not yet saved those changes in the database: • • •
Archive your changes in the database: This option allows you to archive your changes to the server instead of refreshing your document from the server. Refresh unmodified data only: This option allows you to refresh from the database only those items that you have not modified in your document. Cancel your changes and reload database: This option allows you to cancel any changes you have made and start over from the point of the last archive to the database. • •
If you chose Refresh unmodified data only or Cancel your changes and reload database, Atoll proceeds without asking for confirmation. If you chose Archive your changes in the database, the Archive dialogue appears. For information on using the Archive dialogue, see "Archiving the Modifications of an Atoll Document in the Database" on page 126.
3. Under Take into account, you can select the neighbour lists, Intra-technology Neighbours and Inter-technology Neighbours, to refresh. 4. Under Modifications Since the Last Refresh, you can select the Generate Report check box to create a report for the refresh process. 5. Click OK. The document is refreshed according to the selected options. If you selected to generate a report, Atoll creates a text file in CSV (Comma Separated Values) format in the temporary files system folder, and opens it. You can then rename the file and save it where you want. The report lists all the modifications (deletions, additions, and updates) that were stored in the database since the last time you refreshed or opened your document.
2.2.2.5 Archiving the Modifications of an Atoll Document in the Database When you are working on an Atoll document that is attached to a database, you should from time to time archive the modifications you have made to the data on the database. How frequently you should archive your document depends on several factors: the amount and size of changes you make, the number of other users using the database who might benefit from your modifications, etc. What you can archive depends on the user rights the database administrator has given to you. For example, you can have read access to the antennas table, allowing you to create a new Atoll document with the given antennas. However, because only the administrator can modify the properties of the antennas, you will not be able to archive any changes you make to the antennas without write access to the table. The Atoll archiving process is flexible. You can archive all your modifications or only the site-related modifications. As well, when you are archiving, Atoll shows you all modifications that will be archived and, if you want, you can archive only some of them or even undo modifications you have made locally. Occasionally, other users might have modified some of the same data and, when you archive your changes, Atoll will inform you of the possible conflicts and help you resolve them. In this section, the following are explained: • • •
126
"Archiving All Modifications in the Database" on page 127 "Archiving Only Site-Related Data in the Database" on page 127 "Resolving Data Conflicts" on page 127.
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
AT312_UM_E1
2.2.2.5.1
Archiving All Modifications in the Database To archive all your modifications in the database: 1. Select Document > Database > Archive. The Archive dialogue appears (see Figure 2.12). 2. In the Archive dialogue, you can do the following: • • • •
Click Run All to archive all your changes to the database. Select one item under Pending changes and click Run to archive the selected modification to the database Select one item under Pending changes and click Differences to view the differences between the local item and the item on the database. Select one item under Pending changes and click Undo to refresh the modification with the original data from the database.
Figure 2.12: The Archive dialogue 3. If some of the data has been modified on the database since you last refreshed, Atoll stops the archiving process and asks you to resolve the conflict. For information on managing conflicts, see "Resolving Data Conflicts" on page 127. 4. When you are finished archiving, click Close.
2.2.2.5.2
Archiving Only Site-Related Data in the Database Atoll allows you to archive only site-related data if you want. Which data is archived depends on the radio technology you are working with. For example, in a UMTS HSPA radio planning project, the site-related data are: sites, transmitters, cells, and neighbours. To archive only the site-related data in the database: 1. Select the Network explorer. 2. Right-click the Sites folder. The context menu appears. 3. Select Archive. The Archive dialogue appears with only site-related data displayed. 4. In the Archive dialogue, you can do the following: • • • •
Click Run All to archive all your changes to the database. Select one item under Pending Changes and click Run to archive the selected modification to the database Select one item under Pending Changes and click Differences to view the differences between the local item and the item on the database. Select one item under Pending Changes and click Undo to refresh the modification with the original data from the database.
5. If some of the data has been modified on the database since you last refreshed, Atoll stops the archiving process and asks you to resolve the conflict. For information on managing conflicts, see "Resolving Data Conflicts" on page 127. 6. When you are finished archiving, click Close.
2.2.2.5.3
Resolving Data Conflicts Atoll enables several users to use the same database by allowing user to load the data and then freeing the database for other users. However, this also creates the possibility of two users modifying the same data. When the second user attempts to archive his changes, Atoll warns him that the data have been changed since he last refreshed the data and that there is a conflict. Atoll allows you to resolve data conflicts. When Atoll finds a conflict, it displays the warning shown in Figure 2.13.
127
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
© Forsk 2012
Figure 2.13: Conflict warning You have three options: •
• •
Ignore: If you click Ignore, Atoll ignores items causing conflicts in the table being archived, archives all other modifications in the table, and continues with the next table. You can resolve the conflicts after the archiving process has ended. However, if conflicts are found in other tables, Atoll will warn you with the Database Transfer Error dialogue again. Ignore All: If you click Ignore All, Atoll ignores all items causing conflicts in all tables being archived, and archives all other modifications. You can resolve the conflicts after the archiving process has ended. Abort: If you click Abort, the archiving process stops. You can attempt to resolve conflicts before restarting the archiving process.
Whether you abort the archive process to resolve the conflict immediately, or wait until the end of the archive process, the procedure to resolve the conflict is the same. To resolve data conflicts one by one: 1. In the Pending Changes pane of the Archive dialogue, select the conflict you want to resolve and click Resolve. There are two different types of data conflicts: •
On a modified record: You are in the process of archiving your modifications on the database and another user has modified the same data since you last archived or refreshed your data. A conflict is caused only by differences in the same field of the same record between the database and the current Atoll document. The Conflict in Changes dialogue appears, with the fields in conflict highlighted (see Figure 2.14). In the Conflict in Changes dialogue, you can see the value of the field in the database in the Database values column, as well as the value of the same field in your document in the Current values column.
Figure 2.14: The Conflict in Changes dialogue
•
•
If you want to overwrite the database value with the value of the same field in your document, select the check box next to the highlighted change and click Okay. Your modification will be written to the database, overwriting the value there.
•
If you want to accept the value of the field in the database, clear the check box next to the highlighted change and click Okay. Your modification will be lost and the value in the database will remain unchanged.
On a deleted record: You are in the process of archiving your modifications on the database and another user has deleted a record since you last archived or refreshed your data. For information, see "Resolving Data Conflicts" on page 127. Atoll displays a message explaining that the record you are trying to update has been deleted from the database (see Figure 2.15). Select one of the following:
128
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
AT312_UM_E1
Figure 2.15: Conflict on a deleted record • • •
Yes: Select Yes to store your modifications in the database, thereby recreating the deleted record. No: Select No to abandon your modifications to this record and delete this record from your document. Cancel: Select Cancel to cancel.
2. Click Close to close the Archive dialogue. To resolve all the data conflicts: 1. In the Pending Changes pane of the Archive dialogue, select any conflict and click Resolve All. Atoll displays a message explaining how Resolve All works (see Figure 2.16). Select one of the following:
Figure 2.16: Resolving all the data conflicts simultaneously • • •
Yes: Select Yes to accept all the modifications made by other users in the database and update your document with values from the database. No: Select No to overwrite the modifications made by other users in the database with the values from your document. Cancel: Select Cancel to cancel.
2. Click Close to close the Archive dialogue. You should only resolve all the data conflicts when you are certain about the modifications.
2.3 Making a Backup of Your Document Atoll can create and automatically update backups of documents you are working on. Once you have saved the document, Atoll creates a backup of the original document and updates it at a defined interval. For example, for a document named "filename.atl," Atoll will create a backup file called "filename.atl.bak" in the same folder as the original document. You can define the update interval each time you start Atoll. You can also configure Atoll to create automatic backups of external path loss matrices (LOS files) by setting an option in the atoll.ini file. For more information, see the Administrator Manual. When you have activated automatic backup, Atoll automatically creates a backup for every document open. Consequently, if you have a lot of documents open, this operation can take a long time. However, you can optimise the process by opening large documents in separate Atoll sessions, instead of in the same Atoll session. This also improves memory management because each instance of Atoll has its own 2 GB (under 32-bit operating systems; 4 GB under 64-bit operating systems) memory allocation. If you open two large documents in the same Atoll session, these documents will use the same 2 GB memory pool. If you open them in two different Atoll sessions, each document will have its own 2 GB allocated memory. In this section, the following are explained: • •
"Configuring Automatic Backup" on page 130 "Recovering a Backup" on page 130.
129
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
© Forsk 2012
2.3.1 Configuring Automatic Backup You can set up automatic backup for each Atoll session. To configure automatic backup: 1. Select Tools > Configure Auto Backup. The Auto Backup Configuration dialogue appears (see Figure 2.17).
Figure 2.17: Auto Backup Configuration dialogue 2. Select the Activate Auto Backup check box. 3. Select the Prompt before starting Auto Backup check box if you want Atoll to ask you before saving the backup of your file every time (see Figure 2.18). 4. Enter a time interval, in minutes, between consecutive backups in the Automatically save backups every text box. It can take a long time to back up large documents. Therefore, you should set a correspondingly longer interval between backups when working with large documents in order to optimise the process. 5. Click OK. If you selected the Prompt before starting automatic backup check box, Atoll prompts you each time before backing up the document. If you click OK, Atoll proceeds to back up all open documents. If you click Cancel, Atoll skips the backup once.
Figure 2.18: Automatic backup prompt The automatic backup timer is stopped while the prompt is displayed. Atoll displays a message in the Event Viewer every time a backup file is updated. If you are performing calculations, i.e., coverage predictions or simulations, the automatic backup is delayed until the calculations have ended. The timer starts again once the calculations are over. If you save the original document manually, the timer is reset to 0.
2.3.2 Recovering a Backup You can easily recover your backup document and open it in Atoll just like any other Atoll document. To recover your backup document: 1. Using Windows Explorer, navigate to the folder containing your original Atoll document and its backup. 2. If the original document was named "filename.atl," the backup document will be in the same folder and will be called "filename.atl.bak". Rename the document and remove the BAK extension. For example, you could change the name to "filename-backup.atl." 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.
130
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
AT312_UM_E1
3. Open the renamed backup document in Atoll. You will be able to recover all the work up to the last time the backup was saved.
2.4 Making and Sharing Portable Atoll Projects You can create portable Atoll documents in two ways: • •
by embedding all the geographic data in the ATL file, or by creating a compressed archive (ZIP file) containing the ATL file and all geographic data linked to the Atoll document.
In most working environments, geographic data files are stored on a common file server and are linked to the ATL documents of different users over a network. Often these geographic data files are quite large, and it is not feasible to embed these files in an ATL file for reasons related to file size, memory consumption, and performance. It is, therefore, more useful to make a project portable by creating an archive that contains the ATL and all geographic data files. Atoll lets you make an archive containing the ATL file and all geographic data directly from the File menu. To make an archive containing the ATL file and all linked geographic data files: 1. Select File > Save to Zip. The Save As dialogue appears. 2. Select the folder where the created archive is to be stored, enter a File name for the archive to be created, and select "Zip Files (*.zip)" from the Save as type list. Atoll creates a ZIP file containing: •
A copy of the ATL file with the same name as the name of the archive (ZIP file). The ATL file added to the archive contains all the data that might be embedded in it (path loss matrices, geographic data, coverage predictions, simulation results, measurement data, etc.).
•
A ".losses" folder containing a pathloss.dbf file and a LowRes subfolder which contains the pathloss.dbf file corresponding to the extended path loss matrices. Externally stored path loss matrices are not added to the archive because they are not necessary for making a portable document; they can be recalculated based on the network and geographic data in the ATL file. The pathloss.dbf files are stored in the archive because they are needed when reopening the archive in Atoll.
•
A "Geo" folder with all the linked geographic data available in the Geo explorer for the Atoll document. This folder contains subfolders with the same names as the folders in the Geo explorer. Geographic data that are found outside folders in the Geo explorer are stored in files under the Geo folder, and data present within folders in the Geo explorer are stored inside their respective folders. If the geographic data files linked to the document are located on a remote computer, such as a file server over a network, they are first copied to the local computer in the Windows’ temporary files folder and then added to the archive.
Once the portable archive is created, you can open it directly from Atoll without first having to extract it using another tool. To open an archive containing an ATL file and all linked geographic data files: 1. Select File > Open from Zip. The Open dialogue appears. 2. Select the ZIP file that contains the ATL file and linked geographic data files. 3. Click Open. The Browse For Folder dialogue appears. 4. Select the folder where you want to extract the contents of the ZIP file. 5. Click OK. Atoll extracts all the files from the archive to the selected folder. If necessary, it creates the subfolders required for extracting the contents of the Geo folder. Once Atoll has finished extracting files from the archive, it opens the extracted ATL file. Geographic data extracted from the archive are linked to the ATL file. • •
You do not need to have a compression utility, such as WinZip or WinRAR, installed on the computer when working with archived ATL files. The highest compression level is used when creating the archive.
131
Atoll 3.1.2 User Manual Chapter 2: Starting an Atoll Project
132
© Forsk 2012
Chapter 3 Geographic Data This chapter provides information on working with geographic data in an Atoll project.
In this chapter, the following are explained: •
"Geographic Data Types" on page 135
•
"Supported Geographic Data Formats" on page 137
•
"Importing Geo Data Files" on page 137
•
"Digital Terrain Models" on page 144
•
"Clutter Classes" on page 144
•
"Clutter Heights" on page 148
•
"Contours, Lines, and Points" on page 148
•
"Scanned Images" on page 150
•
"Population Maps" on page 151
•
"Custom Geo Data Maps" on page 152
•
"Setting the Priority of Geo Data" on page 155
•
"Displaying Information About Geo Data" on page 158
•
"Geographic Data Sets" on page 158
•
"Editing Geographic Data" on page 160
•
"Saving Geographic Data" on page 162
Atoll 3.1.2 User Manual Chapter 3: Starting a Project
134
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
3 Geographic Data Several different geographic data types are used in an Atoll document. For example: the digital terrain model (DTM), clutter classes, clutter heights, scanned images, population maps, and traffic data maps are types of the geographic data that you can import or create. Some data types, such as clutter classes, can be used to give more realistic calculations. Other types such as scanned images, are used to create a more realistic display of the region under study. You can import a wide variety of both vector and raster-format geo data files. When you import a geo data file into Atoll, you can decide in which folder it goes. The Geo explorer of the Atoll Explorer window has folders for the commonly used data types. Therefore, choosing a folder is choosing what the file will be used for. You can also create your own data type by importing a file and defining what data is to be used. Once you have imported a file into the Atoll document, you can edit the data, define how the geo data will be displayed. Atoll also allows you to manage multiple files for a single data type, deciding the priority of data files with different information or different resolutions. You can also display geo data over items in the Network explorer, either by transferring them to the Network explorer, or by importing them directly to the Network explorer. You can also create and edit geographic data. You can add a vector layer to certain data types to which you can add contours, lines, or points, create new geographic data, or modify existing data. You can also create raster-based geographic data such as traffic maps or clutter classes. You can export most geo data objects (for example, DTM, clutter classes, clutter heights, raster polygons, or vector layers) for use in other Atoll documents or in other applications. Atoll also allows you to save changes you make to geo data objects back to the original files. This enables you to update the original files and, through the process of saving them, recompact the file. This chapter explains the following topics: • • • • • • • • • • • • •
"Geographic Data Types" on page 135 "Supported Geographic Data Formats" on page 137 "Importing Geo Data Files" on page 137 "Clutter Classes" on page 144 "Clutter Heights" on page 148 "Digital Terrain Models" on page 144 "Contours, Lines, and Points" on page 148 "Scanned Images" on page 150 "Population Maps" on page 151 "Custom Geo Data Maps" on page 152 "Setting the Priority of Geo Data" on page 155 "Editing Geographic Data" on page 160 "Saving Geographic Data" on page 162.
3.1 Geographic Data Types An Atoll document can contain several different geographic data types. Atoll supports a wide range of file formats for geographic data files. The different geographic data types play different roles in the Atoll document: •
Geographic data used in propagation calculation: • • •
•
Geographic data used in dimensioning: •
•
Traffic maps
Geographic data used in statistics: • •
•
Digital terrain model Clutter classes Clutter heights
Population maps Custom maps
Geographic data used for display purposes: • • •
Scanned maps Images from web map services (WMS) Contours, lines, and points representing, for example, roads, railways, or regions.
In this section, the following data types are described: • • • •
"Digital Terrain Model" on page 136 "Clutter Classes" on page 136 "Clutter Heights" on page 136 "Contours, Lines, and Points" on page 136
135
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
• • • •
© Forsk 2012
"Scanned Images" on page 136 "Population Maps" on page 136 "Traffic Data Maps" on page 136 "Custom Data Maps" on page 136.
Digital Terrain Model The DTM describes the elevation of the ground over sea level. You can display the DTM in different ways: by single value, discrete values, or by value intervals (see "Display Properties of Objects" on page 43). The DTM is automatically taken into account by the propagation model during computations. Clutter Classes The clutter class geo data file describes land cover or land use. Clutter classes are taken into account by the propagation model during computations. Each pixel in a clutter class file contains a code (from a maximum of 256 possible classes) which corresponds to a clutter class, or in other words to a certain type of ground use or cover. The height per class can be defined as part of the clutter class, however, the height will be defined as an average height for each clutter class. For information on defining the height per clutter class, see "Defining Clutter Class Properties" on page 145. Clutter heights can also be defined by a separate clutter heights file (see "Clutter Heights" on page 136). 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 43). The only propagation models that can take clutter heights into account in calculations are the Standard Propagation Model and WLL model.
Contours, Lines, and Points Atoll supports contours, lines, and points to represent polygons such as regions, or lines such as roads or coastlines, or points. They are used for display only and have no effect on computations. Contours can also be used to create filtering polygons or computation or focus zones. Scanned Images Scanned images are geographic data files which represent the actual physical surroundings, for example, road maps or satellite images. They are used to provide a precise background for other objects or for less precise maps and are used only for display; they have no effect on calculations. Population Maps Population maps contain information on population density or on the total number of inhabitants. Population maps can be used in prediction reports in order to display, for example, the absolute and relative numbers of the population covered. Population maps have no effect on prediction and simulation results. Traffic Data Maps Traffic data maps contain information on capacity and service use per geographic area. Traffic data maps are used for network capacity analyses. Custom Data Maps You can import many different types of files for, for example, revenue, rainfall, or socio-demographic data. You could use the imported data in prediction reports. For example, you could display the predicted revenue for defined coverage. These imported data have no effect on prediction and simulation results.
136
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
3.2 Supported Geographic Data Formats Atoll supports the following geographic data formats: •
•
• • • •
• •
DTM files in the following formats: TIF (8 or 16-bit integer), BIL (8, 16 or 32-bit integer, 32-bit float), Planet (16-bit integer), BMP (8-bit integer), GRD Vertical Mapper (16-bit integer), and Erdas Imagine (8, 16 or 32-bit integer, 32-bit float) Clutter height files in the following formats: TIF (8 or 16-bit integer), BIL (8, 16 or 32-bit integer, 32-bit float), Planet (16-bit integer), BMP (8-bit integer), GRD Vertical Mapper (16-bit integer), and Erdas Imagine (8, 16 or 32-bit integer, 32-bit float) Clutter class and traffic files in the following formats: TIF (8-bit), BIL (8-bit), IST (8-bit), BMP (8-bit), Planet, GRC Vertical Mapper (8-bit), and Erdas Imagine (8-bit) Vector data files in the following formats: AGD, DXF, Planet, SHP, MIF, and TAB. Vector traffic files in the following formats: AGD, DXF, Planet, SHP, MIF, and TAB. Scanned image files in the following formats: TIF (1 to 24-bit), JPEG (1 to 24-bit), JPEG 2000 (1 to 24-bit), BIL (1 to 24-bit), IST (1 to 24-bit), BMP (1 to 24-bit), Planet, Erdas Imagine (1 to 24-bit), GRC Vertical Mapper (1 to 24-bit), and ECW (8 or 24-bit) Population files in the following formats: TIF (16-bit), BIL (16-bit), IST (16-bit), Planet, BMP (16-bit), Erdas Imagine (16-bit), GRD/GRC Vertical Mapper (16-bit), AGD, DXF, SHP, MIF, and TAB. Other data in the following formats: TIF (16-bit), BIL (16-bit), IST (16-bit), Planet, BMP (16-bit), Erdas Imagine (16-bit), GRD/GRC Vertical Mapper (16-bit), AGD, DXF, SHP, MIF, and TAB. All raster maps imported must have the same projection coordinate system.
3.3 Importing Geo Data Files You can import the geographic data you need into the current Atoll document. As explained in "Supported Geographic Data Formats" on page 137, Atoll supports a variety of both raster and vector file formats. When you import a new geo data file, Atoll recognises the file format and suggests the appropriate folder in the Geo explorer. You can embed geo data files in the Atoll document while you are importing them or afterwards (see "Embedding Geographic Data" on page 143). You can share the paths of imported maps and display settings with other users by using Atoll’s user configuration files. For information on exporting the paths of your document’s files or to import the path from another document using user configuration files, see "Geographic Data Sets" on page 158. The instructions in this section do not apply to custom geo data maps. For information on importing or creating a custom geo data map, see "Custom Geo Data Maps" on page 152.
This section explains the following: • • • • • •
"Importing a Raster-format Geo Data File" on page 137 "Importing a Vector-format Geo Data File" on page 139 "Importing MSI Planet® Data" on page 140 "Importing a WMS Raster-format Geo Data File" on page 141 "Grouping Geo Data Files in Folders" on page 143 "Embedding Geographic Data" on page 143. You can use drag-and-drop to import geo data files into a document. The format is automatically recognised and Atoll presents you with the appropriate dialogue.
3.3.1 Importing a Raster-format Geo Data File All raster geo data files must be represented in the same projection coordinate system as the Atoll document itself. To import a geographic data file in a raster format: 1. Select File > Import. The Open dialogue appears. 2. Select the geo data file you want to import.
137
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
You can import more than one geo data file at the same time, providing that the geo data files are of the same type. You can select contiguous files by clicking the first file, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file. 3. Click Open. The File Import dialogue appears (see Figure 3.1). If the Vector Import dialogue appears, go to "Importing a Vector-format Geo Data File" on page 139.
Depending on the type of geo data file you are importing, choose one of the following options: • • • • •
DTM: Select Altitudes (DTM) from the Data Type list. Clutter Classes: Select Clutter Classes from the Data Type list. Clutter Heights: Select Clutter Heights from the Data Type list. Scanned Images: Select Image or Scan from the Data Type list. Population: i.
Select Population from the Data Type list. The Use as list becomes available.
ii. Select from the Use as list whether the imported data are to be interpreted as a Density (number of inhabitants per square kilometre) or as a Value (number of inhabitants). • •
Custom Geo Data: See "Custom Geo Data Maps" on page 152. 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 143. 5. Click Import. The geo data file is imported and listed in the Geo explorer. When you import a traffic data map, the traffic map’s Properties dialogue appears: a. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. b. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. c. Under Services (%), enter the percentage of each service type used in the map. The total percentages must equal 100. d. Under Clutter Distribution, enter for each clutter class the percentage of indoor users. An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define a clutter weighting for traffic density maps because the traffic is provided in terms of user density per pixel. e. For UMTS and CDMA, select whether the users are active in the Uplink/Downlink, only in the Downlink, or only in the Uplink. f. Click OK.
Figure 3.1: Importing a clutter class file
138
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
3.3.2 Importing a Vector-format Geo Data File When you import geo data files in vector format, their geographic system can be converted to the system used by the Atoll document. When you import extremely large vector geo data files, for example, vector files that cover an entire country, you must ensure that at least the centre of the bounding box defining the vector file is within the projection coordinate system defined for the Atoll document. To import a vector-format geographic data file: 1. Select File > Import. The Open dialogue appears. 2. Select the geo data file you want to import. You can import more than one geo data file at the same time, providing that the geo data files are of the same type. You can select contiguous files by clicking the first file, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file. 3. Click Open. The Vector Import dialogue appears (see Figure 3.4). If the File Import dialogue appears, go to "Importing a Raster-format Geo Data File" on page 137.
Depending on the type of geo data file you are importing, choose one of the following options: •
Vector Data: •
Select Geo from the Import to list. When you import vector data, you can simultaneously import the corresponding display configuration file (CFG) by setting an option in the atoll.ini file. The display configuration file will only be imported if it has the same file name and if it is located in the same directory as the imported vector-format file. For more information about setting options in the atoll.ini file, see the Administrator Manual.
•
Population: i.
Select Population from the Import to list.
ii. Under Fields to be imported, the first list contains the attributes of the population vector data file that you are importing, and the second list lets you select whether the attribute corresponds to population density or to a number of inhabitants. iii. Select from the first list which field is to be imported and from the second list whether the imported field is a Density (number of inhabitants per square kilometre for polygons, number of inhabitants per kilometre for lines, or number of inhabitants for points) or a Value (number of inhabitants) (see Figure 3.2 and Figure 3.3).
Figure 3.2: Population density (number of inhabitants/km²)
Figure 3.3: Population values (number of inhabitants per item – polygon/road/point) •
Custom Geo Data: •
•
See "Custom Geo Data Maps" on page 152.
Traffic Data Maps: Select Traffic Maps 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 143. 5. Click Import. The geo data file is imported and listed in the Geo explorer.
139
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
Figure 3.4: Vector Import dialogue • •
You can import ellipses and arcs from MapInfo files (MIF and TAB). Rectangles are interpreted as polygons. You can define mappings between the coordinate system used for the MapInfo/ ESRI vector files, defined in the corresponding MIF/PRJ files, and Atoll. This way, when you import a vector file, Atoll can detect the correct coordinate system automatically. For more information about defining the mapping between coordinate systems, please refer to the Administrator Manual.
3.3.3 Importing MSI Planet® Data MSI Planet® data are contained in a series of files described in index files. The index file is in ASCII text format and contains the information necessary to identify and properly interpret each data file. When you import MSI Planet® data, you can import each type of data separately, by importing the corresponding index file, or you can import several MSI Planet® data files at the same time, by importing several index files. This section explains the following: • •
"Importing One MSI Planet® Data Type" on page 140 "Importing a MSI Planet® Database" on page 141.
3.3.3.1 Importing One MSI Planet® Data Type When you want to import a certain type of MSI Planet® data, such as a DTM or clutter heights, you import the index file containing the information necessary to import the set of files containing the data. To import one type of MSI Planet® data: 1. Select File > Import. The Open dialogue appears. 2. Select the index file you want to import and click Open. The Data Type dialogue appears (see Figure 3.5).
Figure 3.5: Importing an MSI Planet® index file
140
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
3. Select the type of data you are importing and select the Embed check box if you want to embed the data in the current Atoll document. 4. Click OK to import the data into the current Atoll document.
3.3.3.2 Importing a MSI Planet® Database You can import all available MSI Planet® data at the same time by importing all index files. To import the MSI Planet® database: 1. Select File > Import. The Open dialogue appears. 2. Select "Planet® database" from the Files of Type list. The Planet Data Import dialogue appears (see Figure 3.6).
Figure 3.6: Importing an MSI Planet® database 3. For each type of data that you want to import: a. Select the corresponding check box. b. If you want to embed the data, select the Embed check box. c. To locate the MSI Planet® index file, click
. The Open dialogue appears.
d. Select the MSI Planet® index file and click Open. The path and name of the file appears in the corresponding field of the Planet Data to Be Imported dialogue. 4. If you are also importing network data, select the network Technology. 5. When you have selected all the types of data you want to import, click OK. The data is imported into the current Atoll document.
3.3.4 Importing a WMS Raster-format Geo Data File You can import raster images from a Web Map Service (WMS) server into your Atoll document. The image must be in TIF format. All images imported at the same time are imported as a single image. Before you import them, you can arrange them by placing on top the image that is the most important, such as roads. Or, you can place the least transparent image towards the bottom so that the other images imported at the same time remain visible. The image will be referenced in the document; it can not be embedded. Only WMS data mapped with a projection system (for example, the Lambert Conformal-Conic or the Universal Transverse Mercator projection) can be imported. Before importing an image from a WMS server, you must ensure that the coordinate system used in your document is the same projection system supported by the server. All raster geo data files must be represented in the same projection coordinate system as that used by the Atoll document itself.
141
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
To import a geographic data file from a web map service: 1. Select File > Import. The Open dialogue appears. 2. From the Files of Type list, select Connection to a Web Map Services server. The Web Map Services Data Import dialogue appears. 3. Select the URL of the WMS server from the Server URL list or enter it directly. The list of WMS servers that appears in the Server URL list are defined by entries in the atoll.ini file. For information on defining these entries, see the Administrator Manual.
4. Click the Connect button. Atoll connects to the URL of the WMS server and displays the information available along with a description of the service (Figure 3.7 on page 142).
Figure 3.7: The Web Map Services Data Import dialogue 5. In the left pane of the Web Map Services Data Import dialogue, navigate to the item you want to import by clicking the Expand button ( ) to open each level. 6. Select either the image you want to import, or the image group, i.e., a group preceded by an Expand button ( ). 7. Click for each image you want to import. The files you want to import appear in the right pane of the Web Map Services Data Import dialogue. You can remove an image or group of images from the images to be imported by selecting it in the right pane and clicking
.
8. Arrange the order in which you want the images to appear by selecting each image in the right pane and clicking to move it towards the top or to move it toward the bottom. The images will be imported as a single object and their appearance will depend on the order you define here. 9. The Web Map Import dialogue appears. The following information is given about the imported WMS data: • •
Data Types: "Image or Scan" is selected. Geographic Coordinates: The geographic coordinates are the WMS data are given.
10. The Name suggested is the name of the lowest layer to be imported. If desired, you can modify this name. 11. Click Import. The image is imported by reference into the Atoll document. You can not embed a WMS image in your document. If you had selected more than one image or an image group, Atoll imports the group as a single object. You can not modify this object. If you want to remove one of the images or add another one you will go through the import process again.
142
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
3.3.5 Grouping Geo Data Files in Folders By default, when you import scanned images and contours, lines, and points, they appear directly in the Geo explorer. Other data files, such as clutter classes, are listed together in a single Clutter Classes folder. You can, however, group scanned images and contours, lines, and points into folders as well. Once grouped, these geo data files can be displayed or hidden and moved more easily. They retain, however, their own individual display settings; the display settings cannot be managed at the folder level. You create the folder when you import the first geo data file that will be imported into it. When you import the next geo data file, either raster or vector, you can import it directly into the new folder. To create a new geo data folder when importing: 1. Select File > Import. The Open dialogue appears. 2. Select the geo data file and click Open. If the file to be imported is a raster file, the File Import dialogue appears (see Figure 3.1). If the file to be imported is a vector file, the Vector Import dialogue appears (see Figure 3.4). 3. From the Data Type list (on the File Import dialogue) or the Import To list (on the Vector Import dialogue), select New folder in Geo. The New Folder dialogue appears. If you want to import your file to the Network explorer, you can select New folder in Network.
4. Enter a name for the folder in Folder Name box and click OK. 5. Click Import. Your file is imported into the newly created folder. You can now import other geo data files into this folder by selecting it from the Data Type list (on the File Import dialogue) or the Import To list (on the Vector Import dialogue) when you import. You can transfer geo data that has been imported from the Geo explorer to the Network explorer, or vice versa. Right-click the data in the Explorer window and select Move to Network or Move to Geo.
3.3.6 Embedding Geographic Data By default, when you import a geo data file, Atoll creates a link to the file. You can, however, choose to embed the geo data file in your Atoll document, either when you import it or later. When Atoll is linked to a geo data file, the geo data file remains separate and modifying or saving the Atoll document has no effect on the geo data file. When the geo data file is embedded in the Atoll document, it is saved as part of the document. Both linking and embedding present advantages and disadvantages. For more information, see the Administrator Manual. If you are using distributed calculations, you must link your geo data files. Distributed calculations will not work with embedded geo data files. For information, see the Administrator Manual. To embed a geo data file in the current Atoll document while you are importing: •
Select the Embed in Document check box on the File Import or Vector Import dialogue box.
To embed a geo data file that is already linked to the current Atoll document: 1. Select the Geo explorer. 2. Right-click the file you want to embed in the current document. 3. Select Properties from the context menu. 4. Click the General tab of the Properties dialogue. 5. Click Embed. 6. Click OK. The geo data file is now embedded in the current Atoll document.
143
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
3.3.7 Repairing a Broken Link to a Geo Data File By default, when you import a geo data file, Atoll creates a link to the file; the geo data file remains separate and modifying or saving the Atoll document has no effect on the geo data file. If, however, the geo data file is moved, the link will be broken. To repair a broken link from within the Atoll document: 1. Select the Geo explorer. •
If the geo data file is in a folder, such as the Clutter Classes, Traffic Maps, or DTM folder, click folder.
to expand the
2. Right-click on the geo data file whose link you want to repair. The context menu appears. 3. Select Properties from the context menu. 4. On the General tab of the Properties dialogue, click the Find button. 5. Browse to the geo data file, select it and click OK.
3.4 Digital Terrain Models The Digital Terrain Model (DTM) is a geographic data file representing the elevation of the ground over sea level. To manage the properties of the DTM: 1. Select the Geo explorer. 2. Right-click the Digital Terrain Model folder. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab to define the display properties for the DTM. •
For information on Display tab settings, see "Display Properties of Objects" on page 43.
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 148. This section explains the following: • • • • •
"Assigning Names to Clutter Classes" on page 144 "Defining Clutter Class Properties" on page 145 "Adding a Clutter Class" on page 147 "Refreshing the List of Clutter Classes" on page 147 "Displaying Total Surface Area per Clutter Class" on page 148.
3.5.1 Assigning Names to Clutter Classes The clutter class file identifies each clutter class with a code. To make it easier to work with clutter classes, you can assign a descriptive name to each clutter class name. When a clutter class has a descriptive name, it is the name that appears in tip text and reports. When you import a clutter class file in BIL, TIF, JPEG 2000, or IMP format, Atoll can automatically assign names to clutter classes if the clutter class file has a corresponding MNU file. The MNU file contains a list with the clutter class codes and their corresponding names. For more information on the MNU file format and on creating an MNU file, see the Technical Reference Guide. To assign names to clutter classes: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder.
144
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
3. Select Properties from the context menu. 4. Click the Description tab of the Properties dialogue. 5. In the Name column, enter descriptive text for each class identified in the Code column.
3.5.2 Defining Clutter Class Properties The parameters are applied in relation to the location of the receiver being studied and the clutter class of the receiver location. These parameters can be set on the Properties dialogue: To define clutter class properties: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder. 3. Select Properties from the context menu. 4. Click the Description tab of the Properties dialogue. 5. Enter a Name and average Height (m) for each code. If the Height field is left blank, propagation models which use the height information of clutter classes will assume a clutter height of "0" if there is no clutter height map.
6. Enter default values in the first row of the table on the Description tab. or information about each field, see the descriptions in the following step. The default values are used if no clutter map is available. Even if there is a clutter classes map, you can select the Use default values only check box on the at the bottom of the Description tab to make Atoll use the values specified in this row instead of the values defined per clutter class. 7. If desired, you can enter a value for each of the following fields applicable to the current document: •
For all Atoll documents: • •
Model Standard Deviation (dB): to calculate shadowing losses on the path loss, as related to a user-defined cell edge coverage probability. Indoor Loss (dB): to be applied to the path loss and used in coverage predictions, point analysis, and Monte Carlo simulations. Indoor penetration losses depend on the clutter types as well as the operating frequency. You can define an additional indoor loss per frequency band used in the Frequency bands table in GSM GPRS EDGE, UMTS HSPA, CDMA2000 1xRTT 1xEV-DO, and TD-SCDMA documents. This is an option that must first be activated. For more information, contact support.
•
For GSM GPRS EDGE documents: • -
•
C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/I values, as related to a user-defined cell edge coverage probability. Additional Transmit Diversity Gain (DL) (dB): to add to the 3 dB gain if Tx diversity is active at the subcell level. Antenna Hopping Gain (DL) (dB): to apply on a calculated C/I if antenna hopping is active at the subcell level.
For UMTS HSPA, and CDMA2000 1xRTT 1xEV-DO documents: • • • •
•
Ec/Io Standard Deviation (dB): to calculate shadowing losses on the Ec/Io values, as related to a user-defined cell edge coverage probability. DL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values, as related to a userdefined cell edge coverage probability. UL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values, as related to a userdefined cell edge coverage probability. % Pilot Finger: to be used in the Ec/Io calculations. This factor represents the percentage of energy received by the mobile pilot finger. Mobile user equipment has one searcher finger for pilot. The searcher finger selects one path and only energy from this path is considered as signal; energy from other multipaths is considered as interference. For example, if 70% of the total energy is in one path and 30% of the energy is in other multipaths, then the signal energy is reduced to 70% of total energy). Orthogonality Factor: to be used to evaluate DL Eb/Nt. This parameter indicates the remaining orthogonality at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality because of multipath, to 1, indicating perfect orthogonality.
145
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
• • •
For TD-SCDMA documents: • • • •
•
• •
• • •
• • •
C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/(I+N) values, as related to a user-defined cell edge coverage probability. SU-MIMO Gain Factor: to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs in the MIMO tab of reception equipment. Additional Diversity Gain (DL) (dB): to add to the user’s downlink C/(I+N), if the user and its reference cell supports transmit diversity. Additional Diversity Gain (UL) (dB): to add to the user’s uplink C/(I+N), if the user and its reference cell supports receive diversity.
For multi-RAT documents: • • • • • • • • • •
146
C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/(I+N) values, as related to a user-defined cell edge coverage probability. SU-MIMO Gain Factor: to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs in the MIMO tab of reception equipment. Additional STTD/MRC Gain (DL) (dB): to add to the user’s downlink C/(I+N), if the user and its reference cell supports STTD/MRC. Additional STTD/MRC Gain (UL) (dB): to add to the user’s uplink C/(I+N), if the user and its reference cell supports STTD/MRC.
For LTE documents: •
•
P-CCPCH Eb/Nt or C/I Standard Deviation (dB): to calculate shadowing losses on the P-CCPCH Eb/Nt or C/I values, as related to a user-defined cell edge coverage probability. DL Eb/Nt or C/I Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt or C/I values, as related to a user-defined cell edge coverage probability. UL Eb/Nt or C/I Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt or C/I values, as related to a user-defined cell edge coverage probability. DL Orthogonality Factor: to be used to evaluate DL Eb/Nt or C/I. This parameter indicates the remaining orthogonality at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality because of multi-path, to 1, indicating perfect orthogonality. UL Orthogonality Factor: to be used to evaluate UL Eb/Nt or C/I. This parameter indicates the remaining orthogonality at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality because of multi-path, to 1, indicating perfect orthogonality. Spreading Angle (°): to be used in determining the cumulative distribution of C/I gains for statistical smart antenna modelling.
For WiMAX and Wi-Fi documents: •
•
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 user’s downlink HS-PDSCH Ec/Nt, if the user and its reference cell supports transmit diversity.
GSM Model Standard Deviation (dB): to calculate shadowing losses on the path loss (from GSM transmitters only), in relation to a user-defined cell edge coverage probability. GSM Indoor Loss (dB): to be applied to the path loss (from GSM transmitters only) and used in coverage predictions, point analysis, and Monte Carlo simulations. GSM C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/I values (from GSM transmitters only), in relation to a user-defined cell edge coverage probability. GSM Additional Diversity Gain (DL) (dB): to add to the 3 dB gain if diversity is set at the subcell level (GSM transmitters only). UMTS Model Standard Deviation (dB): to calculate shadowing losses on the path loss (from UMTS cells only), in relation to a user-defined cell edge coverage probability. UMTS Indoor Loss (dB): to be applied to the path loss (from UMTS cells only) and used in coverage predictions, point analysis, and Monte Carlo simulations. UMTS Ec/Io Standard Deviation (dB): to calculate shadowing losses on the Ec/Io values (from UMTS cells only), in relation to a user-defined cell edge coverage probability. UMTS DL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values (from UMTS cells only), in relation to a user-defined cell edge coverage probability. UMTS UL Eb/Nt Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt values (from UMTS cells only), in relation to a user-defined cell edge coverage probability. UMTS % Pilot Finger: to be used in the Ec/Io calculations (from UMTS cells only). This factor represents the percentage of energy received by the mobile pilot finger. (Mobile user equipment has one searcher finger for the pilot. The searcher finger selects one path and only energy from this path is considered as signal; energy from other multipaths is considered as interference. For example, if 70% of the total energy is in one path and 30% of the energy is in other multipaths, then the signal energy is reduced to 70% of total energy).
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
•
• • • • • • • •
UMTS Orthogonality Factor: to be used to evaluate DL Eb/Nt (from UMTS cells only). This parameter indicates the remaining orthogonality at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality because of multi-path, to 1, indicating perfect orthogonality. UMTS Spatial Multiplexing Gain Factor: to apply to the spatial multiplexing gain read from the Max Spatial Multiplexing Gain graphs on the MIMO tab of UMTS reception equipment. UMTS Additional Diversity Gain (DL) (dB): to add to the user’s downlink HS-PDSCH Ec/Nt, if the user’s mobile and his reference UMTS cell support transmit diversity. LTE Model Standard Deviation (dB): to calculate shadowing losses on the path loss (from LTE cells only), in relation to a user-defined cell edge coverage probability. LTE Indoor Loss (dB): to be applied to the path loss (from LTE cells only) and used in coverage predictions, point analysis, and Monte Carlo simulations. LTE C/I Standard Deviation (DL) (dB): to calculate shadowing losses on the C/(I+N) values (from LTE cells only), in relation to a user-defined cell edge coverage probability. LTE SU-MIMO Gain Factor: to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs in the MIMO tab of LTE reception equipment. LTE Additional Diversity Gain (DL) (dB): to add to the user’s downlink C/(I+N), if the user’s mobile and his reference LTE cell support transmit diversity. LTE Additional Diversity Gain (UL) (dB): to add to the user’s uplink C/(I+N), if the user’s mobile and his reference LTE cell support receive diversity.
8. If you want to use default values for all clutter classes, select the Use only default values check box at the bottom of the Description tab. 9. Click the Display tab to define the display properties for clutter classes. In addition to the Display tab options described in "Display Properties of Objects" on page 43, each clutter class display type has a visibility check box. By selecting or clearing the visibility check box, you can display or hide clutter class display types individually. Selecting white as the colour for a clutter class value or value interval will cause that clutter class value or value interval to be displayed as transparent.
10. Click OK. You can copy the description table into a new Atoll document after importing the clutter classes file. To copy the description table, select the entire table by clicking the cell in the upper-left corner of the table and press CTRL+C. On the Description tab of the clutter classes Properties dialogue in the new Atoll document, press CTRL+V to paste the values in the table.
3.5.3 Adding a Clutter Class You can add a new clutter class to your document. To add a new clutter class to the your document: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder. 3. Select Properties from the context menu. 4. Select the Description tab from the Properties dialogue. 5. In the blank row marked with column.
at the bottom of the table, enter an unused number from 1 to 255 in the Code
6. Fill in the remainder of the fields as described in step 5. and step 7. of "Defining Clutter Class Properties" on page 145. 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 160.
3.5.4 Refreshing the List of Clutter Classes Under certain circumstances, it can happen that the list of clutter classes on the Description tab of the clutter classes Properties dialogue contains unused clutter classes. For example, if you have imported two clutter class files and then deleted one of them, the list of clutter classes will still contain the clutter classes of the deleted file, even if they are not used in the remaining file. Whenever you want to ensure that the list of clutter classes is accurate and current, you can refresh the list.
147
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
To refresh the list of the clutter classes: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder. 3. Select Properties from the context menu. 4. Select the Description tab from the Properties dialogue. 5. Click Refresh. Atoll removes the unused clutter classes from the list. 6. Click OK.
3.5.5 Displaying Total Surface Area per Clutter Class You can display the total surface area covered by each clutter class in the document. Atoll displays the surface area covered by each clutter class in the focus zone if there is one, in the computation zone if there is no focus zone and, if there is no focus or computation zone, Atoll displays the total surface area covered by each clutter class in the entire document. This information is also available in prediction reports. To display the surface area covered by each clutter class: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder. 3. Select Statistics from the context menu. The Statistics dialogue appears, displaying the surface area (Si in km²) of each clutter class (i) and its percentage (% of i) in the computation zone or focus zone, if one exists. Si % of I = -------------- × 100 Sk
k
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 tip text 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 145). To manage the properties of clutter heights: 1. Select the Geo explorer. 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 43.
5. Click OK to close the Properties dialogue. The clutter height of the current pointer position as given in the clutter height file or in the clutter classes is displayed in the status bar.
3.7 Contours, Lines, and Points In Atoll, you can import or create vector objects such as contours, lines, and points. The imported or created vectors are used primarily for display purposes, but polygons can be used as filters, or computation or focus zones. Vector files can also be used for traffic maps or for population maps. They can also be used as part of an custom geo data map (see "Custom Geo Data Maps" on page 152). In an Atoll document, vector objects such as contours, lines, and points are arranged in vector layers. When you import a vector file, with, for example, roads, Atoll adds the file as a new vector layer containing all the vector objects in the file. The vector object data can be managed in the vector layer table. For information on working with data tables, see "Working with Data Tables" on page 69.
148
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
In this section, the following are explained: • • •
"Managing the Display of a Vector Layer" on page 149 "Managing the Properties of the Vector Layer" on page 149 "Moving a Vector Layer to the Network Explorer" on page 150.
3.7.1 Managing the Display of a Vector Layer Imported geographic vector files can have different attributes depending on their file formats. Atoll can use additional information related to vectors as display parameters. In addition, Atoll can read three-dimensional vector data. To manage the display of a vector layer: 1. Click the Network or Geo explorer on which the vector layer is located. 2. Right-click the vector layer. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Display tab of the Properties dialogue. For information on using the display tab, see "Display Properties of Objects" on page 43. You can manage the display of an individual vector object by right-clicking the vector object in the vector layer folder and selecting Properties from the context menu.
3.7.2 Managing the Properties of the Vector Layer The properties of the objects on the vector layer can be managed in two ways: either from a table containing all vectors and their attributes or from the Properties dialogue. Vector Layer Table All the vector objects of a vector layer and their attributes are listed in the vector table. To open the vector layer table: 1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Open Table from the context menu. The vector table appears. You can edit the contents of this table using the commands from the context menu or from the Edit, Format, and Records menus. For more information on editing tables in Atoll, see "Working with Data Tables" on page 69. Vector Layer Properties Dialogue The vector layer Properties dialogue has three tabs: a General tab, a Table tab, and a Display tab. To open the Properties dialogue of a vector layer: 1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu appears. 2. Select Properties from the context menu. 3. Click the General tab. The following options are available: • •
Name: The name of the vector layer. You can rename the vector layer using this field. Source File: The complete path of the vector layer file if the file is linked to the Atoll document; otherwise the file is described as embedded. • •
•
Find: Click the Find button to redefine the path when the file’s location has changed. Embed: Click the Embed button to embed a linked vector layer file in the Atoll document.
Coordinate System: When a vector layer is linked, the coordinate system used is the file’s, as specified when the file was imported. When the a vector layer is embedded, the coordinate system used is document’s, 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 94.
•
Filter: Click the Filter button to filter the data contained in the vector layer. For information on filtering, see "Advanced Data Filtering" on page 96.
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 70.
149
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
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 43.
3.7.3 Moving a Vector Layer to the Network Explorer In Atoll, all objects in the Network explorer, such as transmitters, antennas, and predictions, are displayed over all objects in the Geo explorer. You may wish, however, to ensure that certain geo data, for example, major geographical features, roads, etc., remain visible in the map window. You can do this by transferring the geo data from the Geo explorer to the Network explorer and placing it above data such as predictions. To transfer a vector layer to the Network explorer: 1. Select the Geo explorer. 2. Right-click the vector layer you want to transfer. The context menu appears. 3. Select Move to Network from the context menu. The vector layer is transferred to the Network explorer. You can transfer the vector layer back to the Geo explorer by right-clicking it in the Network explorer and selecting Move to Geo from the context menu. For more information about display priority in Atoll, see "Setting the Priority of Geo Data" on page 155.
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 150 "Defining the Display Properties of Scanned Images" on page 150.
3.8.1 Importing Several Scanned Images You can import scanned images into the current Atoll document one at a time, as explained in "Importing Geo Data Files" on page 137, or you can import a group of images by importing an index file listing the individual image files. The index file is a text file with the information for each image file on a separate line. Each line contains the following information, with the information separated by a space: • • • • • •
File name: The name of the file, with its path relative to the current location of the index file. XMIN: The beginning X coordinate of the file. XMAX: The end X coordinate, calculated as XMIN + (number of horizontal bins x bin width). YMIN: The beginning Y coordinate of the file. YMAX: The end Y coordinate, calculated as YMIN + (number of horizontal bins x bin width). 0: The zero character ends the sequence.
nice1.tif 984660 995380 1860900 1872280 0 nice2.tif 996240 1004900 1860980 1870700 0 File name
XMIN
XMAX
YMIN
YMAX
0
To import an index 1. Select File > Import. 2. Select the index file and click Open. The File Import dialogue appears (see Figure 3.1). 3. Select Image or Scan from the Data Type list. 4. Click Import. The image files imported and listed in the Geo explorer.
3.8.2 Defining the Display Properties of Scanned Images Because imported images cannot be modified, they have fewer display parameters than other object types. To define the display properties of a scanned image: 1. Select the Geo explorer 2. Right-click the scanned image. The context menu appears.
150
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
3. Select Properties from the context menu. The Properties dialogue appears (see Figure 3.8). 4. Select the Display tab and set the following options: • • • • •
Colour: Select either Automatic, Shades of gray, or Watermark from the list. Transparent Colour: Select White from the list if you wish parts of the scanned image that are coloured white to be transparent, allowing objects in lower layers to be visible. Lightness: Move the slider to lighten or darken the scanned image. Contrast: Move the slider to adjust the contrast. Visibility Scale: Enter a visibility scale minimum in the between 1: text box and maximum in the and 1: text box. When the displayed or printed scale is outside this range, the scanned image is not displayed.
5. Click OK.
Figure 3.8: Scanned image Properties dialogue
3.9 Population Maps Population maps contain information on population density or on the total number of inhabitants. Population maps can be used in prediction reports in order to display, for example, the absolute and relative numbers of the population covered. In this section, the following are explained: • •
"Managing the Display of Population Data" on page 151 "Displaying Population Statistics" on page 151.
3.9.1 Managing the Display of Population Data You can manage the display of population data. To manage the display of population data: 1. Select the Geo explorer. 2. Right-click the Population folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Display tab of the Properties dialogue. For information on using the display tab, see "Display Properties of Objects" on page 43. Vector points added to a vector population map are not displayed if the map is displayed by population density.
3.9.2 Displaying Population Statistics You can display the relative and absolute distribution of population, according to the defined value intervals in the display properties (for information on defining value intervals, see "Defining the Display Type" on page 44), as well as the total popu-
151
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
lation. Atoll displays the statistics for the focus zone if there is one, for the computation zone if there is no focus zone and, if there is no focus or computation zone, Atoll displays the statistics for the entire document. To display the population distribution statistics: 1. Select the Geo explorer. 2. Right-click the Population folder. 3. Select Statistics from the context menu. The Statistics window appears with the distributions of each value interval defined in the display properties. Statistics are displayed only for visible data. See "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38.
3.10 Custom Geo Data Maps You can import maps other than the default maps that Atoll uses. For example, you can import files for the revenue, rainfall, or socio-demographic data. Depending on the type of information displayed, you could use it in prediction reports. For example, you could display the predicted revenue for defined coverage. These maps can be raster files of 8, 16, or 32 bits per pixel or vector-format files that you have either imported or created using the Vector Editor toolbar "Editing Polygons, Lines, and Points" on page 61. You create an custom data map by: 1. Importing an custom geo data file and creating the custom data map folder. 2. Importing other custom geo data files into the newly created custom data map folder, if more than one file will be used for this custom geo data map. In this section, the following are explained: • • • • •
"Creating a Custom Geo Data Map" on page 152 "Adding a File to a Custom Geo Data Map" on page 153 "Managing the Properties of a Custom Geo Data Map" on page 154 "Displaying Statistics on Custom Geo Data" on page 154 "Integrable Versus Non Integrable Data" on page 154.
3.10.1 Creating a Custom Geo Data Map The first step in creating a custom geo data map is importing the first file and creating the custom data map folder. To create an custom geo data map: 1. Select File > Import. The Open dialogue appears. 2. Select the first geo data file that will be a part of the custom data map and click Open. • •
If the selected file is a raster file, the File Import dialogue appears (see Figure 3.1). If the selected file is a vector file, the Vector Import dialogue appears (see Figure 3.4).
3. Click the Advanced button. The New Type dialogue appears (see Figure 3.4). 4. Enter a Name for the custom geo data map. Atoll creates a folder with this name in the Geo explorer and all other files of the new custom geo data map will go in here. 5. Under Supported Input Formats, select the check boxes corresponding to the formats of both the present file and all other files that will constitute the new custom geo data map: • • • •
8-bit Raster 16-bit Raster 32-bit Raster Vector. If you do not select all the formats you need now, you will not be able to add a format later.
6. Under Supported Input Formats, select the check box corresponding to the type of value of the present file and all other files that will constitute the new custom geo data map:
152
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
• • • • •
Classes (8 bits): to create a map of value classes (such as clutter classes) with classes from 0 to 255. Short Integer (16 bits): to create a map with whole values. Long Integer (32 bits): to create a map with whole values. Float (32 bits): to create a map with decimal values. Double (64 bits): to create a map with decimal values.
7. Select the Integrable check box if you want to be able to use imported data as a surface density value and show cumulative custom geo data in prediction reports. • •
To use imported data as a surface density value, you must select the Integrable check box. You can not change the integrable setting once you have created your custom geo data map.
8. Click OK. 9. If the imported file is a raster file, the File Import dialogue appears (see Figure 3.1 on page 138); if the imported file is a vector file, the Vector Import dialogue appears (see Figure 3.4 on page 140): • •
File Import dialogue: From the Use as list, select whether the new data is to be used a Density or as a Value. Vector Import dialogue: Under Fields to be imported, select from the first list which field is to be imported and from the second list whether the imported field is a Density or a Value (see Figure 3.2 on page 139 and Figure 3.3 on page 139). If the file you first import when you create your custom geo data map is an 8-bit raster map, the Use as and Fields to be imported boxes will not be available for any file that is imported into your new custom geo data map. The values in 8-bit maps are codes and not values such as densities.
10. .Click Import. A new folder is created in the Geo explorer containing the geo data file you imported.
Figure 3.9: The New Type dialogue
3.10.2 Adding a File to a Custom Geo Data Map Once you have created the custom geo data map by importing the first file, you can add more files that will be part of the custom map. To add a file to an custom geo data map: 1. Select File > Import. The Open dialogue appears. 2. Select the geo data file that you want to add to the custom data map and click Open. •
If the selected file is a raster file, the File Import dialogue appears (see Figure 3.1). i.
From the File Type list, select the name of the custom geo data map.
ii. From the Use as list, select whether the new data is to be used a Density or as a Value. •
If the selected file is a vector file, the Vector Import dialogue appears (see Figure 3.4).
153
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
i.
From the Import To list, select the name of the custom geo data map.
ii. Under Fields to be imported, select from the first list which field is to be imported and from the second list whether the imported field is a Density or a Value (see Figure 3.2 on page 139 and Figure 3.3 on page 139). •
•
If the file you first imported when you created your custom geo data map was an 8-bit raster map, the Use as and Fields to be imported boxes will not be available for any file that is imported into your new custom geo data map. To use imported data as a surface density value, you must select the Integrable check box.
3. Click Import. The file is added to the custom geo data file in the Geo explorer containing the geo data file you imported.
3.10.3 Managing the Properties of a Custom Geo Data Map To manage the properties of an custom geo data map: 1. Right-click the custom geo data map in the Geo explorer. 2. Select Properties from the context menu: 3. Depending on the imported file types, the following tabs are available: • • •
•
Description: The Description table lists the classes of all 8-bit raster files contained in the custom geo data map. You must enter a different value for each class. Table: The Table tab enables you to manage the contents of the class table presented on the Description tab. For information on working with the Table tab, see "Adding, Deleting, and Editing Data Table Fields" on page 70. 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 154), 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 43.
3.10.4 Displaying Statistics on Custom Geo Data You can display the relative and absolute distribution of each value interval (for information on defining value intervals, see "Defining the Display Type" on page 44) of an custom geo data map. Atoll displays the statistics for the focus zone if there is one, for the computation zone if there is no focus zone and, if there is no focus or computation zone, Atoll displays the statistics for the entire document. To display the statistics of an custom geo data map: 1. Select the Geo explorer. 2. Right-click the custom geo data map. 3. Select Statistics from the context menu. The Statistics window appears with the distributions of each value interval. Statistics are displayed only for visible data. See "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38.
3.10.5 Integrable Versus Non Integrable Data Integrable data can be summed over the coverage area defined by the item in a prediction report (for example, by transmitter or threshold). The data can be value data (revenue, number of customers, etc.) or density data (revenue/km², number of customer/km², etc.). For example, if the integrable data comes from a revenue map, a prediction report would indicate:
154
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
• • •
The percentage of coverage for each revenue class for the entire focus zone, and for each single coverage area (transmitter, threshold, etc.), The revenue of the focus zone and of each single coverage area, The percentage of the revenue map covered for the entire focus zone and for each single coverage area.
Data is considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example, socio-demographic classes, etc. In the example of a socio-demographic classes map, a prediction report would indicate: •
The coverage of each socio-demographic class for the entire focus zone and for each single coverage area (transmitter, threshold, etc.)
3.11 Setting the Priority of Geo Data Atoll lists the imported DTM, clutter class or traffic objects in their respective folders and creates a separate folder for each imported vector data file and scanned image. Each object is placed on a separate layer. Thus, there are as many layers as imported objects. The layers are arranged from top to bottom in the map window as they appear in the Geo explorer. It is important to remember that all objects in the Network explorer, such as transmitters, antennas, and predictions, are displayed over all objects in the Geo explorer.
3.11.1 Setting the Display Priority of Geo Data There are several factors that influence the visibility of geo data: •
•
The display check box: The check box immediately to the left of the object name in the Geo explorer controls whether or not the object is displayed on the map. If the check box is selected ( ), the object is displayed; if the check box is cleared ( ), the object is not displayed. If the check box, is selected but shaded ( ), not all objects in the folder are displayed. For more information, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. The order of the layers: The layer at the top of the Geo explorer is on top of all other layers in the map window. Data on layers below is only visible where there is no data on the top layer or if you adjust the transparency of the objects on the top layer. You can use drag and drop to change the order of layers by dragging a layer in the Geo explorer towards the top or the bottom of the tab. All objects in the Network explorer, such as transmitters, antennas, and predictions, are displayed over all objects in the Geo explorer. Vector geo data, however, can be transferred to the Network explorer, where they can be placed over data such as predictions. In this way, you can ensure that certain vector geo data, for example, major geographical features, roads, etc., remain visible in the map window For more information, see "Moving a Vector Layer to the Network Explorer" on page 150.
•
•
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 45. 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 46.
In Figure 3.10, vector data (including the linear vectors HIGHWAYS, COASTLINE, RIVERLAKE, MAJORROADS, MAJORSTREETS, RAILWAYS and AIRPORT), clutter classes, DTM and scanned image have been imported and a UMTS environment traffic map has been edited inside the computation zone. In the map window, the linear objects (ROADS, RIVERLAKE, etc.) are visible both inside and outside the computation zone. The clutter class layer is visible in the area where there is no traffic data (outside the computation zone). On the other hand, the DTM layer which is beneath the clutter class layer and the scanned map which is beneath the DTM layer, are not visible.
155
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
Figure 3.10: Displaying Geo data layers
3.11.2 Setting the Priority of Geo Data in Calculations The priority of geo data in calculations is determined in much the same way as it is for display. When you make calculations in Atoll, the data taken into account in each folder (Clutter Classes, DTM, etc.) is the data from the top down. In other words, Atoll takes the object on top and objects below only where there is no data in higher levels; what is used is what is seen. The visibility in the context of calculations must not be confused with the display check box ( ). Even if the display check box of an object is cleared ( ), so that the object is not displayed on the map, it will still be taken into consideration for calculations. The only cases where clearing the display check box means that the data will not be used are for population data in reports, and for custom geo data maps. Object folders, for example, the DTM, clutter classes, clutter heights, and traffic density folders, can contain more than one data object. These objects can represent different areas of the map or the same parts of the map with the same or different resolutions. Therefore for each folder, you should place the objects with the best data at the top. These are normally the objects which cover the least area but have the highest resolution. For example, when calculating coverage in an urban area, you might have two clutter class files: one with a higher resolution for the downtown core, where the density of users is higher, and one with a lower resolution but covering the entire area. In this case, by placing the clutter class file for the downtown core over the file with the lower resolution, Atoll can base its calculations for the downtown core on the clutter class file with the higher resolution, using the second file for all other calculations. Population maps and custom geo data maps, both of which can be used in prediction reports follow the same rules of calculation priority. The following sections give several examples to better illustrate how data are used in Atoll: • • •
"Example 1: Two DTM Maps Representing Different Areas" on page 156 "Example 2: Clutter Classes and DTM Maps Representing the Same Area" on page 157 "Example 3: Two Clutter Class Maps Representing a Common Area" on page 157.
3.11.2.1 Example 1: Two DTM Maps Representing Different Areas In this example, there are two imported DTM files: • •
"DTM 1” represents a given area and has a resolution of 50 m. “DTM 2” represents a different area and has a resolution of 20 m.
In this example, the file order of the DTM files in the Explorer window does not matter because they do not overlap; in both Case 1 and Case 2, Atoll will take all the data from both "DTM 1” and "DTM 2” into account.
156
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
Explorer window
Work space
Case 1 DTM • •
DTM 2 (20m) DTM 1 (50m)
Case 2 DTM • •
DTM 1 (50m) DTM 2 (20m)
Figure 3.11: Multi-layer management in calculations – two DTM maps representing different areas
3.11.2.2 Example 2: Clutter Classes and DTM Maps Representing the Same Area In this example, there are two imported maps: • •
A clutter class map called “Clutter.” A DTM map called “DTM”.
Independently of the order of the two maps in the Explorer window, Atoll uses both the clutter and DTM data in calculations. In Case 1, the clutter class map is on top of the DTM map. In Case 2, the DTM map is on top of the clutter class map. In both Case 1 and Case 2, Atoll will use both the clutter and DTM data in calculations. Explorer window
Work space
Case 1 Clutter classes • Clutter DTM • DTM Case 2 DTM • DTM Clutter classes • Clutter Figure 3.12: Multi-layer management in calculations – Clutter and DTM maps representing the same area
3.11.2.3 Example 3: Two Clutter Class Maps Representing a Common Area In this example, there are two imported clutter classes maps: • •
"Clutter 1" represents a large area with a resolution of 50 m. "Clutter 2" represents a smaller area with a resolution of 20 m. This area is also covered by "Clutter 1"
In the case of two clutter class maps, Atoll uses the order of the maps in the Clutter Classes folder in the Geo explorer to decide which data to use. In Case 1, "Clutter 2" is on top of "Clutter 1". Atoll will therefore use the data in "Clutter 2" where it is available, and the data from "Clutter 1" everywhere that is covered by "Clutter 1" but not by "Clutter 2." In Case 2, "Clutter 1" is on top and completely covers "Clutter 2." Therefore, Atoll will only use the data from "Clutter 1."
157
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
Explorer window
Work space
Case 1 Clutter classes • Clutter 2 (20m) • Clutter 1 (50m)
Case 2 Clutter classes • Clutter 2 (50m) • Clutter 1 (20m)
Figure 3.13: Multi-layer management in calculations – two clutter maps representing the same area
3.12 Displaying Information About Geo Data You can display information about a geo data map by using tip text. For information on how to display information in tip text, see "Defining the Object Type Tip Text" on page 46. To display information about the geo data in tip text: •
Hold the pointer over the geo data until the tip text appears. The surface area is only given for closed polygons.
Tip text only appears when the Tip Text button (
) on the toolbar has been selected.
3.13 Geographic Data Sets In Atoll, once you have imported geographic data and defined their parameters, you can save much of this information in a user configuration file. Then, another user, working on a similar Atoll document, can import the user configuration file containing the paths to the imported geographic data and many of the defined parameters. When you save the geographic data set in a user configuration, you save: • • • •
the paths of imported geographic maps map display settings (visibility scale, transparency, tips text, etc.) clutter description (code, name, height, standard deviations, etc.) raster or user profile traffic map description.
In this section, the following are explained: • •
"Exporting a Geo Data Set" on page 159 "Loading a Geo Data Set" on page 159. You can save and load other types of information with user configuration files as well. For information, see the Administrator Manual.
158
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
3.13.1 Exporting a Geo Data Set When you save a geo data set in a user configuration file, the information listed in "Geographic Data Sets" on page 158 is saved into a file. Vectors must be in the same coordinate system as the raster maps.
To save a geo data set in a user configuration file: 1. Select Tools > User Configuration > Save. The User Configuration dialogue appears (see Figure 3.14). 2. In the User Configuration dialogue, select the Geographic Data Set check box.
Figure 3.14: The User Configuration dialogue 3. Click OK, The Save As dialogue appears. 4. In the Save As dialogue, browse to the folder where you want to save the file and enter a File name. 5. Click OK.
3.13.2 Loading a Geo Data Set When you load a user configuration file containing a geo data set, the information listed in "Geographic Data Sets" on page 158 is loaded into your current Atoll document. To load a user configuration file containing a geo data set into your current Atoll document: 1. Select Tools > User Configuration > Load. The Open dialogue appears. 2. Browse to the user configuration file, select it and click Open. 3. The User Configuration dialogue appears. When you load a user configuration file including a geographic data set, Atoll checks if there are already geographic data in the current Atoll document. If so, the option Delete existing geo data appears with other options in the User Configuration dialogue. 4. In the User Configuration dialogue, select the check boxes of the items you want to load into your current Atoll document. 5. If you already have geographic data in your current Atoll document and would like to replace it with any data in the user configuration file you are loading, select the Delete existing geo data check box. If you do not want to replace existing geo data with imported data, clear the Delete existing geo data check box. 6. Click OK. You can automatically start Atoll with a user configuration file by naming the file "atoll.cfg" and placing it in the same folder as the Atoll executable. You can also edit the Windows shortcut to Atoll and add "-cfg " where "" is the full path to the user configuration file.
159
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
3.14 Editing Geographic Data In Atoll, you can edit geo data that you have imported or you can create geo data by, for example, adding a vector layer to the Population folder and then adding polygons. The following types of geographic data can be edited: • • • • •
Clutter classes (for more information, "Editing Clutter Class Maps" on page 160) Contours, lines, and points (for more information, "Editing Polygons, Lines, and Points" on page 61) 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 161) Traffic data maps Custom data maps (for more information, "Editing Population or Custom Data Maps" on page 161).
3.14.1 Editing Clutter Class Maps Clutter class maps and certain traffic maps are raster maps. You can edit these maps by creating or modifying polygons. In this section, the following are explained: • • • •
"Creating a Clutter Polygon" on page 160 "Editing Clutter Polygons" on page 160 "Displaying the Coordinates of Clutter Polygons" on page 161. "Deleting Clutter Polygons" on page 161
3.14.1.1 Creating a Clutter Polygon In Atoll, you can modify imported clutter class maps or create your own maps by adding data in the form of polygons. You can later edit and export the polygons you have created. All modifications you make to clutter class maps are taken into account by propagation model calculations. To create a polygon: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder. The context menu appears. 3. Select Edit from the context menu. The Editor toolbar appears with a clutter or traffic list, a polygon drawing tool a polygon deletion tool
, and a Close button (see Figure 3.15).
Figure 3.15: Editor toolbar 4. From the list, select the clutter class for the polygon you want to create. Clutter classes are defined on the Descriptions tab of the clutter classes Properties dialogue.
5. Click the polygon drawing button (
). The pointer changes to a pencil (
).
6. Click once on the map where you want to begin drawing the polygon. 7. Click each time you change angles on the border defining the outside of the polygon. 8. Double-click to close the polygon. You can copy the exact coordinates of a closed polygon by right-clicking it on the map and selecting Properties from the context menu.
3.14.1.2 Editing Clutter Polygons You can edit clutter polygons by moving existing points of the polygon or by adding or deleting points.
160
,
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
To edit clutter polygons: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder. The context menu appears. 3. Select Edit from the context menu. The Editor toolbar appears (see Figure 3.15). 4. Select the polygon. You can now edit the clutter polygon by: •
Moving a point: i.
Position the pointer over the point you want to move. The pointer changes (
).
ii. Drag the point to its new position. •
Adding a point: i.
Position the pointer over the polygon border where you want to add a point. The pointer changes (
).
ii. Right-click and select Insert Point from the context menu. A point is added to the border at the position of the pointer. •
Deleting a point: i.
Position the pointer over the point you want to delete. The pointer changes (
).
ii. Right-click and select Delete Point from the context menu. The point is deleted.
3.14.1.3 Displaying the Coordinates of Clutter Polygons To display the coordinates of the points defining the polygon area: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder. The context menu appears. 3. Select Edit from the context menu. The Editor toolbar appears (see Figure 3.15). 4. Right-click the polygon and select Properties from the context menu. The Properties dialogue appears with the coordinates of the points defining the polygon and the total area. You can select and copy the coordinates displayed in the Properties dialogue of the polygon.
3.14.1.4 Deleting Clutter Polygons You can delete clutter polygons. To delete a clutter polygon: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder. The context menu appears. 3. Select Edit from the context menu. The Editor toolbar appears (see Figure 3.15). 4. Click the polygon deletion tool (
). The pointer changes (
).
5. Click the polygon you want to delete. The polygon is deleted.
3.14.2 Editing Population or Custom Data Maps Some geographic data maps, for example population maps, and custom data, are made up of individual vector objects. You can modify and create these geo data maps by adding a vector layer and then adding vector objects (contours, lines, and points) to this layer. To create a vector layer and vector objects on a geo data map: 1. Select the Geo explorer. 2. Right-click the geo data object, the Population, or the Custom Data folder, to which you want to add a vector layer. 3. Select Add Vector Layer from the context menu. A new data object called "Vectors" is created in the selected geo data object folder.
161
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
4. Right-click the new vector layer. The context menu appears. 5. Select Edit from the context menu. The vector tools on the Vector Editor toolbar are activated. You can also activate the vector tools by selecting the vector layer to edit from the Vector Editor toolbar list. 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 40.
6. To draw a polygon, click the New Polygon button (
) on the Vector Editor toolbar:
a. Click once on the map where you want to begin drawing the contour. b. Click each time you change angles on the border defining the outside of the contour. c. Double-click to close the contour. 7. To draw a rectangle, click the New Rectangle button (
) on the Vector Editor toolbar:
a. Click the point on the map that will be one corner of the rectangle. b. Drag to the opposite corner of the rectangle. c. Release the mouse to create the rectangle defined by the two corners. 8. Right-click the new polygon or rectangle and select Properties from the context menu. 9. Enter a value: • •
Population: Enter a value in the Population field to indicate the number of inhabitants or the population density. Custom Data Map: The value you enter will depend on the type of custom data map you created.
10. Press ESC to deselect the New Polygon (
) or the New Rectangle (
) button on the Vector Editor toolbar.
11. For Atoll to consider the new vector layer as part of the data map, you must map the vector layer. Right-click the 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 61.
3.15 Saving Geographic Data Atoll allows you to save your geographic data files separately from saving the Atoll document. Atoll supports a variety of both raster and vector file formats (for more information, see "Supported Geographic Data Formats" on page 137). Saving a geographic file separately from saving the Atoll document enables you to: • • • • •
Save modifications you have made to an external file: If you have made modifications to geo data, you can export them to a new external file. Update the source file with modifications you have made: If you have made modifications to a geo data type in Atoll, you can save these changes to the source file. Combine several raster files into one file: If you have several small raster files in one folder of the Geo explorer, you can save them as one file. Export an embedded file to be used in another Atoll document or in another application: You can save a file to an external file, in the same format or in another one. Create a new file from part of a larger one: You can select part of certain geo data types and then save the selected part as a new file.
This section explains the following: • •
162
"Saving Modifications to an External File" on page 163 "Updating the Source File" on page 164
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
• • •
"Combining Several Raster Files into One File" on page 165 "Exporting an Embedded File" on page 165 "Creating a New File from a Larger File" on page 166
3.15.1 Saving Modifications to an External File In Atoll, you can save your modifications to an external file. This section explains the following: • •
"Exporting an Edited Clutter Class Map in a Raster-Format File" on page 163 "Exporting an Edited Vector Layer in Vector-Format File" on page 164.
3.15.1.1 Exporting an Edited Clutter Class Map in a Raster-Format File You can export clutter class modifications in a raster-format file, either in the same format as used in the current Atoll document, or in a different raster format. You can also choose to export the entire clutter class geo data, the part containing the computation zone, or just your modifications to the geo data. When you have made modifications to a raster-format geo data file, exporting either the entire geo data or just your modifications allows you to save those modifications to an external file. To export clutter class modifications in a raster-format file: 1. Select the Geo explorer. 2. Right-click the Clutter Classes folder. 3. Select Save As from the context menu. The Save As dialogue appears. 4. In the Save As dialogue, browse to the folder where you want to save the file, enter a name for the file, and select the file format from the Save as type list. You can select from one of the following file formats: • • • • • • • •
BMP Files (*.bmp): When you select BMP format, Atoll automatically creates the corresponding BPW file containing the georeference information. PNG Files (*.png): When you select PNG format, Atoll automatically creates the corresponding PGW file containing the georeference information. ArcView Grid Files (*.txt): The ArcView text format is intended only for export; no corresponding geo-reference file is created. TIFF Files (*.tif): When you select tagged image file format, Atoll automatically creates the corresponding TFW file containing the georeference information. BIL Files (*.bil): When you select the BIL format, Atoll automatically creates the corresponding HDR file containing the georeference information. When exporting in BIL format, Atoll allows you to export files larger than 2 Gb. JPEG 2000 Files (*.jp2): When you select the JPEG 2000 format, no corresponding geo-reference file is created. JPEG Files (*.jpg): When you select JPG format, Atoll automatically creates the corresponding JGW file containing the georeference information. Vertical Mapper Files (*.grc,*.grd): Files with the extension GRC or GRD are Vertical Mapper files. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 Gb.
5. Click Save. The Export dialogue appears (see Figure 3.16).
Figure 3.16: Export dialogue 6. Under Region, select one of the following: •
The Entire Project Area: This option allows you to export the entire clutter class geo data file, including any modifications you have made to the geo data. The exported geo data file will replace the geo data file in the current Atoll document.
163
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
•
•
Only Pending Changes: This option allows you to export a rectangle containing any modifications you have made to the clutter classes. The exported geo data file will be added as a new object to the Clutter Classes geo data folder. The Computation Zone: This option allows you to export the clutter class geo data contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible. The exported geo data file will be added as a new object to the selected geo data folder.
7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. The suggested resolution value is defined by the following criteria: • • • •
If one object has been modified, the suggested resolution is the resolution of the modified object. If several objects have been modified, the suggested resolution is the highest resolution of the modified objects. If there is no initial clutter class object, the resolution will equal the highest resolution of the DTM maps. If the Atoll document in which you created the clutter class file has no DTM, no other clutter class geo data file, or traffic objects, the suggested resolution is 100 m.
8. Click OK. The selected data is saved in an external file.
3.15.1.2 Exporting an Edited Vector Layer in Vector-Format File You can export an edited vector layer as a vector-format file. A vector layer can contain contours, lines, and points. Along with vector layers you have added to the Geo explorer, the following maps can be exported as vector-format files: • •
Vector-format population maps Vector-format custom maps.
Once you save a vector layer, the exported file replaces the vector layer as a linked file. You can embed the file afterwards (see "Embedding Geographic Data" on page 143). You can simultaneously export the display configuration file (CFG) of the edited vector layer by setting an option in the atoll.ini file. The exported display configuration file will have the same file name and will be saved in the same directory as the exported vectorformat file. For more information about setting options in the atoll.ini file, see the Administrator Manual. To export a vector layer: 1. 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 can be used for vector layers containing only polygons, only lines, or only points. If a vector file has a combination of polygons, lines, and points, you should use the AGD, MIF, or TAB formats instead. MIF and TAB: MapInfo formats.
4. Click Save in the Save As dialogue. The Vector Export dialogue appears, displaying the current coordinate system and allowing you to change the coordinate system by clicking Change. 5. Click Export. The vector layer is saved in the format and with the name you specified and the exported file replaces the vector layer in the current document as a linked file.
3.15.2 Updating the Source File While working on an Atoll document, you may make changes to geo data. If the geo data file is embedded in the Atoll document, Atoll saves the changes automatically when you save the document. If the geo data file is linked, Atoll prompts you to save the changes when you close the document. To update the source file of a linked geo data file: 1. Select the Geo explorer. 2. Right-click the folder containing geo data file whose source file you want to update. The context menu appears. 3. Select Save from the context menu. The linked file is updated.
164
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
You will not be warned that you are replacing the current file. Therefore, ensure that you want to replace the current file before proceeding to the following step. If you do not want to replace the current file, you can save your changes to an external file ("Exporting an Edited Vector Layer in Vector-Format File" on page 164).
3.15.3 Combining Several Raster Files into One File In certain circumstances, for example, after importing an MSI Planet® index file, you may have several geo data files of the same type. You can combine these separate files to create one single file. The files will be combined according to their order from the top down in the folder in the Geo explorer. If the files overlap on the map, the combined file will show the file on the top. You can create a one file from a section of the following geo data types: • • • •
Digital terrain model Clutter classes Clutter heights Scanned maps
To combine individual files into a new file: 1. Select the Geo explorer. 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.17). 6. Under Region, select The Entire Project Area. This option allows you to save the entire area covered by the geo data files, including any modifications you have made to the geo data. 7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. The suggested resolution value is the highest resolution of all objects. 8. Click OK. The selected data is saved as a new file.
3.15.4 Exporting an Embedded File You can export an embedded geo data file to be used in a different Atoll document, or in a different application. When you export an embedded file, Atoll replaces the embedded file in the current Atoll document with the newly exported file. To export an embedded geo data file: 1. Select the Geo explorer. 2. Right-click the folder of the embedded geo data file you want to export. The context menu appears. 3. Select Save As from the context menu. The Save As dialogue appears. 4. Enter a File name and select a file type from the Save as type list. 5. Click OK. If the geo data file is a vector file, the Vector Export dialogue appears (see Figure 3.17).
165
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
© Forsk 2012
Figure 3.17: The Vector Export dialogue a. The Vector Export dialogue displays the coordinate system of the file. To change the coordinate system used for the exported file, click Change. The Coordinate Systems dialogue appears. For information on the Coordinate Systems dialogue, see "Setting a Coordinate System" on page 121. b. Click Export. The geo data file is exported with the selected coordinate system. If the geo data file is a raster file, the Export dialogue appears (see Figure 3.18).
Figure 3.18: Export dialogue a. Under Region, select one of the following: •
• •
The Entire Project Area: This option allows you to export the entire raster-format geo data file, including any modifications you have made to the geo data. The exported file will replace the embedded file in the Geo explorer. Only Pending Changes: This option allows you to export a rectangle containing any modifications you have made to the geo data. The exported file will be added as an object in the geo data folder. The Computation Zone: This option allows you to export the geo data contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible. The exported file will be added as an object in the geo data folder.
b. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1. c. Click OK. The selected data is saved in an external file.
3.15.5 Creating a New File from a Larger File You can create a new file from a section of a larger file. You can use this new file in the same Atoll document, or in a new Atoll document. To create a new file, you must first define the area by creating a computation zone. You can create a new file from a section of the following geo data types: • • • • •
Digital terrain model Clutter classes Clutter heights Scanned maps Population maps
To create a new file from a section of a larger file: 1. Select the Geo explorer. 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.
166
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
AT312_UM_E1
4. Enter a File name and select a file type from the Save as type list. 5. Click OK. The Export dialogue appears (see Figure 3.17). 6. Under Region, select The 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.
167
Atoll 3.1.2 User Manual Chapter 3: Geographic Data
168
© Forsk 2012
Chapter 4 Antennas and Equipment This chapter provides the information to work with antennas and equipment in Atoll.
In this chapter, the following are explained: •
"Working With Antennas" on page 171
•
"Working With Equipment" on page 176
Atoll 3.1.2 User Manual Chapter 4: Starting a Project
170
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 4: Antennas and Equipment
AT312_UM_E1
4 Antennas and Equipment In Atoll, the equipment used to create a network is modelled, along with the characteristics which have a bearing on network performance. This chapter explains working with antennas as well as equipment such as tower-mounted amplifiers, feeder cables, base transceiver station equipment: • •
"Working With Antennas" on page 171 "Working With Equipment" on page 176
4.1 Working With Antennas Atoll enables you to work with antennas in many ways. To create a new antenna, you can import the data necessary from external sources, such as from a spreadsheet or from a Planet-format file. Once you have created an antenna, you can improve signal level prediction by smoothing the high-attenuation points of the vertical pattern. In this section, the following are explained: • • • • • •
"Creating an Antenna" on page 171 "Importing Planet-Format Antennas" on page 173 "Importing 3-D Antenna Patterns" on page 173 "Displaying Antenna Patterns With a Fixed Scale" on page 175. "Smoothing an Antenna Pattern" on page 175. "Printing an Antenna Pattern" on page 175.
4.1.1 Creating an Antenna Each Atoll project template has antennas specific to the technology supported by the template. As well, Atoll allows you to create antennas and set the parameters such as manufacturer, gain, horizontal pattern, and vertical pattern. When you create a new antenna, you can copy the horizontal and vertical antenna patterns from a spreadsheet or word processor.
To create an antenna: 1. Click the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click on the Antennas folder. The context menu opens. 4. Select New from the context menu. The Antennas New Element Properties dialogue appears. 5. Click the General tab. You can enter information in the following fields: • • • •
•
Name: Atoll automatically enters a default name for each new antenna. You can modify the name Atoll enters if you want. Manufacturer: The name of the antenna manufacturer. Gain: The antenna’s isotropic gain. Pattern Electrical Tilt: The antenna’s electrical tilt. This field is for information only; for an antenna’s electrical tilt to be taken into consideration in calculations, it must be integrated into the horizontal and vertical patterns. Atoll automatically calculates the pattern electrical tilt if the Pattern Electrical Tilt field is left blank or has a value of "0." This field has to be correctly filled (i.e., consistent with the defined vertical pattern) if you want the antenna to be available when selecting an antenna for a transmitter. Physical antenna: The name of the physical antenna to which the antenna model belongs. A physical antenna may have one or more antenna models (patterns), corresponding to different electrical downtilts. If you want to flag a physical antenna as obsolete, add the word "obsolete" (not case sensitive) to the name of the physical antenna. Physical antennas flagged as obsolete are not listed among available antennas in the Antenna Selector dialogue It is strongly recommended to enter a name in the Physical antenna field. Atoll uses this entry to group antenna models into physical antennas.
•
Comments: Any additional information on the antenna.
171
Atoll 3.1.2 User Manual Chapter 4: Antennas and Equipment
© Forsk 2012
6. Click the Horizontal Pattern tab. The Horizontal Pattern tab has a table describing the horizontal antenna pattern in terms of the attenuation in dB (Att.) per Angle and a graphical representation of the pattern. Atoll allows you to enter antenna pattern attenuations for as many as 720 angles. Therefore, attenuation values can also be defined for angles other than integer values from 0° to 359°. If you have the horizontal pattern in a spreadsheet or text document, you can copy the data directly into the table: a. Switch to the document containing the horizontal pattern. b. Select the columns containing the angles and attenuation values of the horizontal pattern. c. Copy the selected data.
Figure 4.1: Copying horizontal pattern values d. Switch to Atoll. e. Click the upper-left cell of the Co-polar Section table describing the horizontal pattern. f. Press CTRL+V to paste the data in the table. • •
If there are some blank rows in your data sheet, Atoll will interpolate the values in order to obtain a complete and realistic pattern. When performing a calculation along an angle for which no data is available, Atoll calculates a linear interpolation from the existing pattern values. When Atoll performs linear interpolations on antenna pattern attenuation, interpolations are calculated in Watts by default. You can change this setting to dB by adding an option in the atoll.ini file. For more information on changing options in the atoll.ini file, see the Administrator Manual.
g. Click Apply to display the pattern of the values you have pasted in. 7. Click the Vertical Pattern tab. The Vertical Pattern tab has a table describing the vertical antenna pattern in terms of the attenuation in dB (Att.) per Angle and a graphical representation of the pattern. Atoll allows you to enter antenna pattern attenuations for as many as 720 angles. Therefore, attenuation values can also be defined for angles other than integer values from 0° to 359°. If you have the vertical pattern in a spreadsheet or text document, you can copy the data directly into the table as described in step 6. 8. Click the Other Properties tab. You can define the following fields (not used in any calculation): •
• •
Beamwidth: In a plane containing the direction of the maximum lobe of the antenna pattern, the angle between the two directions in which the radiated power is one-half the maximum value of the lobe. In terms of dB, half power corresponds to -3 dB. In this window, you can enter this angle in degrees. This field must be filled in correctly if you want to display transmitters using a symbol that indicates the beamwidth. FMin: The minimum frequency that the antenna is capable of emitting. FMax: The maximum frequency that the antenna is capable of emitting.
9. Click OK. Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns are correctly aligned when: • •
172
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.
Atoll 3.1.2 User Manual Chapter 4: Antennas and Equipment
AT312_UM_E1
4.1.2 Importing Planet-Format Antennas In Atoll, you can import Planet-format antennas by importing an index file listing the individual antenna files to be imported. Standard Atoll fields are directly imported. Other fields are imported for information only and are accessible on the Other Properties tab of the Antenna Properties dialogue. If you are working with a database, you will have to create the required fields before you import the Planet-format antennas. For more details, see the relevant technical note. To import Planet-format antennas: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click the Antennas folder. The context menu appears. 4. Select Import from the context menu. The Open dialogue appears. 5. Select "Planet 2D Antenna Files® (index)" from the Files of type list. 6. Select the index file you want to import and click Open. The antennas are imported. Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns are correctly aligned when: • •
the horizontal pattern attenuation at 0° is the same as the vertical pattern attenuation at the pattern electrical tilt angle, and the horizontal pattern attenuation at 180° is the same as the vertical pattern attenuation at the 180° less the pattern electrical tilt angle.
4.1.3 Importing 3-D Antenna Patterns You can import three-dimensional antenna patterns in the form of text files. The three-dimensional antenna patterns you import are saved in the Antennas table. During calculations, Atoll interpolates the data of antennas for which only horizontal and vertical cross-sections are available to create a three-dimensional pattern. When you import a three-dimensional antenna pattern, even though only horizontal and vertical sections of the antenna pattern are displayed, Atoll conserves all the information and can use it directly; Atoll does not therefore need to interpolate to recreate the three-dimensional antenna pattern. The text file must have the following format: •
Antenna description: Three separate values are necessary to describe the three-dimensional antenna pattern. The columns containing the values can be in any order: • • •
Azimuth: The range of values allowable is from 0° to 360°, with the smallest allowable increment being 1°. Tilt angle: The range of values allowable is from -90 to 90°, or from 0 to 180°, with the smallest allowable increment being 1°. Attenuation: The attenuation (in dB).
The text file describing the antenna can also contain a header with additional information. When you import the antenna pattern you indicate where the header ends and where the antenna pattern itself begins. To import three-dimensional antenna pattern files: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click the Antennas folder. The context menu appears. 4. Select Import from the context menu. The Open dialogue appears. 5. Select the file to import. 6. Click Open. The Setup dialogue appears (see Figure 4.2).
173
Atoll 3.1.2 User Manual Chapter 4: Antennas and Equipment
© Forsk 2012
Figure 4.2: Importing a 3-D antenna pattern 7. If you already have an import configuration defining the data structure of the imported file, you can select it from the Configuration list. If you do not have an import configuration, continue with step 8. a. Under Configuration, select an import configuration from the Configuration list. b. Continue with step 11. 8. Under Name, you can define a name for the imported antenna pattern. This name will appear in the Antennas folder in the Network explorer. If no name is defined, Atoll will use the file name as the name of the antenna: • •
If the name of the antenna is in the file, check the Value read in the file check box and enter a Keyword identifying the name value in the file. If you want to enter a name for the antenna, clear the Value read in the file check box and enter a name.
9. Under Gain, you can define the antenna gain. If no gain is defined, Atoll will assume that the gain is "0." • •
If the gain of the antenna is in the file, check the Value read in the file check box and enter a Keyword identifying the gain value in the file. If you want to enter a gain for the antenna, clear the Value read in the file check box and enter a gain value.
10. Under Diagram, you define the structure of the antenna pattern file. As you modify the parameters, the results are displayed in the table. • • • •
1st Pattern: Select the first row of the file containing data on the antenna pattern. File Tilt Range: Select the tilt range in the file. The tilt range can be measured from top to bottom or from bottom to top and from 0° to 180° or from -90° to 90°. Field Separator: Select the character that is used in the file to separate fields (" ", "", ";") Decimal Symbol: Select the decimal symbol.
11. In the table under Diagram, click the title in each column in the table and select the data type: Azimuth, Tilt, Attenuation, or . As you modify the parameters, the results are displayed in the table. You can save the choices you have made in the Setup dialogue as a configuration file by clicking the Save button at the top of the dialogue and entering a name for the configuration. The next time you import a three-dimensional antenna pattern file, you can select the same settings from the Configuration file list. 12. Click Import. The antenna patterns are imported into the current Atoll document.
174
Atoll 3.1.2 User Manual Chapter 4: Antennas and Equipment
AT312_UM_E1
4.1.4 Displaying Antenna Patterns With a Fixed Scale Atoll displays the vertical and horizontal antenna patterns using a scale that is automatically adjusted to the highest and the lowest attenuation values of the antenna being displayed. You can, however, display all antennas using a fixed scale in order to visually compare or print antenna patterns. To set the antenna pattern display scale: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click the Antennas folder. The context menu appears. 4. Select Display Patterns Using a Fixed Scale from the context menu. Atoll determines the lowest and the highest antenna attenuation values of all the antennas in the Antennas folder, and uses these values to set the pattern scale. Antenna patterns of all the antennas are now displayed using this scale.
4.1.5 Smoothing an Antenna Pattern Empirical propagation models, such as the Standard Propagation Model (SPM), require antenna pattern smoothing in the vertical plane to better simulate the effects of reflection and diffraction, which, therefore, improves signal level prediction. In Atoll, you can smooth antennas’ vertical as well as horizontal patterns. You should make a copy of the antenna before smoothing its vertical pattern. You can make a copy of the antenna by opening the Antennas table and copying and pasting the antenna data into a new row. For information on data tables, see "Working with Data Tables" on page 69. To smooth the vertical or horizontal pattern of an antenna: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Click the Expand button ( ) to expand the Antennas folder. 4. Right-click the antenna whose pattern you want to smooth. The context menu appears. 5. Select Properties from the context menu. 6. Select the Vertical Pattern or the Horizontal Pattern tab. 7. Right-click the graphical representation of the pattern. The context menu appears. 8. Select Smooth from the context menu. The Smoothing Parameters dialogue appears. 9. Enter the following parameters and click OK to smooth the vertical pattern: • • •
Max Angle: Enter the maximum angle. Smoothing will be applied to the section of the vertical pattern between 0° and the maximum angle (clock-wise). Peak-to-Peak Deviation: Enter the attenuation values to which smoothing will be applied. Atoll will smooth all attenuation values greater than or equal to the peak-to-peak deviation with the defined correction factor. Correction: Enter the correction factor by which the attenuation values will be smoothed.
10. Click OK.
4.1.6 Printing an Antenna Pattern You can print the horizontal or vertical pattern of an antenna. To print an antenna pattern: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click the Antennas folder. The context menu appears. 4. Select Open Table from the context menu. The Antennas table appears. 5. In the Antennas table, right-click the antenna whose pattern you want to print. 6. Select Record Properties from the context menu. The Properties dialogue appears. 7. Select the Horizontal Pattern tab or the Vertical Pattern tab to display the antenna pattern you want to print.
175
Atoll 3.1.2 User Manual Chapter 4: Antennas and Equipment
© Forsk 2012
8. Right-click the antenna pattern and select Linear or Logarithmic from the context menu. 9. Right-click the antenna pattern again and select Print from the context menu.
4.2 Working With Equipment Atoll can model the components of base station. You can define these components and modify their properties in their respective tables. Atoll uses these properties to calculate the downlink and uplink losses and transmitter noise figure in UMTS, CDMA2000, WiMAX, or LTE. In GSM, Atoll calculates the downlink losses only. These parameters can be automatically calculated by Atoll from the properties of the components or they can defined by the user. Base station subsystems consist of the following components: •
• •
Tower-mounted amplifier: Tower-mounted amplifiers (TMAs, also referred to as masthead amplifiers) are used to reduce the composite noise figure of the base station. TMAs are connected between the antenna and the feeder cable. To define a TMA, see "Defining TMA Equipment" on page 176. Feeder cables: Feeder cables connect the TMA to the antenna. To define feeder cables, see "Defining Feeder Cables" on page 176. Transmitter equipment: To define transmitter equipment, see "Defining Transmitter Equipment" on page 176.
4.2.1 Defining TMA Equipment The tower-mounted amplifier (TMA) is used to reduce the composite noise figure of the base station. Once you have defined a TMA, you can assign it to individual transmitters. To create a tower-mounted amplifier: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click the TMA folder. The context menu appears. 4. Select Open Table from the context menu. The TMA table appears. 5. In the table, create one TMA per row. For information on using data tables, see "Working with Data Tables" on page 69. For each TMA, enter: • • • •
Name: Enter a name for the TMA. This name will appear in other dialogues when you select a TMA. Noise Figure (dB): Enter a noise figure for the TMA. Reception Gain (dB): Enter a reception (uplink) gain for the TMA. This must be a positive value. Transmission Losses (dB): Enter transmission (downlink) losses for the TMA. This must be a positive value.
4.2.2 Defining Feeder Cables Feeder cables connect the TMA to the antenna. Once you have defined feeder cables, you can assign them to individual transmitters. To create feeder cables: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click the Feeders folder. The context menu appears. 4. Select Open Table from the context menu. The Feeder table appears. 5. In the table, create one feeder per row. For information on data tables, see "Working with Data Tables" on page 69. For each feeder, enter: • • • •
Name: Enter a name for the feeder cable. This name will appear in other dialogues when you select a feeder cable. Loss per Length: Enter the loss per meter of cable. This must be a positive value. Connector Reception Loss: Enter the connector reception loss. This must be a positive value. Connector Transmission Loss: Enter the connector transmission loss. This must be a positive value.
4.2.3 Defining Transmitter Equipment Transmitter equipment is modelled for UMTS, CDMA2000, TD-SCDMA, WiMAX, and LTE. In GSM, only the downlink losses are modelled. Once you have defined transmitter equipment, it can be assigned to individual transmitters.
176
Atoll 3.1.2 User Manual Chapter 4: Antennas and Equipment
AT312_UM_E1
To create transmitter equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click the Transmitter Equipment folder. The context menu appears. 4. Select Open Table from the context menu. The Transmitter Equipment table appears. 5. In the table, create one entry per row. For information on data tables, see "Working with Data Tables" on page 69. For each transmitter equipment entry, enter: • • • • •
Name: Enter a name for the transmitter equipment. This name will appear in other dialogues when you select transmitter equipment. Noise Figure (dB): Enter the noise figure for the transmitter equipment. This value is not used in GSM GPRS EDGE documents. Downlink Losses Due to the Configuration (dB): Enter the losses on downlink due to the transmitter equipment configuration. Uplink Losses Due to the Configuration (dB): Enter the losses on uplink due to the transmitter equipment configuration. This value is not used in GSM GPRS EDGE documents. CDMA Rho Factor (%): Enter the CDMA Rho factor, as a percentage. The CDMA Rho factor enables Atoll to take into account self-interference produced by the transmitter equipment. Because equipment is not perfect, an input signal will experience some distortion, consequently the output signal will be not be identical. This factor defines how much distortion the system generates. Entering 100% means the system is perfect (there is no distortion) and the output signal will be 100% identical to the input signal. On the other hand, if you specify a value different from 100%, Atoll will consider that the transmitted signal is not 100% signal and that it contains a small percentage of interference generated by the equipment ("self-interference"). Atoll uses this parameter to evaluate the signalto-noise ratio in the downlink. This value is only used in CDMA-based technologies (CDMA2000, UMTS, and TD-SCDMA). It is not used in GSM, WiMAX, and LTE documents.
4.2.4 Updating the Values for Total Losses and the Transmitter Equipment Noise Figure Once equipment is defined and assigned to a transmitter, Atoll can evaluate downlink and uplink total losses and the total noise figure. Atoll uses the entry of the transmitter equipment as the reference point when evaluating total losses and the total noise figure. The transmitter equipment noise figure used by Atoll is the one specified in the transmitter equipment properties. Transmitter reception losses include feeder reception losses, connector reception losses, miscellaneous reception losses, antenna diversity gain, TMA benefit gain (as calculated using the Frii’s 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 transmitter’s Properties dialogue, or Using the Transmitters table, available by right-clicking the Transmitters folder in the Network explorer and selecting Open Table from the context menu.
When you assign equipment to a transmitter using the Equipment Specifications dialogue, Atoll updates the real values when you click OK and close the dialogue. When you assign equipment to a transmitter using the Transmitters table, Atoll does not update the real values automatically. To update the real values (total losses and transmitter equipment noise figure) with the calculated values of all transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Calculations > Update Losses and Noise Figures from the context menu. To update the real values (total losses and transmitter equipment noise figure) with the calculated values of a group of transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Click Group by in the context menu and select the property by which you want to group the transmitters from the Group by submenu. The objects in the folder are grouped by that property.
177
Atoll 3.1.2 User Manual Chapter 4: Antennas and Equipment
© Forsk 2012
4. Click the Expand button ( ) to expand the Transmitters folder. 5. Right-click the group of transmitters whose real values you want to update. The context menu appears. 6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the selected group. 7. In the Transmitters table, select the values you want to update in the following columns and press DEL: • • •
Transmission Loss (dB) Reception Loss (dB) Noise Figure (dB)
Atoll automatically recalculates and updates these values.
178
Chapter 5 Working with Calculations in Atoll This chapter provides the information to work with calculations in Atoll.
In this chapter, the following are explained: •
"Working with Propagation Models" on page 181
•
"Defining Calculation Parameters" on page 199
•
"Managing Path Loss Matrices" on page 201
•
"Predictions Available in Atoll" on page 212
Atoll 3.1.2 User Manual Chapter 5: Starting a Project
180
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
5 Working with Calculations in Atoll Once you have created a network, you can make predictions. There are two types of predictions: •
•
Point predictions using the Point Analysis tool: The Point Analysis tool allows you to predict, at any point on the map, the profile between a reference transmitter and a receiver, the value of the signal levels of the surrounding transmitters, an active set analysis for UMTS, CDMA2000, and TD-SCDMA projects and an interference analysis for GSM/GPRS/ EDGE projects. Coverage predictions: You can calculate standard coverage predictions, coverage by transmitter, coverage by signal level and overlapping zones, and specific coverage predictions such as interference predictions for GSM/GPRS/EDGE projects or handover, service availability, etc. for UMTS, CDMA2000 and TD-SCDMA projects. Many customisation features on coverage predictions are available in order to make their analysis easier.
Atoll facilitates the calculation of coverage predictions with support for multithreading and distributed calculating. The progress of the calculations can be displayed in the Event Viewer window or in a log file. Atoll also allows you to use polygonal zones to limit the amount of resources and time used for calculations. The polygonal zones, such as the filtering zone and the computation zone, help you to restrict calculations to a defined set of transmitters, and to limit calculations and coverage predictions. Depending on the type of project you are working on, you can choose between the propagation models available in Atoll.
5.1 Working with Propagation Models In the section, the following are explained: • • • • • • • • • • • • • •
"Propagation Model Characteristics: Overview" on page 181 "The Standard Propagation Model" on page 182 "The Okumura-Hata Propagation Model" on page 189 "The Cost-Hata Propagation Model" on page 190 "The ITU 529-3 Propagation Model" on page 192 "The ITU 370-7 Propagation Model" on page 193 "The Erceg-Greenstein Propagation Model" on page 193 "The ITU 526-5 Propagation Model" on page 195 "The WLL Propagation Model" on page 195 "The Longley-Rice Propagation Model" on page 196 "The ITU 1546 Propagation Model" on page 196 "The Sakagami Extended Propagation Model" on page 197 "CrossWave Model" on page 197 "Managing Propagation Models" on page 198.
5.1.1 Propagation Model Characteristics: Overview Each propagation model available in Atoll is suited for certain conditions, frequencies and radio technologies. The following table summarises the frequency band, necessary geo data, recommended use of each propagation model. Model
Frequency Range
Geo Data Taken into Account
Recommended Use
ITU 370-7 Vienna 93
100 – 400 MHz
Terrain profile
d > 10 km Low frequencies Broadcast
ITU 1546
30 – 3000 MHz
Terrain profile
1 < d < 1000 km Land and maritime mobile, broadcast
ITU 526-5 (theoretical)
30 – 10000 MHz
Terrain profile
Fixed receivers WLL
WLL
30 – 10000 MHz
Terrain profile Deterministic clutter
Fixed receivers WLL, Microwave links, WiMAX
150 – 1000 MHz
Terrain profile Statistical clutter (at the receiver)
1 < d < 20 km GSM 900, CDMA2000, LTE
Okumura-Hata (Automatic calibration available)
181
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
Model
© Forsk 2012
Frequency Range
Geo Data Taken into Account
Recommended Use
1500 – 2000 MHz
Terrain profile Statistical clutter (at the receiver)
1 < d < 20 km GSM 1800, UMTS, CDMA2000, LTE
300 – 1500 MHz
Terrain profile Statistical clutter (at the receiver)
1 < d < 100 km GSM 900, CDMA2000, LTE
150 – 3500 MHz
Terrain profile Statistical clutter
1 < d < 20 km GSM, UMTS, CDMA2000, WiMAX, LTE
Terrain profile Statistical clutter (at the receiver)
Urban and suburban areas 100 m < d < 8 km Fixed WiMAX
3000 – 8000 MHz
Terrain profile Statistical clutter
1 < d < 20 km WiMAX
200 – 5000 MHz
Terrain profile Statistical or deterministic clutter 3D building and line vectors (optional) Specific morphology, facets and graphs data files (optional)
Any engineering (micro, mini, small and macro cells) GSM, UMTS, CDMA2000, WiMAX, LTE
Cost-Hata (Automatic calibration available) ITU 529-3 Standard Propagation Model (Automatic calibration available) Erceg-Greenstein (SUI) 1900 – 6000 MHz Sakagami Extended (Automatic calibration available)
CrossWave Model
5.1.2 The Standard Propagation Model The Standard Propagation Model is a propagation model based on the Hata formulas and is suited for predictions in the 150 to 3500 MHz band over long distances (from one to 20 km). It is best suited to GSM 900/1800, UMTS, and CDMA2000 radio technologies. The Standard Propagation Model is based on the following formula: K 1 + K 2 × Log ( d ) + K 3 × Log ( H Txeff ) + K 4 × DiffractionLoss + K 5 × Log ( d ) × Log ( H Txeff ) + P R = P Tx – K 6 × H Rx eff + K 7 × Log ( H Rx eff ) + K clutter × f ( clutter ) + K hill, LOS
where: •
PR
received power (dBm)
•
PTx
transmitted power (EIRP) (dBm)
•
K1
constant offset (dB)
•
K2
multiplying factor for Log(d)
•
d
distance between the receiver and the transmitter (m)
•
K3
multiplying factor for Log(HTxeff)
•
H Tx
•
K4
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)
•
K6
multiplying factor for HRxeff
•
K7
multiplying factor for Log(HRxeff)
•
H Rx
•
Kclutter
multiplying factor for f(clutter)
•
f(clutter)
average of weighted losses due to clutter
•
Khill, LOS
corrective factor for hilly regions (=0 in case of NLOS)
•
182
eff
eff
mobile antenna height (m)
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
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 183 "Calculating Diffraction With the SPM" on page 184 "Sample Values for SPM Formulas" on page 184 "Calculating f(clutter) with the Standard Propagation Model" on page 185 "Modelling Fixed Receivers" on page 186 "Defining the Parameters of the Standard Propagation Model" on page 186.
5.1.2.1 Recommendations for Working with the Standard Propagation Model It is important to remember that clutter information can be taken into consideration in both diffraction loss and f(clutter). To avoid taking clutter information into account twice, you should choose one of the following approaches: •
Approach #1: If you specify losses per clutter class, do not consider clutter altitudes in diffraction loss over the transmitter-receiver profile. This approach is recommended if the clutter height information is statistical (i.e., where the clutter is roughly defined and without a defined altitude). Because the Standard Propagation Model is a statistical propagation model, using this approach is recommended.
•
Approach #2: If you consider clutter altitudes, do not define any loss per clutter class. In this case, f(clutter) will be "0;" losses due to clutter will only be taken into account in the calculated diffraction. This approach is recommended if the clutter altitude information is semi-deterministic (i.e., where the clutter is roughly defined with an average altitude per clutter class) or deterministic (i.e., where the clutter is sharply defined with an average altitude per clutter class or where there is a clutter height file). If the clutter height information is an average height defined for each clutter class, you must specify a receiver clearance per clutter class. Both ground and clutter altitude are considered along the whole transmitter-receiver profile except over a specific distance around the receiver (clearance), in which Atoll bases its calculations only on the DTM. The clearance information is used to model streets because it is assumed that the receiver is in the street. It is not necessary to define receiver clearance if the height information is from a clutter height file. In this case, the clutter height information is accurate enough to be used without additional information such as clearance; Atoll calculates the path loss if the receiver is in the street (if the receiver height is higher than the clutter height). If the receiver height is lower than the clutter height, the receiver is assumed to be inside a building. In this case, Atoll does not consider any diffraction for the building (or any clearance) but takes into account the clutter class indoor loss as an additional penetration loss. Nevertheless, Atoll does consider diffraction caused by surrounding buildings. In Figure 5.1 on page 184 this diffraction is displayed with a green line. In order to consider indoor losses inside a building when only using a deterministic clutter map (i.e., a clutter height map), you must clear the Indoor Coverage check box when creating a prediction or indoor losses will be added twice (once for the entire reception clutter class and once as indoor losses).
183
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
Figure 5.1: Diffraction caused by surrounding buildings when the receiver is indoors
5.1.2.2 Calculating Diffraction With the SPM You can set the parameters used to calculate diffraction losses on the Parameters and Clutter tabs of the Standard Propagation Model Properties dialogue. In the Parameters explorer, you can define the calculation method used for diffraction and the K4 factor. The methods available are: • • • •
Deygout Epstein-Peterson Deygout with correction Millington
For detailed information on each method, see the Technical Reference Guide. The methods for calculating diffraction are based on the general method for one or more obstacles described in the ITU 526-5 recommendations. The calculations take the curvature of the earth into account. Along the transmitter-receiver profile, you can choose to take either the ground altitude only or both the ground altitude and the clutter height into account. If you choose to take clutter height into account, Atoll uses the clutter height information in the clutter heights file. Otherwise, it uses average clutter height specified for each clutter class in the clutter classes. When the clutter height information is statistical, Atoll also uses clearance values per clutter class to model streets. To take heights into account when calculating diffraction: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Propagation Models folder. 3. Right-click Standard Propagation Model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Clutter tab. 6. Under Heights, select one of the following for Clutter taken into account in diffraction: • •
1 - Yes: Select "1 - Yes" if you want heights from the clutter heights to be taken into account on top of the DTM when calculating diffraction. 0 - No: Select "0 - No" if you want diffraction to be calculated using only the DTM.
7. Click OK.
5.1.2.3 Sample Values for SPM Formulas The following table gives some possible values for the constants used in the Standard Propagation Model formulas.
K1
184
Minimum
Typical
Maximum
Variable
Variable
Variable
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
Minimum
Typical
Maximum
K2
20
44.9
70
K3
-20
5.83
20
K4
0
0.5
0.8
K5
-10
-6.55
0
K6
-1
0
0
K7
-10
0
0
It is recommended to set K6 to 0, and use K7 instead of K6. K6 is a multiplicative coefficient to a value in dB, which means that slight variations in K6 have considerable impact on the path loss. K1 is a constant; its value depends on the radio frequency. The following table gives some possible values for K1. Frequency (MHz)
K1
935
12.5
1805
22
1930
23
2110
23.8
1900
23
2300
24.7
2500
25.4
2700
26.1
3300
27.8
3500
28.3
Its value is heavily influenced by the values given to losses per clutter class.
5.1.2.4 Calculating f(clutter) with the Standard Propagation Model The average of weighted losses due to clutter, f(clutter), is defined as follows: n
f ( clutter ) =
Li × wi i=1
where L: loss due to clutter. w: weight. n: number of points taken into account over the profile. The losses due to clutter are calculated for the maximum distance from the receiver, defined as Maximum Distance on the Clutter tab of the Standard Propagation Model Properties dialogue. When the Maximum Distance is defined as "0", Atoll only considers the losses on the pixel where the receiver is located. On the Clutter tab, each clutter class is assigned losses and a weighting function, enabling Atoll to give a weight to each point. For more information, see the Technical Reference Guide. The losses per clutter class can be calculated using the Automatic Calibration Wizard. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide.
185
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
The following table gives typical values for losses (in dB) per clutter class: Clutter Class
Losses (dB)
Dense urban
from 4 to 5
Woodland
from 2 to 3
Urban
0
Suburban
from -5 to -3
Industrial
from -5 to -3
Open in urban
from -6 to -4
Open
from -12 to -10
Water
from -14 to -12
The Standard Propagation Model is based on Hata formulas, which are valid for an urban environment. The values above are consistent with an urban environment because losses of 0 dB are indicated for an urban clutter class, with positive values for more dense clutter classes and negative values for less dense clutter classes.
5.1.2.5 Modelling Fixed Receivers The following are suggestions for defining the height of fixed receivers: •
•
You can model the receiver as always being above the clutter, by selecting "1 - Yes" for the Receiver on Top of Clutter option on the Clutter tab of the Standard Propagation Model Properties dialogue. The receiver height will then be sum of the clutter height and the receiver height. This option can be used to model receivers on top of buildings, for example. You can define a specific receiver height for each clutter class in the Rx Height column on the Clutter tab of the Standard Propagation Model Properties dialogue. Or, you can select "(default)" for the receiver height. When creating a coverage prediction, Atoll will then read the receiver height on the Calculation Parameters tab of the Network Settings Properties dialogue in the Parameters explorer.
5.1.2.6 Defining the Parameters of the Standard Propagation Model You can define the parameters of the Standard Propagation Model using the Standard Propagation Model Properties dialogue. Default values have been assigned to the multiplying factors. The default values correspond to the rural (quasi-open) Okumura-Hata formula valid for a frequency of 935 MHz. The values for K values can be calculated using an automatic or assisted calibration method. For more information, see the Measurements and Model Calibration Guide. To define the calculations parameters of the Standard Propagation Model: 1. Select the Parameters explorer. 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.2).
186
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
Figure 5.2: Standard Propagation Model - Parameters tab Under Near Transmitter, you can set the following parameters: •
• •
Maximum Distance: Set the maximum distance for a receiver to be considered near the transmitter. If the distance between the receiver and the transmitter is greater than the set distance, the receiver is considered far from the transmitter. K1 - los and K2 - los: Enter the K1 and K2 values that will be used for calculations when the receiver is in the transmitter line of sight. K1 - nlos and K2 - nlos: Enter the K1 and K2 values that will be used for calculations when the receiver is not in the transmitter line of sight.
Under Far from Transmitter, the values you set will be used for all receivers whose distance from the transmitter is greater than the distance specified in Maximum Distance under Near Transmitter. You can set the following parameters: • •
K1 - los and K2 - los: Enter the K1 and K2 values that will be used for calculations when the receiver is in the transmitter line of sight. K1 - nlos and K2 - nlos: Enter the K1 and K2 values that will be used for calculations when the receiver is not in the transmitter line of sight. The LOS is defined by no obstruction along the direct ray between the transmitter and the receiver.
Under Effective Antenna Height, you can set the following parameters: •
Method: Select the method that will be used to calculate HTxeff, the effective antenna height. You can use the Automatic Calibration Wizard to select the best method for calculating the effective Tx antenna height. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide.
•
Distance min. and Distance max.: The Distance min. and Distance max. are set to 3,000 m and 15,000 m (according to ITU recommendations) for frequencies under 500 MHz and to 0 m and 15,000 m (according to ITU recommendations) for high frequency mobile communications. These values are only used for the "Abs Spot Ht" and the "Enhanced Slope at Receiver" methods. For more information on how these values are used, see the Technical Reference Guide.
187
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
•
© Forsk 2012
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.
Under Other Parameters, you can set the following parameters: • •
K5: Enter the K5 value. K6: Enter the K6 value. It is recommended to set K6 to 0, and use K7 instead of K6. K6 is a multiplicative coefficient to a value in dB, which means that slight variations in K6 have considerable impact on the path loss.
• • •
•
•
•
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 Hata-based propagation model to never calculate a path loss that is lower than the calculated free space loss per pixel. Select "1 - Yes" if you want the propagation model to limit the path loss calculated per pixel to the calculated free space loss. Profiles: Select the method to be used to extract the profile. If you select "1 - Radial," Atoll establishes a profile between each transmitter and each point located on its calculation perimeter (as defined by the calculation radius) and then uses the nearest profile to make a prediction on a point inside the calculation perimeter. This process is called radial optimisation. If you select "2 - Systematic," Atoll systematically determines a profile between each transmitter and each point in its calculation area. This method requires a significantly longer calculation time, therefore, you should choose "1 - Radial" if you want a shorter calculation time. Grid Calculation: Select "0 - Centred" if you want Atoll to perform the calculations at the centre of each pixel or select "1 - Bottom left" if you want Atoll to perform the calculations at the lower left of each pixel.
6. Click the Clutter tab (see Figure 5.3).
Figure 5.3: Standard Propagation Model - Clutter tab Under Clutter Taken into Account, you can set the following parameters under Heights: • • •
188
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. Indoor calculations only: Select "1 - Yes" to create coverage predictions based on indoor calculations only.
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
Under Clutter Taken into Account, you can set the following parameters under Range: • •
Max. distance: Set the maximum distance from a receiver to be considered when calculating f(clutter). Weighting function: Select a weighting function to be used when calculating f(clutter). It enables you to weight losses for each pixel between a receiver and a maximum distance. For more information on weighting functions, see the Technical Reference Guide.
Under Parameters per clutter class, you can set the following parameters for each clutter class: • •
•
Losses: Enter, if desired, losses for each clutter class to be considered when calculating f(clutter). Clearance: Enter, if desired, a clearance around each receiver for each clutter class. The clearance information is used to model streets because it is assumed that the receiver is in the street. The clearance is used when calculating diffraction when statistical clutter is taken into account. Rx Height: Enter, if desired, a specific receiver height for each clutter class. Or, you can select "(default)" for the receiver height. When creating a coverage prediction, Atoll will then read the receiver height on the Calculation Parameters tab of the Network Settings Properties dialogue in the Parameters explorer.
7. Click OK.
5.1.3 The Okumura-Hata Propagation Model The Okumura-Hata model is suited for predictions in the 150 to 1000 MHz band over long distances (from one to 20 km). It is best suited to GSM 900 and CDMA 1xRTT radio technologies. Hata models in general are well adapted to the urban environment. You can define several corrective formulas and associate a formula with each clutter class to adapt the Hata model to a wide variety of environments. You can also define a default formula to be used when no land use data is available. Additionally, you can consider diffraction losses based on the DTM. In this section, the following are explained: • • •
"Defining General Settings (Okumura-Hata)" on page 189 "Selecting an Environment Formula (Okumura-Hata)" on page 189 "Creating or Modifying Environment Formulas (Okumura-Hata)" on page 190.
5.1.3.1 Defining General Settings (Okumura-Hata) To set general parameters on the Okumura-Hata propagation model: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Propagation Models folder. 3. Right-click Okumura-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. You can modify the following settings: •
•
Add diffraction loss: The Okumura-Hata propagation model can take into account losses due to diffraction, using a 1-knife-edge Deygout method, and using the ground altitude given in the DTM. For detailed information on the Deygout method, see the Technical Reference Guide. The calculations take the curvature of the earth into account. Select "1 - Yes" if you want the propagation model to add losses due to diffraction. You can weight this diffraction for each Hata environment formula (see "Creating or Modifying Environment Formulas (Okumura-Hata)" on page 190) Limitation to free space loss: When using a Hata-based propagation model, it is possible to calculate a theoretical path loss that ends up being lower than the free space loss. In Atoll, you can define any Hata-based propagation model to never calculate a path loss that is lower than the calculated free space loss per pixel. Select "1 - Yes" if you want the propagation model to limit the path loss calculated per pixel to the calculated free space loss.
6. Click OK.
5.1.3.2 Selecting an Environment Formula (Okumura-Hata) The Okumura-Hata propagation model can use an environment formula appropriate to each clutter class when calculating. You can assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. To select environment formulas: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Propagation Models folder. 3. Right-click Okumura-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears.
189
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
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 190. 9. Click OK. Correction terms can be evaluated using the Automatic Calibration Wizard. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide.
5.1.3.3 Creating or Modifying Environment Formulas (Okumura-Hata) Several environment formulas are available with the Okumura-Hata propagation model to model different environments. You can modify existing environment formulas used by the Okumura-Hata propagation model or create new environmental formulas. To create or modify an environment formula: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Propagation Models folder. 3. Right-click Okumura-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Click the Formulas button. The Formulas dialogue appears. You can do the following: • • •
Add: To create a new formula, click the Add button and modify the parameters of the formula. Delete: To delete a formula, select the formula and click the Delete button. Modify: To modify an existing formula, select the formula and modify the parameters.
7. Click OK to save your changes and close the Formulas dialogue. 8. Click OK. • •
You can weight the diffraction loss by setting the diffraction multiplying factor within the range [0;1]. Constant values and diffraction multiplying factor can be evaluated using the Automatic Calibration Wizard for each environment formula. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide.
5.1.4 The Cost-Hata Propagation Model The Cost-Hata model is suited for coverage predictions in the 1500 to 2000 MHz band over long distances (from one to 20 km). It is best suited to DCS 1800 and UMTS radio technologies. Hata models in general are well adapted to the urban environment. You can define several corrective formulas and associate a formula with each clutter class to adapt the Hata model to a wide variety of environments. You can also define a default formula to be used when no land use data is available. In this section, the following are explained: • • •
190
"Defining General Settings (Cost-Hata)" on page 191 "Selecting an Environment Formula (Cost-Hata)" on page 191 "Creating or Modifying Environment Formulas (Cost-Hata)" on page 191.
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
5.1.4.1 Defining General Settings (Cost-Hata) To set general parameters on the Cost-Hata propagation model: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Propagation Models folder. 3. Right-click Cost-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Parameters tab. You can modify the following settings: •
•
Add diffraction loss: The Cost-Hata propagation model can take into account losses due to diffraction, using a 1knife-edge Deygout method, and using the ground altitude given in the DTM. For detailed information on the Deygout method, see the Technical Reference Guide. The calculations take the curvature of the earth into account. Select "1 - Yes" if you want the propagation model to add losses due to diffraction. You can weight this diffraction for each Hata environment formula (See "Creating or Modifying Environment Formulas (Cost-Hata)" on page 191) 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.4.2 Selecting an Environment Formula (Cost-Hata) The Cost-Hata propagation model can use an environment formula appropriate to each clutter class when calculating. You can assign a default formula that Atoll can use for all clutter classes for which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. To select environment formulas: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Propagation Models folder. 3. Right-click Cost-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Under Formulas assigned to clutter classes, select the Default formula row. Under this grid, choose the appropriate formula in the formula scrolling list. Atoll uses the default environment formula for calculations on any clutter class to which you have not assigned an environment formula or if you do not have clutter classes in your Atoll document. 7. For each clutter class under Formulas assigned to clutter classes, select a formula from the list. 8. For each clutter class under Additional Losses per Clutter Class, enter an optional correction (in dB). This correction acts as an additional loss on the loss calculated by the chosen formula. 9. Click OK.
5.1.4.3 Creating or Modifying Environment Formulas (Cost-Hata) Several environment formulas are available with the Cost-Hata propagation model to model different environments. You can modify existing environment formulas used by the Cost-Hata propagation model or create new environmental formulas. To create or modify an environment formula: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Propagation Models folder. 3. Right-click Cost-Hata. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Configuration tab. 6. Click the Formulas button. The Formulas dialogue appears. You can do the following: • • •
Add: To create a new formula, click the Add button and modify the parameters of the formula. Delete: To delete a formula, select the formula and click the Delete button. Modify: To modify an existing formula, select the formula and modify the parameters.
7. Click OK to save your changes and close the Formulas dialogue.
191
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
8. Click OK. • •
You can weight the diffraction loss by setting the diffraction multiplying factor within the range [0;1]. Constant values and diffraction multiplying factor can be evaluated using the Automatic Calibration Wizard for each environment formula. For information on the Automatic Calibration Wizard, see the Measurements and Model Calibration Guide.
5.1.5 The ITU 529-3 Propagation Model The ITU 529-3 model is suited for predictions in the 300 to 1500 MHz band over long distances (from one to 100 km). It is best suited to the GSM 900 radio technology. Hata models in general are well adapted to the urban environment. You can define several corrective formulas and associate a formula with each clutter class to adapt the Hata model to a wide variety of environments. You can also define a default formula to be used when no land use data is available. In addition, for long distances 20km Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69.
5.2.3 Defining the Same Calculation Parameters for All Transmitters In Atoll, you can choose one set of calculation parameters and assign them to all transmitters. To define the same calculation parameters for all transmitters: 1. Select the Network explorer. 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: • •
200
Select a Propagation Model Enter a Radius and Resolution.
) in the
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
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. Setting a different main or extended matrix to an individual transmitter as explained in "Defining Calculation Parameters for One Transmitter" on page 199 will override this entry. You can also optimise the path loss matrix radii as explained in "Optimising Path Loss Matrix Storage" on page 204.
5.2.4 Defining a Default Propagation Model When you assign a propagation model to a transmitter, you can choose "(Default Model)" from the list of the propagation models available. Atoll will then calculate path loss using the default propagation model set for the project. To define the default propagation model for the Atoll document: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Predictions tab. 5. Select a Default Propagation Model from the list. 6. Click OK. The selected propagation model will be used for predictions for all transmitters whose main propagation model is "(Default model)."
5.2.5 Defining a Default Resolution When the resolution of the path loss matrix is not defined in the transmitter properties, Atoll uses the default resolution set for the Atoll document. Additionally, this resolution is used as the default coverage resolution when you create a new coverage prediction. To define the default resolution of the Atoll document: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Predictions tab. 5. Enter a Default Resolution. By setting an option in the atoll.ini file, you can set Atoll to use the currently defined default resolution if you clear the value entered in the Resolution text box when you create a coverage prediction. That way, if you have many coverage predictions, you can change their resolution by changing the default resolution and recalculating the coverage predictions. Atoll will then calculate them using the updated resolution. For information on changing entries in the atoll.ini file, see the Administrator Manual. 6. Click OK.
5.3 Managing Path Loss Matrices In this section, the following are explained: • • • • • • • •
"Calculating Path Loss Matrices" on page 202 "Stopping Path Loss Matrix Calculation" on page 202 "Setting the Storage Location of Path Loss Matrices" on page 202 "Using Centralised Path Loss Matrices" on page 203 "Checking the Validity of Path Loss Matrices" on page 203 "Optimising Path Loss Matrix Storage" on page 204 "Tuning Path Loss Matrices Using Measurement Data" on page 205 "Exporting Path Loss Matrices" on page 211.
201
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
5.3.1 Calculating Path Loss Matrices When you calculate a coverage prediction, Atoll automatically calculates non-existent and invalid path loss matrices before calculating the prediction. This can take a lot of time if there are many path loss matrices that must be calculated. Consequently, you can calculate path loss matrices separately, when you have more time and computer resources available. In multi-user environments, the administrator is responsible for shared path loss matrices and can calculate them separately. Users can then base calculations on the updated shared path loss matrices. When you calculate a coverage prediction, Atoll calculates only the non-existent and invalid path loss matrices that intersect the rectangle containing the computation zone, whether or not the computation zone is visible. When you manually calculate the path loss matrices as described in this section, Atoll does not take the computation zone into consideration; it calculates all non-existent and invalid path loss matrices of active and filtered transmitters. To calculate path loss matrices: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Calculations > Calculate Path Loss Matrices from the context menu. Atoll calculates all non-existent and invalid path loss matrices of active and filtered transmitters. You can calculate the non-existent and invalid path loss matrices for all transmitters, for a single transmitter, or for a defined group of transmitters, by expanding the Transmitters folder right-clicking either the single transmitter or the defined group of transmitters and selecting Calculations > Calculate Path Loss Matrices from the context menu. You can prevent Atoll from calculating one or more path loss matrices by locking them. You can lock path loss matrices using the Propagation tab of the Transmitters dialogue. You can lock a single path loss matrix by selecting the check box in the Locked column, or more than one by selecting several path loss matrices and then selecting Lock from the context menu.
5.3.2 Stopping Path Loss Matrix Calculation Depending on the size of the path loss matrices, it can take a long time and a lot of computer resources to calculate them. If necessary, you can stop calculation at any point. To stop calculations: •
Click the Stop Calculations button ( ) in the toolbar. Atoll immediately stops all ongoing calculations. The results of calculations that have already been completed, however, will be saved.
5.3.3 Setting the Storage Location of Path Loss Matrices Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radioplanning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. When you save the path loss matrices to an external directory, Atoll creates: • • •
One file per transmitter with the extension LOS for its main path loss matrix A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices: 1. Select the Network explorer. 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 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.
202
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
When you save the path loss files externally, the external files are updated as soon as calculations are performed and not only when you save the Atoll document. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it, if you have updated the path loss matrices. 5. Click OK.
5.3.4 Using Centralised Path Loss Matrices Using centralised path loss matrices is recommended in a multi-user environment when several users are working on the same radio-planning document. In this case, the radio data is stored in a database. An administrator responsible for calculations calculates the path loss matrices of the entire project and saves them in an external folder accessible to all users. This folder is shared by all users and read only. When the user changes his radio data and recalculates the path loss matrices, the changes to the path loss matrices are stored locally; the common path loss matrices are not modified. In other words, the user can read the information from the shared path loss matrices but any changes he makes will be stored locally, either in the ATL file or in a private external folder. Centralised path loss matrices will be recalculated by the administrator and will take into consideration the changes made by all users to the radio data. • • •
For information on calculating path loss matrices, see "Calculating Path Loss Matrices" on page 202. For information on setting the storage location for local path loss matrices, see "Setting the Storage Location of Path Loss Matrices" on page 202. For information on working in a multi-user environment, see the Administrator Manual.
To use pre-calculated path loss matrices: 1. Select the Network explorer. 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. 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 folder’s Properties dialogue.
5. Click OK.
5.3.5 Checking the Validity of Path Loss Matrices Atoll automatically checks the validity of the path loss matrices when calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid before calculating a coverage prediction. To check whether the path loss matrices are valid: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. 5. Select one of the following display options: • •
Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix: • • •
Transmitter: The name of the transmitter. Locked: If the Locked check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a boolean field indicating whether or not the path loss matrix is valid.
203
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
• • • •
© Forsk 2012
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 205 for more information.
6. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 5.5) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.
Figure 5.5: Path loss matrix statistics
5.3.6 Optimising Path Loss Matrix Storage As explained in "Defining Calculation Parameters" on page 199, you can assign calculation radii for main and extended matrices, either for each transmitter, for a group of transmitters or for all the transmitters in a project. The path loss matrices are then calculated from the transmitter to the distance defined by the calculation radii. In some cases, considering the minimum signal required from the point of view of the receiver, calculating large path losses serves no purpose and has negative consequences in terms of calculation time and the storage of path loss matrices. In Atoll, you can re-evaluate the calculation radii of existing path loss matrices by truncating values which would lead to unnecessary received signal levels. To optimise the calculation radius of the main or extended path loss matrices: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Calculations > Optimise Path Loss Matrices from the context menu. 4. Select the matrices (main or extended) for which you want to re-evaluate the calculation radius. 5. For each selected matrix, enter the minimum signal level which are to be used during matrix reduction. After calculation, Atoll will filter out the path losses leading to signal levels lower than these thresholds. If you enter a higher threshold for extended matrices than that for the main matrices, the lower one (that for the main matrices) will be used for extended matrices as well. 6. Click Calculate. Atoll begins evaluating the calculation radii. Atoll first checks to see whether the path loss matrices are valid before optimising their radius. If the path loss matrices are not valid, Atoll does not optimise their radius. Information about the calculation of the path loss matrix radii are listed in the Available Results table. 7. Select one of the following display options: • •
Display all results: All path loss matrices, including those which do not need optimisation, are displayed. Display modified radii only: Only path loss matrices for which the radius have to be optimised are displayed.
The Available Results table lists the following information for each displayed transmitter: • • • • •
Transmitter: The name of the transmitter. Main Radius: The radius of the main path loss matrix before optimisation. Optimised Main Radius: The radius of the main path loss matrix after optimisation. Extended Radius: The radius of the extended path loss matrix before optimisation. Optimised Extended Radius: The radius of the extended path loss matrix after optimisation.
8. Select the Commit check box for each transmitter for which you want to commit the optimised radius (or radii). You can select one, several, or all the results and right-click in order to select, ignore or commit the results.
204
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
9. Click Commit. The calculation radius (or radii) for all transmitters whose Commit check box is selected is updated. Clearing the Main matrices or Extended matrices check box at the top of the dialogue will not prevent the main or extended matrices from being updated if the given check box was selected before you clicked the Calculate button. If the calculation radii of extended matrices are changed, the extended matrices are deleted and will need to be recalculated with the new radius values. •
•
•
Invalid matrices cannot be optimised and have to be calculated prior to the optimisation process (see "Calculating Path Loss Matrices" on page 202 for more information). Invalid (or non-existent) matrices are displayed in red in the available results list. Even if the radius can be evaluated (and committed to the transmitter properties), path losses are not optimised for locked matrices or matrices in a shared directory (see "Using Centralised Path Loss Matrices" on page 203 for more information). These matrices are displayed in grey in the available results list. You can also optimise path loss matrices using the context menu of a transmitter or group of transmitters. Only the matrices of the selected transmitter or transmitters will be optimised.
5.3.7 Tuning Path Loss Matrices Using Measurement Data In Atoll, the path loss matrices are calculated using the propagation model and parameters defined as explained in "Defining Calculation Parameters" on page 199. However, the results calculated by a propagation model can vary from actual measurements. Atoll allows you to use available drive test data paths and CW measurements to increase the accuracy of calculated path loss matrices. When Atoll applies measurement data to path loss matrices, it first strips the effect of the antenna pattern from the data. Therefore, if the antenna parameters change, the same measurement data can be used to tune the path loss matrices because the effect of the antenna pattern is not present in the data. Atoll uses the selected measurement data to tune a user-defined elliptical area around each measurement point. The main axis of the ellipse is oriented in the direction of the transmitter or repeater. Atoll smoothes the differences between tuned path loss matrix points and uncorrected path loss matrix points using an average error calculated between each measured value and the corresponding value in the path loss matrices. When you use measurement data to tune path loss matrices, the results are stored locally. If you are using shared path loss matrices, these results will be automatically deleted when you make a calculation if the FullResyncPrivShared option is set in the atoll.ini file. If you are using shared path loss matrices, you should disable this option before tuning path loss matrices using measurement data. For more information, see the Administrator Manual. When using measurement data to tune path loss matrices, you need to have valid path loss matrices (for more information on path loss matrix validity, see "Managing Path Loss Matrices" on page 201): 1. Define the elliptical area around the measurement point as explained in "Defining the Area to be Tuned" on page 205. 2. Select the measurement data to be used to tune the path loss matrices: •
•
CW Measurements: You select the CW measurements from the CW Measurements folder as explained in "Tuning Path Loss Matrices Using CW Measurements" on page 207. The selected CW measurements will be used to tune the path loss matrices calculated for the site on which the CW measurements were made. Drive Test Data: You select the drive test data path from the Drive Test Data folder as explained in "Tuning Path Loss Matrices Using Drive Test Data" on page 208. The selected measurements from drive test data path will be used to tune the path loss matrices calculated for the selected transmitter.
Atoll replaces existing path loss matrices with the tuned matrices which remain valid as long as the radio configuration of the network does not change. Atoll creates an external folder containing the catalogue of all the tuning paths as explained in "Managing the Path Loss Tuning Points" on page 209. By activating or deactivating the tuning paths, you can select the tuning path to be applied to the existing path loss matrices. Therefore, even if the path loss is recalculated, the path loss is automatically retuned using the active tuning paths.
5.3.7.1 Defining the Area to be Tuned Atoll tunes the path loss matrices over an elliptical area around each measurement point. The main axis of the ellipse is oriented in the direction of the transmitter.
205
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
To define the elliptical area around each measurement point: 1. Select the Network explorer. 2. Right-click the measurement type that you will use to tune the path loss matrices: • •
CW Measurements: If you are going to use CW measurements to tune the path loss matrices, right-click the CW Measurements folder. The context menu appears. Drive Test Data: If you are going to use drive test data to tune the path loss matrices, right-click the Drive Test Data folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Path Loss Tuning Parameters tab (see Figure 5.6).
Figure 5.6: Defining the ellipse for tuning path loss matrices 5. Under Tuning Ellipse, set the following parameters: • •
Radius of the Axis Parallel to Profile: Enter the radius of the ellipse axis oriented in the same direction as the transmitter (or repeater). Radius of the Axis Perpendicular to Profile: Enter the radius of the ellipse axis perpendicular to the transmitter (or repeater).
6. Click OK.
5.3.7.2 Defining Maximum Corrections and Thresholds on Path Loss Tuning Path loss tuning is done in two steps, as described in the Technical Reference Guide: 1. Correction of the entire path loss matrix: A mean error is calculated between each measured value and the corresponding pixel in the path loss matrix. Mean error is calculated for each path loss matrix (main and extended) of each transmitter. This mean error is then applied to all the pixels in the matrix. This tuning is done to smooth local corrections (step 2) of measured values and not the tuned pixels themselves. 2. Local correction for each measured value. In Atoll, you can set a tuning range in order to limit the tuning in the case the difference between the measurements and the predicted measurements is too great. In addition, you can define a level under which the measured signal strength is not used for path loss tuning. To define the tuning range and the measurement threshold for path loss tuning: 1. Select the Network explorer. 2. Right-click the measurement type that you will use to tune the path loss matrices: • •
CW Measurements: If you are going to use CW measurements to tune the path loss matrices, right-click the CW Measurements folder. The context menu appears. Drive Test Data: If you are going to use drive test data to tune the path loss matrices, right-click the Drive Test Data folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Path Loss Tuning Parameters tab (see Figure 5.6). 5. Under Tuning Range, set the following parameters:
206
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
• • •
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.
5.3.7.3 Tuning Path Loss Matrices Using CW Measurements Atoll allows you to use available CW measurements to increase the accuracy of calculated path loss matrices. To use CW measurements to tune path loss matrices: 1. Select the Network explorer. 2. Select how you want to tune the path loss matrices: To tune the path loss matrix for a single transmitter: a. Click the Expand button ( ) to expand the CW Measurement folder. b. In the CW Measurement folder, click the Expand button ( ) to expand the site folder containing the CW measurement path you want to use to tune the path loss matrices. c. Right-click the CW measurement path in the site folder. The context menu appears. d. Select Tune Path Loss Matrices from the context menu. Atoll immediately begins optimising the path loss matrices for the transmitter on which the CW measurement was made. The progress is displayed in the Event Viewer window. To tune the path loss matrices for all transmitters: a. Right-click the CW Measurement folder. The context menu appears. b. Select Tune Path Loss Matrices from the context menu. The Measurement Path Selection dialogue appears (see Figure 5.7).
Figure 5.7: Selecting all CW measurement paths c. Under Measurement Paths, select All. d. Click OK. Atoll begins optimising the path loss matrices for all transmitters on which CW measurements are available. The progress is displayed in the Event Viewer window. To tune the path loss matrices for selected transmitters using selected CW measurement paths: a. Right-click the CW Measurement folder. The context menu appears. b. Select Tune Path Loss Matrices from the context menu. The Measurement Path Selection dialogue appears (see Figure 5.7). c. Under Measurement Paths, select the option beside the list of CW measurements. d. Select the check box corresponding to each transmitter for which you want to tune the path loss matrices. For some transmitters, more than one CW measurement may exist. In this case, selecting the check box for the transmitter will select all the CW measurements. If you do not want to use all CW measurements, click the Expand button ( ) to expand the transmitter list and then select the single CW measurements you want to use.
207
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
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. For repeaters, Atoll also tunes the path loss matrix of both the donor transmitter and the repeater. The contribution of the repeater and donor to the measured value is calculated based on the ratio of calculated values between the repeater signal and the donor signal. Each evaluated contribution is then used as input to tune the path loss matrix of each element. For more information, please refer to the Technical Reference Guide.
5.3.7.4 Tuning Path Loss Matrices Using Drive Test Data Atoll allows you to use available drive test data paths to increase the accuracy of calculated path loss matrices. To use drive test data to tune path loss matrices: 1. Select the Network explorer. 2. Select how you want to tune the path loss matrices: To tune the path loss matrix using a single drive test data path: a. Click the Expand button ( ) to expand the Drive Test Data folder. b. Right-click the drive test data path you want to use to tune the path loss matrices. The context menu appears. c. Select Tune Path Loss Matrices from the context menu. The Path Loss Tuning dialogue appears (see Figure 5.8).
Figure 5.8: Path Loss Tuning dialogue d. Click the For the following transmitters list. The list opens. e. Select the check box for each transmitter whose path loss matrix you want to tune. f. Click the Select the measured signal levels list. The list opens. g. For each transmitter selected from the For the following transmitters list, select the check box for each measured signal strength that will be used to tune the path loss matrices. h. Click OK. Atoll begins optimising the path loss matrices for the transmitter on which the CW measurement was made. The progress is displayed in the 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.9).
208
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
Figure 5.9: Selecting all CW measurement paths c. Under Measurement Paths, select All. d. Click the For the following transmitters list. The list opens. e. Select the check box for each transmitter whose path loss matrix you want to tune. f.
Click the Select the measured signal levels list. The list opens.
g. For each transmitter selected from the For the following transmitters list, select the check box for each measured signal strength that will be used to tune the path loss matrices. h. Click OK. Atoll begins optimising the path loss matrices for the transmitter on which the CW measurement was made. The progress is displayed in the 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.9). c. Under Measurement Paths, select the option beside the list of drive test data paths. d. Select the check box corresponding to the drive test data you want to use to tune the path loss matrices. e. Click the For the following transmitters list. The list opens. f.
Select the check box for each transmitter whose path loss matrix you want to tune.
g. Click the Select the measured signal levels list. The list opens. h. For each transmitter selected from the For the following transmitters list, select the check box for each measured signal strength that will be used to tune the path loss matrices. 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. For repeaters, Atoll also tunes the path loss matrix of both the donor transmitter and the repeater. The contribution of the repeater and donor to the measured value is calculated based on the ratio of calculated values between the repeater signal and the donor signal. Each evaluated contribution is then used as input to tune the path loss matrix of each element. For more information, please refer to the Technical Reference Guide.
5.3.7.5 Managing the Path Loss Tuning Points After tuning the path loss matrices is complete, Atoll creates a tuning measurement file for each transmitter and stores it in a folder with the extension ".tuning". The .pts tuning file contains a header and a list of points defining the measurement data path excluding the antenna losses which means that the measurement data remains valid even if the antenna parameters change. A tuning file can contain several measurement paths, so that several calibrations can be applied successively on a path
209
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
loss matrix and stored in a single tuning file. All the tuning files are stored as a catalogue in the current project. Each single tuning path can be activated or deactivated in order to be automatically applied to path loss matrices, even after recalculation. Tuning files are stored in the same way as path loss matrices, as explained in "Setting the Storage Location of Path Loss Matrices" on page 202. They can be saved on a network and shared between users. To manage the catalogue of the tuning path loss data: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. 5. Select one of the following display options: • •
Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix: • • • • • • •
Transmitter: The name of the transmitter or repeater. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a boolean field indicating whether or not the path loss matrix is valid. Reason for Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here. Size: The size of the path loss matrix for the transmitter. File: If the path loss matrix is not embedded, the location of the file is listed. Tuned: If the check box is selected, the initial path loss matrix obtained by the propagation model has been tuned by the use of real measurement data.
6. Select the tuning path loss matrices you want to manage using the available catalogue by holding CTRL and click the corresponding line in the Available Results table and then right-clicking. The context menu appears. 7. Select Path Loss Tuning Points from the context menu. The Path Loss Tuning Points dialogue appears.
Figure 5.10: 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: • • • •
• • • • • • •
210
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.
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
•
• • •
Total correction (dB): Displays the mean error between each measured value and its corresponding pixel in the path loss matrix. This is the correction which is applied globally to all the matrices during the first step of path loss tuning (For more information, please refer to the Technical Reference Guide). Valid: This is a boolean field indicating whether or not the measurement path data (excluding the antenna information) are valid. Reason for Invalidity: If the measurement path data is indicated as being invalid, the reason is given here. Comments: Additional comments referring to the measurement entry are given in this field. You can edit the comment by right-clicking the line and selecting Properties from the context menu. When path loss tuning entries are changed (e.g., activated or deleted) Atoll suggests deleting the corresponding path loss matrices.
You can import tuning files to replace an existing tuning or to benefit from a path loss tuning done by another user. The PTS files are imported using a DBF file containing all the information relative to matrices and their tuning. To import a path loss tuning catalogue: 1. Select the Network explorer. 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.
5.3.8 Exporting Path Loss Matrices You can export path loss matrices if you want to use the data in another application. To export an Atoll document’s path loss matrices: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. 5. Right-click the Available Results table and select Select All from the context menu. 6. Right-click the Available Results table and select Export from the context menu. The Calculation Results Export dialogue appears (see Figure 5.11). 7. Set the following export parameters: • • •
Directory: Enter the directory you want to store the exported path loss matrices in or click the Browse button ( ) to navigate to it. The directory must already exist. Exported Values: Select the values that are to be exported: Path Loss (dB), Signal Level (dBm), Signal Level (dBµV), or Signal Level (dBµV/m). Format: Select the format of the exported data: BIL Files (*.bil), TXT Files (*.txt) (Separator: tab), or CSV Files (*.csv) (Separator: ";").
211
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
Figure 5.11: Exporting path loss matrices 8. Click OK to export the path loss matrices.
5.4 Predictions Available in Atoll There are two types of predictions available in Atoll: •
•
Point predictions using the Point Analysis tool: It allows you to predict, at any point on the map, the profile between a reference transmitter and a receiver, the value of the signal levels of the surrounding transmitters, quality and interference analysis for any technology, scrambling code (or PN Offset) collision analysis in UMTS/HSPA (or CDMA2000) projects. Coverage predictions: You can calculate standard coverage predictions, coverage by transmitter, coverage by signal level and overlapping zones, and specific coverage predictions such as interference predictions for GSM/GPRS/EDGE projects or handover, service availability, etc. for UMTS, CDMA2000 and TD-SCDMA projects. Many customisation features on coverage predictions are available in order to make their analysis easier.
In this section, the following are explained: • •
"Making Point Predictions" on page 212 "Making Coverage Predictions" on page 215.
5.4.1 Making Point Predictions In this section, the following are explained: • • • • •
"Starting a Point Analysis" on page 212 "The Views of the Point Analysis Tool" on page 212 "Moving the Receiver on the Map" on page 214 "Taking Indoor Losses into Account" on page 214 "Taking Shadowing into Account in Point Analyses" on page 214.
5.4.1.1 Starting a Point Analysis To make a point analysis: 1. Select Tools > Point Analysis. The Point Analysis window appears and the pointer changes ( receiver. This receiver is placed at the centre of the active map.
) to represent the
If a transmitter was already selected on the map, a line appears connecting the selected transmitter and the receiver. 2. Select the view of the Point Analysis window corresponding to the type of point prediction you want to make. For information on the views available in the Point Analysis window, see "The Views of the Point Analysis Tool" on page 212.
5.4.1.2 The Views of the Point Analysis Tool You can access several views from the Point Analysis tool. These views enable you to make several different point predictions. The views available depend on the radio technology of the current document. When opening the Point Analysis, you can select the appropriate view from the list located at the top left part of the window: •
The Profile View: The Profile view ( ) is available in the Point Analysis tool for GSM/GPRS/EDGE, CDMA, UMTS, TD-SCDMA, WiMAX, Wi-Fi, and LTE projects. The Profile view of the Point Analysis tool displays the profile between a reference transmitter and the receiver. As well, Atoll displays the signal level of the received signal from the selected transmitter. You can also display the path loss or total losses of the selected transmitter. In this view, the results are calculated in real time.
212
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
•
The Reception View: The Reception view ( ) is available in the Point Analysis tool for GSM/GPRS/EDGE, CDMA, UMTS, TD-SCDMA, WiMAX, Wi-Fi, and LTE projects. In multi-RAT projects, there are as many Reception views as there are technologies. The Reception view of the Point Analysis tool displays the predicted signal level from different transmitters in the form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom. The calculations are based on the path loss matrices. Each bar is displayed in the colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they represent. The best server for the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest on an arrow, the signal level received from the corresponding transmitter at the pointer location is displayed in the tip text.
•
The AS Analysis View: The AS Analysis view (
) is available in the Point Analysis tool for CDMA and UMTS projects.
The AS Analysis view displays information on the pilot quality (Ec⁄I0), which is the main parameter used to define the mobile active set, the connection status, and the active set of the probe mobile. •
The Interference View: The Interference view ( ) is available in the Point Analysis window for GSM/GPRS/EDGE projects, WiMAX, and LTE projects. In a multi-RAT projects where GSM and LTE are present, there is one reception window for each of these technologies. The Interference view displays, in the form of a bar graph, the signal level of the selected transmitter, a black bar indicating the total interference experienced by the receiver, and bars representing the interference received from each interferer. In the map window, arrows from the receiver towards each transmitter are displayed in the colour of the transmitters they represent. If you let the pointer rest on an arrow, the interference level received from the corresponding transmitter at the receiver location will be displayed in tip text along with information on the channel being interfered and the type of interference, i.e., co- or adjacent channel.
•
The PN Offset Collision View: The PN Offset Collision view (
) is available in the Point Analysis tool for CDMA projects.
The PN Offset Collision view of the Point Analysis tool gives you information on the reception for any point on the map where there is PN Offset collision. •
The SC Collision View: The SC Collision view (
) is available in the Point Analysis tool for UMTS projects.
The SC Collision view of the Point Analysis tool gives you information on reception for any point on the map where there is scrambling code collision. •
The Details View: The Details view ( ) is available in the Point Analysis tool for GSM/GPRS/EDGE, CDMA, UMTS, TD-SCDMA, WIMAX, and LTE projects. In Multi-RAT projects, there are as many Results views as there are technologies. The Details view displays the current position and height of the receiver, the clutter class it is located on. In addition, it also displays: •
in GSM/GPRS/EDGE projects, you can select to display the results on a specific HCS layer (or all). You can also evaluate either C/I or C/I+N values where the interferences are due to any combination between adjacent channels, co-channels or external sources. Atoll displays for each transmitter its BCCH signal level, the BCCH C/I, the most interfered mobile station allocation (TRX, MAL or MAL-MAIO depending on the hopping mode) and its corresponding C/I.
•
in CDMA projects, you can select to display the results for a specific terminal, service, mobility, carrier, DL rate, and UL rate. Atoll displays for each transmitter its signal level (or RSCP), its path loss, Ec/Io, C/I, DL and UL Eb/Nt values, PN offsets.
•
in UMTS/HSPA projects, you can select to display the results for a specific terminal, service, mobility, carrier. Atoll displays for each transmitter its signal level, Ec/Io, DL and UL Eb/Nt values, scrambling codes.
•
in TD-SCDMA projects, Atoll displays for each transmitter its signal level.
•
in WiMAX projects, you can select to display the results for a specific terminal, service, mobility. Atoll displays for each transmitter its preamble index, its preamble signal C, C/N and I.
213
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
•
© Forsk 2012
in LTE projects, you can select to display the results for a specific terminal, service, mobility. Atoll displays for each transmitter its physical cell ID, its reference signal Level, its RSRP and its RS I.
5.4.1.3 Moving the Receiver on the Map When you make a point analysis, the pointer ( of the receiver in several ways: • • •
) represents the receiver in the map window. You can change the position
You can move the receiver manually You can enter the coordinates of the new position You can place the receiver on a selected site.
To change the position of the receiver manually: • •
Click and drag the receiver to change the position. Release the mouse button to place the receiver. You can move the receiver again by clicking and dragging 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 the X and Y coordinates of the position and click OK. The receiver moves to the specified position. To place the receiver on a selected site: 1. Right-click the receiver (
) in the map window. The context menu appears.
2. Select Target Site from the context menu. The Target Site dialogue appears. 3. Select the site on which you want to place the receiver from the Name list and click OK. The receiver moves to the specified position.
5.4.1.4 Taking Indoor Losses into Account In Atoll you can calculate indoor predictions by taking indoor losses into consideration. You can define default indoor losses for all clutter classes, or you can define different indoor losses for each clutter class so that the characteristics of each clutter class are taken into consideration during calculations. To take indoor losses into account when making a point analysis: 1. Click the Options button (
) at the top of the Point Analysis view. The Calculation Options dialogue appears.
2. Select the Indoor Coverage check box to add indoor losses to the total path loss.
5.4.1.5 Taking Shadowing into Account in Point Analyses Shadowing, or slow fading, is signal loss along a path caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be greater and in 50% of the measured cases, the result will be worse. 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 C⁄I standard deviations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. You can take shadowing into account when you are making a point analysis. To take shadowing into account when making a point analysis: 1. Click the Options button (
) at the top of the Point Analysis view. The Calculation Options dialogue appears.
2. Select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Atoll calculates the shadowing using the appropriate standard deviation defined per clutter class.
214
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
5.4.2 Making Coverage Predictions A coverage prediction displays the results of defined coverage conditions. It is calculated using the path loss matrices and is based on coverage conditions and coverage resolutions. After calculation, Atoll displays the results as a graphical representation of the pixels for which the defined coverage conditions are satisfied. Atoll offers the following general coverage predictions, available for all technologies: • • •
Coverage by transmitter Coverage by signal level Coverage by overlapping zones.
Atoll also offers technology-specific coverage predictions, described in the technology-specific chapters, for example: • • •
Interference predictions in GSM/GPRS/EDGE projects Coding scheme and throughput predictions for GPRS/EDGE UMTS or CDMA2000 coverage predictions.
Atoll gives you a large flexibility over how the results of your coverage prediction are displayed. You can select which attributes should be displayed on the map and how they are displayed. As well, you can define information to be displayed in the legend, in the label, or in tip text. 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 215 "Defining the Storage Location of Coverage Prediction Results" on page 216 "Calculating Coverage Predictions" on page 217 "Exporting the Values per Pixel of a Coverage Prediction" on page 219 "Saving Defined Coverage Predictions" on page 219.
5.4.2.1 Creating Coverage Predictions In Atoll, you can create a coverage prediction using several different methods. Each method has its own advantages. For example, you can create a new coverage prediction and set all of the parameters. Or you can base a new coverage prediction on an existing one. In this section, the following ways of creating a coverage prediction are explained: • • •
5.4.2.1.1
"Creating a New Coverage Prediction" on page 215 "Duplicating a Coverage Prediction" on page 216 "Cloning a Coverage Prediction" on page 216.
Creating a New Coverage Prediction When you create a new coverage prediction, you can select the type of coverage prediction and set all the parameters that define it. The newly created coverage prediction is not automatically calculated. To create a coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select a coverage prediction from the Prediction Types dialogue and click OK. The coverage prediction Properties dialogue appears. The Properties dialogue for a coverage prediction common to all technologies has three tabs: •
General tab: You can rename the coverage prediction, define the coverage resolution, add comments, and define where the coverage prediction results are stored. For information on defining the storage location of the coverage prediction results, see "Defining the Storage Location of Coverage Prediction Results" on page 216. You can also define group, sort, and filter criteria; these criteria will apply to the coverage display, not the results.
• •
Condition tab: You can define the parameters of the coverage prediction. Display tab: You can define how coverage prediction results will be displayed.
5. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
For more information on calculating coverage predictions, see "Calculating Coverage Predictions" on page 217.
215
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
5.4.2.1.2
© Forsk 2012
Duplicating a Coverage Prediction You can create a new coverage prediction by duplicating an existing coverage prediction. When you duplicate an existing coverage prediction, the coverage prediction you create will have the same coverage and display settings as the original one. Duplicating a coverage prediction is a way to quickly create a new coverage prediction with the same settings as an original one. The newly created coverage prediction is not automatically calculated. To duplicate an existing coverage prediction: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Predictions folder. 3. Right-click the coverage prediction you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. A new coverage prediction appears in the Predictions folder with the same name as the original coverage prediction, preceded by "Copy of." The duplicated coverage prediction has the same coverage and display settings as the original one. For information on calculating coverage predictions, see "Calculating Coverage Predictions" on page 217.
5.4.2.1.3
Cloning a Coverage Prediction You can create a new coverage prediction by cloning an existing coverage prediction. When you clone an existing coverage prediction, Atoll creates a copy of the coverage prediction with the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the calculated coverage prediction. Cloning is useful if the existing coverage prediction has a display by discrete values (e.g., coverage by transmitter with a display by transmitter) and if you want a new coverage prediction with another display by discrete values (e.g., display by RNC or BSC). In this case, Atoll maps the results to the selected field and you do not need to recalculate the coverage prediction. On the other hand, cloning is not relevant if you change the display from a discrete field to value intervals, in which case, you must recalculate the coverage prediction. To clone an existing coverage prediction: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Predictions folder. 3. Right-click the coverage prediction you want to clone. The context menu appears. 4. Select Clone from the context menu. A new coverage prediction appears in the Predictions folder with the same name as the original coverage prediction, preceded by "Clone of." The cloned coverage prediction not only has the same coverage and display settings as the original one, but keeps the same results as well. 5. Right-click the cloned coverage prediction. The context menu appears. 6. Select Properties from the context menu. The Properties dialogue appears. 7. Select the Display tab. 8. On the Display tab, keep the Display Type "Discrete Values" selected. 9. Select another value from the Field list to change the value displayed. 10. Click OK to apply the new display parameter.
5.4.2.2 Defining the Storage Location of Coverage Prediction Results When you define and calculate a coverage prediction, Atoll stores the results in the Atoll document by default. You can, however, choose to save the coverage prediction results externally. When you are working on extremely large projects, saving results externally can help reduce the size of the Atoll document and the use of computer resources. These results can also have been calculated on a server. You can also include in your document the results of coverage predictions that were calculated on a server. When the original coverage prediction is updated, the results displayed in the current document will also be updated. You can define the storage location of the results either before you calculate the coverage prediction or afterwards. You can not store externally the results of coverage predictions that are calculated by transmitter instead of by level.
To define the storage location of coverage prediction results: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Predictions folder.
216
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
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 prediction’s Properties dialogue appears. 5. On the General tab, click the button beside Folder ( • •
•
) and select the storage location of the results:
Saving in the Atoll document: To store the results in the document, select Embedded. Saving externally: To store the results externally, select the external storage location. Atoll creates a folder for the results in the same folder with the Atoll document and gives it the name of the document, with the extension "studies." Sharing the results of another coverage prediction: To display the results of a coverage prediction that was calculated in a different document, select Connect to Results to navigate to the XML file describing the coverage prediction results.
Externally stored coverage prediction results can be imported as customised coverage predictions. For more information on importing customised coverage predictions, see "Saving Defined Coverage Predictions" on page 219. For a detailed description of the XML file, see Studies.XML in the Administrator Manual.
5.4.2.3 Calculating Coverage Predictions After you have defined a coverage prediction, you can calculate it. Atoll allows you to define and calculate coverage predictions in two separate steps. This enables you to create one or several coverage predictions at one time, and then calculate them later, when you do not need the computer resources. Before calculating one or more coverage predictions, you can create a computation zone. The computation zone is used to define the area where Atoll carries out calculations. When you create a computation zone, Atoll carries out the calculation for all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Therefore, it takes into consideration base stations inside and base stations outside the computation zone if they have an influence on the computation zone. In addition, the computation zone defines the area within which the coverage prediction results will be displayed. The computation zone is taken into account whether or not it is visible. In other words, if you have drawn a computation zone, it will be taken into account whether or not its visibility check box in the Zones folder of the Geo explorer is selected. You will have to delete the computation zone if you no longer want to define an area for calculations. When working with a large network, the computation zone allows you to restrict your coverage predictions to the part of the network you are currently working on. By allowing you to reduce the number of base stations studied, Atoll reduces both the time and computer resources necessary for calculations. As well, by taking into consideration base stations within the computation zone and base stations outside the computation zone but which have an influence on the computation zone, Atoll gives you realistic results for base stations that are close to the border of the computation zone. If there is no computation zone defined, Atoll makes its calculations on all base stations that are active and filtered and for the entire extent of the geographical data available. For information on creating a computation zone, see "The Computation Zone" on page 55. In this section, the following are explained: • • • • •
5.4.2.3.1
"Calculating Several Coverage Predictions" on page 217 "Calculating a Single Coverage Prediction" on page 218 "Forcing Calculations" on page 218 "Stopping Calculations" on page 218 "Locking Coverage Predictions" on page 218.
Calculating Several Coverage Predictions When you have several defined coverage predictions, you can start calculation when you want and Atoll will calculate them one after the other. When you calculate coverage predictions, only unlocked coverage predictions are calculated. Unlocked coverage predictions are displayed in the Predictions folder with the unlocked icon ( predictions, see "Locking Coverage Predictions" on page 218.
). For information on locking and unlocking coverage
To calculate created coverage predictions: •
Click the Calculate button ( ) in the toolbar. When you click the Calculate button, Atoll first calculates non-existent and invalid path loss matrices and then, unlocked coverage predictions in the Predictions folder. The progress of the calculations is displayed in the Event Viewer window. After calculation, the results are displayed in the map window, if the coverage prediction’s visibility check box has been selected.
217
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
5.4.2.3.2
© Forsk 2012
Calculating a Single Coverage Prediction To calculate a single coverage prediction: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Predictions folder. 3. Right-click the coverage prediction you want to calculate. The context menu appears. 4. Select Calculate from the context menu. Atoll first calculates non-existent and invalid path loss matrices and then, the coverage prediction even if this one has been previously locked. After calculation, the results are displayed in the map window, if the coverage prediction’s 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 ( predictions, see "Locking Coverage Predictions" on page 218.
). For information on locking and unlocking coverage
To force Atoll to recalculate all path loss matrices before calculating coverage predictions: •
Click the Force Calculate button ( ) in the toolbar. When you click the Force Calculate button, Atoll first removes existing path loss matrices, recalculates them and then calculates unlocked coverages predictions. After calculation, the results are displayed in the map window, if the coverage prediction’s 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 don’t want to calculate the coverage predictions at that time. To stop calculations: •
5.4.2.3.5
Click the Stop Calculations button ( ) in the toolbar. Atoll immediately stops all ongoing calculations. The results of calculations that have already been completed, however, will be saved.
Locking Coverage Predictions Coverage predictions are locked by default as soon as they have been calculated. Then, when you calculate new coverage predictions, only unlocked coverage predictions are calculated. Locking a coverage prediction retains the information as calculated under given conditions (e.g., before a new base station is created or before optimising the network). It also saves time by limiting unnecessary recalculation. To prevent Atoll from automatically locking coverage predictions after calculating them, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual. To lock a coverage prediction: 1. Select the Network explorer. 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 Prediction Locked from the context menu. The icon changes to the locked icon ( ) and the Prediction Locked item in the context menu now appears checked. The coverage prediction is now locked and will not be calculated when the Calculate button in the toolbar is clicked. However, if you select Calculate from the coverage prediction’s context menu, Atoll will first unlock the coverage prediction and then calculate it. You can lock all unlocked coverage predictions using the Predictions folder’s context menu.
218
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
5.4.2.3.6
Unlocking Coverage Predictions Coverage predictions are locked by default as soon as they have been calculated. You can unlock a single coverage prediction. To unlock a coverage prediction: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Predictions folder. 3. Right-click the coverage prediction you want to unlock. The context menu appears. Locked coverage predictions are displayed in the Predictions folder with the locked icon (
).
4. Select Prediction Locked from the context menu. The icon changes to the unlocked icon (
) and the Prediction Locked item in the context menu is no longer selected.
You can unlock all locked coverage predictions using the Predictions folder’s context menu.
5.4.2.4 Exporting the Values per Pixel of a Coverage Prediction When you are creating a coverage prediction, you can at the same time export the values per pixel, providing that the Display type is "Value intervals" and the Field used in the prediction is a field calculated by the coverage prediction and not a value taken from the database. For example, you can export the values per pixel of a "Coverage by Transmitter" if the Display type is "Value intervals" and the Field is "Signal Level." However, you can not export the values per pixel if the Display type is "Value intervals" and the Field is "Antenna Gain," because although it can be displayed, antenna gain is not a value calculated by the coverage prediction but read from the database. To export the values per pixel of a coverage prediction: 1. Select the Network explorer. 1. Right-click the Predictions folder and select New Prediction from the context menu to create a new coverage prediction or open the Properties dialogue of an existing one. 2. Click the Display tab and select "Value intervals" as the Display type. 3. For the Field, select a field calculated by that coverage prediction. If the Field selected is not one calculated by the coverage prediction but instead one read from the database, Atoll will not export the values.
4. Click the Result Export tab. If the Result Export tab is not available, the results of that coverage prediction can not be exported.
5. Select the Export calculated values check box. 6. Click the Browse button (
) beside the File box. The Save As dialogue appears.
7. Enter a file name for the text file in which the results will be saved. 8. Click Save. The Save As dialogue closes. 9. In Decimal places on the Result Export tab, enter the number of digits after the decimal point for the exported numeric values. 10. Select a Separator. You can choose from tab, comma, semicolon, and space. 11. Click Calculate. The coverage prediction is calculated and the results exported to the selected text file. The exported results are actual calculated values of the studied parameters not the display levels defined in the Display tab of the coverage prediction properties dialogue.
5.4.2.5 Saving Defined Coverage Predictions Once you have defined a coverage prediction, you can use it again in other Atoll documents, either by using the coverage prediction to create a customised coverage prediction or by saving its coverage and display parameters in a user configuration.
219
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
© Forsk 2012
In this section, the following are explained: • •
5.4.2.5.1
"Saving a Coverage Prediction as a Customised Coverage Prediction" on page 220 "Saving a Defined List of Predictions in a User Configuration File" on page 220.
Saving a Coverage Prediction as a Customised Coverage Prediction Once you have defined a coverage prediction, you can use it as a customised coverage prediction. This coverage prediction will be available to you in the Prediction Types dialogue the next time you want to create a new coverage prediction. The initial parameters of the coverage prediction will be the same as the coverage prediction it is based on but, when you select it in the Prediction Types dialogue, Atoll allows you to modify them. To save a coverage prediction as a customised coverage prediction: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Predictions folder. 3. Right-click the coverage prediction you want to save as a customised coverage prediction. The context menu appears. 4. Select Save as Customised Prediction from the context menu. The Save As dialogue appears. In the Save As dialogue, Atoll proposes a name and location for the XML file that will contain the customised coverage prediction. You can accept the default values or you can change the name and save the XML file in any folder you have write access to. 5. Click Save. Atoll saves the coverage prediction in the selected XML file. The next time you create a new coverage prediction, the customised coverage prediction will be available at the bottom of the list, under the full path and file name of the XML file (see Figure 5.12). If you have other XML template files, you can click the Customised Predictions button and select it in the Open dialogue.
Figure 5.12: Prediction Types dialogue Coverage predictions stored in the XML template files are also directly available in the Calculations menu of the context menus of the Transmitters folder, of a group of transmitters, and of a single transmitter. In a multi-user environment, the administrator can make customised predictions available for all the users by saving the XML file in the Atoll installation directory. For more information, see the Administrator Manual.
5.4.2.5.2
Saving a Defined List of Predictions in a User Configuration File You can save the defined coverage predictions in the Predictions folder in a user configuration file. You can then import this user configuration file into another Atoll document. All the coverage predictions in the user configuration will then be available in the Predictions folder of the new Atoll document and can be calculated. To export a user configuration with the coverage predictions in the Predictions folder: 1. Select Tools > User Configuration > Save. The User Configuration dialogue appears. 2. Select the Prediction List check box, as well as the check box of any other information you want to save as part of the user configuration. 3. Click OK. The Save As dialogue appears. 4. Enter a File name for the user configuration file and click Save. The folder configuration is saved. For information on loading the user configuration into another Atoll document, see "Loading a User Configuration" on page 101.
220
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
AT312_UM_E1
5.4.2.6 Calculating Indoor Coverage In Atoll you can calculate indoor coverage by taking the indoor losses into consideration. Indoor losses are defined per clutter class. You can define a default indoor losses value for all clutter classes. Or, you can define a different indoor losses value for each clutter classes, to take the characteristics of each clutter class into consideration. To calculate indoor coverage when making a coverage prediction: •
When creating the coverage prediction, select the Indoor Coverage check box on the Condition tab of the coverage prediction’s Properties dialogue. The indoor losses defined for the clutter classes will be added to the total path loss for each pixel.
5.4.2.7 Taking Shadowing into Account Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations in reception due to the surrounding environment. Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct. In other words, in 50% of the measured cases, the result will be greater and in 50% of the measured cases, the result will be worse. Atoll uses a model standard deviation with the defined cell edge coverage probability to model the effect of shadowing and thereby create coverage predictions that are reliable more than fifty percent of the time. The additional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the path losses calculated by the propagation model. For example, a properly calibrated propagation model calculates a loss leading to a signal level of -70 dBm. You have set a cell edge coverage probability of 85%. If the calculated shadowing margin is 7 dB for a specific point, the target signal will be equal to or greater than -77 dBm 85% of the time. For information on setting the model standard deviation and the C⁄I standard deviations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. •
When creating the coverage prediction, select the Shadowing Taken into Account check box. Then, you can define the Cell Edge Coverage Probability.
"Microwave Link Classes"
on page 171
221
Atoll 3.1.2 User Manual Chapter 5: Working with Calculations in Atoll
222
© Forsk 2012
Chapter 6 Automatic Cell Planning This chapter provides the information to use the ACP to optimise radio networks.
In this chapter, the following are explained: •
"The ACP Module and Atoll" on page 225
•
"Configuring the ACP Module" on page 229
•
"Optimising Cell Planning with the ACP" on page 233
•
"Running an Optimisation Setup" on page 267
•
"Working with Optimisations in the Explorer Window" on page 269
•
"Viewing Optimisation Results" on page 270
Atoll 3.1.2 User Manual Chapter 6: Starting a Project
224
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
6 Automatic Cell Planning Atoll Automatic Cell Planning (ACP) enables radio engineers designing radio networks to automatically calculate the optimal network settings in terms of network coverage and quality. The ACP can also be used to add sites from a list of candidate sites or to remove unnecessary sites or sectors. Atoll ACP can also be used in multi-RAT and co-planning projects where networks using different radio access technologies must be taken into consideration when calculating the optimal network settings. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and transmission or cell pilot power. ACP can also be used during the initial planning stage of a network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP not only takes transmitters into account in optimisations but also any repeaters and remote antennas. Atoll ACP can also be used to measure and optimise the EMF exposure created by the network. This permits the optimisation of power and antenna settings to reduce excessive EMF exposure in existing networks and optimal site selection for new transmitters. ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have defined the objectives and the network parameters to be optimised, Atoll ACP uses an efficient global search algorithm to test many network configurations and propose the reconfigurations that best meet the objectives. The ACP presents the changes ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the suggested changes. In this section, the following are explained: • • • • • •
"The ACP Module and Atoll" on page 225 "Configuring the ACP Module" on page 229 "Optimising Cell Planning with the ACP" on page 233 "Running an Optimisation Setup" on page 267 "Working with Optimisations in the Explorer Window" on page 269 "Viewing Optimisation Results" on page 270.
6.1 The ACP Module and Atoll Atoll ACP can be used either with existing networks or with networks in the initial planning phases. With existing networks, it is most efficient to focus on tuning the parameters that can be easily changed remotely, for example: • •
Antenna electrical tilt: ACP adjusts the electrical tilt by selecting the best antenna from the antenna group assigned to this transmitter. Power: The power (transmission power for GSM, pilot power for UMTS, total power for LTE, preamble power for WiMAX) is set within a defined minimum and maximum value for each cell or subcell.
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. ACP can also automatically create a list of candidate sites, following user-defined parameters.
ACP optimises the network using objectives to evaluate the optimisation, as well as to calculate its implementation cost. Each objective is defined by a set of rules and a target. A rule is a single key performance indicator on a single layer fulfilling a defined threshold. The target defines the required percentage of pixels in the target zone which must fulfil the set of rules in order for the objective to be met. In this section, the following are explained: • • • • • •
"Using Quality and Cost Objectives in the ACP" on page 226 "Using Zones with ACP" on page 226 "Using Traffic Maps with ACP" on page 227 "Shadowing Margin and Indoor Coverage" on page 227 "ACP and Antenna Masking" on page 227 "EMF Exposure" on page 229.
225
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
© Forsk 2012
6.1.1 Using Quality and Cost Objectives in the ACP ACP optimises the network using user-defined objectives to evaluate the quality of the network reconfiguration, as well as to calculate its implementation cost. Each objective is created from one or more rules. Each rule is an evaluation of a specific quality indicators for a single layer and for a defined zone. Each quality indicator is technology-dependent. By combining rules, you can create an objective that evaluates quality indicators on different layers within the same technology or, for projects that combine several radio access technologies, that evaluates quality indicators from different technologies. The rules can be combined logically, using boolean operators (OR, or AND), to create more complex rules. For example, in a project combining both UMTS and LTE, you could create the following rule: (UMTS 2100 - RSCP > -85dBm OR LTE 2010 - C/N 20dB) You can weight an objective using traffic maps or you can define different weights for different zones. If both weights are used, the zone weight is taken as a supplementary factor to the traffic weight. Each objective has a target. The target defines the required percentage of pixels in the target zone (after applying any traffic and zone weight) which must fulfil the set of rules. For example, if the target is 90%, the objective is fulfilled if 90% of the pixels are covered by the objective rule. Additionally, each objective can be weighted. The weight enables you to give more importance to some objectives over others.
6.1.2 Using Zones with ACP ACP uses different zones during the optimisation process for different purposes. ACP uses the computation zone to define the area where the quality indicators are evaluated. It also uses the computation and focus zones to quickly select the sites which are optimised, although you can also optimise transmitters and sites that are outside the computation or focus zone. All sites and transmitters in the network, including those outside the computation and focus zones are taken into consideration when calculating signal, interference, and best server status. ACP also allows you to import ArcView SHP files as polygon zones, vectors representing roads, railways or lists of fixed locations. ACP enables you to define different targets and different weights for each zone: for the computation zone, for the focus zone, for the hot spots, for each zone based on clutter classes, and for each imported zone. Moreover, ACP enables you to define quality objectives separately for each zone or to use each zone separately when creating candidate sites. In this section, the following are explained: • • •
"Using the Computation Zone and the Focus Zone" on page 226 "Using Custom Zones" on page 226 "Using the Filtering Zone" on page 227.
6.1.2.1 Using the Computation Zone and the Focus Zone Atoll ACP measures the quality indicators within the computation zone. If there is no computation zone, the ACP measures the quality objectives using a rectangle that includes all cells or subcells in the network. You can also use the computation or focus zone to quickly select which cells or subcells are to be optimised, although you can also optimise cells or subcells outside of the zones or a subset within a zone. Atoll ACP allows you to define different targets for the computation zone and the focus zone, as well as for any custom zones. You can also define different weights for each zone. It is recommended to define a computation zone. ACP uses the computation zone as the area in which the quality indicators are calculated and improved during optimisation.
6.1.2.2 Using Custom Zones Atoll ACP allows you to use custom zones, enabling you to define objectives for specific zones, to specify different quality targets for each custom zone, and to display final results per zone. You can create custom zones out of selected clutter classes. If you have more than one layer of clutter classes, with different resolutions, you can set an option in the acp.ini file so that the ACP only uses clutter classes of one resolution (usually the lower resolution). You can also set an option so that the other clutter classes are not displayed in the Zone Definition dialogue (see Figure 6.6 on page 237). For more information on the acp.ini file, see the Administrator Manual. You can create custom zones from the hot spots defined in the Atoll document, or import ArcView SHP files. These files can be polygons, to create hot spots, or they can be vectors representing roads, railways or strings of points. You can also import ArcView SHP files that are points describing a list of fixed locations. You can also define different weights for each zone.
226
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
6.1.2.3 Using the Filtering Zone If there is a filtering zone defined, Atoll ACP will ignore all cells outside of the filtering zone. ACP automatically considers all the cells or subcells that have an effect on the computation and ignores the rest (for example, those that are too far away to have an impact on the computation zone). It is nonetheless recommended to use a filtering zone to speed up initial data extraction from the Atoll document.
6.1.3 Using Traffic Maps with ACP Atoll ACP can use traffic maps to determine the traffic density on each pixel. The traffic density is used to weight each of the quality figures according to traffic and to put more emphasis on high traffic areas. You can set traffic weighting separately for each objective.
Figure 6.1: ACP traffic parameters When you use selected traffic maps, ACP allows you to define a resolution to extract the data from traffic maps. The resolution should usually be the same as the resolution of the traffic maps. To increase the accuracy of the data-extraction process, you can increase the resolution defined in the Resolution (m) text box.
6.1.4 Shadowing Margin and Indoor Coverage Atoll ACP enables you to take indoor coverage and a shadowing margin into consideration. When indoor coverage is taken into consideration, all pixels marked as indoors have an additional indoor loss added to total losses. The indoor loss is defined per clutter class. When the shadowing margin is taken into consideration, the defined shadowing margin is taken into consideration in the calculation of the received useful signal power and interfering signal power. For more information on how shadowing and macro-diversity gains (in UMTS) are calculated, see the Technical Reference Guide. You can set ACP to not take macro-diversity gains in UMTS into consideration by setting the appropriate option in the acp.ini file. You will need to update the corresponding parameters in the atoll.ini file as well. For information on modifying the atoll.ini file, see the Administrator Manual.
6.1.5 ACP and Antenna Masking When ACP performs any type of antenna reconfiguration, it must determine how attenuation to the path loss changes when the antenna is modified. ACP determines changes to path loss attenuation using antenna masking. Using the ACP - Automatic Cell Planning dialogue, you can define the ACP antenna masking method individually for each propagation model. Atoll distinguishes between two categories of propagation models: •
Native models: ACP provides the same prediction results as the original propagation model, by using the Optimised method. For more information, see "Native Propagation Models" on page 228.
227
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
•
© Forsk 2012
Non-native models: If the propagation model is not native to Atoll, ACP offers three different methods of antenna masking. For more information, see "Non-Native Propagation Models" on page 228. Power optimisation, site selection (without reconfiguration), and antenna height optimisation are made independently of the method used to determine changes to path loss attenuation.
6.1.5.1 Native Propagation Models Native propagation models are Atoll models such as SPM, Cost-Hata, Okumura-Hata, ITU propagation models, CrossWave, etc. During antenna optimisation, ACP must calculate how the attenuation to the path loss changes when the antenna is modified, i.e., when the antenna type, tilt, or azimuth is modified. Using the Optimised method, ACP provides the same results as those offered by the native propagation model. ACP calculates the change in attenuation by unmasking the current antenna pattern and then remasking it with the new antenna pattern. This calculation depends strongly on the horizontal and vertical emission angles between a transmitter and the receiving pixel. The Optimised antenna masking method provides accurate prediction of the emission angles, using one of two internal methods: • •
Direct calculation: ACP calculates incidence angles by direct calculation using the raster data. Delegating to the model: ACP calculates incidence angles by delegating the calculation to the propagation model, providing that the propagation model implements the appropriate methods of Atoll's API
ACP automatically selects which internal method to use for each native propagation model: • •
Crosswave: use delegation to model All others native models: use direct calculation You can define the internal method used by setting the appropriate option in the acp.ini file. For information on modifying the acp.ini file, see the Administrator Manual.
6.1.5.2 Non-Native Propagation Models ACP offers three different antenna masking modes for propagation models that are not native: •
Basic: The Basic mode is ACP’s internal antenna masking method. Because the ACP Basic masking method is not the same as the one used to calculate the original path loss matrices, accuracy cannot be guaranteed. ACP’s Basic masking method should deliver acceptable results for any propagation model similar to Atoll’s Standard Propagation Model. You can adjust the following parameters when using the Basic mode: •
Antenna pattern interpolation: The antenna gain calculation method for deriving the antenna gain from a set of angles of incidence. You can select either: • •
• •
• •
Native 3D Interpolation method: The method used by Atoll. For more information on Atoll’s method for 3D interpolation, see the Technical Guide. Linear Interpolation method: A simple linear method with optional smoothing.
Direct view: When selected, the angle of incidence will be the direct Tx-Rx angle. Use clutter height: Specify whether clutter heights should be applied along the profiles between transmitter and receiver. Clutter heights are either extracted from the clutter height file, or from default clutter heights based on the clutter class file. Receiver on top of clutter: Specify whether the receiver should be considered to be on top of the clutter or not.
Improved: The Improved mode performs antenna masking by delegating the calculation of the angles of incidence to the propagation model. If the propagation model does not implement the appropriate methods of Atoll’s API, the Improved mode is not available. You can adjust the following parameter when using the Improved mode: •
Antenna pattern interpolation: The antenna gain calculation method for deriving the antenna gain from a set of angles of incidence. You can select either: •
228
Native 3D Interpolation method: The method used by Atoll. For more information on Atoll’s method for 3D interpolation, see the Technical Guide.
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
• •
Linear Interpolation method: A simple linear method with optional smoothing.
Full Path loss: With this method, ACP precalculates all path loss matrices for all combinations of the parameters which are to be tested. This is a fall-back method for complex propagation models not supported by any other method. ACP does not calculate all path loss matrices for all possible combinations, for example, five possible changes in electrical tilt and five possible changes in azimuth, i.e., 25 path loss matrices to be calculated. ACP only calculates the path loss matrices for the changes which need to be evaluated by the optimisation algorithm. By pre-calculating only the changes to be evaluated, ACP reduces the number of path loss changes to be calculated and reduces the calculation time. While the optimisation is running, ACP uses the pre-calculated path loss matrices. If a change is made to a transmitter that was not taken into the consideration when the path loss matrices were calculated, ACP recalculates the path loss matrix for that change only. The end result is considerable savings in both time and computer resources. Although ACP minimises the number of calculations necessary when using precalculated path loss matrices, it is recommended to: •
•
•
Use precalculated path loss matrices only when necessary. When a propagation model is natively supported, you should use it. Even if a propagation model is not officially natively supported, using the default antenna masking method is often sufficient. Try to limit the number of parameters covered, when using precalculated path loss matrices. For example, only use a 2- or 3-azimuth span. Carefully designing the antenna groups will also reduce the number of unnecessary calculations. Use a temporary path loss storage directory dedicated to your document region when using precalculated path loss matrices. This ensures that future optimisations on this region will be able to use these path losses that have already been calculated.
6.1.6 EMF Exposure EMF exposure is defined as the total electromagnetic field measured at a given location. Although the exact limit on the acceptable level of EMF exposure varies by jurisdiction, it is typically a few V⁄m. Using an internal propagation model specific to EMF exposure, ACP calculates the EMF exposure in two dimensions (for open areas such as parks or roads) or in three dimensions (for buildings). Additionally, with buildings, you can choose to measure the exposure only at the front façade, where the EMF exposure will be the greatest. The internal propagation model calculates EMF exposure using propagation classes which are retrieved from input files. Each propagation class is either opaque, meaning that the signal experiences diffraction losses at the edge of the object but does not go completely through, or transparent, meaning that the signal passes through it (with perhaps some losses) and does not experience diffraction loss. The propagation classes have the following parameters: • • •
Penetration loss (dB): The loss occurring when the signal enters the object. Linear loss (dB/m): A linear loss applied for each metre within an object. The loss is applied only after a given number of metres, specified by the "Linear loss start distance (m)" parameter. Distribution of measurement points: Field strength measurements are made on a set of points within an object. The measurement points can be distributed in either a 3D pattern or in a 2D pattern. For a two-dimensional distribution, the points can be placed either at the bottom (for example, in a park) or at the top (for example, for a bridge) to better reflect where people will be.
The following default propagation classes are provided: • • •
Open: The Open propagation class is for areas without obstacles, such as an open area or water. An open area can also be an elevated area such as a bridge. Such areas are transparent, with no diffraction loss. Vegetation: The Vegetation propagation class is used for areas covered with vegetation, such as parks. They can be considered as transparent but with a certain degree of diffraction loss. Building: The Building propagation class is used for opaque objects such as buildings. The signal experiences some loss when going through and also suffer from diffraction loss.
6.2 Configuring the ACP Module The ACP is configured by defining various options. You can change some of these options using the ACP module. These options can be stored either in the current Atoll project or in the user-defined acp.ini file. Other options can only be changed by editing the global acp.ini file. The ACP reads the defined options in the following order of priority: •
The current Atoll project: You can define certain options using the ACP module and choose to embed them in the current project. Embedding the options in the current project ensures that the document is portable; if you open the Atoll document on a different computer, you will have the same default ACP settings.
229
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
•
•
© Forsk 2012
The user-defined acp.ini: When you define options using the ACP module, you can choose to save them in a userdefined acp.ini. Defining the ACP options using the acp.ini file enables you to use the same settings in different Atoll documents. Additionally, you can manually define settings directly in the acp.ini file, especially settings which can not be defined using the ACP module. The global acp.ini: The global acp.ini file (normally the acp.ini file found in the Atoll installation directory) contains all the options that can be set for the ACP. Unless the same options have been set in either the current project or the user-defined acp.ini, the ACP will use the options set in the global acp.ini to initialise a new ACP setup. Setting options in the global acp.ini ensures that all users of Atoll using that machine will be using the same base set of parameters. Defining the ACP options by editing the global acp.ini file also offers advantages, namely, consistent settings across Atoll documents and the ability to define settings which can not be set using the ACP module.
For information on the options available in the acp.ini file, see the Administrator Manual. In this section, the following are explained: • • •
"Defining the Storage Location of ACP Settings" on page 230 "Defining the Antenna Masking Method" on page 230 "Configuring Default Settings" on page 231.
6.2.1 Defining the Storage Location of ACP Settings You can define where Atoll stores the default settings of the ACP module. To configure the default settings of the ACP module: 1. Select the Network explorer. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Setup Template tab. The location of the settings are either embedded in the Atoll document or stored in an acp.ini file. 5. Click the arrow to the right of the current location of the ACP settings (
). The menu appears:
6. Select where you want the ACP to store the template options: •
• •
Embedded: Atoll will store the ACP settings in the current Atoll document. Embedding the options in the current project ensures that the document is portable; if you open the Atoll document on a different computer, you will have the same default ACP settings. Default User Location: Atoll will store the ACP settings in the default location for the user-defined acp.ini file. Defining the ACP options using the acp.ini file enables you to use the same settings in different Atoll documents. Browse: Clicking Browse enables you to select a location to store the acp.ini file or to select an existing acp.ini file.
6.2.2 Defining the Antenna Masking Method You can define how Atoll ACP calculates path loss changes and set an antenna masking method for each propagation model. These parameters will be applied to all new and duplicated setups. To define how ACP calculates path loss matrices: 1. Select the Network explorer. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears. 4. Click the Setup Template tab. 5. Click Antenna Masking Method in the left-hand pane. Under Antenna Masking Method, you can define how ACP calculates path loss matrices (see Figure 6.2).
230
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
Figure 6.2: The Antenna Masking Model tab 6. Under Propagation Models, select the check boxes in each column to define how ACP will model each propagation model. By default, all available propagation models are displayed. By selecting the Show only used propagation models check box, ACP will only display the propagation models that are actually used in that document. •
Antenna masking method: The antenna masking method column indicates which method is used, "Optimised" for native propagation models and "Basic," "Improved," or "Full Pathloss" for non-native propagation models.
•
Additional Parameters: In the Additional Parameters column, a Browse button (
) appears for each propaga-
tion model not supported natively by the ACP. Clicking the Browse button ( ) opens the Default Propagation Model Parameters dialogue. In the Default Propagation Model Parameters dialogue, you can define the following parameters for each propagation model for which ACP uses the "Basic" or "Improved" method as its default method: •
• • •
Antenna pattern interpolation: Antenna pattern interpolation is the method used to derive the antenna gain from a set of angles of incidence. You can select either the "Native 3D Interpolation" method or the "Linear Interpolation" method. When you select the linear interpolation method, you can also define the degree of smoothing applied. Direct view: Select the Direct View check box if you want ACP to trace a direct line between the transmitter and the receiver when calculating the vertical incidence angle, without taking any obstacle into account. Use clutter height: Select the Use clutter height check box if you want clutter heights to be applied along the profile between transmitter and receiver. Receiver on top of clutter: Select the Receiver on top of clutter check box if the receiver should be considered to be on top of the clutter.
7. Click OK.
6.2.3 Configuring Default Settings You can configure default settings for Atoll ACP that are used for each ACP setup. Each time you create a new ACP setup, these settings will be the default parameters that appear in the Setup dialogue. To configure the default settings of the ACP module: 1. Select the Network explorer. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select Properties from the context menu. The ACP - Automatic Cell Planning Properties dialogue appears.
231
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
© Forsk 2012
4. Select the Setup Template tab. On the Setup Template tab, you can set options that are normally set in the acp.ini file for the following categories: • • • • • •
Antenna Masking Method Optimisation Objective Reconfiguration Multi-storey EMF Exposure.
For information on the various options and their possible values, see the Administrator Manual. 5. Click the Preferences tab (see Figure 6.3).
Figure 6.3: Setting ACP preferences Under Setup Preferences: You can define the following setting: •
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 prediction transparency: Define the default prediction transparency with the slider.
Under Extensions: You can select the check box corresponding to the following extensions to activate them: •
•
Multi-Storey: Select the Multi-Storey check box if you want the ACP to display the options related to multi-storey optimisation. When you have selected the Multi-Storey check box, you will still have to select the option on the Optimisation tab of the Setup dialogue and define the multi-storey options if you want to optimise reception on all floors of multiple storey buildings. EMF Exposure: Select the EMF Exposure check box if you want the ACP to display the options related to EMF exposure. When you have selected the EMF Exposure check box, you will still have to select the option on the Optimisation tab of the Setup dialogue and define the EMF exposure options if you want to optimise the EMF exposure.
6. Click the Storage Directory tab. On the Storage Directory tab (see Figure 6.4), 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 and for new site candidates. This directory is also used to store the matrices of the angles of incidence and other temporary data.
232
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
Figure 6.4: Defining the directory for path loss matrices 7. Under Private Directory, enter the name of the directory or click the arrow to the right of the current directory ( to navigate to the new directory. 8. Under Shared Directory, enter the name of the directory shared by several users or click the Browse button ( right of the current directory to navigate to the new directory.
)
the
When the ACP reads a specific path loss or incidence matrix, it first attempts to read it from the Shared Directory. If the entry does not exist in the Shared Directory, the ACP then tries to read the information from the Private Directory. If the ACP can not find the information in the Private Directory, it then calculates the matrix and stores the results in the Private Directory. The ACP never writes directly to the Shared Directory. There should only be one user with administrator rights who populates this Shared Directory with the results of his Private Directory. No other user should set the Shared Directory as his Private Directory in order to avoid concurrent access. 9. Click OK to save your changes. For more information, see "Defining the Antenna Masking Method" on page 230.
6.3 Optimising Cell Planning with the ACP Optimising cell planning with the Atoll ACP consists of defining the parameters that will be used during the optimisation process and then running the process. Each optimisation, with its parameters and results, is stored in a Setup folder in the ACP - Automatic Cell Planning folder in the Network explorer. In this section, the following are explained: • •
"Creating an Optimisation Setup" on page 233 "Defining Optimisation Parameters" on page 234.
6.3.1 Creating an Optimisation Setup In ACP, you can create an optimisation setup either by creating and running a new one, or by duplicating or opening an existing optimisation, editing the parameters, and then running it. In this section, the following are explained: • • •
"Creating a New Optimisation Setup" on page 234 "Running an Existing Optimisation Setup" on page 234 "Duplicating an Existing Optimisation Setup" on page 234.
233
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
© Forsk 2012
6.3.1.1 Creating a New Optimisation Setup To create a new optimisation setup: 1. Select the Network explorer. 2. Right-click the ACP - Automatic Cell Planning folder. The context menu appears. 3. Select New from the context menu. A dialogue appears in which you can set the parameters for the optimisation setup. For information on the parameters available, see "Defining Optimisation Parameters" on page 234. 4. After defining the optimisation setup: • •
Click the Run button to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 270. Click the Create Setup button to save the defined optimisation. For information on running the optimisation, see "Running an Existing Optimisation Setup" on page 234.
6.3.1.2 Running an Existing Optimisation Setup To run an existing optimisation setup: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 3. Right-click the optimisation you want to run. The context menu appears. • •
Select Run from the context menu to run the optimisation immediately. For information on the optimisation results, see "Viewing Optimisation Results" on page 270. 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 234.
6.3.1.3 Duplicating an Existing Optimisation Setup To duplicate an existing optimisation setup: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 3. Right-click the setup you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The ACP Duplicate Options dialogue appears. 5. Under Data Synchronisation Option, select one of the following: •
•
Partial update: The duplicated ACP setup will have only the data that was changed by the ACP during optimisation. Duplicating the ACP-generated data permits you to create a new setup with up-to-date data even though the data of the original setup is no longer valid. Full update: The duplicated ACP setup will have all the data resynchronised from the database.
6. Run the existing optimisation setup as described in "Running an Existing Optimisation Setup" on page 234.
6.3.2 Defining Optimisation Parameters In Atoll ACP, when you create a new optimisation setup, you must first define all the parameters. You can also modify the parameters of an existing optimisation setup before running it. Creating a new optimisation setup is explained in "Creating a New Optimisation Setup" on page 234. Running an existing optimisation is explained in "Running an Existing Optimisation Setup" on page 234. The optimisation parameters are grouped onto specific tabs of the dialogue. The parameters are the same whether you create a new optimisation setup or whether you modify the parameters of an existing one. In this section, the following parameters are explained: • • • • • •
234
"Setting Optimisation Parameters" on page 235 "Setting Objective Parameters" on page 242 "Setting Network Reconfiguration Parameters" on page 246 "Defining Site Selection Parameters" on page 255 "Defining Antenna Groups" on page 262 "Adding Comments to the Optimisation Setup" on page 267.
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
6.3.2.1 Setting Optimisation Parameters The Optimisation tab allows you to define the various parameters related to the optimisation algorithm. To set the optimisation parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233. 2. Click the Optimisation tab (see Figure 6.5).
Figure 6.5: 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 power, antennas, azimuth, mechanical tilt, antenna height, sites subject to selection) by two. You can accept the number of iterations, or set your own value. Often one-half or one-quarter of the suggested number is sufficient for ACP to find the optimal configuration. Resolution (m): Specify the resolution for the optimisation. Each criterion will be evaluated on each of these pixels. The total number of pixels and the average number per site is indicated. This parameter has a large influence on the accuracy and speed of the optimisation process. You should either set a resolution that is consistent with the path loss and raster data in the Atoll document, or you should set a resolution that will result in between 300 and 3000 positions per site. If the resolution of the optimisation is different from the resolution of the path loss matrices, ACP performs a bilinear interpolation; it uses the four closest path loss values and interpolates among them. The best match between ACP predictions and Atoll predictions is obtained when the ACP resolution matches the path loss resolution.
4. Under Setup, you can set the following optimisation-related parameters: • • • • • •
6.3.2.1.1
"Defining Layer-related Parameters" on page 235 "Defining Zone-related Parameters" on page 236 "Defining Cost Control-related Parameters" on page 237 "Defining Site Classes for Cost Control" on page 238 "Defining Multi-storey-related Parameters" on page 239 "Defining EMF Exposure-related Parameters" on page 240.
Defining Layer-related Parameters On the Optimisation tab of the ACP Setup dialogue, you can define objectives and parameters related to radio layers of the current project. To define layer-related objectives and parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233. 2. Click the Optimisation tab (see Figure 6.5 on page 235). 3. In the pane on the left-hand side, click Layers.
235
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
© Forsk 2012
Under Layers (see Figure 6.5 on page 235), 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 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. If a transmitter on one selected layer that is optimised is linked (by the Shared Antenna field in the Atoll Transmitter table) with a transmitter on another layer that is not used in the optimisation, the second transmitter will not appear on the Reconfiguration tab but any changes to the first transmitter will be applied to the linked transmitter as well.
• •
Name: You can change the name of the layer by clicking it and entering a new name. Reconfiguration: If you want the layer to be taken into consideration for reconfiguration, you can select the check box in the Reconfiguration column. If a transmitter on one selected layer that is optimised is linked (by the Shared Antenna field in the Atoll Transmitter table) with a transmitter on another layer that is not reconfigured, the second transmitter will appear on the Reconfiguration tab but none of its sectors will be reconfigured (except for the electrical tilt, if you are optimising it). It is still possible for you to manually select these transmitters for reconfiguration on the Reconfiguration tab.
•
Site Selection: If you want the layer to be taken into consideration for site selection, you can select the check box in the Site Selection column. If this check box is cleared, all sites belonging to this layer will be considered as existing sites and you will not be able to deselect them on the Reconfiguration tab.
The following columns give information about the layer; they can not be edited: • • •
6.3.2.1.2
Technology: The technology used by the layer. Freq. Band/Carrier: The frequency band and carrier (if applicable) used by the layer. Nb Tx/Cell: The number of sectors in the layer.
Defining Zone-related Parameters On the Optimisation tab of the ACP Setup dialogue, you can define parameters related to the computation and focus zones as well as the hot spots of the current project. To define zone-related objectives and parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233. 2. Click the Optimisation tab (see Figure 6.5). 3. In the pane on the left-hand side, click Zones. Under Zones (see Figure 6.7), 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 custom zones in their defined order, the focus zone, and finally the computation zone. For all zones, the area of the zone is given (for polygons), or the length of the zone (for vectors), or the number of points (for zones composed of points). 4. Reconfiguration Zones: Select the Computation Zone check box to preselect only the sectors in the computation zone and the Focus Zone check box to preselect only the sectors in the focus zone for reconfiguration. If there is no focus zone in the project to be optimised, the computation zone is automatically selected. You can always manually reconfigure sectors outside the selected zone on the Reconfiguration tab. 5. For each zone under Reconfiguration Zones, define the Resolution. You can select the "Default" resolution, or you can define a custom resolution by entering a numeric value. If you select "Ignore," the ACP will not create evaluation points in that zone. 6. Custom Zones: Each hot spot defined in the Atoll document is automatically included as a custom zone under Custom Zones Definition. For each new custom zone, enter a Name in the row marked with the New Row icon ( ) and click the Browse button (
) to open the Zone Definition dialogue. You can import an ArcView SHP file by selecting From
file and clicking 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
236
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
in the reconfiguration zones that are included in one or more clutter class by selecting From clutter classes and selecting the check box corresponding to the clutter class or classes you want to study. If you have set an option in the acp.ini file so that the ACP only uses clutter classes of one resolution (usually the lower resolution), you can also set an option so that the other clutter classes are not displayed in the Zone Definition dialogue. For more information on the acp.ini file, see the Administrator Manual.
Figure 6.6: The Zone Definition dialogue 7. For each zone under Custom Zone Definition, define the Resolution. You can select the "Default" resolution, or you can define a custom resolution by entering a numeric value. If you select "Ignore," the ACP will not create evaluation points in that zone. If the custom zone is based on clutter classes, you can not not change the resolution; you can either select "Use," and the ACP distribute evaluation points in that zone based on the default resolution or "Ignore," and the ACP will not create evaulation points in that zone. You can change the order in which the custom zones will be taken into consideration, by clicking the layer’s number in the Order column and then clicking the Up button ( ) or the Down button ( ). The order has an effect only when assigning weighting to specific zones and thresholds to pixels which belong to two or more intersecting zones. When a zone is fully included in another one, it always has precedence over the zone in which it is located.
Figure 6.7: Configuring zones on the Optimisation tab
6.3.2.1.3
Defining Cost Control-related Parameters On the Optimisation tab of the ACP Setup dialogue, you can define objectives and parameters related to cost control (where cost can either be the financial cost or the required effort). You can define an option in the acp.ini file to display advanced cost options which enable the user to define the maximum number of changes to be made (either as a value or a ratio) and to change the ranking of the order of cost in the final implementation plan: changes with the lowest cost are performed first and changes with the highest cost are performed last. For more information on setting options in the acp.ini file, see the Administrator Manual. To define cost control-related objectives and parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233. 2. Click the Optimisation tab (see Figure 6.5). 3. In the pane on the left-hand side, click Cost Control. Under Cost Control (see Figure 6.8), 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:
237
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
• • •
© Forsk 2012
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 (Better Quality) or cost (Lower Cost).
Figure 6.8: 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. By default, the cost is only a ratio: defining a cost as "0" means that there is no cost associated with a change; defining a cost as "2" means that this change costs twice as much as another change with a defined cost of "1". You can, however, define the cost as a monetary value. You can define the monetary value to be used, for example, yen or dollars, by editing the "Cost: Unit" option under Optimisation on the Setup Template tab of the ACP - Automatic Cell Planning Properties dialogue. For more information about the ACP - Automatic Cell Planning Properties dialogue, see "Configuring Default Settings" on page 231.
•
6.3.2.1.4
In the Site Selection Cost section, under Cost Setting, define the individual costs for each site selection option.
Defining Site Classes for Cost Control On the Optimisation tab of the ACP Setup dialogue, you can create and define site classes. By setting different costs for each site class and assigning each site to a class, ACP can calculate costs that reflect more realistically the actual costs of each site. To create and define site classes: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233. 2. Click the Optimisation tab (see Figure 6.5). 3. In the pane on the left-hand side, click Cost Control. Under Cost Control (see Figure 6.8), you can create site classes and define how the costs will be calculated for each optimisation option and each class. ACP will use the defined costs to calculate the optimisations that are the most cost-effective. To define the costs for a site class: 1. Click the arrow beside the Site Classes list and select a site class. 2. Define the individual costs for each reconfiguration option as explained in "Defining Cost Control-related Parameters" on page 237. To create a site class: 1. Click the New Site Class button (
). The New Site Class dialogue appears.
2. Enter the name for the site class and click OK. The new site class now appears in the list of site classes.
238
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
3. Define the individual costs for each reconfiguration option of the new site class as explained in "Defining Cost Controlrelated Parameters" on page 237. To delete a site class: 1. Click the arrow beside the Site Classes list and select the site class you want to delete. 2. Click the Delete Site Class button ( site class.
). The selected site class is immediately deleted. You can not delete the "Default"
ACP will not ask you to confirm your decision, so ensure that you have selected the correct site class before clicking the Delete Site Class button.
6.3.2.1.5
Defining Multi-storey-related Parameters On the Optimisation tab of the ACP Setup dialogue, you can set the parameters necessary to optimise reception in multistorey buildings. The ACP uses clutter height maps to distribute points in a three-dimensional pattern. You can optimise calculations by defining the calculation step, the zone on which measurement points are distributed and by ignoring buildings under a certain height, where reception on the higher storeys would not be appreciably different than that calculated by the ACP for the ground floor. Once you have defined the multi-storey parameters and run the optimisation, you can view the results by creating either an objective analysis or a quality analysis prediction in the ACP. For more information, see "The Objective Analysis Predictions" on page 281 or "The Quality Analysis Predictions" on page 282. The Multi-storey section of the Optimisation tab is only available if you have selected the Multi-storey check box under Extensions on the Preferences tab of the ACP Properties dialogue. For more information on setting the properties of the ACP module, see "Configuring Default Settings" on page 231. To define multi-storey parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233. 2. Click the Optimisation tab (see Figure 6.5). 3. In the pane on the left-hand side, click Multi-storey. Under Multi-storey, you can define the parameters used to optimise reception in multi-storey buildings.
Figure 6.9: Setting multi-storey optimisationparameters 4. Under Multi-storey, select the Enable Multi-storey check box if you want the ACP to optimise reception in multistorey buildings. 5. Under Vertical Points Distribution, define how the ACP will distribute the measurement points it will use to optimise the reception in multi-storey buildings represented in the clutter height maps: •
• •
•
Distribution zone: Select the zone on which multi-story measurement points are to be distributed. The ACP only distribute points in a three-dimensional pattern where there are clutter height maps, but, by selecting a distribution zone, you can limit calculations to areas where multi-storey reception optimisation is most important, for example, downtown. Storey height (m): Define the height of each storey in metres. The ACP will use this height to calculate the receiver height for the defined number of storeys. Calculation steps (storeys): Define, as a number of storeys, the size of vertical steps between storeys on which the ACP distributes measurement points. The resulting receiver heights are calculated using the defined step and storey height and displayed beside the Storey height. Ignore buildings smaller than (storeys): Define the minimum height (in storeys as defined by the Storey height) of buildings for the ACP to distribute measurement points in three dimensions.
239
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
© Forsk 2012
6. Under Vertical Points Distribution, select the Vertical weight sharing check box if you want the ACP to divide the weight of each measurement point evenly between all 3-D pixels at a given (x, y) location. For example, if a pixel at ground level has a weight of 1 and there are a total of 5 points (1 point at ground level and 1 point every 3 metres) at that location, each 3-D pixel will have a weight of 0.2. If the Vertical weight sharing check box is cleared, each measurement point will have the same weight. For example, if a pixel at ground level has a weight of 1 and there are a total of 5 points (1 point at ground level and 1 point every 3 metres) at that location, the total weight of all measurement points will be five, as opposed to a weight of one outdoors.
6.3.2.1.6
Defining EMF Exposure-related Parameters On the Optimisation tab of the ACP Setup dialogue, you can set the parameters necessary to measure and optimise the EMF exposure caused by the network. The EMF Exposure section of the Optimisation tab is only available if you have selected the EMF Exposure check box under Extensions on the Preferences tab of the ACP Properties dialogue. For more information on setting the properties of the ACP module, see "Configuring Default Settings" on page 231. To define EMF exposure parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233. 2. Click the Optimisation tab (see Figure 6.5). 3. In the pane on the left-hand side, click EMF Exposure. Under EMF Exposure, you can define the parameters used to optimise EMF exposure.
Figure 6.10: Setting EMF exposure parameters 4. Under EMF Exposure, select the Enable EMF exposure calculation check box if you want the ACP to optimise EMF exposure. 5. Use the EMF exposure importance slider to define the importance of EMF exposure in comparison with the other optimisation objectives: • • •
Low: EMF exposure is improved when doing so does not have a strong adverse effect on coverage quality. Medium: There is a trade-off between coverage quality and EMF exposure. Critical: EMF exposure is improved at all costs, even if doing so has a strong adverse effect on coverage quality.
6. Under Distribution of Evaluation Points, define how the evaluation points will be distributed: • • • •
•
Resolution XY (m): Define in metres the horizontal resolution of the evaluation points. Resolution Z (m): Define in metres the vertical resolution of the evaluation points (only for three-dimensional EMF exposure analysis). Building front only: Select the Building front only check box if you only want evaluation points to be distributed on the building façade. Indoor distance analysis (m): If you want evaluation points to be distributed within the building (i.e., if the Building front only check box is not selected), define the maximum distance up to which evaluation points are distributed inside the building. Evaluation on zone: Select the zone (computation, focus, or individual hot spot zone) on which evaluation points will be distributed and on which the EMF exposure will be optimised.
7. Under Raster and Vector Inputs, set the data that will be used to define the profile of the terrain:
240
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
By default, the first entry under Raster and Vector Inputs is "Native clutter classes and clutter heights," the terrain profile obtained from the geo data in Atoll (the clutter classes and DTM). a. Map the clutter classes to the ACP propagation classes by clicking the Browse button ( ) in the Definition column. In the Clutter Definition dialogue that opens (see Figure 6.11), you can map each clutter class to a corresponding propagation class and select the check box of each clutter class that is to be used for EMF evaluation. If you have vector files that fully model the terrain, you can remove the Atoll geo data by selecting the Ignore clutter check box at the bottom of the dialogue.
Figure 6.11: The Clutter Definition dialogue b. Add a file describing the terrain by clicking the Browse button ( ) in the File column. The file must be an ArcView vector file (SHP). Once you have selected a file, the Vector File Definition dialogue appears. In the Vector File Definition dialogue, you can define the parameters of the vector file, i.e., the field defining height, the correspondence between vector class and propagation class, and select which vector class should be used for EMF evaluation.
Figure 6.12: The Vector File Definition dialogue i.
Definition: Under Definition, click the Browse button ( the file’s data to ACP propagation classes.
) corresponding to the file in the File column to map
ii. Used in Evaluation: Select the Used in Evaluation check box for each entry in the File column that you want to use for EMF exposure optimisation. The check box in the Used in Evaluation column is selected for each entry in the File column that is used to define the area where EMF evaluation takes place. iii. Click OK to close the Vector File Definition dialogue. Once you have defined the EMF exposure parameters, you can back up the configuration by clicking the Back Up Configuration button. In future ACP sessions, the same parameters will be applied automatically 8. In the pane on the left-hand side, click Propagation under EMF Exposure. Under Propagation, you can define the propagation classes used to optimise the EMF exposure, as well as additional EMF exposure parameters.
241
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
© Forsk 2012
Figure 6.13: Defining propagation classes 9. Under Propagation Class Definition, set the following parameters for each propagation class. If you want to create a new propagation class, enter the parameters in the row marked with the New Row icon ( ). • •
• • •
Name: The name of the propagation class. Distribution of Evaluation Points: The pattern in which evaluation points will be distributed in that propagation class. The evaluation points can be distributed in either a 3D pattern (for a building, in which EMF calculation must be made vertically as well) or in a 2D pattern. For a two-dimensional distribution, the points can be placed either at the bottom (for example, in a park) or at the top (for example, for a bridge) to better reflect where people will be. Penetration Loss (dB): Define the loss occurring when the signal enters the object. Linear Loss (dB⁄m): Define a linear loss applied for each metre within an object. The loss is applied only after a given number of metres, specified by the Linear Loss Start Distance (m) parameter. Linear Loss Start Distance (m): Define the distance after which the Linear Loss (dB⁄m) is applied.
10. Under Parameters, define the following: • •
•
Use diffraction: This option is currently disabled; evaluation points that are not in the line of sight experience infinite diffraction loss. In other words, points that are not in the line of sight do not experience any EMF exposure. Free space model (worst case): Select the Free space model (worst case) check box if you want the ACP to calculate the worst possible EMF exposure levels under the current conditions. When you select the Free space model (worst case) check box, the ACP treats all objects (i.e., buildings, etc.) as fully transparent and no indoor loss is applied. In other words, even points which are not in line of sight are calculated as if they were in line of sight. Calculation radius (m): Define the maximum distance from a transmitter for which its EMF exposure contribution is calculated.
6.3.2.2 Setting Objective Parameters The Objectives tab allows you to define the various parameters related to the objectives of the optimisation. ACP allows you to set different objectives for each layer selected in the Use column under Layers on the Optimisation tab. You can also combine the objective rules with boolean operators (AND or OR) enabling you to build complex objectives combining several rules. The default objectives are technology dependent. In each technology, a certain number of objectives are proposed that you can then modify. You can create new objectives and add them to the optimisation setup. For information on creating a new objective, see "Creating a New Objective" on page 246. For information on the individual technology-dependent objectives, see the technology-specific chapter: • • • • •
For GSM/GPRS/EDGE: see "GSM Optimisation Objectives" on page 581 in Chapter 8: GSM/GPRS/EDGE Networks For UMTS HSPA: see "UMTS Optimisation Objectives" on page 762 in Chapter 9: UMTS HSPA Networks For LTE: see "LTE Optimisation Objectives" on page 1556 in Chapter 14: LTE Networks. For WiMAX: see "WiMAX Optimisation Objectives" on page 1270 in Chapter 12: WiMAX BWA Networks. For CDMA: see "CDMA Optimisation Objectives" on page 933 in Chapter 10: CDMA2000 Networks.
To set the objective parameters: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233. 2. Click the Objectives tab (see Figure 6.14). When you click Objectives in the left-hand pane of the Objectives tab, the right-hand pane displays a table with all defined objectives, with the layers and type of quality indicator managed by each objective. You can also use the table to create new objectives. For information on creating new objectives, see "Creating a New Objective" on page 246.
242
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
AT312_UM_E1
Figure 6.14: The Objectives tab in UMTS 3. In the left-hand pane, under Objectives, click the objective, for example, in Figure 6.14 in UMTS you would select either UMTS RSCP or UMTS EcIo, to define the coverage parameters of that objective. In the right-hand pane, you can now define the following coverage parameters: •
Target Zone: Select the zone on which the objective is to be evaluated. For more information on using zones with the ACP, see "Using Zones with ACP" on page 226.
•
Traffic Weighting: If you want define non-uniform traffic weighting, click the Browse button ( ) to open the Traffic Definition dialogue. In the Traffic Definition dialogue, you can select either Traffic generated from maps
•
and select the traffic maps or you can select Traffic generated from file and then click the Browse button ( ) to select a traffic map. Weight: You can set the importance of the objective in relation to other objectives by defining a weight. Giving the objective a weight of "0" means that ACP will not consider coverage of this objective in determining the success of the optimisation.
Figure 6.15: The Objectives tab in UMTS
243
Atoll 3.1.2 User Manual Chapter 6: Automatic Cell Planning
© Forsk 2012
4. In the left-hand pane, under Objectives, click Rules under the objective you defined in step 3. to define the rule or rules that will be used to evaluate the objective. For example, in Figure 6.15, you would click Rules under either UMTS RSCP or UMTS EcIo to define the evaluation rule. In the right-hand pane, you can now define the rule or rules that will be used to evaluate the objective. Each row in the table contains one rule. Each rule is an evaluation of a specific quality indicator for a single layer and for a defined zone. Each quality indicator is technology-dependent. By combining rules, you can create an objective that evaluates quality indicators on different layers within the same technology or, for projects that combine several radio access technologies, that evaluates quality indicators from different technologies. •
In the row with the rule you want to edit, or in the row marked with the New Row icon ( a new rule, set the following parameters: • • • • -
) if you want to create
In the first column, select the boolean operator (AND or OR) that will be used to combine the rules. Layer: In the Layer column, select the layer that the rule will be evaluated on. Quality: In the Quality column, select the quality indicator. In the next column, select the operator (greater than ">" or less than "" or less than "=: 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 collision probability is >= and enter a value. If the co- or adjacent channel collision probability is >=: 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 collision 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 Apply to control channel TRXs, control channel TRXs (i.e., BCCH TRXs) will be deleted. Apply to other TRXs: If you select Apply to other TRXs, 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 the defined criteria.
501
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.66: Constraint Violation Resolution
8.4.4.6.3
The Subcells Tab The Subcells tab (see Figure 8.67) shows the subcell indicators, the variation of the number of required TRXs (and corresponding traffic loads), and the allocated preferred frequency groups estimated by the AFP model, if you selected these options when starting the AFP. For each parameter, the table gives the initial and final results. When committing them, they are assigned to the corresponding subcells. If the AFP has been run with the azimuth-oriented allocation strategy, the Subcells tab will also display the preferred groups. If the geometry of the network was incompatible with an azimuth-oriented allocation, the AFP will not attempt to allocate frequency groups.
Figure 8.67: Subcells tab of the AFP Details dialogue
8.4.4.6.4
The Distributions Tab On the Distributions tab (see Figure 8.68), 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
502
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
in the Zoom on selected values list. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values.
Figure 8.68: The Distribution tab of the Details dialogue
8.4.4.7 Committing and Exporting the Frequency Plan Once you have made the necessary modifications to the frequency plan created by the AFP, you can commit the frequency plan to the network or export the frequency plan to a file. In this section, the following are explained: • •
8.4.4.7.1
"Committing an Automatic Frequency Plan" on page 503 "Exporting an Automatic Frequency Plan" on page 503.
Committing an Automatic Frequency Plan To commit the currently displayed frequency plan: 1. Select the Allocation tab. 2. Ensure that the currently displayed frequency plan is the one you want to commit by clicking the Display Options button and selecting the desired frequency plan: •
• •
Display the Plan to be Committed: When you select this option, Atoll displays the frequency plan as it now stands, in other words, Atoll displays the AFP plan with your modifications. You can only modify the entries in the Channel Assignment column in the current plan. Display the Final AFP Plan: When you select this option, Atoll displays the AFP plan as it stood before you began making modifications. Display the Initial Plan: When you select this option, Atoll displays the frequency plan before the AFP session.
3. Click Commit.
8.4.4.7.2
Exporting an Automatic Frequency Plan To export the currently displayed frequency plan: 1. Select the Allocation tab. 2. 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 Plan to be Committed: When you select this option, Atoll displays the frequency plan as it now stands, in other words, Atoll displays the AFP plan with your modifications. You can only modify the entries in the Channel Assignment column in the current plan. Display the Final AFP Plan: When you select this option, Atoll displays the AFP plan as it stood before you began making modifications.
503
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
•
© Forsk 2012
Display the Initial Plan: When you select this option, Atoll displays the frequency plan as it was after the AFP stopped, in other words, Atoll displays the AFP plan without your modifications.
3. Click the Actions button and select Export Results. The Export dialogue appears. 4. Export the frequency plan as explained in "Exporting Tables to Text Files and Spreadsheets" on page 80. 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.
8.4.4.8 Allocating Frequencies Interactively Atoll’s Interactive Frequency Planning (IFP) tool enables you to verify the frequency allocation of transmitters one by one, and improve an existing frequency plan by letting you select the most appropriate channels to assign to TRXs. The IFP tool uses an AFP module to calculate the costs associated with the current and modified frequency plans. For more information on the optional Atoll AFP module, see "The Atoll AFP Module" on page 507. Whereas an automatic frequency planning module (AFP) provides a complete solution in terms of allocated channels, i.e., the best frequency allocation that provides the lowest overall cost, the IFP lets you use your knowledge of the network to improve the frequency plan proposed by the AFP. In Figure 8.69, you can see that the TCH frequency 36 is interfered by a TCH TRX belonging to BRU078_G3 and BRU079_G1. In Figure 8.70, you can see that the candidate replacement channel 19 is better, even if it is also interfered by BRU079_G2. The best candidate is therefore channel 21.
Figure 8.69: TCH channel 36 interfered by TCHs of BRU078_G3 and BRU079_G1
504
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.70: Candidate replacement channel 35 To allocate frequencies interactively using the IFP: 1. Select Tools > IFP. The IFP window appears. 2. Select the Channel Allocation and Analysis view from the top of the IFP window. 3. Select a transmitter from the Transmitter list or by clicking its symbol in the map window. 4. Select the TRX type from the 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 507. 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 Display best candidates only if you want to limit the number of solutions to be calculated and displayed. Selecting this option might reduce calculation time for large networks. iv. Select the Load all the subcells involved in separation constraints check box if you want all subcells potentially involved to be loaded. v. 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 "Channel Separations" on page 477. Exceptional Pairs: For information on the options, see "Channel Separations" on page 477. Intra-technology Neighbours: For information on the options, see "Planning Neighbours" on page 422.
7. Click Calculate. The IFP calculates and displays the cost of the current channel allocation for the selected transmitter. The tool calculates and displays interference probabilities using the active interference matrices available in the GSM Interference Matrices folder in the Network explorer. If the interference matrices in the GSM Interference Matrices folder are not active or if interference matrices are not available, the analysis tool only calculates and displays the interference from a transmitter and its TRXs on itself.
505
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
In the map window, arrows are displayed from the selected transmitter to each interfered or interfering transmitter. The colour of the arrow is the same as the colour of the studied transmitter. The probabilities of interference are displayed as captions for the arrows. The thickness of the lines indicates the interference probability. Different information and options are available depending on the hopping mode of the selected transmitter’s 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 Filtering column lets you select the interference information to be displayed in the fourth column, the Cost Components and Indicators column. You can display the Major 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 Last column displays the various details about the way the cost is evaluated (traffic load, cost components). In addition, it displays the interference probabilities between the TRX of the selected transmitter and the interfering TRXs using the selected options in the Filtering 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 Last column displays the various details about the way the cost is evaluated (traffic load, cost components). In addition, it displays the interference probabilities between the TRX of the selected transmitter and the interfering TRXs using the selected options in the Filtering column.
•
Synthesised 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. The Last column displays the various details about the way the cost is evaluated (traffic load, cost components). In addition, it displays the interference probabilities between the TRX of the selected transmitter and the interfering TRXs using the selected options in the Filtering column.
You can obtain more information on any selected item of any column by double-clicking on it. As an example, you can doubleclick on a cost value in order to display details as shown below:
506
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.71: IFP Detailed Information Window 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 immediately and updated results are displayed.
8.5 The Atoll AFP Module The main role of the Atoll Automatic Frequency Planner (AFP) is assigning frequencies (i.e., channels) to the network in such a way that overall network quality is optimised. As GSM has evolved, many improvements have been integrated into the technology; improvements such as the implementation of baseband and synthesised frequency hopping, discontinuous transmission, and network synchronisation. These improvements have led to a more complicated frequency planning process and, therefore, to the need for an AFP that is advanced enough to help the frequency planner through the entire frequency planning process. The Atoll AFP is an advanced AFP that can take a large number of constraints and directives into consideration when allocating resources. Some of the constraints it can work with are ARFCN separation requirements between transmitters, interference relations, HSN assignment methods, frequency domain constraints, a given fractional load to maintain, etc. The AFP depends on a variety of input data, such as the interference matrix, neighbour relations, traffic information, etc. The Atoll AFP module is implemented using simulated annealing, taboo search, graph heuristics, and machine learning. It manages its time resources to match the target computation time defined by the user. If the target computation time is high, the module will use part of this time to "learn" the network. During the learning phase, the module adjusts its internal parameters. After the learning phase, the AFP will switch to a randomised combinatorial search phase. The Atoll AFP module performs network learning by executing many fast and deterministic instances of the AFP. The instance that results in the best performance can be saved both in the document and in the database. If this experience is conserved, the next time that an AFP is executed, it will start where the learning process ended: it will use the parameter profile of the best solution stored in the AFP model. The most important part of network learning are the parameters controlling trade-offs between the various parts of the algorithm. For example, you can base candidate selection on interference only by choosing frequencies that do not interfere and are not interfered. Or you can base candidate selection only on availability reduction by choosing frequencies that do not reduce the availability of non-interfered frequencies in the surrounding TRXs.
507
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
In Atoll's AFP the two criteria are combined and their relative weight is part of the AFP experience. The advantage of the Atoll AFP is that it simplifies the decision for the user by combining the input elements and presenting the user with a simple result, such as traffic load or total cost, on which to base his decisions. Before continuing, ensure that you are familiar with the prerequisite information explained in "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. In the previous sections, the basic elements of the AFP usage were presented. In this section, the more advanced aspects, as well as what is specific to Atoll's AFP module are presented. The content is presented according to level of complexity. Therefore this section is organised according to the level of complexity: • • •
"Using the Atoll AFP at a Basic Level" on page 508 "Using the Atoll AFP" on page 509 "Advanced AFP usage" on page 530.
8.5.1 Using the Atoll AFP at a Basic Level In this section, you will find the information necessary to run the Atoll AFP to solve a simple problem, or to evaluate a hypothetical "What if" scenario. If you are unfamiliar the AFP cost function or how its parameters are set, you can use the Atoll AFP with its default values. If you are new to the Atoll AFP, you should follow the recommendations in this section. As a new user of the Atoll AFP, the only parameter you should alter is the cost of modifying a TRX and the intermodulation tax. The other settings of the AFP model should be left as is. 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 510 for more information about the cost function. Normally, the first step in using the Atoll AFP, is to configure the parameters of the Atoll AFP module. When you use the AFP at the most basic level, you only need to set the basic, most important parameters. To set the basic parameters of the Atoll AFP module: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the AFP Modules folder. 4. Right-click the Atoll AFP Module. The context menu appears. 5. Select Properties from the context menu. The Atoll AFP Module Properties dialogue appears. 6. Select the Cost tab (see Figure 8.72).
508
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.72: The Cost tab of the AFP Module Properties dialogue 7. Select the Modified TRX check box to restrict the number of modifications to the existing plan. 8. Select the Intermodulation Tax check box in order to try avoiding these products. 9. Click OK to save your changes to the AFP module and close the AFP Module Properties dialogue. All the other AFP settings should be left with their default values. To run a simple AFP process: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Plan > Automatic Allocation from the context menu. The AFP dialogue appears with the AFP Model and Allocations tab displayed. 4. On the AFP Model and Allocations tab, click Next without modifying any of the options. The Separations tab appears. 5. On the Separations tab, click Next without modifying any of the separation rules and without defining any exceptional pairs. The Global Parameters tab appears. 6. On the Global Parameters tab, select From subcells table under Traffic (load and demand). In the third page of the AFP wizard, extract the traffic data from the subcells table. 7. Clear all the check boxes under Locking of existing TRXs of type and clear the DTX check box. 8. Click OK. The final AFP dialogue appears. 9. Set the Target CPU 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, for example around 3,000, 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 488.
8.5.2 Using the Atoll AFP Most users of the AFP use the Atoll AFP at a relatively sophisticated level, assigning frequencies, optimising TRXs, and taking into account all of the constraints on frequency use in a GSM network. This section explains the basic concepts necessary to successfully working with the AFP and explains the parameters of the Atoll AFP module.
509
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
In this section, the following are explained: • • • • •
"An Overview of the AFP Cost Function" on page 510 "Setting the Parameters of the Atoll AFP Module" on page 516 "Frequency Hopping Overview" on page 527 "Azimuth Oriented Assignments (Pattern Allocation, 1/1 1/3 1/x …)" on page 529 "BSIC Allocation" on page 529.
8.5.2.1 An Overview of the AFP Cost Function The Atoll AFP cost function maps two frequency plans (the initial and the final frequencies plans) to a single number: the AFP cost. 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. In this section, the following are explained: • • • • • • • • • • • • • •
8.5.2.1.1
"The Cost Function as a Combination of Separation Violation and Interference Probabilities" on page 510 "Counting Bad TRXs (Nodes) Instead of Bad Relations (Edges)" on page 510 "The Cost of Each TRX" on page 511 "Cost of Each Subcell" on page 511 "An Example of Separation Violation Cost with Frequency Hopping" on page 511 "Interference Cost" on page 512 "Probabilistic Cost Combination" on page 513 "The Cost of Missing and Corrupted TRXs" on page 513 "Cost of Out-of-domain Frequency Assignment" on page 514 "Preferred Group Cost" on page 514 "Intermodulation Cost" on page 514 "Quality Target" on page 515 "Quality Target" on page 515 "AFP Shadowing" on page 516.
The Cost Function as a Combination of Separation Violation and Interference Probabilities The cost function of the Atoll AFP has two main components: the cost for violations of separation constraints and the cost of creating interference. The Atoll AFP gives each separation violation the cost equivalent to a certain amount of interference, making it possible to add both costs and minimise their total. For example, you can decide that a separation violation of 1 costs the same as x% of interfered traffic. This is weighted by the type of violation (for example, co-transmitter separation violations have a higher impact than neighbour separation violations). By defining equivalence between these dissimilar measurements, you can add separation violation and interference costs using their common unit, i.e., the percentage of interfered traffic. Following this principle, all other cost elements are calculated in the same way: • • • • • • •
8.5.2.1.2
The cost component due to allocation changes The cost component of allocating TRXs that belong (or not) to a preferred frequency group (if such a group is defined) The cost component of missing or extra TRXs compared to the number of required TRXs The cost component of corrupted TRXs The cost component of assigned frequencies that are not in the assigned domain The cost component of blocked traffic (calculated only when you set the AFP to optimise the number of required TRXs) The cost component of intermodulation.
Counting Bad TRXs (Nodes) Instead of Bad Relations (Edges) In the following example, each separation violation represents an edge and each TRX a node. The two frequency plans proposed in this example do not respect all separation requirements for all TRXs, meaning that they all have bad nodes and bad edges. They demonstrate the difference between minimizing the number of bad edges or the number of bad nodes. The network in this example consists of 6 TRXs, all having a separation constraint of 1 with each other (i.e., 6 nodes, 15 edges):
510
Case 1
Case 2
F1 is used 4 times; F2 and F3 are used one time each.
F1, F2, and F3 are used two times each.
Number of separation violations is 6 (6 bad edges)
Number of separation violations is 3 (3 bad edges)
Two TRXs have good assignments
No TRX has a good assignment
The spectrum is not equally used
The spectrum is equally used
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
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. The three main advantages of the node-oriented approach are: • • •
The cost function has units which are easy to understand: interfered traffic. It has a greater capacity to optimise the number of TRXs. It has the ability to respect a TRX-based quality target, i.e., to disregard interference at a TRX below a certain value.
The node-oriented approach provides a better correspondence between the AFP cost and the network quality.
8.5.2.1.3
The Cost of Each TRX The AFP cost is added up for each TRX according to the following logic: • • • • •
If TRX α is corrupted, the cost of being corrupted is added to the total cost, and multiplied by T( α ), where T( α ) is an estimate of the traffic time slots for TRX α weighted by the AFP weight for this TRX. If TRX α is missing (i.e., if the required number of TRXs and the actual number of TRXs is different), the cost of the missing TRX is added to the total cost, and multiplied by T( α ). If TRX α has frequencies assigned to it that do not belong to its domain, the cost is added to the total cost, and multiplied by T( α ). Otherwise, the separation cost, the interference cost, the changing load, and the preferred group respect ratio of this TRX are added together (probabilistically) and added to the total cost, and multiplied by T( α ). If this amount is very small, it is discarded (for more information, see "Quality Target" on page 515).
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.
8.5.2.1.4
Cost of Each Subcell When you use the AFP to optimise the number of required TRXs, the cost function is adapted: the traffic load becomes dependent on the number of TRXs. Moreover, a blocked cost component is used. For the purposes of this section, you can assume that the cost of each subcell corresponds to all cases where the allocation strategy does not include the optimisation of the number of TRXs. The AFP cost is the cost of the entire loaded network, not only the cost of the selected or non-locked TRXs. In many cases, the AFP is authorised to change only a part of the network. Therefore, the part of the cost corresponding to the non-locked part of the network and the part of the cost corresponding to the locked part of the network are indicated.
8.5.2.1.5
An Example of Separation Violation Cost with Frequency Hopping In this example, the interference cost is ignored in order to make the separation violation cost easier to understand. The example uses a TRX with only one separation. In this example, Sij represents the required separation between two transmitters. If f1 is assigned at i and f2 at j such that , the separation constraint is not satisfied. A separation constraint violation can be strong or weak. For example, the pair of frequencies 1 and 2 violates a separation requirement of 3. The pair of frequencies 1 and 3 violate this requirement as well but is still a better solution than 1 and 2 and, therefore, should have a lower cost. Frequencies that are part of a MAL with a low fractional load and that violate a separation constraint should not be weighted the same as for non-hopping separation violations. In fact, the separation component is weighted by the burst collision probability, which is the multiplication of the victim's fractional load and the interferer's fractional load.
511
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.73: The Separation tab of the AFP Module Properties dialogue In this example, there is a network with two TRXs on the same cell. The first, TRXi, has a MAL referred to as MALi. It is interfered by TRXk with MALk. TRXi and TRXk have a separation requirement of 2. Their MAL lengths are 5 and 4, respectively. Unfortunately, one of their frequencies is the same (i.e., the separation is 0), while all other frequencies are correct. For a co-channel violation when the required separation is 2, the cost of the separation violation is 90%, as indicated in Figure 8.73 on page 512. Because only one channel of each TRX causes interference, and the length of MALi is 5 and the length of MALi is 4, the collision probability is 1/20. Therefore, the cost to consider is divided by 20: 90/20 or 4.5% for each TRX. Because this example uses frequency hopping, there is an additional hopping gain which provides a slight cost reduction. The exact gain is obtained from the Frequency diversity gain table on the Advanced tab of the Atoll AFP Module Properties dialogue. The gain values are given in dB, and because the two TRXs have different MAL lengths, they have different diversity gains: a gain of 1.4 for a MAL length of 5 and a gain of 1.2 for a MAL length of 4 (assuming the default values were not changed). The diversity gain of 1.4 dB is applied to the separation cost using the following equation:
10
1.4 -------- 10
≈ 1.38
. For TRXi, this result-
ing gain is 4.5%⁄1.38, or 3.25%. 1 90 = 3.41% . The cost will be a little larger because the gain is smaller. For TRXk, the cost will be ------ -----------------------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 combined. 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.
8.5.2.1.6
Interference Cost Traffic on a TRX is interfered if and only if interfering transmitters use the same channel or an adjacent channel. Each case of reuse reduces the amount of good traffic and increases the interference cost. The reuse is weighted by the global interference weighting factor, and takes into account the burst collision probability.
512
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
This example explains how a single interference cost element is calculated. In this example, the network contains only two TRXs belonging to [TX1, BCCH] and [TX2, BCCH]. The interference matrix entry between these two subcells is given in the form of a CDF, a cumulative density function, displayed in Figure 8.74.
Figure 8.74: The interference matrix entry between [TX1, BCCH] and [TX2, BCCH] You can see that the probability of C/I (BCCH of TX2 affecting the BCCH of TX1) being greater than 0 is 100%. The probability of having a C/I at least equal to 31 dB is 31.1%. In the Subcells table, the Min C/I field of the TX1's BCCH subcell of is 12. Therefore, for a C/I level of 12 dB, the probability of interference is 6.5% (because this requirement has a probability of 93.5% of being fulfilled). In order to be converted into cost, the probability of interference 6.5% must be multiplied by the number of time slots, their loads, and the AFP weight.
8.5.2.1.7
Probabilistic Cost Combination In this example, TRX α is subject to a separation violation causing a cost of 30% of T( α ) (where T( α ) is an estimate of the traffic time slots for TRX α weighted by the AFP weight for this TRX) and in addition, a co/adjacent-channel reuse causing this TRX to be 40% interfered. These costs are combined using a probabilistic approach. In this example, the probability of these costs occurring are p(Violation) with a value of 0.3 and p(Interference) with a value of 0.4. The cost of the two together is given by: 1 – ( 1 – p ( violation ) ) × ( 1 – p ( Interference ) ) = 0.58 or 58%
P1, P2, ….Pn are the costs of the probability of a violation of a TRX (one for each of "n" violations). Pn+1, Pn+2, ….Pm are the costs of the probability of interference of a TRX (one for each of "m-n" interferences). Pm+1 is the changing TRX cost described below:
n
The cost of separation for this TRX is therefore: 1 – ∏ ( 1 – Pi )
The additional cost of this TRX is: 1 –
i=1
m+1
n
∏
∏
( 1 – P i ) – 1 – ( 1 – P i ) i=1 i=1
The interference cost uses the "min C/I" value, defined at the subcell level, for which it might have precise interference information. It can apply various gains to this C/I quality target due to frequency hopping and/or DTX.
8.5.2.1.8
The Cost of Missing and Corrupted TRXs It is easy to have a 0-cost solution if the criterion of the required number of TRXs is not fulfilled (for example, by removing all TRXs). This is the main purpose of the missing TRX cost. By default, the exact traffic that a missing TRX was supposed to carry will be counted as a cost. However, you can increase this cost (by 200% for example) if necessary.
513
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Corrupted TRXs are TRXs where the assignment is unusable by the AFP. A few examples of corrupted TRXs would be: • • • •
TRXs with an empty channel list A TRX with a MAL without HSN or without a MAIO for synthesised hopping. A TRX assigned an invalid frequency. A non-hopping or base-band hopping TRX with a MAL that has more than one frequency.
By default, 100% of the traffic that a corrupted TRX is supposed to carry is considered impaired. In some cases, correcting the assignment of resources for a group of corrupted TRXs will not only result in these TRXs being considered corrupted but many other TRXs that, otherwise, would have correctly assigned resources, will also be considered corrupted. 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).
8.5.2.1.9
Cost of Out-of-domain Frequency Assignment If a TRX is assigned out-of-domain frequencies (channels) but has correct ARFCNs, it will have a double influence on the cost: • •
8.5.2.1.10
The usual cost of interference, separation, or modification, and An additional cost of having out-of-domain channels, multiplied by the number of frequencies out of domain and divided by the MAL length.
Preferred Group Cost If a subcell's allocation strategy is group constrained, or if its hopping mode is synthesised hopping, the cost could be influenced by a preferred frequency group in the following ways: • •
When a preferred frequency group is assigned in the subcell table, all frequencies not belonging to this group are considered as interfered if assigned to TRXs of this subcell. If an azimuth-oriented pattern is required by the AFP, then the AFP itself will choose the preferred frequency groups. The AFP will correlate its choice with the azimuth direction.
The group constraint weight is meant to be kept very low. Otherwise it becomes equivalent to a domain constraint. The group constraint weight in converted into a cost as follows: each use of an out-of-group frequency is equivalent to a small amount of interference. This interference is then combined with the other sources of interference and multiplied by the traffic (time slots, load, and AFP weight).
8.5.2.1.11
Intermodulation Cost The purpose of this cost component is to avoid cases where intermodulation can cause problems. It is therefore defined slightly more strictly than in real cases where intermodulation effects occur. The intermodulation violations are summarised as a tax, since they always have relatively low interference probabilities. This tax is applied when the combination of allocated frequencies generates a frequency already allocated within the same site. The weight of the tax depends on the type of combination (order, harmonics, or various amplification spreading violation), on whether the combination of DL frequencies affects UL frequencies, or whether the intermodulation takes place within a same site, transmitter or equipment. Each ARFCN carrier number refers to two physical frequencies: the uplink frequency and the downlink frequency. The translation function from ARFCN to frequency is given by the ARFCN standard. Each physical frequency used in a site could be subject to a second (or third) order or a VASP (Various Amplification Spreading Violation) inter-modulation separation violation. If there are two frequencies, X and Y where X < Y, the following table describes the separation constraint:
514
Constraint Order
Condition
Constraint Applied To
Second order (Harmonics)
Y=2X
X and Y
VASP
Y < X + 600 kHz
X and Y
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
If there are three frequencies, f1, f2, f, the following table describes the separation constraint: Constraint Order
Condition
Constraint Applied To
Second order
f=f1+f2
f, f1 and f2
Third order
f=2f1-f2 f=f1-2f2
f, f1 and f2
The preceding tables summarise five types of violations. Each type has a default weight: Constraint Type
Weight
Second Order
0.02
Harmonics
0.01
VASP
0.0002
Third order
0.002
The costs detailed up to this point are added together and weighted with the inter-modulation weight W, the UL/DL component weight, and the equipment sharing weight. In each intermodulation violation there is an interfering frequency (or frequencies) and an interfered frequency. In all the preceding equations except the VASP, the generator frequency is on the right side of the equations while the interfered frequency is on the left site. The VASP case corresponds to two violations: in the first, the lower frequency is the generator, and the higher frequency is the interfered. It is assumed that the generator frequencies are either all on the uplink or all on the downlink, otherwise, no violation is considered. The interfered frequency can be a downlink or uplink frequency as well. Therefore, there are 4 cases for which 4 weights will multiply the violation cost. Generator Frequencies
Interfered Frequencies
Weight
Description
DL
UL
5
High power amplification pollution interferes with the RX, causing an important noise rise
UL
UL
1
High power received signals generate an inter-modulation product on a weakly received interfered frequency
DL
DL
1
Downlink power control is active over the interfered frequency but is not active over the generators, which generate high noise on the interfered signal
UL
DL
0
This type of interaction can be ignored
The final weight concerns the equipment sharing. This aspect has a crucial effect on the importance of intermodulation. In Atoll, it is assumed that sharing a site implies sharing a transmitter and that sharing a feeder and antenna implies co-cell cohabitation. For co-cell intermodulation (generating frequencies as well as IM belong to the same cell) the intermodulation cost is multiplied by 5.
8.5.2.1.12
Quality Target It is often necessary to deal with small and large amounts of interference differently. For example, an operator might prefer to have 10 transmitters with 2% interfered traffic on each, rather than to have 2 transmitters with 10% interfered traffic on each. On the Cost tab of the Atoll AFP Properties dialogue, you can choose to ignore the interference and separation costs that do not add up to the value of the Accepted Interference Percentage set in the Subcells table for each subcell by clearing the Summed cost of all TRXs check box. TRXs that have a lower percentage of interference than the Accepted Interference Percentage are considered to have no interference and are excluded from the total cost. In other words, the AFP dismisses any TRX whose quality is better than the quality target, enabling it to concentrate the optimisation on the TRXs that really need improvement.
515
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
8.5.2.1.13
© Forsk 2012
Minimum Reuse Distance The Atoll AFP can take into consideration a minimum reuse distance when assigning frequencies or BSIC. Using a minimum reuse distance can help compensate for inaccuracies in the interference matrices or other input data. The reuse distance is considered as a soft constraint. Because the reuse distance is an estimation of possible interference, it is added to the interference probability. The minimum reuse distance is combined as a tax with the interference probability as follows: 1 – (1 – i) × (1 – d)
where i is the interference probability and d is the minimum reuse distance. In the following example, the interference probability is 0.12 and the reuse distance 0.023: 1 – ( 1 – 0.12 ) × ( 1 – 0.023 ) = 0.14024
The tax on reuse distance is defined on the Protection tab of the Atoll AFP Properties dialogue. The tax applied on reuse distance is associated with any additional protection against adjacent channel reuse. The greater the additional protection against adjacent channel reuse defined on the Protection tab, the greater the distance tax. The number of relations based on distance taken into consideration for each transmitter is limited for performance reasons. You can define the maximum number of relations by setting the "GlobalDistanceMatrixDegreeUB" option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual.
8.5.2.1.14
AFP Shadowing Shadowing is important for the AFP. Within the context of the AFP, shadowing is implemented by setting the definition of interference as Flexible on the Protection tab of the Atoll AFP Properties dialogue. Shadowing is so important that in some cases it is enabled automatically, for example, if the interference matrices themselves were not calculated with shadowing. AFP shadowing is applied in relation to the quality threshold. When enabled, traffic having C/I conditions slightly worse than the required threshold is not considered 100% interfered. At the same time, traffic having C/I conditions that are only slightly better than the threshold is not considered as 100% good. This shadowing is performed by repeatedly accessing the CDF function as explained in "Interference Cost" on page 512.
8.5.2.2 Setting the Parameters of the Atoll AFP Module You can define the Atoll AFP-specific parameters used when calculating the cost and set some guidelines for the Atoll AFP module by using the Atoll AFP Module Properties dialogue. To open the Atoll AFP module Properties dialogue: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the AFP Modules folder. 4. Right-click the Atoll AFP Module folder. The context menu appears. 5. Select Properties from the context menu. The Atoll AFP Module Properties dialogue appears. The Atoll AFP Module Properties dialogue consists of 10 tabs: General, Cost, Separation Weights, Interference Matrices, HSN, MAL, Execution, Spacing, Protections, and Advanced. The Cost, Separation Weights, Interference Matrices, Protections, and Advanced tabs include parameters that are taken into account when estimating the cost. The Finalisation tab provides options on how the AFP runs. The other tabs are used to define the allocation strategies for HSN, MAL, MAIO, and BSICs assigned by the AFP. You can make copies of the Atoll AFP module and set different parameters for each copy. All copies will be available in each AFP session. In other words, you will be able to choose from the list of all Atoll AFP modules, each with its own defined parameters. The settings of each Atoll AFP module are saved in the Atoll document but they can also be archived in the database so that all users connected to the same centralised database can use them. For more information on archiving Atoll AFP module settings, see the Administrator Manual. For information on setting the parameters on each of the tabs of the Atoll AFP module, see the following: • • • • • • • •
516
"The Atoll AFP General Tab" on page 517 "The Atoll AFP Cost Tab" on page 517 "The Atoll AFP Separations tab" on page 518 "The Atoll AFP Interference Matrices Tab" on page 520 "The Atoll AFP HSN Tab" on page 521 "The Atoll AFP MAL Tab" on page 521 "The Atoll AFP Finalisation tab" on page 522 "The Atoll AFP Reuse tab" on page 523
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
• •
8.5.2.2.1
"The Atoll AFP Protection Tab" on page 524 "The Atoll AFP Advanced Tab" on page 526
The Atoll AFP General Tab The General tab of the Atoll AFP Module Properties dialogue enables you to change the name of the Atoll AFP module. For example, if you have created a copy of the Atoll AFP and modified some parameters in order to customise the copy for a specific situation, you can give the copy a descriptive name. To display the General tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 516. 2. Click the General tab. 3. Change the name of the Atoll AFP module.
8.5.2.2.2
The Atoll AFP Cost Tab The Cost tab of the Atoll AFP Module Properties dialogue enables you to define the different components that make up the global cost. A component will be taken into consideration by the AFP if it is selected. If its cost or weight is "0," it will not be taken into consideration. The most important parameters on this tab are the interference and separation weights. These are used as multiplicative factors for each incidence of interference or violation. In other words, these parameters can reduce cost. If these two parameters have low values (for example, 0.1 for interference and 0.035 for separation), the AFP will be forced to work using an edge-oriented strategy, which is not the best approach. By default, interference costs are less important than separation violation costs. The second most important parameter is the cost of modifying a TRX. This parameter should be set if the non-locked part of the network is to be changed as little as possible. The example in the following table shows how this parameter can affect total costs. In this example, there is a network with a total of 90 transmitters. 15 of these transmitters are locked. Out of a total of 257 required TRXs, only 193 good TRXs have already been allocated. This leaves 64 TRXs that will have to be created and allocated affecting the other 193 as little as possible: Cost
Effect
For a cost of changing a TRX = 1
AFP changed only 98 TRXS
For a cost of changing a TRX = 0.3
AFP changed only 129 TRXS
For a cost of changing a TRX = 0.1
AFP changed only 139 TRXS
For a cost of changing a TRX = 0
AFP changed 162 TRXS
Selecting the Summed cost of all TRXs check box makes the AFP take the cost of all TRXs into account, whether or not they exceed this quality target. If you clear this check box, the AFP will only take into account the costs of TRXs which do not fulfil the quality thresholds defined in their corresponding subcells. In other words, the AFP dismisses any TRX whose quality is better than the quality target, enabling it to concentrate the optimisation on the TRXs that really need improvement. To display the Cost tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 516. 2. Click the Cost tab (see Figure 8.75).
517
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.75: AFP Module Properties dialogue - Cost tab 3. Under Tax 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 cost each applied to the total cost each time intermodulation might occur because of the allocated frequencies. 5. Under TRX Component, 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 512. 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 511. 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 513. Outside preferred group: If desired, select the check box to make it active and set the cost of an allocated frequency being outside of the preferred group. For more information on the cost of using a frequency outside of the preferred group, see "Preferred Group Cost" on page 514.
6. If desired, select the Summed cost of all TRXs check box to make it active. The AFP will take into account the summed cost of all TRXs, including those that fulfil the quality thresholds defined in their corresponding subcells. 7. Under Traffic, select the traffic source the AFP will use during optimisation: •
•
8.5.2.2.3
Based on the traffic demand (from the Subcells table or default traffic capture): If you choose to use the traffic demand, the AFP will use either the traffic demand defined in the Subcells table or the default traffic capture (depending on what you select when you run the AFP optimisation). Based on the traffic demand calculated from traffic load, number of required TRXs, blocking probability, and Erlang B formula: If you choose to use this option, the AFP will calculate the traffic demand from the traffic load, the number of required TRXs, the blocking probability, and the Erlang B formula.
The Atoll AFP Separations tab The Separations tab of the Atoll AFP Module Properties dialogue enables you to define a weight for each type of separation constraint violation or partial violation.
518
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
You can assign a weight between 0 and 1 for the following types of separation constraint violations: • • • •
Co-cell separation violations 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 infor a partial separation constraint violation. You can also add and remove partial separation constraints using the Add Separation and Remove Separation buttons at the bottom of the tab. To display the Separations tab of the Atoll AFP module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 516. 2. Click the Separations tab (see Figure 8.76).
Figure 8.76: AFP Module Properties dialogue - Separations tab 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.
3. If desired, modify the weight for each of the following: • • • •
Co-transmitter violations Co-site violations Violations between neighbours Violations between exceptional pairs
519
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
8.5.2.2.4
© Forsk 2012
The Atoll AFP Interference Matrices Tab The Interference Matrices tab of the Atoll AFP Module Properties dialogue enables you to define weights that are used to define how interference matrices are combined. 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: • • •
Whether the interference matrix is within 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 516. 2. Click the Interference Matrices tab (see Figure 8.77).
Figure 8.77: AFP Module Properties dialogue - Interference Matrices tab The first component in combining interference matrices is whether a given interference matrix entry is within the scope of the AFP. 3. Under The type of interference matrix, define the parameters for each section: •
Overlapping area based on path loss matrices • •
•
OMC statistics • • •
•
Signal level measurements (RXLEV), neighbours only Signal level measurements (RXLEV), neighbours and extended neighbours Based on reselection
Measurement analysis • •
520
Ratio of overlapping surface Ratio of overlapping traffic
Based on drive test data Based on CW measurements
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
• •
8.5.2.2.5
Based on scan measurements
Under Component depending on the interference matrix quality indicators, the Active check box is selected and cannot be cleared. The Atoll AFP always includes the quality matrix specific to each type of interference matrix when combining interference matrices.
The Atoll AFP HSN Tab The HSN tab of the Atoll AFP Module Properties dialogue enables you to define how the HSN will be allocated when synchronised frequency or base-band hopping is used. 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 516. 2. Click the HSN tab (see Figure 8.78).
Figure 8.78: AFP Module Properties dialogue - HSN tab 3. Under Allocation, select how the HSN will be allocated: • • • •
8.5.2.2.6
By Subcell By Transmitter By Site Free.
The Atoll AFP MAL Tab The MAL tab of the Atoll AFP Module Properties dialogue enables you to define Mobile Allocation List patterns and length priorities when synchronised frequency or base-band hopping is used. 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 516. 2. Click the MAL tab (see Figure 8.79).
521
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.79: AFP Module Properties dialogue - MAL tab 3. Under MAL allocation type, select how the MAL will be allocated for groups of synchronised subcells. • •
Same MAL for all the subcells of a synchronised set, or 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. If you select Max MAL length, you do not need to set any other constraints. If you select Max MAL Length, it is not necessary to set any other constraints.
c. If you selected Adjust MAL lengths, set the following parameters to define how the Atoll AFP will set MAL lengths: i.
Define the value that MAL length/Domain size must not be equal to or greater than.
ii. If you selected Different MALs within a synchronised set as the MAL allocation type in step 3., you can select a Long or Short MAL Strategy (with the option of keeping MAL long enough to allow a certain pattern). iii. Define a Target fractional load and select the Automatic adjustment check box if you want to give the AFP the possibility of modifying this value automatically. The fractional load is It is recommended that you let the AFP automatically adjust the target fractional load.
8.5.2.2.7
The Atoll AFP Finalisation tab The Finalisation tab of the Atoll AFP Module Properties dialogue enables you to define the behaviour of the Atoll AFP module when it reaches the end of the calculation time.
522
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
To display the Finalisation 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 516. 2. Click the Finalisation tab (see Figure 8.80).
Figure 8.80 AFP Module Properties dialogue - Finalisation tab 3. Under Target CPU time, select how the AFP uses the user-defined target computation time: •
•
Fixed duration: If you select Fixed Duration, the AFP stops when this time has elapsed. If a stable solution has been found prior to this limit, the allocation stops. Fixed duration corresponds to the minimum amount of time you reserve for the AFP to find the best solution. Directive duration: This is the Atoll AFP's default. If you select Directive duration, the TCT is used by the AFP 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.
4. Under Result Assignment, select how the AFP assigns the results once the automatic allocation has stopped: • •
8.5.2.2.8
Manual Assignment: You can analyse the best plan before committing it to the document. Automatic Assignment: The AFP automatically assigns the best plan to the document. This approach is recommended if Auto Backup is enabled.
The Atoll AFP Reuse tab The Reuse tab of the Atoll AFP Module Properties dialogue enables you to define an allocation strategy if the selected allocation strategy is "free." To display the Reuse 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 516. 2. Click the Reuse tab (see Figure 8.81).
523
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.81: AFP Module Properties dialogue - Reuse 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 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: • •
8.5.2.2.9
Staggered: The MAIOs assigned to TRXs of a subcell are evenly spaced. Free: The AFP module freely assigns MAIOs.
The Atoll AFP Protection Tab The Protection tab of the Atoll AFP Module Properties dialogue enables you to define additional strategies to evaluate interference. To display the Protection tab of the Atoll AFP Module Properties dialogue: 1. Open the Atoll AFP Module Properties dialogue as explained in "Setting the Parameters of the Atoll AFP Module" on page 516. 2. Click the Protection tab (see Figure 8.81).
524
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.82: 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: • • •
None: no additional protection is added. Weak: 1.5 dB is applied to the initial protection. Strong: 2.5 dB is applied to the initial protection.
For more information about protection against adjacent channel reuse, see "Adjacency Suppression" on page 525. 4. Under Interference definition with respect to the required quality threshold, set a C/I weighting margin around the required quality threshold in order for the AFP to consider the traffic having close-to-threshold C/I conditions as neither 100% satisfactory nor 100% corrupted. For more information, "Interference Cost" on page 512. • • •
Rigid: If you select Rigid, the AFP will evaluate interference only at the defined quality threshold. Intermediate: If you select Intermediate, the AFP will evaluate interference at 3 reference points: the defined quality threshold, and at +/- 2 dB of the quality threshold. Flexible: If you select Flexible, the AFP will evaluate interference at 5 reference points: the defined quality threshold, at +/- 2 dB of the quality threshold, and at +/- 4 dB of the quality threshold. Selecting Flexible has the same effect as shadowing. For interference matrices based on propagation, Atoll can determine whether they have been calculated with shadowing. If shadowing has not been taken into account, the AFP can adapt its settings to more realistically model the network. In other words, if you do not take shadowing into consideration when calculating the interference matrix, Atoll can automatically change its definition of interference from rigid to intermediate, or even to flexible.
Adjacency Suppression Adjacency suppression is defined as the difference between the required C/I and the required C/A (C/A being the "Carrier to Adjacent Intensity ratio"). By default this is set to 18 dB following the GSM specification. You can change this value in the Properties dialogue of the Network Settings folder. When the value of this parameter is used in the AFP (to extract the interference caused by an adjacent channel) you can apply a small safety margin, temporarily reducing the 18 dB to 16.5, or even to 15.5. This safety margin is applied only in the AFP; Atoll's predictions continue to apply the full adjacency suppression.
525
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
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 to strong.
8.5.2.2.10
The Atoll AFP Advanced Tab In the next section, we saw how the fractional load is taken into account: If only one frequency in a MAL is interfered or has a separation violation and the MAL length is 5, then the TRX cost effect will be 1/5 (i.e., 20%) interfered. This means the cost will be 5 times smaller than if the entire MAL was composed of frequencies which are interfered or have a separation violation. In the AFP, the fractional load directly affects the cost. For example, if the MAL length is n, and one of the frequencies has a cost of X, then for the entire MAL the cost will be X/n. If this same MAL is repeated in m TRXs of the transmitter, then the cost will be X*m/n. Although you could create very long MAL in order to reduce the size of m/n, this is an inappropriate solution. Because of the fact that the more n is big, the more we have cost effects: • •
We have more frequencies over which the cost effects are counted. It is harder to find clean frequencies since all frequencies are used all over.
The more the MALs are long, the less we have the benefice of FDM principle which is the main source of the GSM spectral efficiency. It is therefore easy to prove and to demonstrate that the fractional load cost all alone will privilege non hopping and base band hopping plans, where the fractional load is 1. (m = n) This corresponds to the case where all gains are 0 in the advanced property page below:
Figure 8.83: 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.
526
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
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.
8.5.2.3 Frequency Hopping Overview Atoll AFP is capable of performing both free MAL assignment (sometimes called ad hoc), as well as predefined MAL assignment. The instruction indicating the assignment mode to be used is at subcell level: i.e. different subcell can each indicate a different assignment mode. In free assignment mode, the AFP is free to assign any MAL (assuming of course that it belongs to the domain, and not too long). The length of MAL, the HSNs and the MAIOs are assigned in compliance with the user's directives. If the assignment mode is group constrained, the AFP can only assign one of the predefined groups in the domain.
8.5.2.3.1
The Case of Synthesised Hopping + Group Constrained If you are working on a group constrained assignment mode, the success of your assignment will strongly depends on the definition of the groups in the domain. We recommend you work as following: Step 1: decide what will be the MAL size(s) that your domain will permit. Choosing a single MAL size is a current option. Choosing multiple MAL sizes is often called MPR: Multiple pattern Reuse. The more MAL sizes you have the more optimised will be your allocation. We recommend MPR. Step 2: For each length you have chosen, create as many groups as possible having the specific length and if possible, covering the entire domain. Example, For a domain of 60 frequencies, create: 3 groups of 20 frequencies each (mainly reserved for the preferred group allocation of an azimuth oriented allocation) 10 groups with 12 frequencies each + 12 groups of 10 frequencies each (will be used in heavy traffic cases or in "HSN by site" cases). We are giving an example where there are so many groups that some of them must overlap. In addition we could define 20 groups with 6 frequencies each, 24 groups of 4 frequencies each, and even 30 groups with 4 frequencies each. By thus each frequency will belong to an average of 11 groups. Do not hesitate to create groups, the AFP likes groups. When many groups are defined, the quality is almost as good as with free assignment. • •
•
•
8.5.2.3.2
Currently, the AFP always assigns the same MAL to all TRXs within a subcell. The "group constrained" assignment mode is applicable for SFH only. In NH and BBH, the group constrained mode will only concern the respect of the preferred group. Which is a different issue. There is no contradiction between proffered group respect and the pre defined MAL assignment in SFH. When both are relevant, each of the predefined MALs can be more or less included in the preferred group and therefore more or less "preferred". When azimuth oriented pattern allocation is performed at the same time as predefined MAL allocation, only the biggest groups in the domain will be used for the pattern, while the small ones will be used for MAL assignment.
An Atom = A Perfectly Synchronised Set of Equi HSN SFH Subcells An atom is a set of synchronised subcells that share the same HSN, the same frequency domain and have the same length MAL. The MAIO assignment of an atom manages the frequency collisions between the MALs of the atom. If an atom contains more than one subcell, the AFP may assign to it partially different MALs (depending on a user-definable option) but it will always consider the fact that the subcells are synchronised. Atoms can be determined by the user or by the AFP via the HSN allocation. Some restrictions on this definition exist due to some extreme cases: • •
If two subcells have different domains, they cannot belong to the same atom. If two subcells have different limitations on "Max MAL Length", they cannot belong to the same atom.
A warning is generated when HSN assignment directives contradict with these restrictions. You can force the AFP to always assign the same MAL among the subcells of the Atom. When calculating the cost of a TRX in an Atom: It is possible that none of the co-Atom TRXs interfere with the given TRX. This is the most common case, and it is due to the fact that the "on air" frequencies are never the same. However, it is possible that intra-Atom interference exists. In that case, the burst collision which is calculated conform to the MAIO definitions, multiplies the interference probability.
527
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
8.5.2.3.3
© Forsk 2012
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).
8.5.2.3.4
Optimising Hopping Gains If the AFP was given a degree of freedom when choosing MAL lengths, it may opt for longer MAL lengths. In this way, it can profit more from the hopping gains. On the other hand, it might be increasingly hard to find frequencies for these MALs The advanced page, the MAL page, and the HSN page in the AFP property pages provides the capacity to control this convergence. For more details, see the advanced page description. In interference limited network, the default hopping gain values are not sufficiently strong to cause the AFP to converge toward long MALs.
8.5.2.3.5
Fractional Load The Atoll AFP uses the user-defined fractional load as a guide when assigning the HSN and determining the MAL length. A fractional load of X is obtained if the number of TRXs using a certain MAL is only X times the length of the MAL. In Atoll, fractional load does not take the traffic load into consideration. Because the fractional load cannot always be met, this parameter is considered a guide rather than a constraint. When it can be met, the AFP chooses either a MAL length 1/X times longer than the number of TRXs in the biggest subcell of the atom or a MAL length 1/X times longer than the sum of all TRXs in the atom. These are called "the short MAL strategy" and "the long MAL strategy" respectively. You can choose between the two in the MAL tab of the properties dialogue. The value of the fractional load parameter can also be edited and, furthermore, it can even be automatically calibrated by the AFP. • •
8.5.2.3.6
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).
Domain Use Ratio Both HSN assignment and MAL length determination processes are tuned to avoid exceeding a user defined Domain Use Ratio. Domain Use Ratio is the MAL length divided by the total number of frequencies in the domain. For example, a 1/1 reuse pattern has a frequency reuse ratio of 1. A 4/12 reuse pattern can have a reuse ratio between 1/4 and 1/12, depending on whether all TRXs in a site have the same MAL (and HSN) or not.
8.5.2.3.7
HSN Allocation The AFP assigns HSNs at subcell level. It chooses different HSNs for interfering and non-synchronous subcells. For synchronous subcells (usually within a site), the AFP can opt to assign the same HSN and different MAIOs within the set of same-HSN subcells. According to the adapted convention on HSNs for BBH TRXs, the AFP allocates different HSNs to the BCCH TRX and TCH TRXs. The 1st HSN corresponds to timeslots 1 through 7 of the BCCH and TCH TRXs, and the second HSN corresponds to the timeslot 0 of the TCH TRXs only. The second HSN is used in predictions.
The user can control the HSN allocation so that it performs one of the following: • • • •
8.5.2.3.8
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).
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
528
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
averages the cost upon all frame numbers in the synchronised case and upon all collision probabilities in the non-synchronised case.
8.5.2.4 Azimuth Oriented Assignments (Pattern Allocation, 1/1 1/3 1/x …) In order to understand what a pattern allocation in Atoll's AFP is, you must first read the previous chapters, since the pattern allocation in Atoll is performed as following: 1. The AFP first assigns preferred groups to all demanding subcells 2. The AFP assigns what ever needs to be assigned, trying to respect these preferred groups, as explained in the cost description. The conditions for getting a preferred group from the AFP are the following: • • • • • • •
The subcells must be or in synthesised hopping mode, or must have a group constrained allocation directive. This condition is also the condition that determines weather a user defined preferred group can impact the cost. The pattern directive in the AFP property pages defines if we are doing 1/1, 1/3 or 1/5 pattern allocation. By default it is set to 1/3. We will now refer to its value as X. The AFP group weight must not be 0. Only the X biggest groups in the domain will be considered as candidates for the proffered group allocation. Only transmitters in the AFP scope will get a preferred group. The AFP assigned preferred group will overwrite whatever used defined preferred group. Only transmitters that are not lonely in their site will be entitled to a preferred group: •
•
The pattern allocation associates the X main direction axises with the X biggest groups in the domains • • •
• •
Not lonely means that other transmitters of the same band, and layer, (and also active), exist in the site. It assumes these groups are disjoint. It finds the main axis azimuth as the most commune azimuth, and then it spans the other directions so that all the X axises are equi spread. It matches each directional axis to a group.
The AFP will only allocate a preferred group if the transmitters azimuth is clearly aligned with one of the directional 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 using this because it regulates the assignments, and helps the AFP to exist local minima. Be sure to always have 3 big and disjoint groups in your domain. (If the majority of your sites are X-sectorial, X should replace 3). We recommend not imposing the pattern very strongly on your network. It should be kept as a guideline.
8.5.2.5 BSIC Allocation The BSIC allocation algorithm of the AFP includes both hard and soft constraints. The hard constraint is easier to satisfy but must not be violated. A hard-constraint violation is equivalent to an error, and corresponds to handover failures in the network. The soft constraint is more difficult to fully satisfy, and violations of the soft constraint can exist in an operating network. A soft-constraint violation is equivalent to a warning. The hard and soft constraints can be defined as follows: •
Hard Constraint: The same BSIC must not be allocated to two transmitters that: •
have the same BCCH frequency and
•
have first- or second-order neighbour relations.
It is only based on first and second order neighbour relations and BCCH co-channel reuse. •
Soft Constraint: The same BSIC should not be allocated to two transmitters that: •
have the same or adjacent BCCH frequencies and
•
have first- or second-order neighbour relations, or interfere each other.
It is based on first- and second-order neighbour relations, interference matrices, and co- and adjacent channel BCCH reuse. This means that the soft constraint is more demanding than the hard constraint, and has a higher probability of not being satisfied. If the AFP is unable to satisfy the soft constraints, the BSIC allocation algorithm assigns the "least interfering" BSIC to transmitters depending on the interference and separation relations. This leads to increasing the same BSIC+BCCH reuse distance as much as possible.
529
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
In the preceding definitions, all neighbour relations between transmitters are considered, independently of the direction, as shown in Figure 8.84 on page 530.
Figure 8.84Neighbour Relations The same applies for the interference relation; i.e., two transmitters are considered to interfere each other whether the first interferes the second, the second interferes the first, or both interfere mutually. During the allocation, the AFP counts the number of times it was unable to allocate a BSIC due to a constraint that was not satisfied. The AFP respects the BSIC domains defined for transmitters and takes into account the BSIC spacing strategy selected on the Reuse tab of the AFP properties dialogue: • •
Min.: The AFP assigns the minimum possible number of BSICs that satisfies the constraints. Max.: The AFP assigns as many BSICs as possible while keeping them evenly distributed.
8.5.3 Advanced AFP usage Whenever a network becomes spectrum-wise limited, frequency planning becomes the most cost efficient way to optimise its performance. The AFP usage in these cases must evolve in order to include the more advanced capacities of the AFP.
8.5.3.1 Optimising the Number of Required TRXs One of the two new allocation styles is the one in which the AFP is permitted to optimise the number of required TRXs. When this option is selected, the AFP may reduce the number of TRXs compared to the number of required TRXs in order to maximise the amount of correctly served traffic, and consequently, reduce the level of interferences. In the same way, for highly traffic-loaded subcells, the AFP may increase the number of TRXs compared to what is required in order to reduce the blocked traffic. The circuit and packet demand are the two main inputs used for estimating the blocking rates. They can be either directly extracted from the subcell table, or come from the default traffic capture, or be re-estimated by the Atoll AFP Module. It will perform do it using the old traffic load, and the number of required TRXs as input. 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.
530
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
8.5.3.1.1
Soft Blocking Versus Hard Blocking In Performance Enhancements in a Frequency Hopping GSM Network, the authors suggest (as have many others) that network quality is a trade-off between soft blocking and hard blocking.1 Soft blocking is due to interference-related effects (such as dropped calls), which is addressed by frequency planning, while hard blocking is due to circuit shortage during the busiest periods which is addressed by dimensioning. One cost component of the AFP models hard blocking (dimensioning), based on the Erlang B theory. The AFP is therefore capable of finding the optimal trade-off point between soft and hard blocking. The trade-off point is not a global one, but rather is specific to each TRX. The issue of dimensioning during the AFP process is discussed in the following sections: • •
"The Advantage of Combining Dimensioning and Frequency Planning" on page 531 "The AFP and Local Frequency Availability" on page 531.
The Advantage of Combining Dimensioning and Frequency Planning Given the difficulty inherent in combining dimensioning and frequency planning, it is often tempting to do each separately. However, by combing dimensioning and frequency planning, as done by the Atoll AFP, you can exploit local variations of soft versus hard blocking measure and thereby better enhance of network capacity. The advantage of adjusting the number of TRXs while making an automatic frequency allocation is demonstrated in "Example of Combining Dimensioning and Frequency Planning" on page 533. The basic advantage of combining the two is that you can avoid the need to manually find a target blocking rate.
When evaluating the resulting frequency plan, it is important to keep in mind how this frequency plan was created: it was created to maximise the correctly served traffic instead of trying to simply minimse the interfererd traffic. For example, if plan A has more TRXs than plan B, it is possible that an interference prediction for plan A will display more interference, even if plan A is the best plan. It consists on the positive attitude: trying to maximise the correctly served traffic instead of trying to minimise the interfered traffic. The AFP and Local Frequency Availability Combining both soft and hard blocking, the AFP optimises the amount of correctly served traffic for each individual transmitter using frequencies available to it. In this example, there is a transmitter with two subcells: TCH and BCCH. The two subcells absorb the traffic demand together. Let us assume that the traffic demand consists of 25 Erlangs of circuit-switched traffic, and 5 timeslots of packet-switched traffic. Let us also assume that the required number of TCH TRXs is 2 with 1 BCCH TRX. The AFP could just assign 3 TRXs in this cell, exactly as required, or it could study a few additional possibilities: • •
Assign only 2 TRXs, thereby reducing interference. Assign 4 TRXs (one additional TRX), thereby reducing the blocking rate.
The AFP calculates the best option as follows: 1. It calculates the available number of circuits (depending on the HR — half-rate — ratio). 2. Then it calculates the blocking rate using the Erlang B equation and the circuit-switched demand. 3. Once the AFP has calculated how much traffic is served, it can calculate the traffic load (from 0 to 1, with "1" corresponding to a full load). 4. With the traffic load calculated, the AFP can calculate the interference cost as well as the hard blocking cost. The cost representing the interference depends on which frequencies were assigned. The more TRXs there are, the harder it is to find frequencies that are free from interference. In this example, the locally available frequencies are as follows: Only 2 frequencies (f1 and f2) have low interference (i.e., probability of interference = 10%). One frequency (f3) has a medium level of interference (20%). One frequency (f4) has a high level of interference (30%). All the other available frequencies are even more heavily interfered.
1. Thomas Toftegaard Nielsen and Jeroen Wigard, Performance Enhancements in a Frequency Hopping GSM Network(Springer, 2000), 68.
531
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
The entire process is summarised in the table below: Number of circuits
Blocked Traffic (Timeslots)
Traffic load (%)
Interfered traffic on f1 and f2 (Timeslots)
2 TRXs: using f1 and f2.
21
7.4
100%
1.5
0: Since it is not used
0: Since it is not used
Frequency plan 2:
3 TRXs: using f1, f2 and f3.
32.2
0.55
97.7%
1.46
1.56
0: Since it is not used
Frequency plan 3:
4 TRXs: using f1, f2, f3, and f4.
43.4
0: No blocking with 4 TRXs.
74%
1.1
1.18
1.77
Frequency Plan
TRXs
Frequency plan 1:
Interfered traffic on f3 (Timeslots)
Interfered traffic on f4 (Timeslots)
The best plan depends on the locally available frequencies: if there was less interference, the AFP would have chosen frequency plan 3. If f3 and f4 where heavily interfered, the AFP would have chosen frequency plan 1. Because the AFP tries to minimise what is in bold in the table above (i.e., the blocked and interfered traffic), it chooses frequency plan 2 (in which the figures in bold add up to 3.57 timeslots).
8.5.3.1.2
The Sources of Traffic Demand Used by the AFP The Atoll AFP one of several sources for traffic demand: traffic demand can be taken from traffic captures, as is the case with traffic loads, or traffic demand can be entered into the Subcells table using data from the OMC, or the AFP can use traffic loads to calculate traffic demand (if maintaining compatibility with older documents is a concern). • • •
"Traffic Captures as a Source of Traffic Demand" on page 532 "OMC Data as a Source of Traffic Demand" on page 532 "Traffic Loads as a Source of Traffic Demand" on page 532
Traffic Captures as a Source of Traffic Demand If you choose to use traffic maps, a traffic capture can supply the traffic demand. Then, by performing dimensioning or a KPI calculation, this information is committed into the Subcells table. Afterwards, when running an automatic frequency allocation, you can then choose to have the AFP use the traffic information from the default traffic capture or from the Subcells table. OMC Data as a Source of Traffic Demand The traffic demand can come from the OMC and be imported into the Subcells Table: Traffic Data table. For more information on importing OMC traffic into the Subcells Table: Traffic Data table, see "Importing OMC Traffic Data into the Subcells Table: Traffic Data" on page 436. The Subcells Table: Traffic Data table sA specific table is defined in order to absorb OMC traffic readings. To open it: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Subcells > Subcells Table: Traffic Data from the context menu. The Traffic data part of the Subcells table appears. By importing Subcells Table: Traffic Data table into the fields for the BCCH and TCH subcells (which share the same field as they are assumed to share the same traffic management unit) and into the TCH_INNER subcells field, where they exist, you supply the AFP with your OMC traffic. Traffic Loads as a Source of Traffic Demand The AFP can use traffic loads to calculate the traffic demand (if maintaining compatibility with older documents is a concern). Previously, the AFP used the field "traffic load" and the number of required TRXs as its traffic source. When the required number of TRXs is adjusted, 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 user to maintain compatibility with the old traffic model.
8.5.3.1.3
How to control the optimization so that it allocates more or less TRXs? There are several mechanisms by which you can set the AFP to allocate more or fewer TRXs: you can modify the traffic demand to have more or fewer TRXs allocated, you can modify the weights for the interference and separation violation costs, or you can modify the tax for missing (or superfluous) TRXs. Increasing the Traffic Demand to Increase TRX Allocation
532
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
The more there is a demand, the higher will be the pressure on the AFP to allocate more TRXs. As said above, the demand can come, or from the traffic model, or from the subcell table, or from the traffic load values. If demands come from the traffic capture, you can increase demand by recalculating the capture with a higher traffic coefficients. If the demands comes from the OMC, you can bust it up using a spreadsheet. And if it comes from the traffic loads you can do the following: In the AFP property pages, where you indicate that the demand should be regenerated from the traffic loads, you are also requested to bound the actual blocking rate (actual with respect to the number of required TRXs). This is because of the following reason: If your served traffic load is 100%, theoretically, only an infinite circuit demand can generate such a load…
Figure 8.85: 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 where 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…
8.5.3.1.4
Example of Combining Dimensioning and Frequency Planning The following example demonstrates the advantages of combining dimensioning and frequency planning: •
"Less Interference" on page 534
533
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
• •
© Forsk 2012
"Re-adjusting the Number of TRXs to Match OMC Traffic" on page 535 "Frequency Domain and Frequency Band Balancing" on page 536.
Less Interference The example shows that interference can be greatly reduced. The following graphs show the effect of adjusting the number of TRXs on the interfered and served traffic, compared to the initial dimensioning.
Figure 8.86: Effects of adjusting the number of TRXs on traffic
534
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.86: Effects of adjusting the number of TRXs on traffic The preceding 4 frequency plans were all generated using exactly 50 frequencies. All other network parameters remained the same. In the plan "Dim - 76 TRXs" many TRXs were removed by the AFP (76 out of 820). Removing the TRXs reduced interference by a considerable margin but had no impact on the amount of served traffic because reducing TRXs was only considered if the transmitter's load was low. Re-adjusting the Number of TRXs to Match OMC Traffic In a real network, it is often necessary to re-adjust the number of TRXs to match evolution of the traffic. A typical situation is the following snap shot; taken before any adaptation is made.
Figure 8.87: Number of required TRXs vs. Erlang Demand It is normal that not all transmitters having the same number of TRXs have the same traffic demands, therefore the traffic loads will often vary from one transmitter to another. Once the AFP performs its optimisation, the traffic loads become more uniform, as can be observed in the following graph.
535
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.88: Load comparison before and after TRX adjustment Frequency Domain and Frequency Band Balancing A common practice is to split the frequency domains and reserve one frequency domain for BCCH, one for TCH, and one for EGPRS (when used). As well, frequency bands and domains are reserved for the HCS layer. When the network is dimensioned during an automatic frequency allocation, the number of TRXs is adapted without modifying the divisions.
Figure 8.89: Frequency reuse balancing with or without TRX number adjustment In this example, most TRXs that were removed were removed in the 900 band (In the first half of the graph, the red line is almost always below the blue line.)
8.5.3.2 Combining Interference Matrices According to Maximum Likelihood Estimation In general, for a fixed set of data and underlying statistical model, the method of maximum likelihood selects values of the model parameters that produce a distribution that gives the observed data the greatest probability (i.e., parameters that maximise the likelihood function). The AFP uses maximum-likelihood estimation to combine different interference matrices. Different types of interference matrices have different weak points. When combining interference matrices, the most important aspect is differentiating between no interference and unknown interference (i.e., between situations where it can be proven that there is no interference and sitations where it can not be known whether there is interference). Maximum likelihood estimation selects the values from different interference matrices that would have the greatest probability of resulting in the observable data. Additional to the interference matrix itself, Atoll uses information about the type of interference matrix, its quality indicators, and its scope.
536
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
The following sections explain the maximum likelihood combination performed by the Atoll AFP Module. Before describing the combination process, the scope and context of interference matrices is explained.
8.5.3.2.1
Interference Matrix Context The context of an interference matrix refers to the following properties associated with each matrix: • • • • •
The name of the interference matrix (and comments, if any) The external file name (if the matrix is an external file) Whether the interference matrix is active or not The type of the interference (for more information on the types of interference matrices, "Defining Type-Dependant Quality Indicators on Interference Matrices" on page 472) The quality indicators (dependent on the type of interference matrix)
The context of an interference matrix is used mainly to indicate the statistical quality off the interference matrix so that the AFP can weight the information read from the interference matrix accordingly. Atoll 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 concept of an interference matrix context permits a common representation and significance of the parameters influencing the combination process. These parameters are, therefore, described as a set of quality indicators, with meaningful units, such as the number of measurement days, standard deviation, calculation resolution, and whether the interference matrix is based on traffic or surface area. The nine pre-defined types of interference matrices are divided into four groups with respect to their quality indicator representation: OMC-based, drive-test-based, propagation-based, and others. The General tab of the Interference Matrix Properties dialogue gives you access to this information:
Figure 8.90: Definition of Interference Matrix Types Depending on the matrix type, the quality indicators available on 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.
For matrices based on reselection statistics from the OMC: •
The statistic duration
537
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
• •
-
The standard deviation, depending on the equipment quality and measurement post-processing The average number of measurement points in the test mobile data that correspond to a single matrix calculation point.
For matrices based on CW measurements: -
•
The statistic duration Whether the interference information (probabilities) correspond to traffic or surface area.
For matrices based on test mobile data -
•
The standard deviation, depending on the equipment quality and measurement post-processing The average number of measurement points in the handover statistics that correspond to a single matrix calculation point The volume of information Whether the interference information (probabilities) correspond to traffic or surface area.
For matrices based on RXLEV statistics from the OMC: -
•
Whether the interference information (probabilities) correspond to traffic or surface area.
For matrices based on handover statistics from the OMC: -
•
© Forsk 2012
The standard deviation, depending on the equipment quality and measurement post-processing The average number of CW measurement points that correspond to a single matrix calculation point The volume of information Whether the interference information (probabilities) correspond to traffic or surface area.
For matrices based on scan data drive tests: -
The standard deviation, depending on the equipment quality and measurement post-processing The average number of measurement points in the scan data drive test data that correspond to a single matrix calculation point The volume of information Whether the interference information (probabilities) correspond to traffic or surface area.
The context of an interference matrix is not systematically included in the interference matrix files. That is why Atoll asks the user to set up the type and quality indicators of the interference matrix manually.
8.5.3.2.2
Interference Matrix Scope The scope of an interference matrix is the correspondence between a transmitter ID and the following information: • • • • •
538
The name of the transmitter The BSIC (as it was when the IM statistics were gathered) The BCCH (as it was when the IM statistics were gathered) The percentage of coverage of the victim that is taken into consideration in the interference matrix The percentage of coverage of the interferer that is taken into consideration in the interference matrix
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.91: Interference matrix scope The most important information of the scope is the percentage of victim coverage and the percentagle of interferer coverage. In order to understand their significance as well as their use, you should bear in mind that interference matrices must provide interference information between each pair of subcells 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, entries in an interference matrix only exist when there is interference between a given pair of subcells. If an entry (i, j) does not exist in the interference matrix, there are two possible explanations: • •
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 (i.e., only one source of interference information) then no interference is the same as unknown interference. If there is more than one interference matrix, the information missing in one matrix might be available in another. Therefore, it becomes very important to distinguish between the two cases in order to intelligently combine different interference matrices. For example, if you have three interference matrices and, for a given pair of subcells, you have 60% interference in one, unknown interference in the second, and unknown interference in the third, the resulting interference when the three matrices are combined will be 60%. However, if for the same pair of subcells, you have 60% interference in one, no interference in the second, and no interference in the third, the resulting interference when the three matrices are combined will be only 20%. The ideal method for differentiating between no interference and unknown interference would be to keep a matrix of values in memory, which would indicate the reliability of each matrix entry, and thereby indicate the entries for which the interference is "Unknown" as unreliable entries. Unfortunately, this would be completely impractical because this matrix of values would be too large to work with. Therefore, Atoll implements a slightly restricted approach for storing the scope of interference matrices. Interference matrices contain two reliability indicators at transmitter level, i.e., the reliability when a transmitter is the victim, and the reliability when it is the interferer. This information is stored in the columns % of Victim Coverage and % of Interferer Coverage. The reliability of an entry (i, j) is calculated as follows: VictimCoverage(Transmitter(i)) * InterfererCoverage(Transmitter(j)) This implementation is simple and sufficient for the most interference matrices.
539
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Creation of the Interference Matrix Scope The scope of an interference matrix is created by the tool that creates the interference matrix. If the interference matrix is created by Atoll, the AFP scope will be set to the initial set of victims, corresponding to SEL + RING (see "The Scope of the AFP and the Scope of the Interference Matrix" on page 489). This means that even when only one transmitter is present inside the computation zone, many other transmitters might be taken into account. Atoll adds all potential interferers to this set, and calculates the interference matrix entries between all pairs of this set. This set becomes the scope of the interference matrix, with 100% at both victim and interferer coverage. Other software can be used to edit the interference matrix scope using the general API features, or by saving the interference matrix as a CLC file and editing it. The CLC file format can store all the interference matrix information (see the Technical Reference Guide for more information). •
•
•
The scopes of the interference matrices are automatically created when old CLC, IM0, IM1, or IM2 files are imported. The scope is created using the current BSIC and BCCH allocation, and finding the set of all victims and the set of all interferers. The interference matrix scope internally manages the transmitter IDs. When exchanging information with a CLC file, these ID's are visible to the user. They are arbitrary numbers used to index the interference matrix entries. Even if an addin is used to create the interference matrix, the association of transmitter names to IDs is carried out by Atoll. The addin will associate the interference information to pairs of transmitter ID's. The CLC and DCT files have the same mapping of transmitter names to transmitter IDs. There are no restrictions on transmitter IDs as long as they are unique integers under 231.
Two possibilities (examples) for editing the interference matrix information could be: •
•
An addin that imports an interference matrix should know its scope. For example, if it is an OMC addin, and the OMC covers 50 transmitters, the scope will contain 50 transmitters. Their indexes will be supplied by Atoll once added to the scope. The percentage of victim and interferer coverage should be 100%. When generating an interference matrix from CW measurements, there might be a few transmitters which were correctly scanned and others that were not. In this case, the correctly scanned transmitters would have good percentage of victim and interferer coverage, while the others would not.
Use of the BSIC and BCCH in the Scope The BSIC and BCCH fields in the scope are used for the cases where the BSIC and BCCH allocation, during the period when the interference matrix information was gathered, was different from the current BSIC and BCCH allocation.
8.5.3.2.3
Keeping the Interference matrix Up to Date An interference matrix is no longer valid once the network has changed. However, currently this fact is left under the user responsibility. Atoll will try to perform some matrix maintenance in order to reduce overhead, yet this help is not guaranteed. start here When a CLC file (and its corresponding DCT) are imported, the transmitter indexes in the files can be arbitrary. In order to improve access time, Atoll changes these indexes to the ADO record ID as index. When you rename or delete a transmitter, or when the ADO index is changed, the interference matrix is automatically updated, and saved when the Atoll document is saved. Instead of updating the interference matrix every time a transmitter is renamed or deleted, Atoll stores the events in memory, and updates the interference matrix only when it is used. It checks the ADO record ID's and, if they have been changed, the changes are taken into account. When an Interference matrix is externalised, Atoll does not always manage to keep it updated as described above. Calculate your Interference Matrices as often as you calculate your path loss matrices.
8.5.3.2.4
Interference Matrix Combination in Atoll AFP Module Interference matrices are combined in a manner that follows these two important guidelines: • •
540
The cost function definition does not change. If earlier, interference values were read from a single interference matrix. Now, they are read from more than one interference matrix. When the interference matrices are correctly managed in Atoll, no further parameterisation (weighting) is required.
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
The Interference Matrices tab (see "The Atoll AFP Interference Matrices Tab" on page 520) available in the Atoll AFP Module properties dialogue displays and lets to modify the weights that control the interference matrix combination. The interference matrix combination is carried out as follows: 1. The Atoll AFP Module asks Atoll to load a subset of the active interference matrices of the document. This subset is determined by comparing each interference matrix scope with the AFP scope. Only the interference matrices whose scope intersects the AFP scope are loaded. 2. The Atoll AFP Module then reads the scope and context information of each loaded interference matrix. The interference, p(i, v, x), of subcell i (interferer) on subcell v (victim) for a given C/I level x, can be read from more than one interference matrix. 3. The Atoll AFP Module combines all the values of p(i, v, x) by performing a weighted average. Therefore, it calculates as many weights as the number of p(i, v, x) entries for a pixel. These "reliability weights" are calculated by multiplying the following three components: a. Component quantifying the membership to the AFP scope: VictimCoverage(Transmitter(v)) x InterfererCoverage(Transmitter(i)) For interference matrices based on OMC statistics, if the scope indicates that both i and v had the same BCCH, the component will be 0. b. Component depending on the interference matrix type. c. Component depending on the interference matrix quality indicators: The "Reliability Calculation". The equations are different for the different classes of types since the quality indicators are different as well: i.
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: 0.4
(1 + n × r + 1) Component C = --------------------------------------------4 × (σ + 1)
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 matrices of other types do not participate in the weighting, since they are or Upper bound IMs or Lower bounds IMs.
8.5.3.3 The Storage of a frequency plan in Atoll Atoll stores a single frequency plan. It is stored in its TRX table records, and also in its subcell and transmitter tables. Some AFP Quality indicators can even be stored in the Site table. In this chapter we will depict the various issues concerning this storage.
8.5.3.3.1
The TRX table particularity Atoll's TRX table enables the following: • • • •
Support of an external ID space of the TRXs of a transmitter (important for import and export utilities). MAL/channel at TRX level. MAIO at TRX level. Fine locking: The user can lock specific TRXs in an unlocked transmitter.
The TRX table does not contain an "active" field. Therefore, all TRXs in it should contain a valid frequency or MAL and are all considered to be on air. It is better to remove a TRX record than removing only the frequency or MAL from its channels list.
541
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
8.5.3.3.2
© Forsk 2012
Factors Influencing the AFP Which Can Be Set at Several Levels There are certain factors which affect the AFP directives that can be set at different levels in the GSM project: • • •
8.5.3.3.3
During an AFP optimisation, the channels and MAIO currently assigned to a TRX will not be changed if the TRX is locked in the TRXs table or if the transmitter is locked in the Transmitters table. The AFP weighing can be set at the transmitter level and at the subcell level. The final AFP weight will be the product of both weights (i.e., the transmitter AFP weight multiplied by the subcell AFP weight). The domain definition can be modified at the subcell level by defining excluded channels.
Redundancy Between TRXs, Subcells and Transmitter Tables Some AFP-relevant entries can be found in the TRXs, Subcells, and Transmitters tables, creating a certain level of redundancy: • • •
The channel list in the Transmitters table is a combination of all channels appearing in the TRXs of a transmitter (depending on the hopping modes used and the number of subcells). The hopping mode of a transmitter is the hopping mode of its default traffic carrier (the TCH TRX Type). The frequency band of the transmitter (the one used by the propagation model), is read from the domain of the BCCH subcell of the transmitter.
Atoll considers the lowest level of information as the accurate source. For example: • •
Atoll automatically updates the TRXs table if the channel list of a transmitter in the Transmitters table is modified. The frequency band of a transmitter cannot be edited.
In cases where the data management is perfectly controlled (for example, when several users are working on the same project), it can happen that issues of consistency can occur. In that case, you might want to run a subcell audit as explained in "Checking Consistency in Subcells" on page 574 to verify where consistency has been lost and how to correct it.
8.5.3.3.4
AFP Performance Indicators (AFP PI's) The AFP can be used to generate different AFP performance indicators (AFP PI's). The AFP PIs are visible in the AFP results window, and once commit is applied, they can be seen in Atoll's TRXs, subcells, transmitters and sites tables. The most important AFP PIs are found in the subcell table, and are now visible in a dedicated read only table view. The TRX Rank PI and Its Use The AFP TRX Rank provides a ranking of the TRXs in a subcell. If a TRX rank is high, it implies that the frequency (channel) corresponding to this TRX has bad usage conditions. TRX ranks indicate the best and worst quality TRXs in each subcell. The best TRX might be a candidate for extensive GPRS or EDGE usage. The worst TRX will be the TRX that is potentially removable. The OMC might use rank (or preference) information for better RRM (first charge the good TRXs, only after charge the bad ones …). • •
Rank = 1 is the best rank. TRX Rank is the corresponding field in the TRX table.
As it is during an AFP process that frequencies and MALs/MAIOs for different TRXs of a subcell are chosen, the AFP tool stores and manipulates the information about TRXs in good and in bad conditions. If you choose AFP Rank indicator to be allocated when starting an AFP session, each cost improving solution will go through a TRX rank assignment. If no improving plan is found, TRX rank will be assigned for the initial plan (like BSIC). TRX ranking within a subcell is performed on the basis of TRX costs. A TRX will be considered locked for TRX Rank assignment if and only if it is not selected for AFP allocation or if it has been locked. The Theory of "Scheduling" in Frequency Planning TRX rank is Atoll's AFP implementation of "Scheduling", which can help increase performance in certain particular cases. Example: imagine the case where a cell and its neighbour are not loaded with traffic at the same time (for example, a stadium and its parking lot). In such cases, it is possible to decrease call blocking by adding one or two dirty TRXs to the concerned cells. (assuming clean TRXs do not exist for spectral reasons). What you will need to do is the following: 1. You need an OMC that can be informed about the TRX ranking, and that knows not to use the bad TRXs when load is normal or low. They get into use only when the load is high. 2. You need to relax the interference matrix entries and the separation relation constraints between the two oppositely correlated cells. 3. You need to run the AFP with TRX rank. The spectral efficiency of scheduling can not be fully acquired by real time RRM, since the latest is of a caustic nature. You can be sure to obtain a bigger gain if the scheduling order is pre-defined.
542
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
8.5.3.3.5
The AFP Cost Performance Indicators Total cost and separation violation cost component at the TRX, subcell, transmitter, and site levels can be calculated and displayed as AFP performance indicators. These are the cumulated total costs and the cumulated separation violation costs of each TRX, subcell, transmitter and site. In order to be able to compute and display these results, you must add AFP_COST and AFP_SEP_COST fields (of type SINGLE) to the TRX, 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. As well, this can automatically limit the modification scope to the problematic cells/sites. This can deliver a significant quality gain.
8.5.3.3.6
The AFP Subcell Performance Indicators Four AFP performance indicators can be committed into 4 subcell fields. These fields are then displayed in a separate view of the subcell table. And also in a separate page in the AFP output dialogue.
8.5.3.4 Various Tips and Tricks In this section, there are a few methods that will help you use the AFP more efficiently. • • • •
8.5.3.4.1
"Focusing the AFP on the Problematic Areas" on page 543 "Learning the Network and Solving the hard Spots at the same time" on page 543 "Better Understanding the Point Analysis Tool" on page 544 "Why aren't the traffic loads incorporated in the interference matrix?" on page 545.
Focusing the AFP on the Problematic Areas In this small paragraph we propose a simple strategy for obtaining improved frequency plans. Let us assume that we have X hours of available computation time: • • • • • •
First, we launch the AFP during X/2 hours, then; we stop it and commit the results (if good). Lock all TRXs in the network. Find the areas that generate problems. For example, some sites with separation violations. Unlock the worst 10 sites. For each such site, unlock 2 - 4 neighbouring transmitters. Run the AFP for an additional X * 30 minutes (the remaining half of the time).
A more simple way to detect the hard spots is by committing cell or site level KPIs to the corresponding tables. The principle remains the same: Let the AFP work only on the small part where the interference is strongest.
8.5.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 minimise the number of changes). 8. Assuming that the long execution on a small area had improved the result, commit the plan. 9. If not, reduce the cost of changing a TRX, or reduce the number of locked transmitters, or both. Repeat the two previous steps until an improving long execution is achieved. 10. Now you can run the AFP on entire network. Keep the same cost for changing a TRX, so that the basic plan obtained in the beginning is not too strongly modified.
543
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
If step N° 10 has provided a good plan then it might be worth while sharing your AFP experience with all the other users: • • • •
8.5.3.4.3
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.
Better Understanding the Point Analysis Tool It is often useful to know what exactly causes interference conditions at a point. This is one of the important roles of the point analysis tool. Yet because of its complexity, some users are afraid to use it, which is a pity. The point analysis is complicated only because it is a very rich tool. It provides the user with the information of how are the interferers of a TRX at a point, what are the different gains (power offsets, burst collision probability, DTX, adjacency suppression), and how do the different components combine to a "total interference" on a channel or on a mobile allocation. Example 1: Combination of Interference Effects This figure depicts the case where one co-channel and two adjacent channel interferers are combined to create total interference (the gain value (the empty part - 18 dB) shows that they are adjacent). For each of the two adjacent interferers, C/I > 12 dB, while for their combination, the total interference, C/I < 12 dB. This example demonstrates the fact that geographic interference combination is more accurate than the interference cost of the AFP. Assuming the required quality to be 12 dB, this specific point would not contribute to the AFP cost, while it would be considered as interfered in the interference coverage prediction.
Figure 8.92: Combination of Interference Effects Example 2: Counting Strong Interference Only Once In this case, two strong interferences are combined to create an extra strong total interference. C/I is very weak for both interferers. Therefore, the point under analysis contributes to both IM entries, which are considered in the AFP cost. This example demonstrates the fact that geographic interference combination is more accurate than the interference cost of the AFP because of counting this point only once as an interfered point (and not twice as in the AFP).
544
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.93: Counting Strong Interference Only Once
8.5.3.4.4
Why aren't the traffic loads incorporated in the interference matrix? Atoll maintains the traffic load separate from the interference information. Before justifying this choice we must depict the two alternatives: • •
The mixed option: The interference information contains the traffic information as well. In this way, each IM entry will contain the quantity of traffic interfered if a co-channel or adjacent channel reuse exists. The separated option: The AFP has separate access to traffic load information and to interference probabilities (As in Atoll).
The main reasons for choosing the second implementation are the following: • • • • • • •
Option 2 is a superset that contains option 1. But option 1, being a subset, does not contain option 2 (i.e. once the information are mixed they cannot be separated). It does not create any overhead (the size of the additional information is negligible compared to the size of the IM). It helps keeping the unit definitions simpler. It facilitates merging IMs with different traffic units. The traffic information can be used for weighting the separation violation component, as well as the interference component. The traffic load can be used in deciding whether a TRX can be left uncreated. The gain introduced by the traffic load of the interferer depends on the hopping mode and the MAL size. Incorporating this gain in the IM (as a result of the mixed option) means that the IMs become hopping-mode and MAL-size dependent. This is a bad idea since the AFP should be able to change the MAL. And the user should be able to change the hopping mode without recalculating the IM. In addition, an IM calculated externally to Atoll, with a non-hopping BCCH can be used for the hopping TCH.
8.5.3.5 The Role of the AFP Administrator The AFP administrator is the person who knows the AFP better than anybody else in the company. It is the AFP administrator that evaluates the AFP, and therefore it his him that decides how it should be configured. The AFP administrator has a very powerful control tool which is the centralised database. It is there that he can publish his pre-defined and pre-configured AFP models.
545
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
8.6 Analysing Network Quality When you are working on a GSM/GPRS/EDGE network, you can analyse the quality of the network using the coverage predictions provided in Atoll. For GSM/GPRS/EDGE networks, Atoll provides both circuit and packet-specific coverage predictions as well as quality indicator predictions for both GSM and GPRS/EDGE. In this section, the following are explained: • • • • • • • • • •
"Evaluating the Quality of a Frequency Plan" on page 546 "Interference Coverage Predictions" on page 548 "Packet-Specific Coverage Predictions" on page 558 "Making a Circuit Quality Indicator (BER, FER, or MOS) Coverage Prediction" on page 566 "Making a Service Area Analysis Coverage Prediction" on page 568 "Studying Interference Between Transmitters" on page 571 "Auditing a GSM/GPRS/EDGE Frequency Plan" on page 572 "Checking Consistency in Subcells" on page 574 "Displaying the Frequency Allocation" on page 575 "Calculating Key Performance Indicators of a GSM/GPRS/EDGE Network" on page 578
8.6.1 Evaluating the Quality of a Frequency Plan Creating an AFP-compatible interference coverage prediction is the most precise and objective way of evaluating the quality of the frequency plan. It is more precise than the AFP cost estimation because it is based on the calculated radio conditions at each point and not on interference matrices. It is also more objective because it does not depend on the AFP module used to create the frequency plan evaluated. When you create an AFP-compatible interference coverage prediction, you must observe the following rules (for information on defining and calculating an interfered zones coverage prediction, see "Studying Interference Areas" on page 552: • •
Select Interfered Zones as the coverage prediction from the Prediction Types dialogue. Use the same service area model when calculating the interfered zones coverage prediction that you used when calculating the interference matrices.
Figure 8.94: Generating interference matrices
546
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.95: Defining the interfered zones coverage prediction 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 8.94, you should use the same settings when creating the interfered zones coverage prediction (see Figure 8.95): • • • •
Under Coverage Conditions, use the default settings for Subcell C threshold and Server. Under Interference Conditions, use the default settings for the Subcell C⁄I threshold. Under Interference Conditions, use the same DTX definition as you used when you ran the AFP. Under Interference Conditions, select "From subcell table" for the Traffic Load, and select the Detailed Results check box.
After defining and calculating the coverage prediction as explained in "Studying Interference Areas" on page 552, generate a report as explained in ""Displaying a Coverage Prediction Report" on page 416. When the Columns to Be Displayed dialogue appears, select the check boxes corresponding to the following columns (see Figure 8.95): • •
Served load (timeslots weighted by the AFP weight) Served load (timeslots weighted by the half rate traffic ratio).
Figure 8.96: Defining the report on the interfered zones coverage prediction The resulting report is shown in Figure 8.97.
547
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.97: 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 up in the report. In Figure 8.97, the interfered traffic for channel 25 is outlined in red. The total amount of traffic per TRX is the sum of: • •
Served load (timeslots weighted by the AFP weight): The traffic load is multiplied first by the AFP cost factor and then multiplied by the number of timeslots. Served load (Erlangs weighted by the half rate traffic ratio): The traffic load is multiplied first by the number of timeslots and then multiplied by 1/(1 - Half of the half-rate ratio)
The total amount of traffic per TRX is given in parentheses, and added. This way, you can see the ratio between interfered traffic and the total amount of traffic. The final ratio is outlined in green in Figure 8.97. 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 8.97 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.
Figure 8.98: Considerations in frequency planning
8.6.2 Interference Coverage Predictions The interference coverage predictions described in this section depend on the existence of a frequency plan. If you have not yet allocated frequencies, you must do so before carrying out any of the coverage predictions described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. Each of the interference coverage predictions described in this section can be carried out based on a fixed noise value or based on the settings for a particular terminal. For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 618.
548
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
The following GSM-specific coverage predictions are explained in this section: • •
"Making Quality Predic ons Based on C⁄I or C⁄(I+N)" on page 549 "Studying Interference Areas" on page 552.
You can also study interference areas by using the Point Analysis window: • •
"Analysing Interference Areas Using a Point Analysis" on page 555 "Example of Analysing Interference Using a Point Analysis" on page 556.
Atoll also enables you to model interference coming from an external project. For more information, see "Modelling Intertechnology Interference" on page 623.
8.6.2.1 Making Quality Predictions Based on C⁄I or C⁄(I+N) In Atoll, you can make quality predictions based on C⁄I or C⁄(I+N) levels once channels have been allocated. If you have not yet allocated frequencies, you must do so before carrying out the coverage prediction described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. The coverage by C⁄I level prediction enables you to determine C⁄I levels for transmitters sharing either an identical channel or an adjacent channel with other transmitters as a function of the carrier-to-interference ratio. If desired, you can limit the quality coverage prediction to a specific channel. You can calculate the coverage by C⁄I or by C⁄I + N. "N" is the receiver total noise and is defined as the thermal noise (set to -121 dBm) + noise figure. When you calculate the coverage by C⁄I + N, you can select whether the noise figure used is a fixed value or the noise value set for a selected terminal. If Detailed Results is selected on the Conditions tab, the following results are displayed per pixel, depending on the hopping mode set for the subcells covered by the coverage prediction: • • •
Non-hopping mode: A TRX channel of the selected TRX type (BCCH, TCH, TCH_EGPRS or TCH_INNER). Base-band hopping: The MAL of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER). Synthesised-frequency hopping: The MAL-MAIO of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER).
To make a coverage prediction by C⁄I levels: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by C/I Level and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 8.99). On the Conditions tab, you can define the signals that will be considered for each pixel.
549
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.99: Condition settings for a coverage prediction by C/I levels 7. Under Signal Conditions, set the following parameters: •
Click the down arrow button and select one of the following thresholds: • •
•
• •
•
Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration, assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter. When you select "HCS Servers" or "All," there might be areas where several transmitters experience interference. On these pixels, several C⁄I values are calculated. Therefore, on the Display tab, you select to display either the lowest C⁄I level or the highest C⁄I level (for more information, see "Comparing Service Areas in Calculations" on page 596). 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 coverage prediction. 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.
•
Click the down arrow button and select one of the following thresholds: • •
•
550
Subcell C/I Threshold: to use the C⁄I threshold specified for each subcell (including the defined power reduction) as the lower end of the C⁄I range. Global C/I Threshold: to enter a threshold to be used for all subcells as the lower end of the C⁄I range.
Select either "C⁄I" or "C⁄(I+N)".
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
•
Click the down arrow button and select one of the following thresholds: • •
Subcell C/I Threshold: to use the C⁄I threshold specified for each subcell (including the defined power reduction) as the upper end of the C⁄I range. Global C/I Threshold: to enter a threshold to be used for all subcells as the upper end of the C⁄I range. The defined C⁄I values define the range of C⁄I 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 C⁄I range to be considered.
•
Select whether you want the defined C⁄I or C⁄I+N condition to be Satisfied By: • •
At least one TRX: When you select the option At least one TRX, the defined interference condition must be satisfied by at least one TRX on a given pixel for the results to be displayed on that pixel. The worst TRX: When you select the option The worst TRX, Atoll selects the worst results for each pixel. If the worst results do not satisfy the defined interference condition, the results will not be displayed on that pixel. These options are available only if a lower C/I Threshold is set.
•
If you have selected "C/(I+N)", you can define the value to be added to the interference. The defined noise figure is added to the thermal noise value (defined by default at -121 dBm) to calculate the value of N. Select one of the following: • •
Based on Terminal: Select Based on Terminal if you want to use the noise figure defined for a terminal and select the terminal from the list. Fixed Value: Select Fixed Value if you want to enter a value and then enter the noise figure in the text box.
9. If you want discontinuous transmission mode for TRXs which support it taken into account during the calculation of interference, select the DTX taken into account check box and enter the percentage of time during which a user is talking in the Voice Activity Factor text box. 10. Select the Traffic Load that will be used to calculate interference: • •
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, 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. Intra-technology third order intermodulation interference can also be optionally taken into account in the total interference. This option requires activation through changes in the database. For more information, contact support. 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 C⁄I levels, the Display Type "Value Intervals" based on the Field "C⁄I level (dB)" is selected by default. If you selected "HCS Servers" or "All" from the Server list on the Conditions tab, there can be areas where several transmitters experience interference. On these pixels, several C⁄I values are calculated. Therefore, you can base the results displayed on either the Field "Min. C⁄I level (dB)" or "Max. C⁄I level (dB)" as well as the "C⁄I level (dB)" Field. For information on defining display properties, see "Display Properties of Objects" on page 43. 14. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 15. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately
551
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
•
© Forsk 2012
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. By changing the parameters selected on the Conditions tab and by selecting different results to be displayed on the Display tab, you can calculate and display information other than that which has been explained in the preceding sections.
8.6.2.2 Studying Interference Areas In Atoll, you can study interference zones once channels have been allocated. If you have not yet allocated frequencies, you must do so before carrying out the interfered zones coverage prediction. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. You can create an interfered zones coverage prediction to predict areas where transmitters suffer interference caused by other transmitters using the same channel or an adjacent channel. Atoll calculates the C⁄I level on each pixel where reception conditions are satisfied. Of these, Atoll calculates the coverage for pixels where the calculated C⁄I is lower than the defined upper limit. The pixel is coloured according to the selected attribute of the interfered transmitter attribute. If Detailed Results is selected on the Conditions tab, the following results are displayed per pixel, depending on the hopping mode set for the subcells covered by the coverage prediction: • • •
Non-hopping mode: A TRX channel of the selected TRX type (BCCH, TCH, TCH_EGPRS or TCH_INNER). Base-band hopping: The MAL of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER). Synthesised-frequency hopping: The MAL-MAIO of the subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER).
To make a coverage prediction by interfered zones: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types 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 216. 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 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 8.100). On the Conditions tab, you can define the signals that will be considered for each pixel.
552
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.100: Condition settings for a coverage prediction by interfered zones 7. Under Signal Conditions, set the following parameters: •
•
• •
•
Click the down arrow button and select one of the following thresholds: • Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. • Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range. In Figure 8.99, a Global C Threshold less than or equal to -105 dBm will be considered. Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration, assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on page 596). 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 C⁄I 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 Conditions, 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 coverage prediction. When you define a channel, by default Atoll ignores all TRXs using baseband or synthesised hopping. If you clear the NonHopping 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.
•
Click the down arrow button and select one of the following thresholds: • •
•
Subcell C/I Threshold: to use the C⁄I threshold specified for each subcell (including the defined power reduction) as the lower end of the C⁄I range. Global C/I Threshold: to enter a threshold to be used for all subcells as the lower end of the C⁄I range.
Select either "C⁄I" or "C⁄(I+N)".
553
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
•
Click the down arrow button and select one of the following thresholds: • •
•
© Forsk 2012
Subcell C/I Threshold: to use the C⁄I threshold specified for each subcell (including the defined power reduction) as the upper end of the C⁄I range. Global C/I Threshold: to enter a threshold to be used for all subcells as the upper end of the C⁄I 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, cochannels, 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 806. Intra-technology third order intermodulation interference can also be optionally taken into account in the total interference. This option requires activation through changes in the database. For more information, contact support. 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 interfered zones, the Display Type "Discrete Values" based on the Field "Transmitter" is selected by default. In the Network explorer, 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. In the Network explorer, the coverage prediction results are first arranged by interfered transmitter and then by C/I level.
For information on defining display properties, see "Display Properties of Objects" on page 43. 14. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 15. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
554
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
•
•
By changing the parameters selected on the Conditions tab and by selecting different results to be displayed on the Display tab, you can calculate and display information other than that which has been explained in the preceding sections. As explained in "Displaying a Coverage Prediction Report" on page 416, you can display a prediction report on the interfered predictions indicating the amount of correctly served traffic out of the total traffic covered by the coverage prediction by selecting the options Served load (Timeslots weighted either by the AFP weight or by the Half rate traffic ratio) after having calculated the prediction report. The total served load (Timeslots weighted by the AFP weight) is obtained by the product between the number of timeslots, the AFP weight and the traffic load. The total served load (Timeslots weighted by the HR Ratio) is obtained by the product between the number of timeslots, 1 ⁄ ( 1 – HR ⁄ 2 ) and the traffic load. The actual loads given by the report come from the ratio between the covered area and the total service area.
8.6.2.3 Analysing Interference Areas Using a Point Analysis In Atoll, you can study the interferers of a transmitter using the Point Analysis. If you have not yet allocated frequencies, you must do so before using the Point Analysis to study interferers. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. To make a point analysis to study interference areas: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis Tool ( pointer changes (
) in the Radio Planning toolbar. The Point Analysis Tool window appears and the
) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: • • •
Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: • •
Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.
4. Select the Interference view. The Interference view displays, in the form of a bar graph, the signal level of the selected transmitter, a black bar indicating the total interference experienced by the receiver, and bars representing the interference received from each interferer. The information displayed in the bar graph depends on the hopping mode of the subcell identified in the left margin of the graph: • • •
In Non-Hopping Mode, you can study the interference level on either a specific channel or on the most interfered one of either of a specific subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER) or all of the selected transmitter. In Base Band Hopping Mode, you can study the interference level on either a specific MAL or on the most interfered one of either of a specific subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER) or all of the selected transmitter. In Synthesised Frequency Hopping Mode, you can study the interference level on either a specific MAL-MAIO pair or on the most interfered one of either of a specific subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER) or all of the selected transmitter.
Figure 8.101 on page 557 gives an example of the Interference view. The signal level of the transmitter, Site10_3, is -95.61 dB and is indicated by a red bar. The black bar indicates the total interference experienced by the receiver (-98.65 dB). The seven interferers are responsible for -102.69 dB (olive green), -103.06 dB (yellow), -107.31 dB (purple), -111.56 dB (olive green), -115.38 dB (green), -115.50 dB (pink), and -117.13 dB (olive green). The bars indicating the interference caused by Site17_1 and Site15_1 are only partially filled. The entire bar indicates the interference that could potentially be caused by the transmitter whereas the filled part of the bar indicates the actual interference caused. A transmitter’s 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 tip text along with information on the channel being interfered and the type of interference, i.e., co-channel or adjacent channel interference.
555
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Intra-technology third order intermodulation interference can also be optionally taken into account in the total interference. This option requires activation through changes in the database. For more information, contact support. 5. You can change the following options at the top of the Interference view: • • • • •
Transmitter: Select the transmitter from the list. The transmitters in the list are sorted in the order of decreasing signal level received at the pointer location. 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 C⁄I or by C⁄(I+N).
6. Right-click the Interference view 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, or Total losses from the Result Type list. You can select the Indoor Coverage check box to add indoor losses.
7. Click the Details tab. The Details 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 tip text along with information on the channel being interfered and the type of interference, i.e., co-channel or adjacent channel. Intra-technology third order intermodulation interference can also be optionally taken into account in the total interference. This option requires activation through changes in the database. For more information, contact support. 8. You can change the following options at the top of the Details 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 C⁄I or by C⁄(I+N). Thermal noise is taken into account in the second method only.
For each transmitter, you can display the interference on each subcell or on the most interfered one. You can click the Expand button ( ) of each transmitter order to expand the list of all its interferers and their individual I and C/I levels.
8.6.2.4 Example of Analysing Interference Using a Point Analysis When you use the Point Analysis to study the interferers of a transmitter, the Interference view displays, in the form of a bar graph, the signal level of the selected transmitter, a black bar indicating the total interference experienced by the receiver, and bars representing the signal levels from each interferer contributing to total interference. The bars representing the signal level of the transmitter or of the interferers consist of two parts: a solid part which indicates the received 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 75%. As with interfered zones coverage predictions and coverage predictions by C⁄I levels, Atoll analyses the most interfered channel of the studied transmitter if it is using non-hopping model.
556
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.101: Point Analysis Tool - Interference view The transmitters in this example are the following: • • • • • • • • • •
BRU038_G2 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 17 is assigned to the TCH TRX. BRU099_G1 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 17 is assigned to the TCH TRX. BRU005_G1 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 16 is assigned to the BCCH TRX. BRU063_G1 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 17 is assigned to the BCCH TRX. BRU096_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 17 is assigned to the BCCH TRX. BRU061_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 17 is assigned to the BCCH TRX. BRU094_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 17 is assigned to the TCH TRX. BRU065_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 18 is assigned to the TCH TRX. BRU006_G3 has two subcells: one of TRX type BCCH and one of TRX type TCH. Neither has a power reduction defined. Channel 16 is assigned to the TCH TRX. Non-hopping mode is assigned to the all the subcells, whatever the TRX type is (BCCH or TCH).
The Point Analysis gives the following results: •
•
•
The signal level of the transmitter BRU038_G2 is -81.33 dBm and is indicated by a light green bar. It could have been -75.94 dB, but was decreased by 5.39 dB due to the shadowing margin. Only the signal level (C) is reduced by the shadowing margin (as calculated by the cell edge coverage probability and the C⁄I standard deviation defined per clutter class). The interference level (I) is not affected by the shadowing margin. The black bar indicates the total interference experienced by the receiver (-84.74 dB). Atoll calculates the interference level by considering 100% of the voice activity factor and traffic load. Neither DTX, nor the traffic load of TRXs are taken into account in evaluating the interference levels. The eight interferers are responsible for -86.56 dB (Dark Blue), -93.94 dB (Green), -95.13 dB (Cyan), -96.44 dB (Light Green), -101.56 dB (Orange), -103.13 dB (Yellow), -107.06 dB (Yellow) and -109.19 dB (Green). The bars indicating the interference caused by BRU005_G1, BRU065_G3 and BRU006_G3 are only partially filled. An entire bar indicates the interference that could potentially be caused by the transmitter whereas a filled part of the bar indicates the actual interference caused. Intra-technology third order intermodulation interference can also be optionally displayed. This option requires activation through changes in the database. When available, the intra-technology third order intermodulation interference level is displayed as a bar with the title format "Interferer Name: I3 (first channel, second channel)". For more information on how to activate this option, contact support.
At the top of the Interference view, the name of the most interfered channel on BRU038_G2 is channel 17 and the C/I received is 3.41 dB. An analysis of the interferers gives the following information: •
•
The bars representing BRU099_G1, BRU063_G1, BRU096_G3, BRU061_G3 and BRU094_G3 are full. On two out of five transmitters, channel 17 is assigned to the TCH TRX of the transmitter. For the other three transmitters, channel 17 is assigned to the BCCH TRX. They are, therefore, co-channel interferers. No power reduction is defined, therefore the interference is not reduced. The bars representing BRU065_G3, BRU006_G3 and BRU005_G1 are partly full. The bars are only partly full because the interference is reduced: on these transmitters, channel 17 is not assigned; channel 16 is assigned to the BCCH TRX of BRU005_G1 and to the TCH TRX of BRU006_G3. In addition, channel 18 is assigned to the TCH TRX of BRU065_G3. They are, therefore, adjacent channel interferers and their interference is reduced by the adjacent channel protection level of 18 dB (the default value defined in the GSM Network Settings properties). No power reduction is defined for
557
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
this subcell. If a power reduction of 3 dB had been defined for this subcell, the interference would have been reduced by an additional 3 dB. A fractional load might be another reason for reduced interference.
8.6.3 Packet-Specific Coverage Predictions The packet-specific coverage predictions described in this section can use an existing frequency plan. If you have not yet allocated frequencies, you can do so before carrying out any of the coverage predictions described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. The coverage predictions described in this section can only be made on transmitters that are packet-capable, in other words, GPRS or EDGE-capable transmitters. For information on defining packet capabilities on a transmitter, see "Creating or Modifying a Transmitter" on page 375. Each of the packet-specific coverage predictions described in this section can be carried out based on a fixed noise value or based on the settings for a particular terminal as well as the settings for a particular mobility. For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 618. For information on defining a mobility, see "Modelling GSM/GPRS/EDGE Mobility Types" on page 618. The following packet-specific coverage predictions are explained in this section: • • •
"Making a Coverage Prediction by GPRS/EDGE Coding Schemes" on page 558 "Making a Coverage Prediction by Packet Throughput" on page 560 "Making a BLER Coverage Prediction" on page 563
8.6.3.1 Making a Coverage Prediction by GPRS/EDGE Coding Schemes In Atoll, you can make a coverage prediction of the GPRS/EDGE coding schemes, whether channels have been allocated or not. If you have not yet allocated frequencies, you can do so before carrying out the coverage prediction described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. You can make a coverage prediction of the coding schemes for either GPRS, for EDGE, or for both. The choice of coding scheme is based on the radio conditions (C, C and C/I, or C/N, C/N and C/(I+N)). Therefore, the better the values for C and C⁄I are, the higher the throughput of the selected coding scheme will be. As well, you can restrict the coverage prediction to a selected terminal or mobility or to a combination of terminal and mobility. When you restrict the coverage prediction to a selected terminal, Atoll bases the coverage prediction on the C and C⁄I graphs for the selected terminal, as well as on its noise figure. As well, Atoll respects the terminal’s defined coding scheme limit. When you select a mobility, Atoll considers which transmitters have the coding scheme configuration that can support the selected mobility and the coding scheme threshold for that mobility. For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 618. A coverage prediction by coding schemes enables you to determine the coding scheme assigned to transmitters sharing either an identical channel or an adjacent channel with other transmitters. Coding schemes are assigned according to the radio condition (i.e., C, C and C/I, with or without thermal noise) and optionally according to a specific hopping mode, frequency band, mobility type and MAL (See "Creating or Modifying a Coding Scheme Configuration" on page 609 for more information). To make a coverage prediction by GPRS/EDGE coding schemes: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by GPRS/EDGE Coding Scheme 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 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 8.102). On the Conditions tab, you can define the signals that will be considered for each pixel.
558
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.102: Condition settings for a coverage prediction by GPRS/EDGE coding scheme 7. Under Coverage Conditions, set the following parameters: •
• •
•
Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration, assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations" on page 596). 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 C⁄I 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. If, under GPRS/EDGE, you select C and not C⁄I 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. Intra-technology third order intermodulation interference can also be optionally taken into account in the total interference. This option requires activation through changes in the database. For more information, contact support.
•
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.
559
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
• •
© Forsk 2012
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.
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 C⁄I. 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 C⁄I graphs for the selected terminal, as well as on its noise figure. As well, Atoll respects the terminal’s 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 43. When creating a coverage prediction by discrete values, you can not export the values per pixel.
11. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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.6.3.2 Making a Coverage Prediction by Packet Throughput In Atoll, you can make a coverage prediction of the packet throughput or quality, whether channels have been allocated or not. If you have not yet allocated frequencies, you can do so before carrying out the coverage prediction described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. You can calculate the following types of predictions using the Packet Throughput and Quality Analysis prediction: •
•
•
560
RLC/MAC throughput per timeslot: Based on the coding scheme used on each pixel (see "Making a Coverage Prediction by GPRS/EDGE Coding Schemes" on page 558) and the calculated quality, Atollextracts the RLC/MAC throughput as defined in the coding scheme configuration assigned to transmitters. Application throughput per timeslot for a selected service: Using the RLC/MAC throughput and the application throughput parameters (scaling factor and offset) defined for the selected service (see "Creating or Modifying a GSM/ GPRS/EDGE Service" on page 616), Atoll evaluates the throughput per timeslot on the application layer. Max throughput for a selected service-terminal pair: Using the application throughput per timeslot for a selected service, Atoll can evaluate a maximum throughput for a selected terminal, assuming that the terminal uses several timeslots to transmit the packet-switched data. The number of timeslots used by the terminal is given by the product of the number of DL timeslots per carrier and the number of simultaneous carriers (for EDGE evolution terminals) as defined in the terminal properties (see "Creating or Modifying a GSM/GPRS/EDGE Terminal" on page 618). For example, for an EDGE evolution terminal using 4 DL timeslots on a carrier and 2 simultaneous carriers, the maximum throughput will be 8 times the corresponding application throughput per timeslot. In addition, the number of timeslots per carrier defined in the terminal can be limited by the maximum number of timeslots permitted for the considered service (see
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
•
"Creating or Modifying a GSM/GPRS/EDGE Service" on page 616). User throughput for a selected service-terminal pair and considering the reduction factor obtained from a selected dimensioning model: Using the maximum throughput for a selected service terminal, Atoll can evaluate an end-user throughput by applying a reduction factor expressing the actual capacity of the serving transmitter and its occupancy to the maximum throughput. The reduction factor is obtained from the dimensioning model graphs (see "Defining a GSM/GPRS/EDGE Dimensioning Model" on page 450) and is the function of the number of available connections and the subcell traffic load. The number of connections is the ratio between the number of available packet timeslots (the sum of dedicated packet-switched and shared timeslots) and the number of terminal timeslots (as seen above).
You can make a coverage prediction of the packet throughput per timeslot for either GPRS, for EDGE, or for both. As well, you can restrict the coverage prediction to a selected terminal or mobility or to a combination of terminal and mobility. When you restrict the coverage prediction to a selected terminal, Atoll bases the coverage prediction on the C and C⁄I graphs for the selected terminal. As well, Atoll respects the terminal’s 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 C⁄I and C⁄(I+N). For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 618. To make a coverage prediction by packet throughput per timeslot: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Packet Throughput and Quality Analysis 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 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 8.103). On the Conditions tab, you can define the signals that will be considered for each pixel.
Figure 8.103: Condition settings for a Packet Throughput coverage prediction
561
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
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 596). 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 C⁄I 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. 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. Intra-technology third order intermodulation interference can also be optionally taken into account in the total interference. This option requires activation through changes in the database. For more information, contact support.
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: • • •
•
•
•
• • •
562
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 C⁄I. 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 C⁄I graphs for the selected terminal. As well, Atoll respects the terminal’s 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.
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
•
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 C⁄I to be selected. Otherwise, Atoll will choose the coding scheme by considering only the coding scheme admission threshold in terms of C and/or C⁄I.
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 coverage prediction 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 provided by a specific terminal from the previous display. Average Application Throughput/Timeslot: The average application throughput/timeslot that the transmitter can carry on one timeslot per pixel for a particular service. If there are different coverage areas for different TRXs, this coverage prediction will calculate the union of these coverages and display the average values over these coverage areas, whereas the other coverage predictions for application throughput/timeslot perform an intersection of these coverage zones, keeping the minimum value of throughput per pixel. 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 coverage prediction will calculate the union of these coverages and display the average values over these coverage areas, whereas the other coverage predictions for throughput perform an intersection over these coverage zones keeping the minimum value of throughput per pixel. 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 coverage prediction will calculate the union of these coverages and display the average values over these coverage areas, whereas the other coverages for throughput perform an intersection over these coverage zones, keeping the minimum value of throughput per pixel.
For information on defining display properties, see "Display Properties of Objects" on page 43. 12. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 13. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
8.6.3.3 Making a BLER Coverage Prediction In Atoll, you can make a coverage prediction of the block error rate (BLER) measured per transmitter, whether channels have been allocated or not. If you have not yet allocated frequencies, you can do so before carrying out the coverage prediction described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. The BLER is determined after Atoll determines which coding scheme is to be selected for a given C or C and C⁄I. When the coding scheme has been determined, 1 - BLER represents the efficiency factor applied to the maximum throughput of the coding scheme to obtain the served throughput. The BLER can be determined for each pixel.
563
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
You can make a BLER coverage prediction for either GPRS, for EDGE, or for both. As well, you can restrict the coverage prediction to a selected terminal or mobility or to a combination of terminal and mobility. When you restrict the coverage prediction to a selected terminal, Atoll bases the coverage prediction on the C and C⁄I graphs for the selected terminal. As well, Atoll respects the terminal’s 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 C⁄I and C⁄(I+N). For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 618. To make a BLER coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Packet Quality Throughput Analysis 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 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 8.104). On the Conditions tab, you can define the signals that will be considered for each pixel.
Figure 8.104: Condition settings for a BLER coverage prediction 7. Under Coverage Conditions, set the following parameters: •
•
564
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 596). Enter a hand-over margin in the With a Margin text box. The default value is "4 dB."
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
•
• •
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 C⁄I for the BLER coverage prediction. 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. Intra-technology third order intermodulation interference can also be optionally taken into account in the total interference. This option requires activation through changes in the database. For more information, contact support.
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 C⁄I. 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 C⁄I graphs for the selected terminal, as well as on its noise figure. As well, Atoll respects the terminal’s 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 43. 11. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219.
565
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
12. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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.6.4 Making a Circuit Quality Indicator (BER, FER, or MOS) Coverage Prediction In Atoll, you can make a circuit quality indicator coverage prediction based on the bit error rate (BER), the frame erasure rate (FER), or the mean opinion score (MOS). The circuit quality indicator coverage predictions refer to the codec configuration assigned to a transmitter or, optionally, to a terminal. For information on using codec configuration in transmitters and terminals, see "Using Codec Configurations in Transmitters and Terminals" on page 608. The circuit quality indicator coverage prediction can use an existing frequency plan. If you have not yet allocated frequencies, you can do so before carrying out any of the coverage predictions described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. Each of the circuit-specific predictions described in this section can be carried out based on a fixed noise value or based on the settings for a particular terminal as well as the settings for a particular mobility. For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 618. For information on defining a mobility, see "Modelling GSM/GPRS/ EDGE Mobility Types" on page 618. The circuit quality indicator coverage prediction displays the areas where the selected circuit quality indicator (BER, FER, or MOS) for the transmitter satisfies the user-defined criteria. The quality indicator is calculated using C⁄N or C⁄N and C⁄(I+N) and the adaptation or quality thresholds defined for the codec configuration on each transmitter. Transmitters that have no codec configuration defined are not taken into consideration in this coverage prediction. If a transmitter has a codec configuration, Atoll proceeds as follows: • •
If a terminal type is not defined or does not have codec configuration assigned, Atoll considers the codec configuration assigned to the transmitter only. If the terminal and the transmitter have different codec configuration, Atoll determines the intersection of the codec modes contained in the transmitter and terminal codec configuration. The codec mode is then selected according to the calculated C⁄N or C⁄N and C⁄I + N on and optionally according to a specific hopping mode, frequency band, mobility type and MAL (See "Creating or Modifying Codec Configuration" on page 606 for more information) each pixel. For a given quality or a given codec mode, look-up tables defined in codec configuration provide the circuit quality indicator (BER, FER, or MOS) displayed as a result.
The quality indicator used for ideal link adaptation is determined by the codec configuration assigned to the transmitters. To make a circuit quality indicator coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Circuit Quality Indicator Analysis 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 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 8.105). On the Conditions tab, you can define the signals that will be considered for each pixel.
566
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.105: 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 596). 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. If, under Quality Indicators Calculation, you select Calculations Based on C⁄N 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. You can also select interferences coming from an external project using another technology. For more information, see "Modelling Inter-technology Interference" on page 806.
567
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Intra-technology third order intermodulation interference can also be optionally taken into account in the total interference. This option requires activation through changes in the database. For more information, contact support. 9. Under Quality Indicators Calculation, set the following parameters: •
• •
• •
Select Calculations Based on C⁄N if you want to base the coverage prediction on C⁄N. If you select Calculations Based on C⁄N 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 C⁄N 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 C⁄N or C⁄N and C⁄I + 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 43. 11. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 12. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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.
8.6.5 Making a Service Area Analysis Coverage Prediction In Atoll, you can make a service area analysis coverage prediction whether channels have been allocated or not. If you have not yet allocated frequencies, you can do so before carrying out the coverage prediction described in this section. For information on creating a frequency plan, see "Allocating Frequencies, BSICs, HSNs, MALs, and MAIOs" on page 455. For a circuit-switched service, the aim of this prediction is to show the areas where, according to the radio conditions, a codec mode can be obtained, as explained in "Making a Circuit Quality Indicator (BER, FER, or MOS) Coverage Prediction" on page 566. For a packet-switched service, the aim of this prediction is to show the areas where, according to the radio conditions, a coding scheme can be obtained, as explained in "Making a Coverage Prediction by GPRS/EDGE Coding Schemes" on page 558. 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 C⁄I graphs for the selected terminal, as well as on its noise figure. As well, Atoll respects the terminal’s defined codec mode (or coding scheme) limit. When you select a mobility, Atoll considers which transmitters have the codec (or coding scheme) configuration that can support the selected mobility and the codec mode (or coding scheme) threshold for that mobility. For information on defining a terminal, see "Modelling GSM/GPRS/EDGE Terminals" on page 618.
568
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
To make a Service Area Analysis (DL) coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Service Area Analysis (DL) 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 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 8.105). On the Conditions tab, you can define the signals that will be considered for each pixel.
Figure 8.106: Condition settings for Service Area 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 596). 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.
8. Under Interference Condition, you can define how Atoll will evaluate interference for the codec mode (or coding scheme) selection. 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.
569
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
•
•
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: • •
•
© Forsk 2012
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 806. Intra-technology third order intermodulation interference can optionally be taken into account in the total interference. This must be activated by making certain changes in the database. For more information, contact support.
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 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. Under Coding, set the following parameters: •
• •
•
• •
Select Calculations Based on C⁄N if you want to base the coverage prediction on C⁄N. If you select Calculations based on C⁄N for the coverage prediction, the only option to select under Interference conditions is the TRX type to consider from the TRXs list. The codec mode (or coding scheme) is selected according to signal level and receiver noise N. Select Calculations Based on C⁄(I+N) if you want to base the coverage prediction on C⁄N 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 (or coding scheme) configurations, Atoll determines the intersection of the codec modes (or coding schemes) contained in the transmitter and terminal codec (or coding scheme) configuration. The codec mode (or coding scheme) is then selected according to the calculated C⁄N or C⁄N and C⁄I + N on each pixel. 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 (or coding scheme) applicable for the selected mobility on the codec configuration. Enter a Noise Figure. By default, a noise figure of 8 dB is used if no terminal is selected. Select which Service you want to base the coverage prediction on. If you select a circuit-switched service, the service will be served if at least one codec mode can be selected. If you select a packet-switched service, the service will be served if at least one coding scheme can be selected.
11. Click the Display tab. Only the Display Type "Unique" can be selected. Pixels are covered with a unique colour if the selected service can be provided on the considered pixel. For information on defining display properties, see "Display Properties of Objects" on page 43. 12. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 13. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
570
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
8.6.6 Studying Interference Between Transmitters In Atoll, you can use the Tx-to-Tx Interference tool to study the effects of an interfering signal from one transmitter on the signal of any other transmitter within the computation zone. You can restrict the interference to a set threshold or you can base it on a selected coverage prediction. Using a coverage prediction enables you to compare the results of the Tx-to-Tx Interference tool to the results of the selected coverage prediction. You must have a computation zone defined to use the Tx-to-Tx Interference tool. For information on creating a computation zone, see "Creating a Computation Zone" on page 402.
To display interference between transmitters on the map: 1. Click Tools > Tx-to-Tx Interference. The Tx-to-Tx Interference 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.
•
Select the transmitter whose signal is interfering from the Interferer list or click the Interferer button ( select the transmitter by clicking it on the map. The victim and interferer transmitters are displayed on the map with specific icons (
and
) and select ) and
).
3. Under Coverage conditions, select what you are going to base the interference calculation on: • •
Signal level: Enter a signal threshold. Based on prediction: Select the coverage prediction on which you want to base the interference calculation.
4. Click Calculate. The interference will be displayed on the map if you have selected the Visible check box (see Figure 8.107).
Figure 8.107: 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 Zoom on selected values section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. You can copy the graph by clicking the Copy button.
571
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
• •
© Forsk 2012
You can print the graph by clicking the Print button. Under Statistics based on prediction conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.
8.6.7 Auditing a GSM/GPRS/EDGE Frequency Plan When you have assigned frequencies to the TRXs, either manually or automatically, you can make an audit of the frequency plan. The audit allows you to verify the consistency and validity of the following GSM/GPRS/EDGE network parameters: •
• •
The transmitters to be allocated: The transmitters to be allocated, or TBA transmitters, are the active and filtered transmitters belonging to the transmitters folder from which the AFP was started and that are located within the focus zone. The potential interferers: The potential interferers are transmitters whose calculation radius intersects the calculation radius of any TBA transmitter. Transmitters involved in the separation conditions with TBA transmitters: These are the neighbours, co-site transmitters, transmitters or subcells of exceptional pairs and, in case of BSIC allocation, neighbours of neighbours.
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. Select the Network explorer. 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.)
572
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
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 478. 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 477. 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. 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 8.108). 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 8.108: 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 8.109). 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.
573
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.109: Separation violations
8.6.8 Checking Consistency in Subcells When network data is imported into an Atoll document, inconsistencies can occur between parameters that can be defined on the subcell and TRX and parameters that can be defined on the transmitter. Additionally, some subcell values which are either used in an AFP or in predictions can be outside an acceptable range. This can lead to, for example, unrealistic results or long calculation times. You can perform an audit on the consistency of all of these parameters and have Atoll automatically correct these problems as well. For each transmitter, Atoll checks that: • • • • •
The number of TRXs in the Transmitters table corresponds to the number of TRXs defined for this transmitter in the TRXs table. The list of channels used by the transmitter consists of all the channels assigned to TRXs of the transmitter. The BCCH of the transmitter is the same as the channel assigned to the BCCH TRX of the transmitter. The number of required TRXs indicated in the Transmitters table equals the sum of required TRXs of the transmitter’s subcells. The hopping mode of the transmitter corresponds to the hopping mode defined for its TCH subcell.
For each subcell, Atoll checks the following values: number of required TRXs, number of required BCCHs, traffic load, reception threshold, min C/I, half-rate traffic ratio, mean power control gain, DL power reduction, AFP weight, target rate of traffic overflow, max percentage of interference, maximum MAL size. To make a subcell audit: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Subcells > Audit from the context menu. The Subcell Audit dialogue appears. 4. Under Consistency of redundant values in the transmitters, subcells, and TRXs tables, select the Audit the values and generate a report in the Event Viewer check box. Any problems found by the audit will be displayed in the Event Viewer grouped by transmitter. 5. If you want Atoll to update the transmitter parameters that are inconsistent with their subcells and TRXs, select the Fix inconsistencies between transmitters and their subcells check box. 6. Under Compatibility of the main subcell values, select the Audit the values and generate a report in the Event Viewer check box. Warnings will be displayed in the Event Viewer for inconsistent values: • • • • • • • • • • • •
If the number of required TRXs is greater than 31 If the number of required BCCHs is not 1 If the traffic load is less than < 0.1 If the reception threshold is greater than -60 dBm or is less than -112 dBm If the min C/I is greater than 18 dB If the half-rate traffic ratio is greater than 100% or is less than 0 If the mean power control gain is greater than 16 dB If the DL power reduction is greater than 25 dB or is less than 0 dB If the AFP weight is greater than 3 or is less than 0.2 If the target rate of traffic overflow is greater than 100 or is less than 0 If the maximum percentage of interference is greater than 100 or is less than 1 if the maximum MAL size is greater than 62.
7. If you want Atoll to fix the subcell values as follows, select the Fix incompatibilities found in the main values check box. • • • • • •
574
If the number of required TRXs is greater than 62 or is less than 1, it is replaced by 1 If the number of required BCCHs is not 1, it is replaced by 1 If the traffic load is greater than 1 or is less than 0, it is replaced by 1 If the reception threshold is greater than -50 dBm or is less than -116 dBm, it is replaced by -102 dBm If the minimum C/I is greater than 25 dB, it is replaced by 12 If the half-rate traffic ratio is greater than 100% or less than 0, it is replaced by 40%
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
• • • • • •
If the mean power control gain is greater than 32 dB or less than 0 dB, it is replaced by 4 If the DL power reduction is greater than 25 dB or less than 0 dB, it is replaced by 0 If the AFP weight is greater than 100 or less than 0, it is replaced by 1 If the target rate of traffic overflow is greater than 100 or less than 0, it is replaced by 0 If the maximum percentage of interference is greater than 100 or less than 1, it is replaced by 1 If the maximum MAL size is greater than 62, it replaced by 62.
8. Click OK. If you choose to fix the incompatible values, Atoll displays the report in the Event Viewer. Values that are inconsistent are changed and Atoll displays warnings to inform you of unrealistic values.
8.6.9 Displaying the Frequency Allocation Atoll provides several tools that enable you to view the frequency allocation. You can use these tools to analyse a frequency plan by displaying the overall distribution of channels or channel and BSIC use on the map. You can also search for channels or BSICs. In this section, the following are explained: • • • •
"Using Find on Map to Display Channel Reuse" on page 575 "Displaying the Frequency Allocation Using Transmitter Display Settings" on page 576 "Grouping Transmitters by Frequencies" on page 577 "Displaying the Channel Allocation Histogram" on page 577.
8.6.9.1 Using Find on Map to Display Channel Reuse In Atoll, you can use Find on Map to search for BCCH and non-BCCH channels, and BSICs. The Find on Map tool allows you to view channel and BSIC reuse on the map. Find on Map enables you to find transmitters using a given channel, BSIC or NCC-BCC, or combination of HSN and MAIO. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Channel reuse and any potential problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 406. By including the BCCH, BSIC, and channel list of each transmitter in the transmitter label, the search results will be easier to understand. For information on defining the label, see "Defining the Object Type Label" on page 46. Searching for Channels You can use Find on Map to search for a channel. You can search in all channels, in control channels, or in non-control channels. To find a channel using Find on Map: 1. Click Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "GSM Channel." 3. In the Channel list, enter a channel that you would like to allocate. 4. Define where you want Atoll to search for the selected channel: • •
Used as BCCH: Atoll will search for the channel when used as a BCCH. Used as TCH: Atoll will search for the channel when used as a TCH.
By default, Find on Map displays only co-channel subcells. If you want adjacent channels to be displayed as well, select the Adjacent channels check box. 5. Click Search. When you search for both BCCH and TCH TRX types, transmitters with the same channel for BCCH are displayed in red. Transmitters with the same channel for any TCH are displayed in orange. Transmitters with two adjacent channels (i.e., a channel higher and a channel lower) are displayed in yellow. Transmitters with a lower adjacent channel are displayed in green; transmitters with a higher adjacent channel are displayed in green. Colours used for co-channel cases take precedence over the colours used for adjacent channels. All other transmitters are displayed as grey lines. When you search for the BCCH or TCH TRX types, transmitters with the same channel are displayed in red. Transmitters with two adjacent channels (i.e., a channel higher and a channel lower) are displayed in yellow. Transmitters with a lower adjacent channel are displayed in green; transmitters with a higher adjacent channel are displayed in green. Colours used for co-channel take precedence over the colours used for adjacent channels. All other transmitters are displayed as grey lines.
575
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
If you cleared the Adjacent channels check box, transmitters using the same channel are displayed in red; all others, including transmitters with adjacent channels, are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window. Searching for a Combination of TRX and Subcell Parameters You can use Find on Map to search for a combination of TRX and subcell parameters: a channel, BSIC or NCC-BCC, as well as HSN and MAIO. To find a BSIC-BCCH pair using Find on Map: 1. Click Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "BSIC-BCCH Pair." 3. Select the parameters on which you want to search: •
BCCH channel: Enter a BCCH channel number. If you do not enter a BCCH channel number, Atoll will search all specified channels according to the other parameters.
•
BSIC or NCC-BCC: Enter either a BSIC or a value for the NCC and for the BCC.
4. Click Search. Transmitters that match the defined search parameters are displayed in red. All other transmitters are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Search Tool window. To find a combination of TCH channel and HSN or MAIO using Find on Map: 1. Click Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "Channel-HSN/MAIO Pair." 3. Select the Channel/BSIC/HSN/MAIO tab. 4. From the Channel list, select the channel number. 5. Select the parameters on which you want to search: • •
HSN: If you want to search for a channel number and an HSN, select HSN and select an HSN number. MAIO: If you want to search for a channel number and a MAIO, select MAIO and select a MAIO number.
6. 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.
8.6.9.2 Displaying the Frequency Allocation Using Transmitter Display Settings You can use the display characteristics of transmitters to display frequency allocation-related information on the map. To display frequency allocation-related information on the map: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. You can display the following information per transmitter: • •
BCCH: To display the BCCH of a transmitter, select "Discrete values" as the Display Type and "BCCH" as the Field. BSIC: To display the BSIC of a transmitter, select "Discrete values" as the Display Type and "BSIC" as the Field.
You can display the following information in the transmitter label or tip text: • • • • •
576
BCCH: To display the BCCH of a transmitter’s 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 transmitter’s subcells, select "HSN" from the Label or Tip Text Field Definition dialogue. MAIO: To display the MAIO allocated to a transmitter’s subcells, select "MAIO" from the Label or Tip Text Field Definition dialogue.
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
• •
• • • • •
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. 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. 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 43.
8.6.9.3 Grouping Transmitters by Frequencies You can group transmitters in the Network explorer by their channel list or by their frequency band, or by both. To group transmitters by channels or by frequency band: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group By. The Group dialogue appears. 5. Under Available Fields, select the parameter you want to group transmitters by: • •
Frequency band Channels
6. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to the list of parameters on which the transmitters will be grouped. 7. If you do not want the transmitters to be sorted by a certain parameter, select it in the Group these fields in this order list and click grouped.
. The selected parameter is removed from the list of parameters on which the transmitters will be
8. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters to be grouped: a. Select a parameter and click
to move it up to the desired position.
b. Select a parameter and click
to move it down to the desired position.
9. Click OK to save your changes and close the Group dialogue.
8.6.9.4 Displaying the Channel Allocation Histogram Atoll has a frequency distribution analysis tool. You can open the frequency distribution analysis tool by right-clicking the Transmitters folder in the Network explorer and then selecting Frequency Plan > Channel Distribution from the context menu. The frequency distribution analysis tool gives you a three-column table with: • • •
The channel number The load (i.e., the number of occurences weighted by the fractional load) The number of times that channel is used.
The load is the same as the number of TRXs if synthesised hopping is not used. When synthesised hopping is used, the frequency load is the sum of 1/(MAL size) of all the TRXs using this frequency.
577
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
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 489. The frequency load distribution can be displayed as a histogram by clicking the Histogram button. The histogram is similar to the one on the Distributions tab in the AFP Progress dialogue. For more information, see "The Distributions Tab" on page 502. The Relationship Between Uniform Distribution and Quality You should be aware that uniform distribution is not always synonymous with quality. While it is clear that in some cases the frequency usage distribution can be a quality indicator, it is not always the case. For this reason the Atoll AFP does not have a cost dedicated to non-uniformity of spectral use. Therefore Atoll AFP can create non-uniform frequency distributions. •
•
When the frequency assignment problem (FAP) is easy, the AFP reaches a 0-cost solution and stops immediately. If it was instructed to use the minimum spectrum possible, the AFP will use the smaller ARFCNs more than the larger ones (and will leave the largest ARFCNs untouched, for future use). Otherwise, the AFP will try to spread spectrum use. By default this directive is free for AFP tuning. In many cases, a large volume of allocation constraints exists for adjacent channel reuse. The two end-channels, (the biggest and the smallest in the domain), have fewer constraints, because they have only one adjacent channel in use, and are therefore heavily used. The adjacent channels (the second in the domain, and the one before the biggest in the domain) are used less often than the others because they each have a heavily used adjacent channel. Because the third domain frequency is adjacent to a seldom used channel, it will be used more often than usual. In the case of a continuous domain, which is small, and whose size is impair, this effect will resonate strongly and will provide a significant reduction in usage of the second, fourth, sixth, etc., frequencies of the domain.
After you have manually or automatically allocated frequencies, you can view channel allocation in the form of a table or a histogram. For each channel used, Atoll displays both the channel load (i.e., the number of times the channel is used, weighted by the fractional load) and the total number of times the channel is used. The information in the table can either be copied or exported for use in another application. To display the channel allocation table or histogram: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Frequency Plan > Channel Distribution. The Channel Use Statistics table appears. 4. You can do the following: •
•
Export: Click the Export button to open the Export 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 and Spreadsheets" on page 80. 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 Zoom on selected values list. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. In the Distribution Histogram 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.
8.6.10 Calculating Key Performance Indicators of a GSM/GPRS/ EDGE Network Atoll allows the user to calculate and analyse key performance indicators (KPI), such as the reduction factor, the blocking probability, and the delay, that are currently defined for the network. This allows you to verify how well the network satisfies basic performance criteria. To calculate key performance indicators: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Traffic > Dimensioning and KPI Calculation from the context menu. The Dimensioning/KPIs dialogue appears (see Figure 8.110).
578
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.110: The KPI Calculation dialogue: The Dimensioning/KPI dialogue 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 whether the KPI calculation will be based on the traffic demand calculated in the default traffic capture or the current values (circuit and packet demands) in the Subcells table. •
If you select From subcell table, define the following additional parameters: •
• • •
Specify the Minimum throughput reduction factor that can be accepted in the network. When running a traffic capture, this parameter is evaluated (but not displayed) during the calculation. The minimum throughput reduction factor models the fact that, at the user level, the user throughput can be reduced because of how much it will be multiplexed with other users. In other words, this parameter will be affected by the traffic load which is a consequence of dimensioning. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. Under Circuit Services (%), enter the percentage of each type of circuit service used in the map. The total percentages must equal 100. Under Packet Services (%), enter the percentage of each type of packet service used in the map (assuming the packet is made of maximum bit rate and constant bit rate packet services). The total percentages must equal 100.
6. Click Calculate to calculate 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.
579
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
•
Target Rate of Traffic Overflow (%): This input parameter defines the percentage of traffic that is allowed to overflow from one subcell to another in case the traffic assigned to this subcell is greater than the maximum traffic that it can accommodate. It can be considered an anticipation of the percentage of traffic that will be rejected from higher priority subcells or layers to lower ones. The value is specified for each subcell.
•
Half-rate Traffic Ratio (%): This input parameter is defined per subcell and indicates the percentage of subcell traffic that uses half-rate access. If the values are different for BCCH and TCH subcells, Atoll will use the values for the target rate of traffic overflow and the half-rate traffic ratio from the BCCH subcell.
•
Packet demand (Kbps): The Packet Traffic Demand is the total traffic demand in kilobits per second generated by packet-switched service users within the coverage area of the transmitter.
•
Packet average demand (timeslots): The number of timeslots needed to satisfy the packet traffic demand depends on the maximum throughput that a packet timeslot can support.
•
Average Number of Timeslots per Connection (Packet): This input parameter defines the average number of timeslots used by packet-switched-traffic users while accessing services. Packet-switched services allow up to eight timeslots per connection. The average number of timeslots per connection corresponds to the average number of downlink timeslots (multiplied by the number of simultaneous carriers in EDGE Evolution, if any) over which a single mobile terminal can communicate at one time.
•
Circuit Demand (Erlangs): The Circuit Traffic Demand is the total traffic demand in Erlangs generated by circuitswitched-service users within the coverage area of the transmitter. For concentric cell types, the traffic demand on TCH subcells is different from the one calculated during the traffic capture. For concentric cell types, the traffic demand on TCH subcells is calculated from the traffic demand of the capture and the effective rate of traffic overflow.
•
Circuit average demand (timeslots): The Average Demand in Circuit Timeslots is calculated taking into account the effect of half-rate circuit-switched traffic: two half-rate users are equivalent to one full-rate user.
•
Average Number of Timeslots per Connection (Circuit): The Average Number of Timeslots per Connection (Circuit) is an input parameter. The number of timeslots per connection is "1" for full-rate traffic, otherwise it depends on the half-rate traffic ratio. At present, Atoll only models circuit calls using 1 timeslot per connection; this parameter is for forward compatibility.
•
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.
580
•
Probability of Circuit Blocking Rate (or Delay) (%): The Circuit Blocking Rate is the grade of service (GoS) indicator for circuit-switched traffic. It can be either the rate at which calls are blocked (Erlang B) or delayed (Erlang C), depending on which queuing model the dimensioning model uses.
•
Minimum Throughput Reduction Factor (%): The Minimum Throughput Reduction Factor is the lowest throughput reduction factor that can still guarantee service availability. The Minimum Throughput Reduction Factor is one of the criteria for packet-switched traffic dimensioning. It is calculated using the parameters defined for the services: the minimum service throughput; the maximum number of timeslots per connection; the required availability; and the per pixel timeslot capacity of the subcell coverage area. This parameter is calculated when making the traffic capture or is user-defined depending on the source of traffic demand on which the KPI calculation is based.
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
•
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. 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.
8.7 Optimising Network Parameters Using the ACP Atoll Automatic Cell Planning (ACP) enables radio engineers designing GSM networks to automatically calculate the optimal network settings in terms of network coverage and quality. The ACP can also be used to add sites from a list of candidate sites or to remove unnecessary sites or sectors. Atoll ACP can also be used in co-planning projects where networks using different radio access technologies must be taken into consideration when calculating the optimal network settings. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and transmission power. ACP can also be used during the initial planning stage of a GSM network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP not only takes transmitters into account in optimisations but also any repeaters and remote antennas. Atoll ACP can also be used to measure and optimise the EMF exposure created by the network. This permits the optimisation of power and antenna settings to reduce excessive EMF exposure in existing networks and optimal site selection for new transmitters. ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have defined the objectives and the network parameters to be optimised, Atoll ACP uses an efficient global search algorithm to test many network configurations and propose the reconfigurations that best meet the objectives. The ACP presents the changes ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the suggested changes. The ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 6: Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how you can view the results of an optimisation. In this section, only the concepts specific to GSM networks are explained: • • •
"GSM Optimisation Objectives" on page 581 "GSM Quality Parameters" on page 582 "The GSM Quality Analysis Predictions" on page 582.
8.7.1 GSM Optimisation Objectives ACP optimises the network using user-defined objectives to evaluate the quality of the network reconfiguration. The objectives are dependent on the technology used by the project and are consistent with the corresponding coverage predictions in Atoll. In projects using GSM, either alone, or in a co-planning or multi-RAT project, the following objectives are used: • •
Coverage Cell dominance
For information on setting objective parameters, see "Setting Objective Parameters" on page 242 of Chapter 6: Automatic Cell Planning.
581
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
8.7.2 GSM Quality Parameters When you create an optimisation setup, you define how the ACP evaluates the objectives. The quality parameters are technology dependent. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own predictions. However, if you have saved the display options of an ACP prediction 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. In projects using GSM, either alone, or in a co-planning or multi-RAT project, the following quality parameters are used: • •
Overlap BCCH signal level
To define the quality parameters for GSM: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233 in Chapter 6: Automatic Cell Planning. 2. Click the Objectives tab. 3. Under Criteria, in the left-hand pane, under Parameters, expand GSM. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own predictions. However, if you have saved the display options of an ACP prediction 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 prediction display options as the default, see "Changing the Display Properties of ACP Predictions" on page 284. For information on saving a configuration file, see "Configuring Default Settings" on page 231. If you want to use a coverage prediction, the coverage prediction must have already been calculated.
4. Click Overlap. In the right-hand pane, you can define how the ACP will evaluate overlapping coverage. 5. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, define an Overlap threshold margin and select either Subcell C threshold, the reception threshold defined per subcell, or Global C threshold and define a reception threshold to be used for all subcells from the a Minimum signal level list. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate overlapping coverage using the same parameters that were used to calculate the coverage prediction.
6. Under GSM in the left-hand pane under Parameters, select BCCH Signal Level. 7. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate the BCCH signal level using the same parameters that were used to calculate the coverage prediction.
8.7.3 The GSM Quality Analysis Predictions The quality analysis predictions enable you to display the BCCH quality and overlapping coverage predictions in the Atoll map window. These predictions are the same as those displayed on the Quality tab of the optimisation’s Properties dialogue. The quality analysis predictions are the equivalent of predictions created by different Atoll coverage predictions: • •
The BCCH predictions correspond to the Atoll coverage by C⁄I level in GSM. For more information, see "Making Quality Predic ons Based on C⁄I or C⁄(I+N)" on page 549. The overlapping zones predictions correspond to the Atoll overlapping zones coverage prediction. For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 412.
Making these predictions available within ACP enables you to quickly validate the optimisation results without having to commit the results and then calculate a coverage prediction in Atoll. The ACP predictions display results very similar to those that Atoll would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before
582
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
basing any decision to commit the optimisation results on the predictions produced by ACP, you should keep the following recommendations in mind: • • • •
You should verify the results with a different Atoll coverage prediction, such as the interfered zones prediction. ACP generated predictions are generated using the entire set of proposed changes. They do not take into account the change subset defined on the Change Details tab. Multiple carriers are not supported by ACP; the predictions are only provided for the requested carrier. Even after committing the optimisation results, differences can remain between the ACP predictions and the predictions resulting from Atoll coverage predictions.
You can view the exact BCCH value on any pixel by letting the pointer rest over the pixel. The BCCH value is then displayed in tip text. For the overlapping zones prediction, you can set the best server threshold on the User Preferences tab of the ACP Properties dialogue (see "Configuring Default Settings" on page 231) or by setting the CellOverlap parameter in the acp.ini file. For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network state, and a prediction showing the changes between the initial and final state.
8.8 Verifying Network Capacity An important step in the process of creating a GSM/GPRS/EDGE network is verifying the capacity of the network. This is done using measurements of the strength of the pilot signal in different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: • • • • • • •
"Importing a Drive Test Data Path" on page 583 "Displaying Drive Test Data" on page 586 "Defining the Display of a Drive Test Data Path" on page 586 "Network Verification" on page 587 "Exporting a Drive Test Data Path" on page 594 "Extracting CW Measurements from Drive Test Data" on page 594 "Printing and Exporting the Drive Test Data Window" on page 595.
8.8.1 Importing a Drive Test Data Path In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, commas, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: • •
The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving subcells, neighbour subcells, or any other subcells). In GSM/GPRS/EDGE networks, a transmitter is identified by its BCCH and its BSIC. Therefore, you must indicate during the import process which columns contain the BCCH and the BSIC of transmitters and the BSIC format (decimal or octal) used in the file.
You can import a single drive test data file or several drive test data files at the same time. If you regularly import drive test data files of the same format, you can create an import configuration. The import configuration contains information that defines the structure of the data in the drive test data file. By using the import configuration, you will not need to define the data structure each time you import a new drive test data file. To import one or several drive test data files: 1. Select the Network explorer. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. You can import one or several files. Select the file or files you want to open. If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import.
583
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
5. Click Open. The Import of Measurement Files dialogue appears. Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue. 6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Import configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Import configuration, select an import configuration from the Import configuration list. b. Continue with step 10. •
•
When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. If several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters: • • •
Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement Conditions, • •
Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document.
8. Click the Setup tab (see Figure 8.111).
584
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.111: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal Symbol used in the file. b. Click the Setup button to link file columns and internal Atoll fields. The Drive Test Data Setup dialogue appears. c. Under Measurement point position, select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in the drive test data file. You can also identify the columns containing the XY coordinates of each point in the drive test data file by selecting them from the Field row of the table on the Setup tab.
d. If you are importing data using BSIC/BCCH as transmitter identifiers: i.
Select By BSIC/BCCH under Transmitter Identification.
ii. In the BCCH Identifier box, enter a string that is found in the column names identifying the BCCH of the scanned subcells. For example, if the string "BCCH" is found in the column names identifying the scrambling code group of scanned cells, enter it here. Atoll will then search for columns with this string in the column name. iii. If there is no BCCH information contained in the drive test data file, leave the BCCH Identifier box empty. iv. In the BSIC Identifier box, enter a string that is 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. v. From the BSIC Format list, select the scrambling code format, either "Decimal" or "Octal." e. If you are importing data using Cell ID as transmitter identifiers: i.
Select By Cell ID under Transmitter Identification.
ii. In the Cell ID Identifier box, enter a string found in the column name identifying the cell Ids of scanned transmitters. For example, if the string "Cell_ID" is found in the column names identifying the Cell_ID of scanned transmitters, enter it here. Atoll will then search for the column with this string in the column name. f.
Click OK to close the Drive Test Data Setup dialogue.
585
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
•
•
If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Setup dialogue, Atoll should recognise all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "". If a column is marked with "", it will not be imported. The data in the file must be structured so that the columns identifying the BCCH and the BSIC are placed before the data columns for each subcell. Otherwise Atoll will not be able to properly import the file.
9. If you want to save the definition of the data structure so that you can use it again, you can save it as an import configuration: a. On the Setup tab, under Import configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll’s installation folder. If you cannot write into that folder, you can click the Browse button to choose a different location. c. Enter a Configuration name and an Extension of the files that this import configuration will describe (for example, "*.csv"). d. Click OK. Atoll will now select this import configuration automatically every time you import a drive test data path file with the selected extension. If you import a file with the same structure but a different extension, you will be able to select this import configuration from the Import configuration list. • •
•
You do not have to complete the import procedure to save the import configuration and have it available for future use. When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking the Expand button ( ) in front of the file under Import configuration to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Import configuration and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The mobile data are imported into the current Atoll document.
8.8.2 Displaying Drive Test Data When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see information about the transmitters at that location. To display information about a single drive test data point: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Select the display check box beside the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want server and neighbour information. Atoll displays an arrow pointing towards the serving transmitters and neighbours (see Figure 8.116 on page 593), 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 44.
8.8.3 Defining the Display of a Drive Test Data Path Drive test data paths have the standard Atoll display dialogue to allow you to define the display according to any available attribute, to manage permanent labels on the map, tip texts, and the legend. To open the display dialogue of a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder.
586
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
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 Advanced 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. •
• • •
Fast Display forces Atoll to use the lightest symbol to display points. Fast Display is useful when you have a very large amount of points which would require a great amount of computer resources to display. Using Advanced Display on symbols is possible only if the Fast Display check box is cleared. You can sort drive test data paths in alphabetical order in the Network explorer by selecting Sort Alphabetically from the Drive Test Data context menu. You can save the display settings (such as colours and symbols) of a drive test data path in a user configuration file to make them available for use on another drive test data path. To save or load the user configuration file, click the Actions button on the Display tab of the path properties dialogue and select Save or Load from the Display Configuration submenu.
8.8.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 587 "Predicting the Signal Level on Drive Test Data Points" on page 589 "Creating Coverage Predictions on Drive Test Data Paths" on page 590 "Displaying Statistics Over a Drive Test Data Path" on page 591 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 592 "Analysing Data Variations Along the Path" on page 592.
8.8.4.1 Filtering Incompatible Points Along Drive Test Data Paths When using a drive test data path, some measured points might present values that are too far outside of the median values to be useful in calibration. As well, test paths might include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from the more lightly populated region between the two. In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter classes where the incompatible points are located, or by filtering out points according to their properties. To filter out incompatible points by clutter class: 1. Select the Network explorer. 2. Right-click the Drive Test Data on which you want to filter out incompatible points: • •
All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder. The context menu appears.
3. Select Filter from the context menu. The CW Measurement Filter dialogue appears.
587
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
4. In the Per Clutter window, under Filter, clear the check boxes of the clutter classes you want to filter out. Only the clutter classes whose check box is selected will be taken into account. 5. If you want to keep the measurement points that are inside the focus zone, select the Use focus zone to filter check box. 6. If you want to permanently remove the measurement points outside the filter, select the Delete Points Outside Filter check box. If you permanently delete measurement points and later want to use them, you will have to re-import the original measurement data. To filter out incompatible points using a filter: 1. Select the Network explorer. 2. Right-click the Drive Test Data on which you want to filter out incompatible points: • •
All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder. The context menu appears.
3. Select Filter from the context menu. The CW Measurement Filter 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 8.112).
Figure 8.112: The Filter dialogue - Advanced tab i.
588
Underneath each column name, enter the criteria on which the column will be filtered as explained in the following table: Formula
Data are kept in the table only if
=X
value equal to X (X can be a number or characters)
X
value not equal to X (X can be a number or characters)
X
numerical value is greater than X
=X
numerical value is greater than or equal to X
*X*
text objects which contain X
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Formula
Data are kept in the table only if
*X
text objects end with X
X*
text objects which start with X
ii. Click OK to filter the data according to the criteria you have defined. Combinations of filters are first made horizontally, then vertically. For more information on filters, see "Advanced Data Filtering" on page 96. iii. Click OK to apply the filter and close the dialogue. You can update heights (of the DTM, and clutter heights) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones by selecting Refresh Geo Data from the context menu of the Drive Test Data Paths folder.
8.8.4.2 Predicting the Signal Level on Drive Test Data Points To predict the signal level on drive test data points: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to create the point prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Point predictions, select Point Signal Level and click OK. The Point Signal Level Properties dialogue appears (see Figure 8.113).
Figure 8.113: Point Signal Level Properties Dialogue The errors between measured and predicted signal levels can be calculated and added to the drive test data table. 6. If you want to calculate errors between measured and predicted signal levels, under Select signal levels for error calculations, select the names of the columns representing measured signal level values in the drive test data table for which you want to calculate the errors (see Figure 8.114). If you do not want to add this information to the drive test data table, continue with step 7.
Figure 8.114: Selecting measured signal levels for which errors will be calculated 7. Click OK. A new point prediction is created for the selected drive test data path. 8. Right-click the drive test data path. The context menu appears. 9. Select Calculations > Calculate All the Predictions from the context menu.
589
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the drive test data table for the predicted point signal level from the serving cell and the errors between the measured and predicted values.
Figure 8.115: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations) New columns are also added for the predicted point signal level from each neighbour cell and the errors between the predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Data Variations Along the Path" on page 592. The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main matrix. For more information on propagation models, see Chapter 5: Working with Calculations in Atoll.
8.8.4.3 Creating Coverage Predictions on Drive Test Data Paths You can create the following coverage predictions for all transmitters on each point of a drive test data path: • •
Coverage by Signal Level Coverage by C/I Level
To create a coverage prediction along a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Standard Predictions, select one of the following coverage predictions and click OK: •
•
Coverage by Signal Level: Click the Conditions tab. •
At the top of the Conditions tab, you can set the range of signal level to be considered. You can click the down arrow button and select one of the following thresholds: Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range.
• • • •
Under Server, select "All" to consider all servers. If you select 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.
Coverage by C/I: Click the Conditions tab. •
•
• •
590
On the Conditions tab, you can define the signals that will be considered for each pixel. You can click the down arrow button and select one of the following thresholds: Subcell C Threshold: to use the reception threshold specified for each subcell (including the defined power reduction) as the lower end of the signal level range. Global C Threshold: to enter a threshold to be used for all subcells as the lower end of the signal level range. Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration, assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter. When you select "Best Signal Level per HCS Layer" or "All," there might be areas where several transmitters experience interference. On these pixels, several C⁄I values are calculated. Therefore, on the Display tab, you select to display either the lowest C⁄I level or the highest C⁄I level (for more information, see "Comparing Service Areas in Calculations" on page 596). Enter a hand-over margin in the With a Margin text box. The default value is "4 dB." If you select Shadowing Taken into Account, you can change the Cell Edge Coverage Probability. Shadowing margins (depending on the entered cell edge coverage probability and the model standard deviation per clutter class) are applied to the values for C.
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
• • •
You can select the Indoor Coverage check box to add indoor losses. Under Interference Conditions, you can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list. Select "C⁄I" or "C⁄(I+N)". On the same line, click the down arrow buttons on the left and on the right and select one of the following thresholds: Subcell C/I Threshold: to use the C⁄I threshold specified for each subcell (including the defined power reduction) as the lower end of the C⁄I range. Global C/I Threshold: to enter a threshold to be used for all subcells as the lower end of the C⁄I range. You can not select Subcell C/I Threshold as both the lower and the upper end of the C⁄I range to be considered.
•
•
•
•
•
Select whether you want the defined interference condition to be Satisfied By: At least one TRX: When you select this option, the defined interference condition must be satisfied by at least one TRX on a given pixel for the results to be displayed on that pixel. The worst TRX: When you select this option, Atoll selects the worst results for each pixel. If the worst results do not satisfy the defined interference condition, the results will not be displayed on that pixel. If you selected C/(I+N), you can define the value to be added to the interference. The defined noise figure is added to the thermal noise value (defined at -121 dBm) to calculate the value of N. Select one of the following: Based on Terminal: to use the noise figure defined for a terminal and select the terminal from the list. Fixed Value: to enter a value and then enter the noise figure in the text box. If you want discontinuous transmission mode for TRXs which support it taken into account during the calculation of interference, select the DTX taken into account check box and enter the percentage of time during which a user is talking in the Voice Activity Factor text box. Select the Traffic Load that will be used to calculate interference: 100%: The maximum traffic load (subcells entirely loaded). From subcell table: The subcell traffic load as defined or as calculated during dimensioning. From the Interference Sources list, select whether the interference should be calculated from adjacent channels, co-channels, or from both. The adjacent channel effect on the victim channel, i.e., the interference, is decreased by the adjacent channel protection level.
Intra-technology third order intermodulation interference can also be optionally taken into account in the total interference. This option requires activation through changes in the database. For more information, contact support. •
Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed depend on the subcell frequency hopping mode: Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode. Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping mode. Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in synthesised frequency hopping mode.
6. When you have finished setting the parameters for the coverage prediction, click OK. You can create a new coverage prediction by repeating the procedure from step 1. to step 6. for each new coverage prediction. 7. When you have finished creating new coverage predictions for these drive test data, right-click the drive test data. The context menu appears. 8. Select Calculations > Calculate All the Predictions from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Working with Calculations in Atoll). You can display the information in these new columns in the Drive Test Data window. For more information on the Drive Test Data window, see "Analysing Data Variations Along the Path" on page 592.
8.8.4.4 Displaying Statistics Over a Drive Test Data Path Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path. To display the statistics for a specific Drive Test Data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder.
591
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
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.8.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter You can extract a specific field for a specific transmitter on each point of an existing drive test data path. The extracted information will be added to a new column in the table for the drive test data. To extract a field from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to extract a field. The context menu appears. 4. Select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter 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. 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.
8.8.4.6 Analysing Data Variations Along the Path In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use the Drive Test Data window to see which cell is the serving cell for a given test point. To analyse data variations using the Drive Test Data window. 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Click the drive test data you want to analyse and select Drive Test Data from the Tools menu. The Drive Test Data window appears (see Figure 8.116)
592
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Figure 8.116: The Drive Test Data window 4. Click Display at the top of the Drive Test Data window. The Display Parameters dialogue appears (see Figure 8.117).
Figure 8.117: The Display Parameters dialogue 5. 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. 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.
6. You can display the data in the drive test data path in two ways:
593
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
• •
© Forsk 2012
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 593). 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 44. 7. You can display a second Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters 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. 8. You can change the zoom level of the Drive Test Data window display in the Drive Test Data window in the following ways: •
Zoom in or out: i.
Right-click the Drive Test Data window.
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. 9. 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. 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.116 on page 593).
8.8.5 Exporting a Drive Test Data Path You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.
8.8.6 Extracting CW Measurements from Drive Test Data You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears. 5. Under Extract CW Measurements: a. Select one or more transmitters from the For the Transmitters list. b. Select the field that contains the information that you want to export to CW measurements from the For the Fields list.
594
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
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.
8.8.7 Generating Interference Matrices from a Drive Test Data Path You can generate interference matrices from drive test data paths and extract the results to the Interference Matrix folder. To generate Interference Matrices from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract Interference Matrices from the context menu. The Interference Matrix Export dialogue appears. 5. Under Storage File: a. Click the Browse button to select the path and the name of the interference matrix file to be generated. b. Select the field that contains the signal level information that you want Atoll to convert into C/I values from the Select the measured signal levels list. 6. Click OK. Atoll creates a new interference matrix item in the Interference Matrix folder which can be used like any other interference matrix (See "Interference Matrices" on page 466).
8.8.8 Printing and Exporting the Drive Test Data Window You can print or export the contents of the Drive Test Data window, using the context menu in the Drive Test Data window. To print or export the contents of the Drive Test Data window: 1. Select the Network explorer. 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.116 on page 593). 5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 592. 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.9 Advanced Configuration In this section, the following advanced configuration options are explained: • • • • •
"Setting HCS Layers" on page 596 "Comparing Service Areas in Calculations" on page 596 "Cell Types" on page 600 "TRX Configuration" on page 604 "Codec Configuration" on page 605
595
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
• • • • • • • •
© Forsk 2012
"Coding Scheme Configuration" on page 608 "Timeslot Configurations" on page 611 "Advanced Transmitter Configuration Options" on page 612 "GSM/GPRS/EDGE Multi-Service Traffic Data" on page 616 "Defining the Interferer Reception Threshold" on page 620 "Advanced Modelling of Hopping Gain in Coverage Predictions" on page 620 "Modelling Shadowing" on page 621 "Modelling the Co-existence of Networks" on page 622
8.9.1 Setting HCS Layers You can model hierarchical networks in Atoll by defining hierarchical cell structure (HCS) layers. HCS layers are defined by the following parameters: • • •
Priority Layer reception threshold Maximum speed.
The priority and layer reception threshold are used to determine the best server on each pixel. When there are several possible transmitters, the best server will be determined by the priority. If there are transmitters on different layers having the same priority, the transmitter for which the difference between the received signal level and the layer reception threshold will be selected as the best server. Transmitters whose received signal level is below the layer reception threshold will be ranked by signal level, but will not be chosen as best server. The HCS layer reception threshold is considered only if no specific HCS layer reception threshold has been defined at the transmitter level (on the General tab of the transmitter’s Properties dialogue). You can set Atoll to select the transmitter with the highest received signal level as the serving transmitter by changing an option in the atoll.ini file. For more information on changing options in the atoll.ini file, see the Administrator Manual. The maximum speed is used to select HCS layer users according to the speed defined in the mobility. To define HCS layers: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Right-click the HCS Layers folder. The context menu appears. 4. Select Open Table. The HCS Layers table appears. 5. In the row marked with the New Row icon ( ), enter the following parameters to define a HCS layer (for information on working with data tables, see "Working with Data Tables" on page 69): • • • •
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 predictions when the HCS server option is selected.
8.9.2 Comparing Service Areas in Calculations For any coverage prediction, traffic analysis, or interference matrix calculation, transmitter service areas can be defined differently according to the server selection made on the Conditions tab of the dialogue used to define the calculation. On the Conditions tab, you can select: • • • • • •
•
596
All: All servers will be taken into consideration. Best Signal Level: The best signal level from all servers on all layers will be taken into consideration. Second Best Signal Level: The second best signal level from all servers on all layers will be taken into consideration. Best Signal Level per HCS Layer: The best signal level from all servers on each HCS layer will be taken into consideration. Second Best Signal Level per HCS Layer: The second best signal level from all servers on each HCS layer will be taken into consideration. HCS Servers: The best signal level by HCS layer on each pixel will be taken into consideration, assuming the signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter. Highest Priority HCS Server: The best signal level of all the severs on the highest priority HCS layer will be taken into consideration, assuming the priority of the layer is defined by its priority field and its signal level exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter.
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
• •
Best Idle Mode Reselection Criterion (C2): The best C2 from all servers will be taken into consideration. Grouped HCS Servers: The best signal level by HCS layer on each pixel will be taken into consideration, assuming the signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter. In addition, layers are grouped by supported mobility types.
A server is considered on a pixel if its calculated signal level exceeds the lower boundary of the signal level defined either globally on the Conditions tab of the coverage prediction or specifically for each subcell in coverage prediction, traffic analysis, and interference matrix calculations. Selecting the server to be taken into consideration retains one or several servers on each pixel, according to a combination of HCS layer properties (layer priority, maximum speed allowed on the layer, layer admission threshold) and the calculated signal level on each pixel. Example of Service Areas In this example, the following network is used: • • •
3 tri-sector base stations on a micro layer 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
Priority (0:Lowest)
Max Speed (km/h)
Layer Reception Threshold (dBm)
Macro Layer
2
100
-90
Micro Layer
3
10
-84
Umbrella Layer
1
300
-105
The subcell reception threshold is -102 dBm for the micro cells and -105 dBm for the macro and the umbrella cells. Three mobility types are defined in this project: Pedestrian (3km/h), 50 km/h and 90 km/h The resulting services areas are displayed in the following graphics for each selection. •
All: All servers are taken into consideration
Composite Coverage
Umbrella Layer Coverage
Macro Layer Coverage
Micro Layer Coverage
Figure 8.118: Coverage by Transmitter on All the servers Figure 8.118 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.
597
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Composite Coverage
Umbrella Layer Coverage
Macro Layer Coverage
Micro Layer Coverage
Figure 8.119: Coverage by Transmitter for the Best Signal Level Figure 8.119 shows the service areas of the transmitters having the best signal level on each pixel, without any layer taken into consideration. Cells are in competition if their calculated signal level is higher than the subcell reception thresholds. Overlapping between transmitters and between HCS layers is not possible. •
Best Signal Level per HCS Layer: The best signal level from all servers on each HCS layer is taken into consideration.
Composite Coverage
Umbrella Layer Coverage
Macro Layer Coverage
Micro Layer Coverage
Figure 8.120: Coverage by Transmitter for the Best Signal Level per HCS Layer Figure 8.120 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. •
598
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.
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
Composite Coverage
Umbrella Layer Coverage
Macro Layer Coverage
Micro Layer Coverage
Figure 8.121: Coverage by Transmitter for the HCS Servers Figure 8.121 shows the service areas of the transmitters having the best signal level on each pixel, for each HCS layer. Cells are in competition per layer assuming their calculated signal level is higher than the subcell reception thresholds and the HCS layer reception threshold. Overlapping between HCS layers is possible, but overlapping between transmitters on a given HCS layer is not possible. In the case above, the micro layer overlaps the macro layer and its borders are defined by the maximum between the subcell reception thresholds (-102 dBm) and the micro layer threshold (-84 dBm), i.e. -84 dBm. In addition, the macro layer overlaps the umbrella layer and its borders are defined by the maximum between the subcell reception thresholds (-105 dBm) and the macro layer threshold (-90 dBm), i.e. -90 dBm. The umbrella layer is displayed when its signal level exceeds the maximum between the subcell reception thresholds and the umbrella layer threshold, i.e. -105 dBm. •
Highest Priority HCS Server: The best signal level of all the severs on the highest priority HCS layer are taken into consideration, assuming the priority of the layer is defined by its priority field and its signal level exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter.
Composite Coverage
Umbrella Layer Coverage
Macro Layer Coverage
Micro Layer Coverage
Figure 8.122: Coverage by Transmitter for the Highest Priority HCS Server
599
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.122 shows the service areas of the transmitters having the best signal level on each pixel, on the highest priority HCS layer. The priority HCS layer is the layer for which the priority value is the highest and for which the calculated signal level is higher than its subcell reception thresholds and the HCS layer reception threshold. Overlapping between HCS layers and between transmitters of a given HCS layer is not possible. If two layers have the same priority, the traffic is served by the transmitter for which the difference between the received signal strength and the HCS threshold is the highest. The way competition is managed between layers with the same priority can be modified. For more information, see the Administrator Manual. •
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: [TMP] ExtraServZone = 1
Composite Coverage
Umbrella Layer Coverage
Macro Layer Coverage
Micro Layer Coverage
Figure 8.123: Coverage by Transmitter for the Grouped HCS Servers Figure 8.121 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 km⁄h mobility and the macro layer has a higher priority than the umbrella layer with the 50 km⁄h and 90 km⁄h 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.
8.9.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: •
600
"TRX Types" on page 601
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
• •
"Creating a Cell Type" on page 601 "Examples of Cell Types" on page 602.
8.9.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 GPRS EDGE.mdb." For information on the Atoll document template, see the Administrator Manual.
8.9.3.2 Creating a Cell Type A cell type must have a BCCH TRX type for the broadcast control channel and a TCH TRX type for the default traffic carrier; it can also have a TCH_INNER or TCH_EGPRS TRX type. You can not have more than one instance of a given TRX type in a cell type. To create a cell type: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Right-click the Cell Types folder. The context menu appears. 4. Select Open Table. The Cell Types table appears. 5. In the row marked with the New Row icon ( dialogues when you select a cell type.
), enter the name of the new cell type. This name will appear in other
6. Select the row containing the cell type and click the Properties button ( erties dialogue appears.
) in the Table toolbar. The cell type’s Prop-
In the cell type’s Properties dialogue, you can add and define the TRX types that will constitute the cell type. 7. Under TRX Types, in the row marked with the New Row icon ( ), enter the following parameters to define a TRX type (for information on working with data tables, see "Working with Data Tables" on page 69): • • • • • •
• •
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 predictions 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. 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 8.7).
601
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
If the traffic overflow target is set to a value lower than the grade of service, it means that the traffic rejected (according to the queuing model selected in the dimensioning model: Erlang B or Erlang C) will be lost and will not overflow to other subcells. •
•
Hopping Mode: Select the frequency hopping mode supported by this TRX type. The hopping mode can be either "Base Band Hopping mode (BBH)" or "Synthesised Hopping mode (SFH)." If frequency hopping is not supported, select "Non Hopping." Allocation Strategy: Select the allocation strategy used during manual or automatic frequency planning. There are two available allocation strategies: • •
•
•
• •
•
•
•
•
•
Free: Any of the channels belonging to the frequency domain can be assigned to TRXs. Group Constrained: Only channels belonging to a same frequency group in the frequency domain can be assigned. You can use the Preferred Frequency Group to define the preferred group of frequencies when using the AFP.
Max. MAL Length: Enter the maximum length of the mobile allocation list (MAL), in other words, the maximum number of channels allocated to the TRXs of subcells based on this TRX type during automatic frequency planning if the Hopping Mode is either SFH (Synthesised Frequency Hopping) or BBH (Base Band Hopping) and if the Allocation Strategy is Free. HSN Domain: Select the HSN domain for this TRX type. Only hopping sequence numbers (HSN) belonging to the selected HSN domain will be allocated to subcells during automatic or manual frequency planning. The HSNs are allocated if the Hopping Mode is either SFH (Synthesised Frequency Hopping) or BBH (Base Band Hopping). Lock HSN: If the HSN assigned to this TRX type is to be kept when a new AFP session is started, select the Lock HSN check box. AFP Weight: Enter an AFP weight. The AFP weight is used to increase or decrease the importance of a subcell during automatic frequency planning. The value must be a real number. The higher the AFP weight is, the higher the constraint on the TRX type. The AFP weight artificially multiplies the cost function which has to be minimised by the AFP. % Max. Interference: Enter the maximum level of interference allowable during automatic frequency planning. The interference is defined as a percentage of area or traffic, as defined during the calculation of the interference matrices. Mean Power Control Gain (dB): The average reduction in interference due to power control in downlink. This gain is used when calculating interference generated by the subcell. Interference generated by the subcell is reduced by this value during C/I calculations. Default TRX Configuration: Select the default TRX configuration for this TRX type. It will apply to all TRXs belonging to a subcell based on this TRX type. By selecting the default TRX configuration, the maximum number of GPRS and EDGE coding schemes is set at the TRX type level. You can also define the TRX configuration for each TRX. EDGE Power Backoff (dB): Enter the average power reduction for EDGE transmitters due to 8PSK, 16QAM and 32QAM modulations in EDGE. This has an impact on the EDGE service zone which can be seen in traffic analysis and EDGE predictions. Diversity Mode: The type of diversity supported by the subcell ("None," "Tx Diversity," or "Antenna Hopping"). If you select "Tx Diversity," the signal is transmitted as many times as there are antennas. If you select "Antenna Hopping," the signal is transmitted successively on each antenna. In "Tx Diversity mode," transmitting on more than one antenna, the signal experiences a gain of 3 dB. For any diversity mode, an additional transmission diversity gain can be defined per clutter class in order to correctly model gain due to the environment (see "Defining Clutter Class Properties" on page 145 for more information). The resulting gain will increase the C/I value at the terminal served by the considered subcell. An Other Properties tab appears on the Properties dialogue if you have added userdefined fields to the Cell Types table.
8. Click OK to close the cell type’s Properties dialogue. 9. Click the Close button ( ) to close the Cell Types table.
8.9.3.3 Examples of Cell Types When you create a new GSM/GPRS/EDGE document, some cell types are provided by default. In this section, the parameters for two examples of cell types are given: • •
"Normal Cell Type" on page 602 "Concentric Cell Type" on page 603.
Normal Cell Type A normal cell type consists of two TRX types:
602
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
• •
BCCH TRX type TCH TRX type
The following table describes the parameters to be specified for each hopping mode.
Parameter
Where Used in Atoll
Frequency domain
Hopping mode Non hopping
BBH
SFH
Automatic or manual frequency planning
x
x
x
Maximum MAL (Mobile Allocation List) length
Automatic frequency planning
Not used
x
x
Allocation strategy
Automatic or manual frequency planning
x
x
x
C/I threshold
Interference predictions, Automatic frequency planning
x
x
x
% max interference
Automatic frequency planning
x
x
x
DL power reduction
Signal level predictions
= 0 for BCCH = 0 for TCH
= 0 for BCCH = 0 for TCH
= 0 for BCCH = 0 for TCH
Hopping mode
Interference predictions
Non Hopping
Base Band Hopping
Synthesised Hopping
Reception threshold
Signal level predictions
x
x
x
AFP weight
Automatic frequency planning
x
x
x
HSN domain
Automatic frequency planning
Not used
x
x
Lock HSN
Automatic frequency planning
x
x
x
DTX supported
Automatic frequency planning, Interference predictions
x
x
x
Half-rate traffic ratio
Traffic analysis
x
x
x
Target rate of traffic overflow
Traffic analysis
x
x
x
Timeslot configuration
Dimensioning
x
x
x
Default TRX configuration
Traffic analysis, Packet predictions
x
x
x
EDGE Power Backoff
Traffic analysis, Packet predictions
x
x
x
Diversity Mode
Signal level predictions
x
x
x
Concentric Cell Type A concentric cell type consists of three TRX types: • • •
BCCH TRX type TCH TRX type TCH_INNER
The following table describes the parameters to be specified for each hopping mode.
Parameter
Where Used in Atoll
Frequency domain Maximum MAL (Mobile Allocation List) length
Hopping mode Non hopping
BBH
SFH
Automatic or manual frequency planning
x
x
x
Automatic frequency planning
Not used
x
x
603
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Parameter
Where Used in Atoll
Allocation strategy
Hopping mode Non hopping
BBH
SFH
Automatic or manual frequency planning
x
x
x
C/I threshold
Interference predictions, Automatic frequency planning
x
x
x
% max interference
Automatic frequency planning
x
x
x
DL power reduction
Signal level predictions
= 0 for BCCH => 0 for TCH 0 for TCH_INNER
= 0 for BCCH => 0 for TCH 0 for TCH_INNER
= 0 for BCCH => 0 for TCH 0 for TCH_INNER
Hopping mode
Interference predictions
Non Hopping
Base Band Hopping
Synthesised Hopping
Reception threshold
Signal level predictions
x
x
x
AFP weight
Automatic frequency planning
x
x
x
HSN domain
Automatic frequency planning
Not used
x
x
Lock HSN
Automatic frequency planning
x
x
x
DTX supported
Automatic frequency planning, Interference predictions
x
x
x
Half-rate traffic ratio
Traffic analysis
x
x
x
Target rate of traffic overflow
Traffic analysis
x
x
x
Timeslot configuration
Dimensioning
x
x
x
8.9.4 TRX Configuration In GSM/GPRS/EDGE projects, coding schemes are modelled using a 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, the value for the TRX configuration is read from the TRXs. The TRX configuration, and any parameters or limitations, will have be defined again for the TRXs. Otherwise, the configuration will not be taken into account during calculations. In this section, the following is described: •
"Creating or Importing TRX Configuration" on page 604.
8.9.4.1 Creating or Importing TRX Configuration In Atoll, you can create or import a TRX configuration for GSM/GPRS/EDGE documents. To create a new TRX configuration: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Right-click the TRX Configurations folder. The context menu appears. 4. Select Open Table. The TRX Configurations table appears. 5. In the row marked with the New Row icon ( ), enter the following parameters to create a TRX configuration (for information on working with data tables, see "Working with Data Tables" on page 69): • • •
604
Name: Select a TRX type from the list. Max. GPRS CS: Enter the maximum number of coding schemes that the GPRS-compatible configuration can use. Max. EDGE CS: Enter the maximum number of coding schemes that the EDGE-compatible configuration can use.
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
•
Comments: You can enter comments in this field if you want.
If you have a TRX configuration data in text or comma-separated value (CSV) format, you can import it into the TRX Configuration table in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the TRX Configuration table of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. To import a new TRX configuration: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Network Settings > TRX Configurations. The TRX Configuration table appears. The HSN Domains table contains a entry called "Standard." 4. Right-click the TRX Configuration table. The context menu appears. 5. Select Import from the context menu. For information on importing table data, see "Importing Tables from Text Files" on page 82.
8.9.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 606). 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 607). In this section, the following are described: • • • • •
"Opening the Codec Mode Table" on page 605 "Creating or Modifying Codec Configuration" on page 606 "Setting Codec Mode Adaptation Thresholds" on page 606 "Setting Codec Mode Quality Thresholds" on page 607 "Using Codec Configurations in Transmitters and Terminals" on page 608. Codec configurations can be adapted in order to create an advanced model of the frequency hopping gain effect on the quality indicator predictions (see "Advanced Modelling of Hopping Gain in Coverage Predictions" on page 620).
8.9.5.1 Opening the Codec Mode Table You can access the table containing all the codec modes which can be used to create or modify and codec configurations. This table is read-only and cannot be edited. To open the Codec Mode table: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the Codec Modes folder. 4. In the Codec Modes folder, right-click List. The context menu appears. 5. Select Open Table. 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.
605
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
8.9.5.2 Creating or Modifying Codec Configuration You create a codec configuration by creating a new entry in the Codec Configuration table. Additional parameters, such as the adaptation thresholds and the quality thresholds, can be set in the Properties dialogue for the codec configuration. The additional parameters are explained in the following sections: • •
"Setting Codec Mode Adaptation Thresholds" on page 606 "Setting Codec Mode Quality Thresholds" on page 607
To create or modify a codec configuration: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the Codec Modes folder. 4. In the Codec Modes folder, right-click Configurations. The context menu appears. 5. Select Open Table. The Codec Configurations table appears. 6. 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. 7. 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 (C⁄N or C⁄N and C⁄I + N). QI for Ideal Link Adaptation: Select the quality indicator to be used if the Ideal Link Adaptation check box is selected. Reference Noise (dBm): Enter the receiver noise that provided the mapping (thresholds - codecs). In coverage predictions, for a specific terminal leading to another receiver total noise, the thresholds will be shifted by the noise difference. You can add new fields to the Codec Configuration table by right-clicking the table and selecting Table Fields from the context menu. The new fields will appear in the Codec Configuration table and on the Other Properties tab of the selected codec configuration’s Properties dialogue.
8.9.5.3 Setting Codec Mode Adaptation Thresholds A GSM network has a variety of different codec modes that allow it to optimise resource usage. These codec modes include Full Rate (FR), Half Rate (HR), Enhanced Full Rate (EFR), and many Adaptive Multi-Rate (AMR) modes and can be seen in the read-only codec mode table (See"Opening the Codec Mode Table" on page 605). A GSM network, with different codec configurations on different transmitters, can dynamically allocate and manage resources based on interference levels. You can define quality thresholds for each codec mode compatible with the codec configuration in the Adaptation Thresholds tab in the codec configuration Properties dialogue. These thresholds are used in calculations when the codec configuration does not have the capacity for ideal link adaptation. To define the codec mode adaptation thresholds to be used when the codec configuration does not have the capacity for ideal link adaptation: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the Codec Modes folder. 4. In the Codec Modes folder, right-click Configurations. The context menu appears. 5. Select Open Table. The Codec Configurations table appears. 6. In the Codec Configuration table, right-click the record describing the codec configuration for which you want to define adaptation thresholds. The context menu appears. 7. Select Record Properties from the context menu. The codec configuration Properties dialogue appears. 8. Select the Adaptation Thresholds tab. Each codec mode adaptation threshold has the following parameters: • •
606
Codec Mode: The codec mode. Mobility: The mobility to which the codec mode adaptation threshold corresponds. You can select "All" if you want it to apply to all mobilities.
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
• • • •
Frequency Hopping: The type of frequency hopping to which the codec mode adaptation threshold corresponds. 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 the codec mode adaptation threshold corresponds. You can select "All" if you want it to apply to any frequency band. Adaptation Threshold (dB): Enter the adaptation threshold for the codec mode. Adaptation thresholds are used for codec mode selection when the codec configuration does support ideal link adaptation. MAL Length: The mobile allocation list length to which the codec mode adaptation threshold corresponds. You can create a new adaptation threshold by entering the parameters in the row marked with the New Row icon ( ).
9. Click OK.
8.9.5.4 Setting Codec Mode Quality Thresholds You can define quality thresholds for each codec mode compatible with the codec configuration in the Adaptation Thresholds tab in the codec configuration Properties dialogue. These thresholds are used in calculations when the codec configuration has the capacity for automatic mode selection. The quality indicators that can be used with codec configuration are Bit Error Rate (BER), Frame Error Rate (FER), and Mean Opinion Score (MOS). You can define each a quality threshold for each quality indicator, in combination with specific codec modes, mobilities, frequency hopping modes, and frequency bands, as a function of C⁄N and C⁄I + N. These quality thresholds are used in calculations when codec configuration has the capacity for ideal link adaptation. The quality threshold chosen respects the combination of codec modes, mobilities, frequency hopping modes, and frequency bands as well as the selected quality indicator. To define the codec mode quality graphs to be used when the codec configuration has the capacity for automatic mode selection: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the Codec Modes folder. 4. In the Codec Modes folder, right-click Configurations. The context menu appears. 5. Select Open Table. The Codec Configurations table appears. 6. In the Codec Configuration table, right-click the record describing the codec configuration for which you want to define adaptation thresholds. The context menu appears. 7. Select Record Properties from the context menu. The codec configuration Properties dialogue appears. 8. Select the Quality Graphs tab. Each quality indicator graph has the following parameters: • • • • • •
•
Quality Indicator: The quality indicator. Codec Mode: The codec mode to which the quality indicator graph corresponds. Mobility: The mobility to which the quality indicator graph corresponds. You can select "All" if you want it to apply to all mobilities. Frequency Hopping: The type of frequency hopping to which the quality indicator graph corresponds. You can select "All" if you want it to apply to all types of frequency hopping. Frequency Band: The frequency band to which the quality indicator graph corresponds. You can select "All" if you want it to apply to all frequency bands. QI = f(C/N): The values of the graph defining the selected quality indicator threshold as a function of C⁄N. You can view the graph and edit its values by selecting the row containing the quality indicator and clicking the C⁄N Graph button. QI = f(C/I): The values of the graph defining the selected quality indicator threshold as a function of C⁄I. You can view the graph and edit its values by selecting the row containing the quality indicator and clicking the C⁄I Graph button. If intra-technology third order intermodulation interference is taken into account, Atoll assumes that the C⁄I graphs include the effect of this interference whereas the C⁄N graphs do not. This option requires activation through changes in the database. For more information, contact support.
•
MAL Length: The mobile allocation list length to which the quality indicator graph corresponds. You can create a new quality indicator threshold by entering the parameters in the row marked with the New Row icon ( ).
607
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
9. Click OK.
8.9.5.5 Using Codec Configurations in Transmitters and Terminals In Atoll, codec configurations can be assigned to transmitters and terminals. If a codec configuration is assigned on both the transmitter and terminal, Atoll takes the codec modes common to both and finds the possible modes, using the terminal-side thresholds if the defined thresholds are different on transmitter and terminal sides. If no codec configuration is defined either at the transmitter or in the terminal, the transmitter will not be considered in the specific quality indicators coverage prediction. To assign a codec configuration to a transmitter: 1. Select the Network explorer. 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 transmitter’s Properties dialogue appears. You can also access a transmitter’s 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. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Click the Expand button ( ) 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 terminal’s Properties dialogue appears. 6. Select the Codec Configuration from the list.
8.9.6 Coding Scheme Configuration In Atoll, you can model a coding scheme configuration with coding schemes and their related thresholds. Any GPRS/EDGEcapable transmitters must have a coding scheme configuration assigned to them. In this section, the following are described: • • • • •
"Opening the Coding Schemes Table" on page 608 "Creating or Modifying a Coding Scheme Configuration" on page 609 "Using Coding Scheme Configuration in Transmitters and Terminals" on page 610 "Adapting Coding Scheme Thresholds for a Maximum BLER" on page 610 "Displaying Coding Scheme Throughput Graphs" on page 611. You can adapt coding scheme configurations in order to create an advanced model of the frequency hopping gain effect on the GPRS/EDGE predictions (see"Advanced Modelling of Hopping Gain in Coverage Predictions" on page 620).
8.9.6.1 Opening the Coding Schemes Table You can access the table containing all the coding schemes that can be used to create or modify and coding scheme configurations. This table is read-only and can not be edited. To open the Coding Schemes table: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the Coding Schemes folder. 4. In the Coding Schemes folder, right-click List. The context menu appears. 5. Select Open Table. The Coding Schemes table appears. It displays the following information:
608
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
•
Name: The name of the coding scheme: • • • •
• • • • •
CS: Coding schemes for GPRS MCS: Modulation and coding schemes for EGPRS (EDGE) DAS: Downlink coding schemes for EGPRS2-A (EDGE Evolution) DBS: Downlink coding schemes for EGPRS2-B (EDGE Evolution)
Number: The coding scheme number. By default the limit is 4 in GPRS, 9 in GPRS, and 12 in GPRS2 (EDGE evolution) Technology: The technology the coding scheme can be used for: GPRS or EDGE. EGPRS and EGPRS2 (EDGE evolution) are grouped together into EDGE. Modulation: The modulation of the coding scheme. For any coding scheme except the ones using the modulations GMSK (GPRS) and QPSK (DBS-5 and DBS-6 in EGPRS2), a power backoff is applied on the GPRS/EDGE service area. Coding: The coding of the selected coding scheme. Coding is convolutional for GPRS and EGPRS, turbo for EGPRS2 (EDGE evolution). Max throughput (Kbps): For a given quality, if several codec modes are possible, the one with the highest priority (highest number) is retained.
8.9.6.2 Creating or Modifying a Coding Scheme Configuration You create a coding scheme configuration by creating a new entry in the Coding Scheme Configurations table. The coding scheme thresholds for a coding scheme configuration can be set in its Properties dialogue. To create or modify a coding scheme configuration: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the Coding Schemes folder. 4. In the Coding Schemes folder, right-click Configurations. The context menu appears. 5. Select Open Table. The Coding Scheme Configurations table appears. 6. If you are creating a new coding scheme configuration, enter the name of the coding scheme configuration in the row marked with the New Row icon ( ). This name will appear in other dialogues when you select a coding scheme configuration. If you are modifying an existing coding scheme configuration, continue with the following step. 7. 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 C⁄N. 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 configuration’s Properties dialogue.
8. In the Coding Scheme Configurations table, right-click the record describing the coding scheme configuration for which you want to define adaptation thresholds. The context menu appears. 9. Select Record Properties from the context menu. The coding scheme configuration’s Properties dialogue appears. The coding scheme configuration’s Properties dialogue has a General tab which allows you to modify the properties described above. 10. Select the Thresholds tab. Each coding scheme threshold has the following parameters: • • • •
•
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 C⁄I. You can view the graph and edit its values by selecting the row containing the coding scheme and clicking the C⁄I Graph button. If intra-technology third order intermodulation interference is taken into account, Atoll assumes that the C⁄I graphs include the effect of this interference whereas the C graphs do not. This option requires activation through changes in the database. For more information, contact support.
609
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
• • • • • • •
© Forsk 2012
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. MAL Length: The mobile allocation list length to which the coding scheme (and its related quality thresholds) applies. You can create a new coding scheme threshold by entering the parameters in the row marked with the New Row icon ( ).
11. Click OK. 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 coverage prediction if these parameters correspond to the ones defined in that coverage prediction. 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.
8.9.6.3 Using Coding Scheme Configuration in Transmitters and Terminals In Atoll, a coding scheme configuration can be assigned to transmitters. If a coding scheme configuration is assigned on both the transmitter and terminal, Atoll takes the coding scheme configuration common to both and finds the possible modes, using the terminal-side thresholds if the defined thresholds are different on transmitter and terminal sides. If no coding scheme configuration is defined either at the transmitter or in the terminal, the transmitter will not be considered in certain quality indicators coverage predictions. To assign a coding scheme configuration to a transmitter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter to which you want to assign the coding scheme configuration. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. You can also access a transmitter’s 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. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Click the Expand button ( ) 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 terminal’s Properties dialogue appears. 6. Select the GPRS Configuration from the list.
8.9.6.4 Adapting Coding Scheme Thresholds for a Maximum BLER You can have Atoll automatically calculate the reception and C⁄I thresholds for a coding scheme configuration. You enter the acceptable Block Error Rate (BLER) in the coding scheme configuration’s Properties dialogue and Atoll calculates the thresh-
610
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
olds required to ensure that the defined BLER is never exceeded. The admission threshold corresponds to 1 - BLER X max. throughout calculated for the coding scheme. To calculate the reception and C/I thresholds for a coding scheme configuration: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the Coding Schemes folder. 4. In the Coding Schemes folder, right-click Configurations. The context menu appears. 5. Select Open Table. The Coding Scheme Configurations table appears. 6. In the Coding Scheme Configurations table, right-click the record of the coding scheme configuration for which you Atoll to automatically calculate reception and C⁄I thresholds. The context menu appears. 7. Select Record Properties from the context menu. The coding scheme configuration’s Properties dialogue appears. 8. Select the Thresholds tab. 9. Under Calculate the Thresholds to Get the Following BLER Value, enter a value in the BLER text box and click the Calculate button. Atoll calculates the thresholds required to satisfy the entered BLER. 10. Click OK to close the coding scheme configuration’s Properties dialogue and save the new threshold values.
8.9.6.5 Displaying Coding Scheme Throughput Graphs In GPRS/EDGE technology, coding schemes are linked with data transmission redundancy levels. With coding schemes, two types of information is transmitted: user data and error correction data. There is a trade-off between accurate data transmission and transmission rates. Low error correction offers potentially higher transmission rates, but also a higher 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 C⁄I 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 C⁄I for a given coding scheme: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Click the Expand button ( ) to expand the Coding Schemes folder. 4. In the Coding Schemes folder, right-click Configurations. The context menu appears. 5. Select Open Table. The Coding Scheme Configurations table appears. 6. In the Coding Scheme Configurations table, right-click the record describing the coding scheme configuration for which you Atoll to automatically calculate reception and C⁄I thresholds. The context menu appears. 7. Select Record Properties from the context menu. The coding scheme configuration’s Properties dialogue appears. 8. Select the Thresholds tab. 9. 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 C⁄I.
If intra-technology third order intermodulation interference is taken into account, Atoll assumes that the C⁄I graphs include the effect of this interference whereas the C graphs do not. This option requires activation through changes in the database. For more information, contact support. 10. Click OK to close the dialogue.
8.9.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.
611
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
In this section, the following is explained: •
"Creating or Modifying a Timeslot Configuration" on page 612.
8.9.7.1 Creating or Modifying a Timeslot Configuration To create or modify a timeslot configuration: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Right-click the Timeslot Configurations folder. The context menu appears. 4. Select Open Table. The Timeslot Configurations table appears. 5. If you are creating a new timeslot configuration, enter the name of the timeslot configuration in the row marked with the New Row icon ( ). This name will appear in other dialogues when you select a timeslot configuration. If you are modifying an existing timeslot configuration, continue with the following step. 6. Select the row containing the timeslot configuration and click the Properties button ( timeslot configuration’s Properties dialogue appears.
) in the Table toolbar. The
Under Mapping between TRX numbers and timeslot configurations, each row corresponds to a distribution of timeslots and is identified by an index number. During dimensioning, Atoll determines the number of circuit and packet timeslots required to meet the traffic demand. Atoll uses the timeslot configuration to determine how many TRXs are needed to meet the need in timeslots. If, during dimensioning, there are not enough index numbers in the timeslot configuration, Atoll reuses the last index number in the timeslot configuration. 7. In the timeslot configuration’s Properties dialogue, enter the following information for each index number: • • •
Number of Shared Timeslots: The number of timeslots that can be used for both circuit-switched (GSM) and packet-switched (GPRS and EDGE) services. Number of Circuit Timeslots: The number of timeslots that can be used only for both circuit-switched (GSM) services. Number of Packet Timeslots: The number of timeslots that can be used only for packet-switched (GPRS and EDGE) services. 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.
8. Click OK to close the timeslot configuration’s Properties dialogue. 9. Click the Close button ( ) to close the List of Timeslot Configurations table.
8.9.8 Advanced Transmitter Configuration Options Atoll offers several options to help you configure more complex transmitter situations. These options are explained in this section: • •
"Defining Extended Cells" on page 612 "Advanced Modelling of Multi-Band Transmitters" on page 613.
8.9.8.1 Defining Extended Cells GSM cells usually cover an area within a 35 km radius. But, as user locations and their distances from the base station vary, and radio waves travel at a constant speed, the signal from users who are further than 35 km from the base station can be delayed by almost an entire timeslot. This delay creates interference with the signal on the adjacent timeslot. Extended GSM cells enable the operator to overcome this limit by taking this delay into consideration when defining the timing advance for users in the extended cells. Extended cells can cover distances from 70 to 140 km from the base station. In a network with extended cells, Atoll will calculate coverage predictions from the extended cell’s defined minimum to maximum range, but will calculate interference caused by the extended cell beyond these ranges, inwards and outwards. To define an extended cell: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter for which you want to define an extended cell. The context menu appears.
612
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. You can also access a transmitter’s 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.
8.9.8.2 Advanced Modelling of Multi-Band Transmitters In Atoll GSM/GPRS/EDGE projects, all subcells share the same frequency band by default. However, by changing an option in the atoll.ini file, you can model transmitters with more than one frequency band. For more information on changing options in the atoll.ini file, see the Administrator Manual. Once you have set the multi-band option in the atoll.ini file and restarted Atoll, you can modify the properties of existing transmitters to change them to multi-band transmitters or create a multi-band transmitter template. The relevant properties of all multi-band transmitters can be accessed in a special table. In this section, the following are explained: • • •
8.9.8.2.1
"Defining a Multi-Band Transmitter" on page 613 "Creating a Multi-Band Template" on page 614 "Accessing the Multi-Band Propagation Parameters Table" on page 616.
Defining a Multi-Band Transmitter Each subcell on a transmitter is assigned a frequency domain. After making the necessary changes in the atoll.ini file, you must change the frequency domain of one or more non-BCCH subcells to a domain on a frequency band that is different from the frequency band used by the BCCH. You can then modify the frequency-band-specific settings: • • •
Antenna type, height, mechanical and additional electrical downtilt, Equipment losses Propagation models and path loss matrices.
This settings are taken into account in: • • • •
Coverage predictions Traffic capture Dimensioning Interference matrices.
To define the propagation settings for a frequency band used by a subcell: 1. Select the Network explorer. 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 transmitter’s Properties dialogue appears. You can also access a transmitter’s 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 propagation Properties dialogue appears. 9. Click the General tab. The following parameters are displayed: • •
Name: The name is composed of the multi-band transmitter this subcell belongs to followed by the frequency band, separated by "@". This field cannot be edited. ID: The ID is a user-definable network-level parameter for cell identification. You can enter an ID that is different from the name of the base transmitter.
613
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
• •
•
© Forsk 2012
Site: The Site on which the base transmitter is located. This field cannot be edited. Shared Antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the same site or on sites with the same position and that share the same antenna. The entry in the field must be the same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna Position, you can modify the position of the antenna: • •
Relative to Site: Select this option if you want to enter the antenna position as an offset with respect to the site location, and then enter the x-axis and y-axis offsets, Dx and Dy, respectively. Coordinates: Select this option if you want to enter the coordinates of the antenna, and then enter the x-axis and y-axis coordinates of the antenna, X and Y, respectively.
10. Click the Transmitter tab. You can set the following parameters: •
•
•
•
Total Losses: You can enter a value for Total Losses or let Atoll calculate losses according to the characteristics of the equipment assigned to the transmitter. The Equipment Specifications 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. • • •
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
11. Click the Propagation tab. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. 12. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Transmitters table. 13. Click OK.
8.9.8.2.2
Creating a Multi-Band Template If you will be creating new multi-band base stations, you can first create a multi-band template with the necessary parameters, including the propagation model parameters for each subcell using a different frequency band. When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. To create a multi-band template, you must have an appropriate multi-band cell type to assign to the template. If you have not already created a multi-band cell type, you must do so before creating the template. For information on creating a cell type, see "Creating a Cell Type" on page 601. 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. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the GSM Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears.
614
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
4. Select Management... from the context menu. The Station Templates Management dialogue appears. 5. 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. 6. 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. d. Make any other necessary changes to the station template parameters. For information on the parameters available, see "Modifying a Station Template" on page 379. e. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes. 7. 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 8.124): • •
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 8.124: 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 8.125): •
Under Main Antenna, you can modify the following: the Height/Ground of the antennas from the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of building), the main antenna Model, 1st Sector Azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Mechanical Downtilt, and the Additional Electrical Downtilt for the antennas. • •
•
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide.
Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Working with 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 365.
615
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
Figure 8.125: Properties dialogue for frequency band of a multi-band template 8. 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 "@". 9. Repeat step 7. for every frequency band modelled by the multi-band template.
8.9.8.2.3
Accessing the Multi-Band Propagation Parameters Table In a GSM/GPRS/EDGE multi-band document, you can access the properties of all multi-band transmitters using the MultiBand Propagation Parameters table. To open the Multi-Band Propagation Parameters table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Subcells > Multi-Band Propagation Parameters from the context menu. The Multi-Band Propagation Parameters table appears. Multi-band transmitters are identified in the Transmitter column, with the subcells using a frequency band other than the main frequency band for that transmitter identified with a name composed of the multiband transmitter they belong to followed by the frequency band, separated by "@".
8.9.9 GSM/GPRS/EDGE Multi-Service Traffic Data In Atoll, you can define the traffic data in the GSM/GPRS/EDGE network. The data will be used in different network calculations, such as, dimensioning and coverage predictions. In this section, the following are explained: • • •
"Modelling GSM/GPRS/EDGE Services" on page 616 "Modelling GSM/GPRS/EDGE Mobility Types" on page 618 "Modelling GSM/GPRS/EDGE Terminals" on page 618.
8.9.9.1 Modelling GSM/GPRS/EDGE Services You can model both circuit and packet-switched GSM/GPRS/EDGE services. In this section, the following are explained: • •
8.9.9.1.1
"Creating or Modifying a GSM/GPRS/EDGE Service" on page 616 "Displaying the GSM/GPRS/EDGE Services Table" on page 617
Creating or Modifying a GSM/GPRS/EDGE Service You can define the various user services in GSM/GPRS/EDGE documents. The services can be circuit-switched or dataswitched. Currently the only circuit-switched service in a GSM/GPRS/EDGE network is a GSM voice service that uses a single timeslot. The quality requirement parameters of services are mostly used in the dimensioning process.
616
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
To create or modify a service: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears. You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.
5. Edit the fields on the General tab to define the new service: • • •
Name: Atoll proposes a name for the new service, but you can change the name to something more descriptive. Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for each user during Monte-Carlo simulations. Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate is the average rate obtained by a user of the service. How the average requested rate is used in Atoll depends on the type of service: •
•
Circuit: This rate is the average rate obtained by a user of the service. It is used in simulations during user distribution generation to calculate the number of users attempting a connection and to determine their activity status. Packet: 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.
6. Click the Parameters tab to define the new service. 7. 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). 8. 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. 9. Max. Packet Delay: The maximum period of time that a packet can be delayed before transmission. 10. 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. 11. 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. 12. Max. Number of Timeslots per carrier: The maximum number of timeslots per carrier is used during dimensioning to limit the number of timeslots that can be assigned to a user using this service on a carrier. This parameter applies to packet-switched services. For constant bit rate packet-switched services such as VoIP, this parameter has to be set to "1". 13. 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. 14. Click OK.
8.9.9.1.2
Displaying the GSM/GPRS/EDGE Services Table You can display the parameters of all the services in the Services table. You can modify any of the parameters or create a new service. To display the Services table: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the Services folder. The context menu appears. 4. Select Open Table from the context menu. The Services table appears. For information on working with tables in Atoll, see "Working with Data Tables" on page 69.
617
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
8.9.9.2 Modelling GSM/GPRS/EDGE Mobility Types In a multi-layer GSM/GPRS/EDGE network, the speed the user is travelling is one of the most important criteria in allocating the user to a server. A mobile user travelling at a high speed is usually allocated a channel on the macro layer rather than on the micro layer in order to minimise signalling and system load and to spread the traffic over several layers. In this section, the following are explained: • •
8.9.9.2.1
"Creating or Modifying a GSM/GPRS/EDGE Mobility Type" on page 618 "Displaying the GSM/GPRS/EDGE Mobility Types Table" on page 618.
Creating or Modifying a GSM/GPRS/EDGE Mobility Type To create or modify a mobility type: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. You can modify the properties of an existing mobility type by right-clicking the mobility type in the Mobility Types folder and selecting Properties from the context menu.
5. On the General tab, you can enter or modify the following parameters in the Mobility Types New Element Properties dialogue: • •
Name: Enter or modify the descriptive name for the mobility type. Speed: Enter or modify an average speed for the mobility type. 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.
8.9.9.2.2
Displaying the GSM/GPRS/EDGE Mobility Types Table You can display the parameters of all the mobility types in the Mobility Types table. You can modify any of the parameters or create a new mobility type. To display the Mobility Types table: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the Mobility Types folder. The context menu appears. 4. Select Open Table from the context menu. The Mobility Types table appears. For information on working with tables in Atoll, see "Working with Data Tables" on page 69.
8.9.9.3 Modelling GSM/GPRS/EDGE Terminals In GSM/GPRS/EDGE, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a car’s on-board navigation device. In Atoll, a terminal is modelled in terms of its GSM and GPRS/EDGE-relevant parameters. In this section, the following are explained: • •
8.9.9.3.1
"Creating or Modifying a GSM/GPRS/EDGE Terminal" on page 618 "Displaying the GSM/GPRS/EDGE Terminals Table" on page 619.
Creating or Modifying a GSM/GPRS/EDGE Terminal To create or modify a terminal: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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.
618
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
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. Click the General tab. You can modify the following parameter: •
Name: You can change the name of the terminal.
6. Click the Parameters tab. You can modify the following parameters: • •
• • • •
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 multi-band network. Noise Figure: The noise caused by the terminal. This value is added to the thermal noise (set to -121 dBm by default) in predictions when studying C⁄N or C⁄I + N instead of C or C⁄I. DTX Supported: The DTX Supported check box is selected if the terminal supports DTX (Discontinuous Transmission) technology. 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. The highest number of GPRS (or EDGE) coding schemes available to the terminal is limited by the maximum number of GPRS (or EDGE) coding schemes defined for the TRX configuration assigned to a transmitter.
•
•
Number of DL Timeslots per carrier: If the terminal is GPRS or EDGE-compatible, you can enter the maximum number of downlink timeslots the terminal can use on a carrier. Terminals using only circuit-switched services will 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 452 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 452 for more information). 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.
7. Click OK.
8.9.9.3.2
Displaying the GSM/GPRS/EDGE Terminals Table You can display the parameters of all the terminals in the Terminals table. You can modify any of the parameters or create a new terminal. To display the Terminals table: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder.
619
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
© Forsk 2012
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 69.
8.9.10 Defining the Interferer Reception Threshold In Atoll, you can define a limit on the received signal level. This limit is used by Atoll to limit the input of interferers in calculations. When the interferer reception threshold is set, the performance of calculations based on C⁄I, such as coverage by C⁄I level, interfered zones. and GPRS/EDGE predictions can be improved. As well, the performance of calculations using the Interference view of the Point Analysis window, traffic analyses, and interference histograms can also be improved. This value is used as a filter criterion on interferers. Atoll will discard all interferers with a signal level lower than this value. To define the interferer reception threshold: 1. Select the Parameters explorer. 2. Right-click the GSM Network Settings folder. The context menu appears. 3. Select Properties from the context menu. The GSM Network Settings Properties dialogue appears. 4. Click the Calculations Parameters tab. 5. Under Calculation Limitation, enter an Interferer Reception Threshold in dBm. 6. Click OK.
8.9.11 Advanced Modelling of Hopping Gain in Coverage Predictions Using frequency hopping has an advantage from the point of view of interference in the way interference can be smoothed over several frequencies. In addition, radio link resistance to fast fading is increased and its efficiency is optimised. Because this effect of hopping can be noticed on voice quality and on throughput, you can define specific admission thresholds for codec modes and coding schemes according to specific MAL lengths. If you want Atoll to take advanced modelling of hopping gains in coverage predictions, the administrator (or you, if you have administrator rights) has to add the field MAL_LENGTH to the CodecQualityTables and EGPRSQuality tables. Adding this custom field provides a MAL_LENGTH column in the definition of each codec configuration (Quality Graphs tab) and each coding scheme configuration. For codec configurations, it means that you can define a specific codec mode graph per MAL length where the graph efficiency increases as the MAL length increases, too (see Figure 8.126 on page 620).
Figure 8.126: 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 566), 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.: •
620
if the mobile MAL length exceeds all the MAL lengths defined in the quality indicator graphs, the closest MAL length is selected;
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
•
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 8.127 on page 621).
Figure 8.127: Coding Scheme Configuration Properties (with MAL length definition) In GPRS/EDGE coverage predictions (see "Packet-Specific Coverage Predictions" on page 558), 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.
8.9.12 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 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 C⁄I. 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 145. Shadowing can be taken into consideration when Atoll calculates the signal level (C) and the signal-to-noise ratio (C⁄I) for: •
A point analysis (see "Making a Point Analysis to Study the Profile" on page 393)
621
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
•
• •
© Forsk 2012
A coverage prediction (see "Studying Signal Level Coverage" on page 395, "Interference Coverage Predictions" on page 548, "Packet-Specific Coverage Predictions" on page 558, and "Making a Circuit Quality Indicator (BER, FER, or MOS) Coverage Prediction" on page 566) Neighbours (see "Allocating Neighbours Automatically" on page 424) Traffic capture (see "Calculating and Displaying a Traffic Capture" on page 447).
You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per Clutter Class" on page 622.
8.9.12.1 Displaying the Shadowing Margins per Clutter Class To display the shadowing margins per clutter class: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins dialogue appears (see Figure 8.128). 4. You can set the following parameters: • •
Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin: • •
From Model: The model standard deviation. Atoll will display the shadowing margin on the signal level. C⁄I: The C⁄I standard deviation. Atoll will display the shadowing margin on the C⁄I level.
5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.
Figure 8.128: The Shadowing Margins dialogue
8.9.13 Modelling the Co-existence of Networks In Atoll, you can study the effect of interference received by your network from other GSM/GPRS/EDGE networks. The interfering GSM/GPRS/EDGE network can be a different part of your own network, or a network belonging to another operator. To study interference from co-existing networks: 1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a Group of Base Stations" on page 384. 2. For the interfering network’s transmitters, set the Transmitter Type to Extra-Network (Interferer Only) as explained in "Transmitter Description" on page 365. During calculations, Atoll will consider the transmitters of type Extra-Network (Interferer Only) when calculating interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interference. Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network. If the interfering network is a part of your own network, this information would be readily available. However, if the interfering network belongs to another operator, the information available might not be accurate.
622
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
AT312_UM_E1
8.9.14 Modelling Inter-technology Interference Analyses of GSM networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in a GSM network. Atoll can take into account interference from co-existing networks in calculations. •
Interference received by mobiles on the downlink: Interference can be received by mobiles in a GSM network on the downlink from external base stations and mobiles in the vicinity. Interference from external base stations (also called downlink-to-downlink interference) can be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (CDMA, TDMA, OFDM). These graphs are then used for calculating the interference from the external base stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-technology IRFs" on page 623. Interference from external mobiles (also called uplink-to-downlink interference) can be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your GSM network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled in Atoll using the Inter-technology DL Noise Rise definable for each TRX in the GSM network. This noise rise is taken into account in all interference-based calculations. For more information on the Inter-technology DL Noise Rise, see "TRX Definition" on page 373.
Figure 8.129: Interference received by mobiles on the downlink
8.9.14.1 Defining Inter-technology IRFs Interference received from external base stations on mobiles of your GSM network can be calculated by Atoll. Atoll uses the inter-technology interference reduction factor (IRF) graphs for calculating the interference levels. An IRF graph represents the variation of the Adjacent Channel Interference Ratio (ACIR) as a function of frequency separation. ACIR is determined from the Adjacent Channel Suppression (ACS) and the Adjacent Channel Leakage Ratio (ACLR) parameters as follows: 1 ACIR = ------------------------------------1 1 ------------- + ----------------ACS ACLR
An IRF depends on: • • • •
The interfering technology (TDMA, CDMA, and OFDM) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).
IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your GSM document, i.e., when Atoll is in co-planning mode. To define the inter-technology IRFs in the victim network: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Inter-technology Interference Reduction Factors. The context menu appears. 4. Select Open Table. The Inter-technology Interference Reduction Factors table appears. 5. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter: • •
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.
623
Atoll 3.1.2 User Manual Chapter 8: GSM/GPRS/EDGE Networks
• •
© Forsk 2012
Victim Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfered network. This channel width must be consistent with that used in the main document. Reduction Factors (dB): Click the cell corresponding to the Reduction Factors (dB) column and the current row in the table. The Reduction Factors (dB) dialogue appears. •
Enter the interference reduction factors in the Reduction (dB) column for different frequency separation, Freq. Delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document. • •
Reduction values must be positive. If you leave reduction factors undefined, Atoll assumes there is no interference.
6. When you have finished defining interference reduction factors, click OK.
624
Chapter 9 UMTS HSPA Networks This chapter provides the information to use Atoll to design, analyse, and optimise a UMTS HSPA network.
In this chapter, the following are explained: •
"Designing a UMTS Network" on page 627
•
"Planning and Optimising UMTS Base Stations" on page 628
•
"Studying Network Capacity" on page 729
•
"Optimising Network Parameters Using the ACP" on page 762
•
"Verifying Network Capacity" on page 764
•
"Co-planning UMTS Networks with Other Networks" on page 776
•
"Advanced Configuration" on page 795
Atoll 3.1.2 User Manual Chapter 9: Starting a Project
626
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9 UMTS HSPA Networks Atoll enables you to create and modify all aspects of a UMTS HSPA (HSDPA and HSUPA) network. Once you have created the network, Atoll offers many tools to let you verify the network. Based on the results of your tests, you can modify any of the parameters defining the network. The process of planning and creating a UMTS HSPA network is outlined in "Designing a UMTS Network" on page 627. Creating the network of base stations is explained in "Planning and Optimising UMTS Base Stations" on page 628. Allocating neighbours and scrambling codes is also explained. In this section, you will also find information on how you can display information on base stations on the map and how you can use the tools in Atoll to study base stations. In "Studying Network Capacity" on page 729, using traffic maps to study network capacity is explained. Creating simulations using the traffic map information and analysing the results of simulations is also explained. Using drive test data paths to verify the network is explained in "Verifying Network Capacity" on page 764. Filtering imported drive test data paths, and using the data in coverage predictions is also explained.Filtering imported drive test data paths, and using the data in coverage predictions is also explained.
9.1 Designing a UMTS Network Figure 9.1 depicts the process of planning and creating a UMTS HSPA network. 1 Open an Existing Project or Create a New One 2 Network Configuration - Add Network Elements - Change Parameters 3 Basic Predictions (Best Server, Signal Level) 4 Neighbour Allocation
5a Traffic Maps
5c
5b Monte-Carlo Simulations
User-defined values 5 Cell Load Conditions 6a
6 UMTS/HSPA Predictions
Prediction Study Reports 7
Scrambling Code Plan
Figure 9.1: Planning a UMTS network - workflow The steps involved in planning a UMTS HSPA network are described below. The numbers refer to Figure 9.1. 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. 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 637 "Creating or Modifying a Transmitter" on page 637 "Creating or Modifying a Cell" on page 638.
627
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
You can also add base stations using a base station template (see "Placing a New Station Using a Station Template" on page 638). 3. Carry out basic coverage predictions ( • •
3
)
"Making a Point Analysis to Study the Profile" on page 656 "Studying Signal Level Coverage" on page 658 and "Signal Level Coverage Predictions" on page 667
4. Allocate neighbours, automatically or individually ( •
4
).
"Planning Neighbours" on page 705.
5. Before making more advanced coverage predictions, you need to define cell load conditions (
5
).
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 729). You can define them manually either on the Cells tab of each transmitter’s Properties dialogue or in the Cells table (see "Creating or Modifying a Cell" on page 638) (
5c
).
6. Make UMTS-specific coverage predictions using the defined cell load conditions ( • • •
).
"UMTS-Specific Predictions" on page 681 "HSDPA Quality and Throughput Analysis" on page 697 "HSUPA Quality and Throughput Analysis" on page 700.
7. Allocate scrambling codes ( •
6
7
).
"Planning Scrambling Codes" on page 720.
9.2 Planning and Optimising UMTS Base Stations As described in Chapter 2: Starting an Atoll Project, you can start an Atoll document from a template, with no sites, or from a database with a set of sites. As you work on your Atoll document, you will still need to create sites and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any other additional equipment, such as the TMA, feeder cables, etc. In a UMTS project, you must also add cells to each transmitter. A cell refers to the characteristics of a carrier on a transmitter. Antenna - Azimuth - Mechanical tilt
TMA Antenna - Height
Feeder Cable
Transmitter - Noise figure - Power
Site - X, Y coordinates
Figure 9.2: A transmitter Atoll lets you create one site, transmitter, or cell at a time, or create several at once by creating a station template. Using a station template, you can create one or more base stations at the same time. In Atoll, a base station refers to a site with its transmitters, antennas, equipment, and cells. Atoll allows you to make a variety of coverage predictions, such as signal level or transmitter coverage predictions. The results of calculated coverage predictions can be displayed on the map, compared, or studied.
628
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Atoll enables you to model network traffic by allowing you to create services, users, user profiles, environments, and terminals. This data can be then used to make quality predictions, such as effective service area, noise, or handover status predictions, on the network. In this section, the following are explained: • • • • • • • • • • • •
"Creating a UMTS Base Station" on page 629 "Creating a Group of Base Stations" on page 647 "Modifying Sites and Transmitters Directly on the Map" on page 647 "Display Tips for Base Stations" on page 648 "Creating a Dual-Band UMTS Network" on page 648 "Creating a Repeater" on page 648 "Creating a Remote Antenna" on page 653 "Setting the Working Area of an Atoll Document" on page 656 "Studying a Single Base Station" on page 656 "Studying Base Stations" on page 660 "Planning Neighbours" on page 705 "Planning Scrambling Codes" on page 720.
9.2.1 Creating a UMTS Base Station When you create a UMTS site, you create only the geographical point; you must add the transmitters and cells afterwards. The site, with the transmitters, antennas, equipment, and cells is called a base station. In this section, each element of a base station is described. If you want to add a new base station, see "Placing a New Station Using a Station Template" on page 638. If you want to create or modify one of the elements of a base station, see "Creating or Modifying a Base Station Element" on page 637. If you need to create a large number of base stations, Atoll allows you to import them from another Atoll document or from an external source. For information, see "Creating a Group of Base Stations" on page 647. This section explains the various parts of the base station process: • • • • •
"Definition of a Base Station" on page 629 "Creating or Modifying a Base Station Element" on page 637 "Placing a New Station Using a Station Template" on page 638 "Managing Station Templates" on page 639 "Duplicating an Existing Base Station" on page 646.
9.2.1.1 Definition of a Base Station A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. You will usually create a new base station using a station template, as described in "Placing a New Station Using a Station Template" on page 638. This section describes the following elements of a base station and their parameters: • • •
"Site Description" on page 630 "Transmitter Description" on page 630 "Cell Definition" on page 633.
629
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
9.2.1.1.1
© Forsk 2012
Site Description The parameters of a site can be found in the site’s Properties dialogue. The Properties dialogue has two tabs: •
The General tab (see Figure 9.3):
Figure 9.3: New Site dialogue • •
Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If you want to change the default name that Atoll gives to new sites, see the Administrator Manual. Position: By default, Atoll places the new site at the centre of the map window. You can modify the location of the site here. While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 41.
•
• •
Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can specify the actual altitude under Real, if you want. If an altitude is specified here, Atoll will use this value for calculations. Comments: You can enter comments in this field if you want.
The Equipment tab: • • • • •
Max Number of Uplink Channel Elements: The maximum number of physical radio resources for the current site in the uplink. By default Atoll enters the maximum possible (256). Max Number of Downlink Channel Elements: The maximum number of physical radio resources for the current site in the downlink. By default Atoll enters the maximum possible (256). Max Iub Uplink Backhaul Throughput: The maximum Iub backhaul throughput for the current site in the uplink. Max Iub Downlink Backhaul Throughput: The maximum Iub backhaul throughput for the current site in the downlink. Equipment: You can select equipment from the list. To create new site equipment, see "Creating Site Equipment" on page 800. If no equipment is assigned to the site, Atoll considers the following default values: • • • • •
9.2.1.1.2
Rake efficiency factor = 1 MUD factor = 0 Carrier selection = UL minimum noise Downlink and uplink overhead resources for common channels = 0 The option AS Restricted to Neighbours is not selected, and Atoll uses one channel element on the uplink or downlink for any service during power control simulation.
Transmitter Description The parameters of a transmitter can be found in the transmitter’s 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 633), the Propagation tab (see Chapter 5: Working with Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 43).
630
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
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 630. 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 796. Shared antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the same site or on sites with the same position and that share the same antenna. The entry in the field must be the same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. This field is also used for dual-band transmitters to synchronise antenna parameters for different frequency bands. Under Antenna Position, you can modify the position of the antennas (main and secondary): • •
•
Relative to Site: Select this option if you want to enter the antenna positions as offsets with respect to the site location, and then enter the x-axis and y-axis offsets, Dx and Dy, respectively. Coordinates: Select this option if you want to enter the coordinates of the antenna, and then enter the x-axis and y-axis coordinates of the antenna, X and Y, respectively.
The Transmitter tab (see Figure 9.4):
Figure 9.4: Transmitter dialogue - Transmitter tab •
Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed in red in the Transmitters folder in the Network explorer.
631
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
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 9.5), the equipment you select and the gains and losses you define are used to initialise total transmitter UL and DL losses: •
TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button ( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equipment" on page 176.
•
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 176. Transmitter: You can select transmitter equipment from the Transmitter list. You can click the Browse button
•
• • •
( ) to access the properties of the transmitter equipment. For information on creating transmitter equipment, see "Defining Transmitter Equipment" on page 176. Feeder Length: You can enter the feeder length at transmission and reception. Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value you enter must be positive. Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter must be positive.
Figure 9.5: The Equipment Specifications dialogue Any loss related to the noise due to a transmitter’s repeater is included in the calculated losses. Atoll always takes the values in the Real boxes into consideration in prediction even if they are different from the values in the Computed boxes. The information in the real Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Total Losses at transmission and reception and the real Noise Figure at reception if you want. Any value you enter must be positive. •
Antennas: •
•
Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered must include the height of building. Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens a dialogue displaying all the possible antennas based on the same physical antenna as the currently selected one. Selecting the Electrical tilt of the antenna model displays the appropriate antennas under Available Antennas. Selecting the antenna under Available Antennas and clicking OK assigns the antenna to the transmitter. The other fields, Azimuth, Mechanical Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.
632
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
• • •
•
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. The mechanical and additional electrical downtilts defined for the main antenna are also used for the calculations of smart antennas.
Under Diversity, you can select the number of transmission and reception antenna ports used for MIMO (No. of ports). MIMO systems are supported by some HSDPA bearers (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+). For more information on how the number of antenna ports are used, see "Multiple Input Multiple Output Systems" on page 804. 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. • • •
9.2.1.1.3
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Cell Definition In Atoll, a cell is defined as a carrier, with all its characteristics, on a transmitter; the cell is the mechanism by which you can configure a UMTS multi-carrier network. In other words, a transmitter has one cell for every carrier. When you create a transmitter, Atoll automatically creates one cell for the transmitter. The following explains the parameters of a UMTS cell, including the parameters for HSDPA and HSUPA functionality. As you create a cell, Atoll calculates appropriate values for some fields based on the information you have entered. You can, if you want, modify these values. The properties of a UMTS cell are found on Cells tab of the Properties dialogue of the transmitter to which it is assigned. The following HSDPA options apply to all the cells of the transmitter: •
Inter-Carrier Power Sharing: You can enable power sharing between cells by selecting the Inter-Carrier Power Sharing check box under HSDPA and entering a value in the Maximum Shared Power box. In order for Inter-Carrier Power Sharing to be available, you must have at least one HSDPA carrier with dynamic power allocation. Inter-Carrier Power Sharing enables the network to dynamically allocate available power from R99-only and HSDPA carriers among HSDPA carriers. When you select Inter-Carrier Power Sharing and you define a maximum shared power, the Max Power of each cell is used to determine the percentage of the transmitter power that the cell cannot exceed. The most common scenario is where you have R99-only cells that are not using 100% of their power and can share it with an HSDPA carrier. To use power sharing efficiently, you should set the Max Power of the HSDPA cells to the same value as the Maximum Shared Power. For example, if the Maximum Shared Power is defined as 43 dBm, the Max Power of all HSDPA cells should be set to 43 dBm in order to be able to use 100% of the available power. In this case, all of an R99 cell’s unused power can be allocated to the HSDPA cell.
•
Under Multi-cell, the following dual-cell HSDPA options are available: •
Mode: The multi-cell HSDPA mode. You can activate dual-cell HSDPA support for the transmitter. When dual-cell HSDPA is active, HSDPA users can simultaneously connect to two HSDPA cells of the transmitter for data transfer, i.e., users of dual-cell HSDPA receive the HS-DSCH on two separate carriers. The R99 A-DPCH bearer is still transmitted on one of the two cells, which is called the anchor cell. A dual-cell HSDPA user can be assigned two different HSDPA bearers in the two cells, depending on separate CQI values.
•
Scheduler Algorithm: The scheduling technique that will be used to rank the HSDPA users to be served. The sheduler manages a single queue of users at the Node B. All users belonging to the transmitter, i.e., dual-cell HSDPA and single-carrier HSDPA users, are ranked together in a single list. Dual-cell HSDPA users are considered twice in the list because they might be assigned two different HSDPA bearers in the two cells.
633
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Atoll supports the following algorithms: •
• •
•
Max C/I: "n" HSDPA users (where "n" corresponds to the sum of the maximum numbers of HSDPA users defined for all HSDPA cells) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by the channel quality indicator (CQI). Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order). Proportional Fair: "n" HSDPA users (where "n" corresponds to the sum of the maximum numbers of HSDPA users defined for all HSDPA cells) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order according to a random parameter which corresponds to a combination of the user rank in the simulation and the channel quality indicator (CQI).
MUG=f(No. Users): The multi-user diversity gain graph as a function of the number of users. The average cell throughput is higher with multiple users than with a single user. It is used to calculate the peak gross throughput per cell when the scheduling algorithm is "Proportional Fair". The MUG graph is only available if you have set the peak HSDPA throughput option in the atoll.ini file. For more information, see the Administrator Manual.
In transmitters that support multi-cell HSDPA, the multi-cell HSDPA scheduler algorithm and MUG graph are used in calculations instead of the HSDPA scheduler algorithms and MUG graphs set per cell. The following parameters can be set for each individual cell of the transmitter: •
• • • • • •
Name: By default, Atoll names the cell after its transmitter, adding the carrier number in parentheses. If you change transmitter name or carrier, Atoll does not update the cell name. You can enter a name for the cell, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names cells, see the 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. Active: If this cell is to be active, you must select the Active check box. Max Power (dBm): The maximum available downlink power for the cell. Pilot Power (dBm): The pilot power. SCH power (dBm): The average power of both the synchronisation channels (P-SCH and S-SCH). The SCH power is only transmitted 1⁄10 of the time. Consequently, the value entered for the SCH power should only be 1⁄10 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 Ec⁄I0 margin in comparison with the Ec⁄I0 of the best server. It is used to determine which cells, apart from the best server, will be part of the active set. DL Peak Rate per User (kbps): The downlink peak rate per user in kbps. The DL peak rate per user is the maximum connection rate in the downlink for a user. The DL and UL peak rates are taken into account during power control simulation. UL Peak Rate per User (kbps): The uplink peak rate per user in kbps. The UL peak rate per user is the maximum connection rate in the uplink for a user. The DL and UL peak rates are taken into account during power control simulation. Max DL Load (% Pmax): The percentage of the maximum downlink power (set in Max Power) not to be exceeded. This limit will be taken into account during the simulation if the option DL Load is selected. If the DL load option is not selected during a simulation, this value is not taken into consideration. Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit can be taken into account during the simulation. Total Power (dBm or %): The total transmitted power on downlink is the total power necessary to serve R99 and HSDPA users. This value can be a simulation result or can be entered by the user. By default, the total power is set as an absolute value. You can set this value as a percentage of the maximum power of the cell by right-clicking the UMTS Network Settings folder in the Parameters explorer 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.
•
•
634
UL Load Factor (%): The uplink cell load factor. This factor corresponds to the ratio between the uplink total interference and the uplink total noise. The uplink cell load factor is a global value and includes the inter-technology uplink interference. This value can be a simulation result or can be entered by the user. UL Reuse Factor: The uplink reuse factor is determined from uplink intra and extra-cell interference (signals received by the transmitter respectively from intra and extra-cell terminals). This is the ratio between the total uplink interference and the intra-cell interference. This value can be a simulation result or can be entered by the user.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
• • • • • • • • •
•
•
Scrambling Code Domain: The scrambling code domain to which the allocated scrambling code belongs. This and the scrambling code reuse distance are used by the scrambling code planning algorithm. SC Reuse Distance: The scrambling code reuse distance. This and the scrambling code domain are used by the scrambling code planning algorithm. Primary Scrambling Code: The primary scrambling code. SC Locked: The status of the primary scrambling code allocated to the cell. If the SC Locked check box is checked, the automatic allocation tool considers that the current primary scrambling code is not modifiable. Comments: If desired, you can enter any comments in this field. Max Number of Intra-carrier Neighbours: The maximum number of intra-carrier neighbours for this cell. This value is used by the intra-carrier neighbour allocation algorithm. Max Number of Inter-carrier Neighbours: The maximum number of inter-carrier neighbours for this cell. This value is used by the inter-carrier neighbour allocation algorithm. Max Number of Inter-technology Neighbours: The maximum number of inter-technology neighbours for this cell. This value is used by the inter-technology neighbour allocation algorithm. Inter-technology UL Noise Rise: This noise rise represents the interference on this cell on the uplink created by the mobiles and base stations of an external network. This noise rise will be taken into account in uplink interferencebased calculations involving this cell in the simulation. It is not used in predictions (AS Analysis and coverage predictions). In predictions, Atoll calculates the uplink total interference from the UL load factor which includes inter-technology uplink interference. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 806. 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. Neighbours: You can access a dialogue in which you can set both intra-technology (intra-carrier and inter-carrier) and inter-technology neighbours by clicking the Browse button ( ning Neighbours" on page 705.
). For information on defining neighbours, see "Plan-
The Browse button ( ) might not be visible in the Neighbours box if this is a new cell. You can make the Browse button appear by clicking Apply.
•
HSPA Support: The HSPA functionality supported by the cell. You can choose between None (i.e., R99 only), HSDPA, HSPA (i.e., HSDPA and HSUPA) or HSPA+. When HSDPA is supported, the following fields are available: •
HSDPA Dynamic Power Allocation: If you are modelling dynamic power allocation, the HSDPA Dynamic Power Allocation should be checked. During a simulation, Atoll first allocates power to R99 users and then dynamically allocates the remaining power of the cell to the HS-PDSCH and HS-SCCH of HSDPA users. At the end of the simulation, you can commit the calculated available HSDPA power and total power values to each cell. In the context of dynamic power allocation, the total power cannot exceed the maximum power minus the power headroom.
•
•
•
•
•
Available HSDPA Power (dBm): When you are modelling static power allocation, the HSDPA Dynamic Power Allocation check box is cleared and the available HSDPA power is entered in this box. This is the power available for the HS-PDSCH and HS-SCCH of HSDPA users. Power Headroom (dB): The power headroom is a reserve of power that Atoll keeps for Dedicated Physical Channels (DPCH) in case of fast fading. During simulation, HSDPA users will not be connected if the cell power remaining after serving R99 users is less than the power headroom value. HS-SCCH Dynamic Power Allocation: If you are modelling dynamic power allocation the HS-SCCH Dynamic Power Allocation check box should be checked and a value should be entered in HS-SCCH Power (dBm). During power control, Atoll will control HS-SCCH power in order to meet the minimum quality threshold (as defined for each mobility type). The value entered in HS-SCCH Power (dBm) is the maximum power available for each HS-SCCH channel. The calculated power for each HSDPA user during the simulation cannot exceed this maximum value. HS-SCCH Power (dBm): The value for each HS-SCCH channel will be used if you are modelling dynamic power allocation. If you have selected the HS-SCCH Dynamic Power Allocation check box and modelling dynamic power allocation, the value entered here represents a maximum for each HSDPA user. If you have not selected the HS-SCCH Dynamic Power Allocation check box and are modelling static power allocation, the value entered here represents the actual HS-SCCH power per HS-SCCH channel. Number of HS-SCCH Channels: The maximum number of HS-SCCH channels for this cell. Each Packet (HSDPA Best Effort), Packet (HSDPA - Variable Bit Rate), Packet (HSPA - Best Effort), and Packet (HSPA - Variable Bit Rate)
635
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
user consumes one HS-SCCH channel. Therefore, at any given time (over a time transmission interval), the number of HSDPA bearer users cannot exceed the number of HS-SCCH channels per cell. HS-DSCH transmissions without an accompanying HS-SCCH are performed for Packet (HSPA - Constant Bit Rate) users. Therefore, the number of HS-SCCH channels is not taken into account when managing the number of Packet (HSPA - Constant Bit Rate) users connected at a given time. • • •
•
•
Min. Number of HS-PDSCH Codes: The minimum number of OVSF codes available for HS-PDSCH channels. This value will be taken into account during simulations in order to find a suitable bearer. Max Number of HS-PDSCH codes: The maximum number of OVSF codes available for HS-PDSCH channels. This value will be taken into account during simulations and coverage predictions in order to find a suitable bearer. Max Number of HSDPA Users: The maximum number of HSDPA bearer users [i.e., Packet (HSDPA - Best Effort) users, Packet (HSDPA - Variable Bit Rate) users, Packet (HSPA - Best Effort) users, Packet (HSPA - Variable Bit Rate) users, and Packet (HSPA - Constant Bit Rate) users] that this cell can support at any given time. Number of HSDPA Users: The number of HSDPA bearer users is an average and can be used for certain coverage predictions. You can enter this value yourself, or have the value calculated by Atoll using a simulation. Dual-cell HSDPA users are counted once in each cell they are connected to. HSDPA Scheduler Algorithm: The scheduling technique that will be used to rank the HSDPA users to be served: • Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by the channel quality indicator (CQI). • Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order). • Proportional Fair: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order according to a random parameter which corresponds to a combination of the user rank in the simulation and the channel quality indicator (CQI). The random parameter is calculated by giving both the user simulation rank and the CQI a weight of 50%. You can change the default weights by setting the appropriate options in the atoll.ini file. For more information, see the Administrator Manual.
•
MUG Table = f(No. Users): You can access the MUG (Multi-User Gain) table by clicking the Browse button ( ). The MUG table is a graph of throughput gain as a function of the number of users. The average cell throughput is higher with multiple users than with a single user. The MUG graph is only available if you have set the peak HSDPA throughput option in the atoll.ini file. For more information, see the Administrator Manual.
•
MIMO Support: The MIMO method used by the cell when it supports HSPA+. You can choose between None, Transmit Diversity, or Spatial Multiplexing.
In transmitters that support multi-cell HSDPA, the multi-cell HSDPA scheduler algorithm and MUG graph are used in calculations instead of the HSDPA scheduler algorithms and MUG graphs set per cell. When HSUPA is supported, the following fields are also available: • •
• •
DL HSUPA Power: The power (in dBm) allocated to HSUPA DL channels (E-AGCH, E-RGCH, and E-HICH). This value must be entered by the user. Max Number of HSUPA Users: The maximum number of HSUPA bearer users (i.e., Packet (HSPA - Best Effort) users, Packet (HSPA - Variable Bit Rate) users and Packet (HSPA - Constant Bit Rate) users) that this cell can support at any given time. UL Load Factor Due to HSUPA (%): The uplink cell load contribution due to HSUPA. This value can be a simulation result or can be entered by the user. Number of HSUPA Users: The number of HSUPA bearer users is an average and can be used for certain coverage predictions. This value can be a simulation result or can be entered by the user. By default, the SCH power, the CCH power, the HS-SCCH power and the HSUPA power are set as absolute values. You can set these values as relative to the pilot power by right-clicking the UMTS Network Settings folder in the Parameters explorer and selecting Properties from the context menu. Then, on the Global Parameters tab of the Properties dialogue, under DL Powers, you can select Relative to Pilot. The SCH power, the CCH power, the HSSCCH power, and the HSUPA power values are automatically converted and set as relative to the pilot power.
636
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9.2.1.2 Creating or Modifying a Base Station Element A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: • • •
9.2.1.2.1
"Creating or Modifying a Site" on page 637 "Creating or Modifying a Transmitter" on page 637 "Creating or Modifying a Cell" on page 638.
Creating or Modifying a Site You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 630, through the site’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create a new site: 1. Select the Network explorer. 2. Right-click the Sites folder. The context menu appears. 3. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 9.3 on page 630). 4. Modify the parameters described in "Site Description" on page 630. 5. Click OK. To modify the properties of an existing site: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Sites folder.
3. Right-click the site you want to modify. The context menu appears. 4. Select Properties from the context menu. The site’s Properties dialogue appears. 5. Modify the parameters described in "Site Description" on page 630. 6. Click OK. If you are creating several sites at the same time, or modifying several existing sites, you can do it quickly by editing or pasting the data directly in the Sites table. You can open the Sites table by right-clicking the Sites folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
9.2.1.2.2
Creating or Modifying a Transmitter You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio Planning toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 630, through the transmitter’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create a new transmitter: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 9.4). 4. Modify the parameters described in "Transmitter Description" on page 630. 5. Click OK. When you create a new transmitter, Atoll automatically creates a cell based on the default station template. For information on creating a cell, see "Creating or Modifying a Cell" on page 638. To modify the properties of an existing transmitter: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Transmitters folder.
3. Right-click the transmitter you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Modify the parameters described in "Transmitter Description" on page 630.
637
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
6. Click OK. •
•
9.2.1.2.3
If you are creating several transmitters at the same time, or modifying several existing transmitters, you can do it more quickly by editing or pasting the data directly in the Transmitters table. You can open the Transmitters table by rightclicking the Transmitters folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77. If you want to add a transmitter to an existing site on the map, you can add the transmitter by right-clicking the site and selecting New Transmitter from the context menu.
Creating or Modifying a Cell You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Definition" on page 633, through the Properties dialogue of the transmitter where the cell is located. To create or modify a cell: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Transmitters folder.
3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Definition" on page 633. 7. Click OK. •
•
If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder in the Network explorer and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 77), or import data into the table (see "Importing Tables from Text Files" on page 82). If you want to add a cell to an existing transmitter on the map, you can add the cell by right-clicking the transmitter and selecting New Cell from the context menu.
9.2.1.3 Placing a New Station Using a Station Template In Atoll, a station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template: 1. In the Radio Planning toolbar, select a template from the list.
2. Click the New Transmitter or Station button (
638
) in the Radio Planning toolbar.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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 pointer’s current location are visible in the Status bar.
4. Click to place the station.
•
•
To place the station more accurately, you can zoom in on the map before you click the New Station button. For information on using the zooming tools, see "Changing the Map Scale" on page 49. If you let the pointer rest over the station you have placed, Atoll displays its tip text with its exact coordinates, allowing you to verify that the location is correct.
You can also place a series of stations using a Atoll template. You do this by defining an area on the map where you want to place the stations. Atoll calculates the placement of each station according to the defined hexagonal cell radius in the station template. For information on defining the cell radius, see "Creating a Station Template" on page 640. To place a series of stations within a defined area: 1. In the Radio Planning 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.
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. You can work with the sites and transmitters in these stations as you work with any station object, adding, for example, another antenna to a transmitter. Placing a Station on an Existing Site When you place a new station using a station template as explained in "Placing a New Station Using a Station Template" on page 638, the site is created at the same time as the station. However, you can also place a new station on an existing site. To place a station on an existing site: 1. In the Network explorer, clear the display check box beside the Hexagonal Design folder. 2. In the Radio Planning toolbar, select a template from the list. 3. Click the New Station button (
) in the Radio Planning 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.
9.2.1.4 Managing Station Templates Atoll comes with UMTS station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio Planning toolbar (see Figure 9.6).
Figure 9.6: The Radio Planning toolbar In this section, the following are explained: • • •
"Creating a Station Template" on page 640 "Modifying a Station Template" on page 640 "Copying Properties from One Station Template to Another" on page 645
639
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• •
9.2.1.4.1
© Forsk 2012
"Modifying a Field in a Station Template" on page 645 "Deleting a Station Template" on page 645.
Creating a Station Template When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. To create a station template: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the Station Templates table, right-click the station template that most closely resembles the station template you want to create. The context menu appears. 6. Select Copy from the context menu. 7. Right-click the row marked with the New Row icon (
). The context menu appears.
8. Select Paste from the context menu. The station template you copied in step 5. is pasted in the new row, with the Name of the new station template given as the same as the template copied but preceded by "Copy of". 9. Edit the parameters of the new station template in the table or as explained in "Modifying a Station Template" on page 640.
9.2.1.4.2
Modifying a Station Template You can modify a station template directly in the Station Templates table, or you can open the Properties dialogue for that station template and modify the parameters in the dialogue. To modify a station template: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. Right-click the station template you want to modify. The context menu appears. 6. Select Record Properties from the context menu. The station template’s Properties dialogue appears. 7. Click the General tab of the Properties dialogue. On this tab (see Figure 9.7), you can modify the following: the Name of the station template, the number of Sectors, each with a transmitter, and the Hexagon Radius, i.e., the theoretical radius of the hexagonal area covered by each sector.
640
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Figure 9.7: Station Template Properties dialogue – General tab •
Under Main Antenna, you can modify the following: the Height/Ground of the antennas from the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of building), the main antenna Model, 1st Sector Azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Mechanical Downtilt, and the Additional Electrical Downtilt for the antenna. • •
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide.
•
Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
•
Under Comments, you can add additional information. The information you enter will be the default information in the Comments field of any transmitter created using this station template.
8. Click the Transmitter tab. On this tab (see Figure 9.8), if the Active check box is selected, you can modify the following: •
Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifications dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or transmitter equipment. For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 630.
•
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.5 on page 632). Any loss related to the noise due to a transmitter’s repeater is included in the calculated losses. Atoll always considers the values in the Real boxes in predictions even if they are different from the values in the Computed boxes. You can modify the real Total Losses at transmission and reception if you want. Any value you enter must be positive.
•
The information in the real Noise Figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Noise Figure at reception if you want. Any value you enter must be positive.
•
Under Diversity, you can select the number of transmission and reception antenna ports used for MIMO (No. of ports). MIMO systems are supported by some HSDPA bearers (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+). For more information on how the number of antenna ports are used, see "Multiple Input Multiple Output Systems" on page 804. R99 bearers only support transmit and receive diversities. You can define the transmit diversity method from the Transmission list when more than one transmission antenna port is available. The receive diversity method de-
641
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
pends on the number of reception antenna ports selected (2RX for two reception antenna ports and 4RX for four reception antenna ports).
Figure 9.8: Station Template Properties dialogue – Transmitter tab 9. Click the W-CDMA/UMTS tab. On this tab (see Figure 9.9), you modify the Carriers (each corresponding to a cell) that this station supports. For information on carriers and cells, see "Cell Definition" on page 633. •
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.
642
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Figure 9.9: Station Template Properties dialogue – W-CDMA/UMTS tab • • • • •
•
Under Primary Scrambling Code, you can modify the Reuse Distance and the scrambling code Domain. Under Power, you can select the Power Shared Between Cells check box. As well, you can modify the Pilot, the SCH, the Other CCH powers, and the AS Threshold. Under Simulation Constraints, you can modify the Max Power, the Max DL Load (defined as a percentage of the maximum power), the DL Peak Rate/User, the Max UL Load Factor, and the UL Peak Rate/User. Under Load Conditions, you can modify the Total Transmitted Power, the UL Load Factor, and the UL Reuse Factor. Under Inter-technology Interferences, you can modify the UL and DL noise rise which respectively model the effect of terminals and stations of an external network on the network cells and the effect of terminals of an external network interfering the mobiles served by the network cells. For more information on inter-technology interferences, See "Modelling Inter-technology Interference" on page 806. You can also modify the Number of Uplink and Downlink Channel Elements, the Max Iub Uplink and Downlink Backhaul Throughputs and select the Equipment.
10. Click the HSPA/HSPA+ tab. On this tab (see Figure 9.10), you can define the HSPA functionality supported by the cells. You can choose between None (i.e., R99 only), HSDPA, HSPA (i.e, HSDPA and HSUPA), HSPA+ (transmit diversity) or HSPA+ (spatial multiplexing). When HSDPA functionality is supported, you can modify the following under HSDPA (for more information on the fields, see "Cell Definition" on page 633): •
•
You can select the Allocation Strategy (Static or Dynamic). If you select Static as the Allocation Strategy, you can enter the available HSDPA Power. If you select Dynamic as the Allocation Strategy, Atoll allocates the HSDPA power to cells during the simulation. Atoll first allocates power to R99 users and then dynamically allocates the remaining power of the cell to the HS-PDSCH and HS-SCCH of HSDPA users. At the end of the simulation, you can commit the calculated available HSDPA power and total power values to each cell. Under Multi-cell, you can modify the multi-cell HSDPA Mode, select a multi-cell HSDPA scheduler Algorithm, and enter a MUG=f(No. Users) graph. Multi-cell HSDPA options are available if the dual-cell HSDPA option has been activated. The MUG graph is only available if you have set the peak HSDPA throughput option in the atoll.ini file. For more information, see the Administrator Manual.
643
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• • •
© Forsk 2012
Under HS-PDSCH, you can modify the Min. and Max Number of Codes and the Power Headroom. Under HS-SCCH, you can select the Allocation Strategy (Static or Dynamic) and the Number of Channels. If you select Static as the Allocation Strategy, you can enter the HS-SCCH Power. Under Scheduler, you can modify the Algorithm, the Max Number of Users, the Number of Users, and you can enter a MUG=f(No. Users) graph. The MUG graph is only available if you have set the peak HSDPA throughput option in the atoll.ini file. For more information, see the Administrator Manual.
Under HSUPA, if HSUPA functionality is supported, you can modify the following (for more information on the fields, see "Cell Definition" on page 633): •
You can modify the DL Power, the UL Load, the Max Number of Users, and the Number of Users.
Figure 9.10: Station Template Properties dialogue – HSDPA tab 11. Click the Neighbours tab. In this tab (see Figure 9.11), you can modify the Max Number of Intra- and Inter-Carrier Neighbours and the Max Number of Inter-technology Neighbours. For information on defining neighbours, see "Planning Neighbours" on page 705.
Figure 9.11: Station Template Properties dialogue – Neighbours tab 12. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Sites table, or if you have defined an additional field in the Station Template Properties dialogue. 13. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.
644
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9.2.1.4.3
Copying Properties from One Station Template to Another You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the Stations Templates table, copy the settings in the row corresponding to the station template you want to copy from and paste them into the row corresponding to the station template you want to modify.
9.2.1.4.4
Modifying a Field in a Station Template To modify a field in a station template: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Right-click the Station Templates folder. The context menu appears. 4. Select Properties from the context menu. The Station Template Properties dialogue appears. 5. Select the Table tab. 6. On the Table tab, you have the following options: •
Add: If you want to add a user-defined field to the station templates, you must have already added it to the Sites table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Type’s Data Table" on page 71) for it to appear as an option in the station template properties. To add a new field: i.
Click the Add button. The Field Definition dialogue appears.
ii. Enter a Name for the new field. This is the name that will be used in database. iii. If desired, you can define a Group that this custom field will belong to. When you open an Atoll document from a database, you can then select a specific group of custom fields to be loaded from the database, instead of loading all custom fields. iv. In Legend, enter the name for the field that will appear in the Atoll document. v. For Type, you can select from Text, Short integer, Long integer, Single, Double, True/False, Date/Time, and Currency. If you choose text, you can also set the field Size (in characters), and create a Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER after each one. vi. Enter, if desired, a Default value for the new field. vii. Click OK to close the Field Definition dialogue and save your changes. •
Delete: To delete a user-defined field: i.
Select the user-defined field you want to delete.
ii. Click the Delete button. The user-defined field appears in strikeout. It will be definitively deleted when you close the dialogue. •
Properties: To modify the properties of a user-defined field: i.
Select the user-defined field you want to modify.
ii. Click the Properties button. The Field Definition dialogue appears. iii. Modify any of the properties as desired. iv. Click OK to close the Field Definition dialogue and save your changes. 7. Click OK.
9.2.1.4.5
Deleting a Station Template To delete a station template: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Station Templates folder.
4. In the Station Templates folder, right-click the station template you want to delete. The context menu appears. 5. Select Delete from the context menu. The template is deleted.
645
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
9.2.1.5 Duplicating an Existing Base Station You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same transmitter, and cell parameter values as the original base station. If no site exists where you place the duplicated base station, Atoll will create a new site with the same parameters as the site of the original base station. Duplicating a base station allows you to: • •
Quickly create a new base station with the same settings as the original base station in order to study the effect of a new base station on the coverage and capacity of the network, and Quickly create a homogeneous network with stations that have the same characteristics.
To duplicate an existing base station: 1. Select the Network explorer. 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 > Without Neighbours from the context menu, if you want to duplicate the base station without the intra- and inter-technology neighbours of its transmitters. Select Duplicate > With Outward Neighbours from the context menu, if you want to duplicate the base station along with the lists of intra- and inter-technology neighbours of its transmitters.
5. Place the new base station on the map using the mouse: •
Creating a duplicate base station and site: In the map window, move the pointer over the map to where you would like to place the duplicate. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 9.12).
Figure 9.12: Creating a duplicate base station and site •
Placing the duplicate base station on an existing site: In the map window, move the pointer over the existing site where you would like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 9.13).
Figure 9.13: Placing the duplicate base station on an existing site •
•
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 49. 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. If the duplicate base station was placed on a new site, the site, transmitters, and cells of the new base station have the same names as the site, transmitters, and cells of the original base station with each name marked as "Copy of." The site, transmitters, and cells of the duplicate base station have the same settings as those of the original base station. If the duplicate base station was placed on an existing site, the transmitters, and cells of the new base station have the same names as the transmitters, and cells of the original base station with each name preceded by the name of the site on which the duplicate was placed. All the remote antennas and repeaters of any transmitter on the original site are also duplicated.
646
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Any duplicated remote antennas and repeaters will retain the same donor transmitter as the original. If you want the duplicated remote antenna or repeater to use a transmitter on the duplicated base station, you must change the donor transmitter manually. You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each duplicate base station. For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 629.
9.2.2 Creating a Group of Base Stations You can create base stations individually as explained in "Creating a UMTS Base Station" on page 629, or you can create one or several base stations by using station templates as explained in "Placing a New Station Using a Station Template" on page 638. However, if you have a large data-planning project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations. When you import data into your current Atoll document, the coordinate system of the imported data must be the same as the display coordinate system used in the document. If you cannot change the coordinate system of your source data, you can temporarily change the display coordinate system of the Atoll document to match the source data. For information on changing the coordinate system, see "Setting a Coordinate System" on page 121. You can import base station data in the following ways: •
Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. The table you copy data from must have the same column layout as the table you are pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77. •
Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80. For information on importing table data, see "Importing Tables from Text Files" on page 82. You can quickly create a series of base stations for study purposes using the Hexagonal Design tool on the Radio Planning toolbar. For information, see "Placing a New Station Using a Station Template" on page 638.
9.2.3 Modifying Sites and Transmitters Directly on the Map In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu in the Network explorer. However, in a complex radio-planning project, it can be difficult to find the data object in the Network explorer, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. You can also select a site to display all of the transmitters located on it in the Site Configuration window. When selecting a transmitter, if there there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: • •
"Working with the Site Configuration Window" on page 37 "Selecting One of Several Transmitters" on page 41
647
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• • • •
© Forsk 2012
"Moving a Site Using the Mouse" on page 41 "Moving a Site to a Higher Location" on page 42 "Changing the Azimuth of the Antenna Using the Mouse" on page 42 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42.
9.2.4 Display Tips for Base Stations Atoll allows to you to display information about base stations in a number of different ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations: •
•
•
•
Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object type’s data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information will lead to a cluttered display. For information on defining the label, see "Defining the Object Type Label" on page 46. Tip text: You can display information about each object, such as each site or transmitter, in the form of tip text that is only visible when you move the pointer over the object. You can choose to display more information than in the label, because the information is only displayed when you move the pointer over the object. You can display information from any field in that object type’s data table, including from fields that you add. For information on defining the tip text, see "Defining the Object Type Tip Text" on page 46. Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example, you can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active sites. You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns a colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding it. For information on defining the transmitter colour, see "Defining the Display Type" on page 44. Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can select a symbol that graphically represents the antenna half-power beamwidth (
). If you have two transmitters on the
same site with the same azimuth, you can differentiate them by selecting different symbols for each ( For information on defining the transmitter symbol, see "Defining the Display Type" on page 44.
and
).
9.2.5 Creating a Dual-Band UMTS Network In Atoll, you can model a dual-band UMTS network, i.e., a network consisting of 2100 MHz and 900 MHz transmitters, in one document. Creating a dual-band UMTS network consists of the following steps: 1. Defining the two frequency bands in the document (see "Defining Frequency Bands" on page 796). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Working with Calculations in Atoll). 3. Assigning a frequency band, with its propagation model, to each transmitter (see "Transmitter Description" on page 630). 4. Defining the frequency bands with which terminals are compatible (see "Modelling UMTS HSPA Terminals" on page 685).
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 a radio link or a microwave link. The server side re-transmits the received signal. Atoll models RF repeaters and microwave repeaters. The modelling focuses on: • •
The additional coverage these systems provide to transmitters in the downlink. The UL total gain value in service areas predictions (effective service area and UL Eb/Nt service area) and the noise rise generated at the donor transmitter by the repeater.
In this section, the following are explained: • • • • • •
648
"Opening the Repeaters Table" on page 649 "Creating and Modifying Repeater Equipment" on page 649 "Placing a Repeater on the Map Using the Mouse" on page 649 "Creating Several Repeaters" on page 650 "Defining the Properties of a Repeater" on page 650 "Tips for Updating Repeater Parameters" on page 652.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor transmitter are amplified.
9.2.6.1 Opening the Repeaters Table Repeaters and their defining parameters are stored in the Repeaters table. To open the Repeaters table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Repeaters > Open Table from the context menu. The Repeaters table appears.
9.2.6.2 Creating and Modifying Repeater Equipment You can define repeater equipment to be assigned to each repeater in the network. To create repeater equipment: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the Radio Network Equipment folder.
3. In the Radio Network Equipment folder, right-click Repeater Equipment. The context menu appears. 4. Select Open Table from the context menu. The Repeater Equipment table appears. 5. Enter the following in the row marked with the New Row icon (
):
a. Enter a Name and Manufacturer for the new equipment. b. Enter a Noise Figure (dB). The repeater causes a rise in noise at the donor transmitter, so the noise figure is used to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive value. c. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if there are any. d. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier gain using the buttons to the right of the Amplification gain box ( dialogue.
) on the General tab of the repeater Properties
e. Enter the maximum power that the equipment can transmit on the downlink in the Max Downlink Power column. This parameter enables Atoll to ensure that the downlink power after amplification does not exceed the limit of the equipment. f.
If desired, enter a Max Uplink Power, an Internal Delay and Comments. These fields are for information only and are not used in calculations.
To modify repeater equipment: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the Radio Network Equipment folder.
3. In the Radio Network Equipment folder, right-click Repeater Equipment. The context menu appears. 4. Select Open Table from the context menu. The Repeater Equipment table appears. 5. Change the parameters in the row containing the repeater equipment you want to modify.
9.2.6.3 Placing a Repeater on the Map Using the Mouse In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site, or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater or of a remote antenna. To create a repeater and place it using the mouse: 1. Select the donor transmitter, repeater, or remote antenna. You can select it from the Transmitters folder in the Network explorer, or directly on the map. 2. Click the arrow next to New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
3. Select Repeater from the menu.
649
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty icon. By default, the repeater has the same azimuth as the donor. Its tip text and label display the same information as displayed for the donor. As well, its tip text identifies the repeater and the donor. In the explorer window, the repeater is found in the Transmitters folder of the Network explorer under its donor transmitter, repeater, or remote antenna. For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on page 650. •
•
When the donor is a transmitter, you can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. You can hide the link by clicking it again. When the donor is a repeater or a remote antenna, Atoll displays a spider-type link showing the entire chain down to the donor transmitter. The same spider-type link is displayed when you click any of the items belonging to the chain is clicked (i.e., donor transmitter, any repeater, or any remote antenna).
9.2.6.4 Creating Several Repeaters In Atoll, the characteristics of each repeater are stored in the Repeaters table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document. To paste the information into the Repeaters table: 1. Open the Repeaters table as explained in "Opening the Repeaters Table" on page 649. 2. Copy the data from the source document and paste it into the Repeaters table. 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 77.
9.2.6.5 Defining the Properties of a Repeater To define the properties of a repeater: 1. Right-click the repeater either directly on the map, or in the Repeaters table (for information on opening the Repeaters table, see "Opening the Repeaters Table" on page 649). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
Name: You can change the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created. •
•
•
If the donor is a remote antenna or another repeater, then "RepZ" is preceded by "RemA_" or "RepB_" where "A" and "B" identify the donor remote antenna and the donor repeater. In Multi-RAT documents, a repeater’s name is "SiteX_T_Y_RepZ" where "T" stands for the technology (either GSM, UMTS, or LTE)..
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, a remote antenna, or another repeater. Clicking the Browse button (
• •
650
) opens the Properties dialogue of the selected donor.
You can change the Site on which the repeater is located. Clicking the Browse button ( ) opens the Properties dialogue of the selected site. You can enter a value in the Shared antenna (coverage side) field for the repeater. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
Under Antenna Position, you can define the position of the repeater, if it is not located on the site itself: • •
• •
Relative to Site: Select Relative to Site, if you want to define the position of the repeater relative to the site itself and then enter the XY offsets. Coordinates: Select Coordinates, if you want to define the position of the repeater by its XY coordinates.
You can select equipment from the Equipment list. Clicking the Browse button ( ) opens the Properties 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 Link Losses and proceed to step 5. If you select Air, select a Propagation Model and enter the Propagation Losses or click Calculate to determine the actual propagation losses between the donor and the repeater. If you do not select a propagation model, the propagation losses between the donor transmitter and the repeater are calculated using the ITU 526-5 propagation model. When you create an off-air repeater, it is assumed that the link between the donor transmitter and the repeater has the same frequency as the network. If you want to create a remote antenna, you must select Optical Fibre Link.
•
If you selected Air under Donor-Repeater Link, enter the following information under Antenna: •
Model: The type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. Select a Physical Antenna (a physical antenna can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the repeater. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the repeater.
•
•
Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of the building. Mechanical Azimuth and Mechanical Downtilt display additional antenna parameters. You can click the Calculate button to update the mechanical azimuth and mechanical downtilt values after changing the repeater donor side antenna height or the repeater location. If you choose another site or change site coordinates in the General tab, click Apply before clicking the Calculate button.
•
If you selected Air under Donor-Repeater Link, enter the following information under Feeders: i.
Type: The type of feeder is visible in the Type list. You can click the Browse button ( erties of the feeder.
) to access the prop-
ii. Length: Enter the Length of the feeder cable at Transmission and at Reception. 5. Click the Coverage Side tab. You can modify the following parameters: • •
Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Network explorer) are calculated. Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply before clicking the Calculate button. Atoll uses the DL total gain values to calculate the signal level received from the repeater. The UL total gain value is considered in UL Eb/Nt service area predictions. The DL total gain is applied to each power (pilot power, SCH power, etc.). The UL total gain is applied to each terminal power. The total gains take into account losses between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses), amplification gain, and coverage characteristics (coverage antenna gain and transmission feeder losses).
651
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
•
© Forsk 2012
Under Antennas, you can modify the following parameters: •
•
Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of building. Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the repeater. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas. and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the repeater.
• •
Mechanical 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. • • •
•
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. •
Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.
6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propagation parameters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
9.2.6.6 Tips for Updating Repeater Parameters Atoll provides you with a few shortcuts that you can use to change certain repeater parameters: • •
You can update the calculated azimuth and downtilt of the donor-side antennas of all repeaters by selecting Repeaters > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu. You can update the UL and DL total gains of all repeaters by selecting Repeaters > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected repeaters by creating a custom Boolean field named "FreezeTotalGain" in the Repeaters table and setting the value of the field to "True." Afterwards, when you select Repeaters > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for repeaters with the custom field "FreezeTotalGain" set to "False."
• •
652
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 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9.2.7 Creating a Remote Antenna Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder cable. A remote antenna is connected to the base station with an optical fibre. Remote antennas allow you to ensure radio coverage in an area without a new base station. In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a remote antenna, as opposed to a repeater, does not have any equipment and generates no amplification gain nor noise. In certain cases, you may want to model a remote antenna with equipment or a remote antenna connected to a base station that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a Repeater" on page 648. In this section, the following are explained: • • • • •
"Opening the Remote Antennas Table" on page 653 "Placing a Remote Antenna on the Map Using the Mouse" on page 653 "Creating Several Remote Antennas" on page 654 "Defining the Properties of a Remote Antenna" on page 654 "Tips for Updating Remote Antenna Parameters" on page 655.
9.2.7.1 Opening the Remote Antennas Table The remote antennas and their defining parameters are stored in the Remote Antennas table. To open the Remote Antennas table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Remote Antennas > Open Table from the context menu. The Remote Antennas table appears.
9.2.7.2 Placing a Remote Antenna on the Map Using the Mouse In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it to an existing base station without antennas, or have Atoll automatically create a new site. To create a remote antenna and place it using the mouse: 1. Select the donor transmitter. You can select it from the Transmitters folder in the Network explorer, or directly on the map. Ensure that the remote antenna’s donor transmitter does not have any antennas.
2. Click the arrow next to New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
3. Select Remote Antenna from the menu. 4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its tip text and label display the same information as displayed for the donor transmitter. As well, its tip text identifies the remote antenna and the donor transmitter. For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote Antenna" on page 654. •
•
When the donor is a transmitter, you can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. You can hide the link by clicking it again. When the donor is a repeater or a remote antenna, Atoll displays a spider-type link showing the entire chain down to the donor transmitter. The same spider-type link is displayed when you click any of the items belonging to the chain is clicked (i.e., donor transmitter, any repeater, or any remote antenna).
653
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
9.2.7.3 Creating Several Remote Antennas In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in your current Atoll document. To paste the information into the Remote Antennas table: 1. Open the Remote Antennas table as explained in "Opening the Remote Antennas Table" on page 653. 2. Copy the data from the source document and paste it into the Remote Antennas table. The table you copy data from must have the same column layout as the table you are pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
9.2.7.4 Defining the Properties of a Remote Antenna To define the properties of a remote antenna: 1. Right-click the remote antenna either directly on the map, or in the Remote Antennas table (for information on opening the Remote Antennas table, see "Opening the Remote Antennas Table" on page 653). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
Name: You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RemZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the remote antenna when it was created. •
•
•
If the donor is a repeater or another remote antenna, then "RemZ" is preceded by "RepA_" or "RemB_" where "A" and "B" identify the donor repeater and the donor remote antenna. In Multi-RAT documents, a remote antenna’s name is "SiteX_T_Y_RemZ" where "T" stands for the technology (either GSM, UMTS, or LTE).
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another remote antenna, or a repeater. Clicking the Browse button (
• •
•
) opens the Properties dialogue of the selected donor.
You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens the Properties dialogue of the selected site. You can enter a value in the Shared Antenna (coverage side) field for the remote antenna. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna Position, you can define the position of the remote antenna, if it is not located on the site itself: • •
Relative to Site: Select Relative to Site, if you want to define the position of the remote antenna relative to the site itself and then enter the XY offsets. Coordinates: Select Coordinates, if you want to define the position of the remote antenna by its XY coordinates. A remote antenna does not have equipment.
4. Click the Donor Side tab. You can modify the following parameters: •
Under Donor-Repeater Link, select Optical Fibre Link and enter the Fibre Losses.
5. Click the Coverage Side tab. You can modify the following parameters: •
654
Select the Active check box. Only active remote antennas (displayed in red in the UMTS Transmitters folder in the Network explorer) are calculated.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
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 Eb⁄Nt service area predictions. The DL total gain is applied to each power (pilot power, SCH power, etc.). The UL total gain is applied to each terminal power. The total gains take into account losses between the donor transmitter and the remote antenna.
•
Under Antennas, you can modify the following parameters: •
•
Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the remote antenna is situated on a building, the height entered must include the height of the building. Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the remote antenna. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas. and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the remote antenna.
• •
Mechanical 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. • • •
•
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. 6. Click the Propagation tab. Since remote antennas are taken into account during calculations, you must set propagation parameters, as with transmitters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
9.2.7.5 Tips for Updating Remote Antenna Parameters Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters: •
You can update the UL and DL total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected remote antennas by creating a custom Boolean field named "FreezeTotalGain" in the Remote Antennas table and setting the value of the field to "True." Afterwards, when you select Remote Antennas > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for remote antennas with the custom field "FreezeTotalGain" set to "False."
•
You can select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
655
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
9.2.8 Setting the Working Area of an Atoll Document When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the sites that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of sites covered by a coverage prediction, each with its own advantages: •
Filtering the desired sites You can simplify the selection of sites to be studied by using a filter. You can filter sites according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 107. This enables you to keep only the base stations with the characteristics you want to study. The filtering zone is taken into account whether or not it is visible. For information on filtering, see "Filtering Data" on page 95.
•
Setting a computation zone Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated predictions in order to see the effects of small changes in site configuration, the savings in time is considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc., while the focus zone or hot spot is the area taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 665.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.
9.2.9 Studying a Single Base Station As you create a site, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of sites can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the site you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of sites once you have optimised the settings for each individual site. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Atoll enables you to assign both a main propagation model, with a shorter radius and a higher resolution, and an extended propagation model, with a longer radius and a lower resolution. By using a calculation radius, Atoll limits the scope of calculations to a defined area. By using two matrices, Atoll allows you to calculate high resolution path loss matrices closer to the transmitter, while reducing calculation time by using an extended matrix with a lower resolution. You can assign a propagation model to all transmitters at once, to a group of transmitters, or to a single transmitter. Assigning a propagation model is explained in "Assigning a Propagation Model" on page 663. In this section, the following are explained: • •
"Making a Point Analysis to Study the Profile" on page 656 "Studying Signal Level Coverage" on page 658.
9.2.9.1 Making a Point Analysis to Study the Profile In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a UMTS user. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on each selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 663. To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis button ( pointer changes (
656
) in the Radio Planning toolbar. The Point Analysis window appears and the
) to represent the receiver.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: • • •
Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: • •
Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.
4. Select Profile from the list at the top of the Point Analysis window. The profile analysis appears in the Profile view of the Point Analysis window. The altitude (in metres) is reported on the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some propagation models using a 3 knife-edge Deygout diffraction method, the results might display two additional attenuations peaks. The total attenuation is displayed above the main peak. The results of the analysis are displayed at the top of the Profile view: • • • •
The received signal strength of the selected transmitter The propagation model used The shadowing margin and the indoor loss (if selected) The distance between the transmitter and the receiver.
You can change the following options at the top of the Profile view: • •
Transmitter: Select the transmitter from the list. Carriers: Select the carrier to be analysed.
5. At the top of the Profile view, you can click one of the following buttons: •
: Click the Properties button (
•
: Click the Options button ( • • • •
•
•
) to display the Properties dialogue of the selected transmitter. ) to display the Calculation Options dialogue. You can change the following:
Change the X and Y coordinates to change the current position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select Signal Level, Path loss, or Total losses from the Result Type list. You can select the Indoor Coverage check box to add indoor losses.
: Click the Geographic Profile button ( ) if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate or display signal levels and losses. : Click the Link Budget button (
) to display a dialogue with the link budget.
•
: Click the Report button ( ) to display a text document with details on the displayed profile analysis. Detailed reports are only available for the standard propagation model.
•
: Click the Copy button ( ) to copy the Profile view. You can then paste the contents of the Profile view as a graphic into a graphic editing or word-processing programme.
•
: Click the Print button (
) to print the Profile view.
657
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Figure 9.14: Point Analysis - Profile view
9.2.9.2 Studying Signal Level Coverage As you are building your radio-planning project, you might want to check the coverage of a new base station without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single site. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. You can use the same procedure to study the signal level coverage of several sites by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 89. To study the signal level coverage of a single base station: 1. Select the Network explorer. 2. Right-click the Transmitters folder and select Group by > Site from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated. If you want to study only sites by their status, at this step you could group them by status.
3. Select the propagation parameters to be used in the coverage prediction: 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. For the main propagation model: • •
658
Select a Main Propagation Model Enter a Main Calculation Radius and Main Resolution.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
f.
If desired, for the extended propagation model: • •
Select an Extended Propagation Model Enter an Extended Calculation Radius and Extended Resolution.
g. Close the table. 4. In the Transmitters folder, right-click the group of transmitters you want to study and select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. The Prediction Types dialogue lists the predictions available. They are divided into Standard Predictions, supplied with Atoll, and Customised Predictions. Unless you have already created some customised coverage predictions, the Customised Predictions list will be empty. 5. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 6. You can configure the following parameters in the Properties dialogue: •
General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient:
•
Size of the Coverage Prediction
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
According to the size of the country
Conditions tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel (see Figure 9.15). • • • • •
At the top of the Conditions tab, you can set the signal level range to be considered. In Figure 9.15, a signal level less than or equal to -120 dBm will be considered. Under Server, select "All" to consider signal levels from all servers. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "Best (All Bands)" to have the carrier selected according to the carrier selection method defined for the site equipment. The coverage prediction displays the strength of the received pilot signal.
Figure 9.15: Condition settings for a signal level coverage prediction
659
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
•
© Forsk 2012
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 43. You can create tip text with information about the coverage prediction by clicking the Browse button ( next to the Tip Text box and selecting the fields you want to display in the tip text. You can select the Add to Legend check box to add the displayed value intervals to the legend.
)
If you change the display properties of a coverage prediction after you have calculated it, you may make the coverage prediction invalid. You will then have to recalculate the coverage prediction to obtain valid results. •
Result Export tab: You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219.
7. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the 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 in the Network explorer. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button (
) beside the coverage prediction in the Predictions
), Atoll only calculates unlocked coverage predictions (
).
9.2.10 Studying Base Stations When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Figure 9.16 gives an example of a computation zone. In Figure 9.16, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction.
660
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Figure 9.16: 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.16) 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 661 "Assigning a Propagation Model" on page 663 "The Calculation Process" on page 665 "Creating a Computation Zone" on page 665 "Setting Transmitters or Cells as Active" on page 666 "Signal Level Coverage Predictions" on page 667 "Analysing a Coverage Prediction" on page 671 "UMTS-Specific Predictions" on page 681 "HSDPA Quality and Throughput Analysis" on page 697 "HSUPA Quality and Throughput Analysis" on page 700 "Printing and Exporting Coverage Prediction Results" on page 701.
9.2.10.1 Path Loss Matrices Path loss is caused by objects in the transmitter-receiver path and is calculated by the propagation model. In Atoll, the path loss matrices are needed for all base stations that are active, filtered and whose propagation zone intersects a rectangle containing the computation zone (for an explanation of the computation zone, see "Studying Signal Level Coverage" on page 658) and must be calculated before predictions and simulations can be made. Storing Path Loss Matrices Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. in the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radioplanning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources.
661
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: • • •
One file per transmitter with the extension LOS for its main path loss matrix A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices: 1. Select the Network explorer. 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 Private directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally. Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private directory.
When you save the path loss files externally, the external files are updated as soon as calculations are performed and not only when you save the Atoll document. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it, if you have updated the path loss matrices. •
Shared directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the common path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see The Administrator Manual.
5. Click OK. Checking the Validity of Path Loss Matrices Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. 5. Select one of the following display options: • •
Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix: • • •
662
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.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
• • •
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.
6. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 9.17) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.
Figure 9.17: Path loss matrix statistics
9.2.10.2 Assigning a Propagation Model In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 664, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 664, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 663, this is the propagation model that will be used for all transmitters, except for those to which you will later assign a propagation model either individually or as part of a group. When you assign a propagation model globally, you override any selection you might have already made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 201, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following are explained: • • •
"Assigning a Propagation Model to All Transmitters" on page 663 "Assigning a Propagation Model to a Group of Transmitters" on page 664 "Assigning a Propagation Model to One Transmitter" on page 664.
Assigning a Propagation Model to All Transmitters In Atoll, you can choose a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears.
663
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
4. Click the Propagation tab. 5. Under Main Matrix: • •
Select a Propagation Model Enter a Radius and Resolution.
6. If desired, under Extended Matrix: • •
Select a Propagation Model Enter a Radius and Resolution.
7. Click OK. The selected propagation models will be used for all transmitters. Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 664 will override this entry.
Assigning a Propagation Model to a Group of Transmitters Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters and then assigning the propagation model. To define a main and extended propagation model for a defined group of transmitters: 1. Select the Network explorer. 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. You can group transmitters by several properties by using the Group By button on the Properties dialogue. For more information, see "Advanced Grouping" on page 90.
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)
To enter the same values in one column for all transmitters in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69. Assigning a Propagation Model to One Transmitter If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters.
664
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Transmitters folder.
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main Matrix: • •
Select a Propagation Model Enter a Radius and Resolution.
7. If desired, under Extended Matrix: • •
Select a Propagation Model Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter.
9.2.10.3 The Calculation Process When you create a coverage prediction and click the Calculate button (
), Atoll follows the following process:
1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button (
).
3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( Predictions folder. •
You can stop any calculations in progress by clicking the Stop Calculations button (
•
) beside the coverage prediction in the
) in the toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.
9.2.10.4 Creating a Computation Zone To create a computation zone: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Zones folder.
3. Right-click the Computation Zone. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the zone.
ii. Click once on the map to define each point on the map where the border of the zone changes direction. iii. Click twice to finish drawing and close the zone. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the computation zone.
ii. Drag to the opposite corner of the rectangle that will define the computation zone. When you release the mouse, the computation zone will be created from the rectangle defined by the two corners. The computation zone is delimited by a red line. If you clear the computation zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account.
665
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
You can also create a computation zone as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the 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. You can also combine an existing computation zone with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Computation Zone from the context menu. 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 in the Geo explorer and selecting Import from the context menu. Fit Zone to Map Window: You can create a computation zone the size of the map window by selecting Fit Zone to Map Window from the context menu. You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the computation zone in the user configuration: For information on saving the computation zone in the user configuration, see "Saving a User Configuration" on page 101. Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone in the Geo explorer and selecting Export from the context menu.
9.2.10.5 Setting Transmitters or Cells as Active When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Before you define a coverage prediction, you must ensure that all the transmitters on the sites you want to study have been activated. In the explorer window, active transmitters are indicated with a red icon (
) in the Transmitters folder and with the defined
colour on the map and inactive transmitters are indicated with an empty icon (
)in the Transmitters folder and on the map.
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 zone’s context menu. To set an individual transmitter as active: 1. Select the Network explorer. 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. Select the Network explorer. 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 rightclick the group of transmitters you want to set as active. The context menu appears.
3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one transmitter as active using the Transmitters table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table. The Transmitters table appears with each transmitter’s 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. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cell’s parameters in a row.
666
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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. Select the Geo explorer. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder. 3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 54.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Working with Calculations in Atoll. Calculating path loss matrices can be extremely time and resource intensive when you are working on larger projects. Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the Atoll computing server application on other workstations or on servers. Once the computing server application is installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on the network. For information on distributed calculations, see the Administrator Manual.
9.2.10.6 Signal Level Coverage Predictions Atoll offers a series of standard coverage predictions that are common to all radio technologies. Coverage predictions specific to UMTS are covered in "UMTS-Specific Predictions" on page 681, "HSDPA Quality and Throughput Analysis" on page 697, and "HSUPA Quality and Throughput Analysis" on page 700. Once you have created and calculated a coverage prediction, you can use the coverage prediction’s context menu to make the coverage prediction into a customised prediction which will appear in the Prediction Types dialogue. You can also select Duplicate from the coverage prediction’s context menu to create a copy. By duplicating an existing prediction that has the parameters you want to study, you can create a new coverage prediction more quickly than by creating a new coverage prediction. If you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the coverage prediction with the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the calculated coverage prediction. You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to load it into a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predictions are saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations, see "Saving a User Configuration" on page 101. The following standard coverage predictions are explained in this section: • • •
9.2.10.6.1
"Making a Coverage Prediction by Signal Level" on page 667 "Making a Coverage Prediction by Transmitter" on page 669 "Making a Coverage Prediction on Overlapping Zones" on page 670.
Making a Coverage Prediction by Signal Level A coverage prediction by signal level allows you to predict the best signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by signal level: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 9.18). On the Conditions tab, you can define the signals that will be considered for each pixel.
667
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
•
© Forsk 2012
• •
At the top of the Conditions tab, you can set the range of signal level to be considered. In Figure 9.18, a signal level less than or equal to -120 dBm will be considered. Under Server, select "All" to consider all servers. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability.
•
You can select the Indoor Coverage check box to add indoor losses.
•
You can select the Carrier to be studied, or select "Best (All Bands)" to have the carrier selected according to the carrier selection method defined for the site equipment. The coverage prediction displays the strength of the received pilot signal.
Figure 9.18: Condition settings for a coverage prediction by signal level 7. Click the Display tab. 8. Under Display Type, select "Value Intervals." Under Field, select "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 43. 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. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately.. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 9.19).
668
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Figure 9.19: Coverage prediction by signal level You can run a specific prediction study displaying a coverage by pilot signal level for a given terminal, service, mobility and carrier as explained in "Making a Pilot Signal Quality Prediction" on page 687.
9.2.10.6.2
Making a Coverage Prediction by Transmitter A coverage prediction by transmitter allows the user to predict which server is the best at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by transmitter: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Transmitter and click OK. The Coverage by Transmitter Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 9.20). On the Conditions tab, you can define the signals that will be considered for each pixel. •
At the top of the Conditions tab, you can set the range of signal level to be considered. In Figure 9.20, 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 "Best (All bands)" to have the carrier selected according to the carrier selection method defined for the site equipment.
669
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Figure 9.20: 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. You can also predict which server is the second best server on each pixel by selecting "Second best signal level" on the Conditions tab setting "Discrete Values" as the Display Type and "Transmitter" as the Field on the Display tab.
9.2.10.6.3
Making a Coverage Prediction on Overlapping Zones Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction of overlapping zones on the signal level, path loss, or total losses within a defined range. To make a coverage prediction on overlapping zones: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 9.21). On the Conditions tab, you can define the signals that will be considered for each pixel. •
670
At the top of the Conditions tab, you can set the range of signal level to be considered. In Figure 9.21, a signal level less than or equal to -120 dBm will be considered.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
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 "Best (All bands)" to have the carrier selected according to the carrier selection method defined for the site equipment. The coverage prediction displays the strength of the received pilot signal.
Figure 9.21: 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 43. When creating a coverage prediction displaying the number of servers, you can not export the values per pixel.
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. By changing the parameters selected on the Conditions tab and by selecting different results to be displayed on the Display tab, you can calculate and display information other than that which has been explained in the preceding sections.
9.2.10.7 Analysing a Coverage Prediction Once you have completed a prediction, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 658). If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38.
671
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
In this section, the following tools are explained: • • • • • •
9.2.10.7.1
"Displaying the Legend Window" on page 672 "Displaying Coverage Prediction Results Using Tip Text" on page 672 "Using the Point Analysis Reception View" on page 672 "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 673 "Viewing Coverage Prediction Statistics" on page 676 "Comparing Coverage Predictions: Examples" on page 677.
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: •
9.2.10.7.2
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction identified by the name of the coverage prediction.
Displaying Coverage Prediction Results Using Tip Text You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 658). To get coverage prediction results in the form of tip text: •
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined in the Display tab of the coverage prediction properties (see Figure 9.22).
Figure 9.22: Displaying coverage prediction results using the tip text
9.2.10.7.3
Using the Point Analysis Reception View Once you have calculated the coverage prediction, you can use the Point Analysis tool. 1. Click the Point Analysis button ( pointer changes (
) in the Radio Planning toolbar. The Point Analysis window appears and the
) to represent the receiver.
2. At the top of the Point Analysis window, select the Reception view (see Figure 9.23). The predicted signal level from different transmitters is reported in the Reception view in the form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed in the map window. The best server of the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer location is displayed in the tip text. 3. At the top of the Reception view, select the carrier to be analysed.
672
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Figure 9.23: Point Analysis - Reception view 4. At the top of the Reception view, you can click one of the following buttons: •
: Click the Options button ( • • •
•
) to display the Calculation Options dialogue. You can change the following:
Change the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses.
: Click the Copy button ( ) to copy the Reception view. You can then paste the contents of the Reception view as a graphic into a graphic editing or word-processing programme.
•
: Click the Print button (
) to print the Reception view.
You can also select the Details view from the top of the Point Analysis window to get more information. The Details view displays the profile of the receiver (the combination of terminal, service, mobility, and carrier) and, for each transmitter, its distance from the receiver, its signal level (or RSCP), its path loss, Ec/Io, DL and UL Eb/Nt values, and scrambling code.
9.2.10.7.4
Creating a Focus Zone or Hot Spot for a Coverage Prediction Report The focus zone and hot spots define an area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spots in addition to the focus zone. It is important not to confuse the computation zone and the focus zone and hot spots. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc., while the focus zone and hot spots are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spots. To define a focus zone or hot spot: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spots, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the focus zone or hot spot.
ii. Click once on the map to define each point on the map where the border of the focus zone or hot spot changes direction. iii. Click twice to finish drawing and close the focus zone or hot spot. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the focus zone or hot spot.
ii. Drag to the opposite corner of the rectangle that will define the focus zone or hot spot. When you release the mouse, the focus zone or hot spot will be created from the rectangle defined by the two corners. A focus zone is delimited by a green line; a hot spot is delimited by a heavy black line. If you clear the zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a focus zone or hot spot as follows: • •
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a focus zone or hot spot by right-clicking it and selecting Use As > Focus Zone or Use As > Hot Spot from the context menu. You can also combine an existing focus
673
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
•
•
© Forsk 2012
zone or hot spot with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Hot Spot or Add To > Hot Spot from the context menu. 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 zone or hot spot. You can import it by right-clicking the Focus Zone folder or Hot Spots in the Geo explorer and selecting Import from the context menu. When you import hot spots, you can import the name given to each zone as well. Fit Zone to Map Window: You can create a focus zone or hot spot the size of the map window by selecting Fit Zone to Map Window from the context menu. You can save the focus zone or hot spots in the following ways, so that you can use it in a different Atoll document: •
•
Saving the focus zone in the user configuration: For information on saving the focus zone in the user configuration, see "Saving a User Configuration" on page 101. Exporting the focus zone or hot spots: You can export the focus zone or hot spots by right-clicking the Focus Zone or the Hot Spots folder in the Geo explorer and selecting Export from the context menu.
You can include population statistics in the focus zone or hot spot by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137.
9.2.10.7.5
Displaying a Coverage Prediction Report Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage prediction’s Properties dialogue. The coverage prediction report is displayed in a table. For information on working with tables, see "Working with Data Tables" on page 69. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 74. Atoll bases the report on the area covered by the focus zone and hot spots; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot must be defined before you display a report; it is not necessary to define it before calculating coverage. The focus zone or hot spot does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 673. Once you have generated a report, you can export it to a text file or to an Excel spreadsheet. For more information on exporting a coverage prediction report, see "Exporting a Coverage Prediction Report" on page 675. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Predictions folder.
3. Right-click the coverage prediction for which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Define the format and content of the report: You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down.
to move it up or
You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied.
674
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spots and on the focus zone if available or on the hot spots and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Select the Network explorer. 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.
to move it up or
You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spots by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137. Normally, Atoll takes all geo data into consideration, whether it is displayed or not. However, for the population statistics to be used in a report, the population map has to be displayed. To include population statistics in the focus zone or hot spots: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. 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 in the Geo explorer 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 154.
9.2.10.7.6
Exporting a Coverage Prediction Report Once you have generated a coverage prediction report as explained in "Displaying a Coverage Prediction Report" on page 674, you can export it to a text file or to a spreadsheet.
675
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
To export a coverage prediction report: 1. Right-click the report and select Export from the context menu or click the Export button ( The Save As dialogue appears.
) in the Table toolbar.
2. In the Save As dialogue, enter the File name and select the format from the Save as type list: • • • •
TXT: To save the report as a text file. CSV: To save the report as a comma-separated values file. XLS: To save the report as an Excel spreadsheet. XML Spreadsheet 2003: To save the report as an XML spreadsheet.
3. Click Save to export the coverage prediction report.
9.2.10.7.7
Viewing Coverage Prediction Statistics Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage prediction colours, interval steps, and shading as defined on the Display tab of the coverage prediction’s Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spots are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before calculating coverage. For information on defining a focus zone, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 673. To display the statistics on a coverage prediction: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Predictions folder.
3. Right-click the coverage prediction whose statistics you want to display. The context menu appears. 4. Select Histogram from the context menu. The Statistics dialogue appears with a histogram of the area defined by the focus zone (see Figure 9.24). • •
• • •
676
Under Histogram based on covered areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Zoom on selected values section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics based on prediction conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Figure 9.24: Histogram of a coverage prediction by signal level
9.2.10.7.8
Comparing Coverage Predictions: Examples Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison in one of the following ways: • •
•
Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both predictions are displayed in red). Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and pixels covered by only one prediction are blue). Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for example, pixels covered by both predictions are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).
To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction. 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 677 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 679.
Example 1: Studying the Effect of a New Base Station If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can verify if a newly added base station improves coverage.
677
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 667. The results are displayed in Figure 9.25. An area with poor coverage is visible on the right side of the figure.
Figure 9.25: 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 629, or by placing a station template, as explained in "Placing a New Station Using a Station Template" on page 638. 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 9.26).
Figure 9.26: 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.
678
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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.27, shows clearly the area covered only by the new base station.
Figure 9.27: Comparison of both signal level coverage predictions Example 2: Studying the Effect of a Change in Transmitter Tilt If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can see how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 669. The results are displayed in Figure 9.28. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated by a red oval in Figure 9.28.
679
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Figure 9.28: 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 9.29).
Figure 9.29: 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: • • •
680
Intersection Union Difference
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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.30, shows clearly the increase in coverage due to the change in antenna tilt.
Figure 9.30: Comparison of both transmitter coverage predictions
9.2.10.8 UMTS-Specific Predictions In UMTS, the quality of the signal and the size of the area that can be covered are influenced by the network load. As the network load increases, the area a cell can effectively cover decreases. For this reason, the network load must be defined in order to calculate UMTS-specific predictions. If you have traffic maps, you can do a Monte-Carlo simulation to model power control and evaluate the network load for a generated user distribution. If you do not have traffic maps, Atoll can calculate the network load using the UL load factor and DL total power defined for each cell. In this section, the UMTS-specific coverage predictions will be calculated using UL load factor and DL total power parameters defined at the cell level. For the purposes of these predictions, each pixel is considered a non-interfering user with a defined service, mobility type, and terminal. Before making a coverage prediction, you will have to set the UL load factor and DL total power and the parameters that define the services and users. These are explained in the following sections: • •
"Setting the UL Load Factor and the DL Total Power" on page 682. "Service and User Modelling" on page 682.
Several different types of UMTS-specific coverage predictions are explained in this section: • • •
"Making a Pilot Signal Quality Prediction" on page 687 "Studying Service Area (Eb⁄Nt) Downlink or Uplink" on page 688 "Studying the Effective Service Area" on page 690.
The following noise predictions, also coverage predictions, are explained: • • •
"Studying the Total Noise Level on the Downlink" on page 692 "Calculating Pilot Pollution" on page 693 "Studying Inter-technology Downlink Interference" on page 694.
Another type of coverage prediction, the handover prediction, is also explained: •
"Making a Handoff Status Coverage Prediction" on page 695.
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 696.
Interference from an external project can also be modelled. For an explanation of modelling external interference, see "Modelling Inter-technology Interference" on page 806.
681
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
9.2.10.8.1
© Forsk 2012
Setting the UL Load Factor and the DL Total Power If you are setting the UL load factor and the DL total power for a single transmitter, you can set these parameters on the Cells tab of the transmitter’s Properties dialogue. However, you can set the UL load factor and the DL total power for all cells using the Cells table. To set the UL load factor and the DL total power using the Cells table: 1. Select the Network explorer. 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 633.
To enter the same values in one column for all cells in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69.
9.2.10.8.2
Service and User Modelling Before you can model services, you must already have R99 radio bearers defined in your Atoll document. Only the following R99 radio bearer parameters are used in predictions: • •
Max TCH Power (dBm) The type of bearer.
For information on defining R99 radio bearers, "Defining R99 Radio Bearers" on page 798. In this section, the following are explained: • • •
"Modelling UMTS HSPA Services" on page 682 "Creating a UMTS HSPA Mobility Type" on page 685 "Modelling UMTS HSPA Terminals" on page 685.
Modelling UMTS HSPA Services Services are the various services available to subscribers. These services can be either circuit-switched or packet-switched services. This section explains how to create a service. However, only the following parameters are used in predictions: • • • • • •
R99 bearer parameters Downgrading capabilities Handover capabilities HSPA capabilities Body loss HSPA application throughput parameters
Before you can model services, you must have defined R99 bearers. For information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 798. To create or modify a service: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the Traffic Parameters folder.
3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears.
682
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.
5. Edit the fields on the General tab to define the new service: • •
•
Name: Atoll proposes a name for the new service, but you can change the name to something more descriptive. Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for each user during Monte-Carlo simulations. For packet-switched services, this parameter is used when working with sector traffic maps and user density traffic maps. For circuit-switched services, the parameter is taken into consideration with all traffic maps. Average Requested Throughput: You can enter the average requested throughput for uplink and downlink. This throughput is the average throughput obtained by a user of the service. It is used in simulations during user distribution generation to calculate the number of users attempting a connection and to determine their activity status.
6. Click the UMTS tab to define the new service. 7. Select an R99 Radio Bearer from the list. If you want to edit the settings of the selected R99 radio bearer, click the Browse button (
) to open the bearer’s Properties dialogue.
8. Select a service Type: • • •
Circuit (R99): For circuit services, select Circuit (R99). Packet (R99): For packet services that can only use R99 channels, select Packet (R99). Packet (HSDPA - Best Effort): For best effort applications that can use HSDPA channels, select Packet (HSDPA Best Effort). The HSDPA service is linked to a R99 bearer in order to manage the connection to the R99dedicated channel A-DPCH.
• • •
Packet (HSPA - Best Effort): For best effort applications that can use HSDPA and HSUPA channels, select Packet (HSPA -Best Effort). Packet (HSDPA - Variable Bit Rate): For variable bit rate services using HSDPA channels, select Packet (HSDPA Variable Bit Rate). Packet (HSPA - Variable Bit Rate): For variable bit rate services using HSPA channels, select Packet (HSPA - Variable Bit Rate).
9. For all types of services, define the following parameters: •
Preferred/Allowed Carriers: You can select one of the available carriers or all carriers. The specified carrier is considered in simulation when admitting a transmitter to the mobile active set. If you select "Preferred Carriers" and the transmitter uses the specified carrier, Atoll selects it. Otherwise, it will choose another one, using the carrier selection mode defined in the site equipment properties. The carrier specified for the service is not used in predictions (i.e., AS analysis and coverage predictions). In predictions, Atoll considers the carrier selection mode defined in the site equipment properties. If no preferred carrier is specified in the service properties, it will consider the carrier selection mode defined in the site equipment properties. If you select "Allowed Carriers" Atoll will only use the defined carriers. If they are not available, service will be rejected.
•
•
Bearer Downgrading: Select the Bearer downgrading check box if the service supports bearer downgrading on uplink and downkink. Bearer downgrading is not allowed for Packet (HSDPA - Variable Bit Rate) and Packet (HSPA - Variable Bit Rate) services. Soft Handoff Allowed: Select the Soft Handoff Allowed check box if you want the network to be able to use soft handoff with this service. HSDPA channels do not use soft handover even if the Soft Handoff Allowed check box is selected. If you want the HSUPA service to be operated using soft handover, select the Soft Handoff Allowed check box. Soft handover will be applied to R99 and HSUPA channels only.
• •
Priority: Enter a priority for this service. "0" is the lowest priority. Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For example, in a voice connection the body loss, due to the proximity of the user’s head, is estimated to be 3dB.
10. If you selected Circuit (R99) as the Type in step 8., continue to step 13. If you selected Packet (R99), Packet (HSDPA Best Effort), Packet (HSPA - Best Effort), Packet (HSPA - Constant Bit Rate), Packet (HSDPA - Variable Bit Rate), or
683
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Packet (HSPA - Variable Bit Rate) as the Type in step 8., click the Packet button to define the parameters used to determine the probability of activity for each user during Monte-Carlo simulations. These parameters are used when working with user profile traffic maps only. Click the Packet tab. In the Packet dialogue, you can set the following parameters for packet-switched services: •
Under BLER, you can define the following: •
•
Under Session, you can set: • •
•
Average Number of Packet Calls: Enter the average number of packet calls in the uplink and downlink during one session. Average Time Between Two Packet Calls: Enter the average time between two packet calls (in milliseconds) in the uplink and downlink.
Under Packet Calls, you can set: • • •
•
Efficiency Factor: The uplink and downlink efficiency factors are used to determine duration of usage by the user during Monte-Carlo simulations.
Min. Size (Kbytes): Enter the minimum size of a packet call in kilobytes in the uplink and downlink. Max Size (Kbytes): Enter the maximum size of a packet call in kilobytes in the uplink and downlink. Average Time Between Two Packets (ms): Enter the average time between two packets in milliseconds in the uplink and downlink.
Under Packet, you can set: •
Size (Bytes): Enter the packet size in bytes in the uplink and downlink.
11. Click Commit to save your changes and close the Packet dialogue when you have finished setting the parameters. 12. If you selected a packet service (i.e., Packet (HSDPA - Best Effort), Packet (HSPA - Best Effort), Packet (HSPA - Constant Bit Rate), Packet (HSDPA - Variable Bit Rate), or Packet (HSPA - Variable Bit Rate) as the Type in step 8., set the following parameters: Under Application Throughput: •
Set a Scaling Factor between the application throughput and the RLC (Radio Link Control) throughput and a throughput Offset. These parameters model the header information and other supplementary data that does not appear at the application level.
For Packet (HSDPA - Best Effort) services, set the following parameters under HSPA Parameters: •
E-DPCCH/A-DPCH Activity Factor: The downlink E-DPCCH/A-DPCH activity factor is used to estimate the average power on A-DPCH channels.
For Packet (HSPA - Best Effort) services, set the following parameters under HSPA Parameters: •
E-DPCCH/A-DPCH Activity Factor: The uplink and downlink E-DPCCH/A-DPCH activity factors are used to estimate the average power on E-DPCCH and A-DPCH channels.
For Packet (HSPA - Constant Bit Rate) service, set the following parameters under HSPA Parameters: • •
E-DPCCH/A-DPCH Activity Factor: The E-DPCCH/A-DPCH activity factor is used to estimate the average power on A-DPCH channels. Min Throughput Demand: Enter the minimum required bit rate that the service should have in order to be available in the uplink and downlink.
For Packet (HSDPA - Variable Bit Rate) service, set the following parameters under HSPA Parameters: • • •
E-DPCCH/A-DPCH Activity Factor: The downlink E-DPCCH/A-DPCH activity factor is used to estimate the average power on A-DPCH channels. Max Throughput Demand: Enter the maximum bit rate that the service can require in the downlink. Min Throughput Demand: Enter the minimum required bit rate that the service should have in order to be available in the downlink.
For Packet (HSPA - Variable Bit Rate) service, set the following parameters under HSPA Parameters: • • •
E-DPCCH/A-DPCH Activity Factor: The uplink and downlink E-DPCCH/A-DPCH activity factors are used to estimate the average power on E-DPCCH and A-DPCH channels. Max Throughput Demand: Enter the maximum bit rate that the service can require in the uplink and downlink. Min Throughput Demand: Enter the minimum required bit rate that the service should have in order to be available in the uplink and downlink. The uplink and downlink E-DPCCH/A-DPCH activity factors have been set to 0.1 and cannot be changed. These values are used to estimate the average power on E-DPCCH and A-DPCH channels.
684
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
13. Click OK. Creating a UMTS HSPA Mobility Type In UMTS, information about receiver mobility is important to efficiently manage the active set: a mobile used by someone travelling a certain speed and a mobile used by a pedestrian will not necessarily be connected to the same transmitters. Ec⁄I0 requirements and Eb/Nt targets per radio bearer and per link (up and down) are largely dependent on mobile speed. The following parameters are used in predictions: • •
Ec⁄I0 threshold HS-SCCH Ec⁄Nt Threshold
To create or modify a mobility type: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the Traffic 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. You can modify the properties of an existing mobility type by right-clicking the mobility type in the Mobility Types folder and selecting Properties from the context menu.
5. On the General tab, you can enter or modify the following parameters in the Mobility Types New Element Properties dialogue: • •
Name: Enter or modify the descriptive name for the mobility type. Speed: Enter or modify an average speed for the mobility type. This field is for information only; the average speed is not used by any calculation.
6. On the Parameters tab, you can enter or modify the following parameters in the Mobility Types New Element Properties dialogue: • •
Ec⁄I0 Threshold: Under Active Set Management, enter or modify the minimum Ec⁄I0 required from a transmitter to enter the active set. This value must be verified for the best server. HS-SCCH Ec⁄Nt Threshold: Under HSDPA, enter or modify the minimum quality required in order for the HSDPA link to be available. This parameter is used by Atoll to determine the HS-SCCH power when the user has selected dynamic allocation in the cell properties. For static allocation, Atoll calculates the HS-SCCH Ec⁄Nt from the HS-SCCH power set in the cell properties and compares it to this threshold. This field is only used with HSDPA.
7. Click OK. Modelling UMTS HSPA Terminals In UMTS, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a car’s on-board navigation device. The following parameters are used in predictions: • • • • • • • • • •
Receiver equipment Main and secondary bands Maximum terminal power Gain and losses Noise figures Active set size DL rake factor CDMA Rho factor Compressed mode capability HSPA capability and HSPA-specific categories: • • •
UE category Number of reception antenna ports MUD factor (for HSDPA only).
To create or modify a terminal: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the Traffic 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.
685
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
You can modify the properties of an existing terminal by right-clicking the terminal in the Terminal folder and selecting Properties from the context menu.
5. Click the General tab. You can modify the following parameter: •
Name: You can change the name of the terminal.
6. Click the Parameters tab. You can modify the following parameters: Under Transmission/Reception: •
UMTS Equipment: Select a type of reception equipment from the list. You can create a new type of reception equipment by using the Reception Equipment table. You can open open the Reception Equipment table by clicking the Expand button ( ) to expand the UMTS Network Settings folder, and then right-clicking the Reception Equipment folder and selecting Open Table from the context menu.
• • • • • •
Min. Power: Set the minimum transmission power. The minimum and maximum transmission power make up the dynamic range for uplink power control. Max Power: Set the maximum transmission power. Gain: Set the antenna gain. Losses: Set the reception losses. Active Set Size: Set the active set size. The active set size is the maximum number of transmitters to which a terminal can be connected at one time. DL Rake Factor: Set the DL rake factor. This enables Atoll to model the rake receiver on DL. The rake efficiency factor, used for calculating recombination in uplink has to be set in the site equipment properties. For information on setting site equipment properties, see "Creating Site Equipment" on page 800.
•
CDMA Rho factor (%): This parameter enables Atoll to take into account the self-interference produced by the terminal. Because hardware equipment is not perfect, the input signal experiences some distortion which affects, in turn, the output signal. This factor defines how much distortion the system generates. Entering 100% means the system is perfect (there is no distortion) and the output signal will be 100% equal to the input signal. On the other hand, if you specify a value different than 100%, Atoll considers that the transmitted energy is not 100% signal and contains a small percentage of interference generated by the equipment, i.e., self-interference. Atoll considers this parameter to calculate the signal to noise ratio in the uplink.
•
Compressed Mode Supported: Check the Compressed Mode Supported check box if the terminal uses compressed mode. Compressed mode is generally used to prepare hard-handover of users with single receiver terminals.
Under Frequency Bands: • •
Main Band: Select the frequency band with which the terminal is compatible and enter the terminal Noise Figure for the main frequency. Secondary Band: Select a second frequency band with which the terminal is compatible and enter the terminal Noise Figure for the second frequency. Leave the Secondary Band field empty if the terminal works only on one frequency band. There are two different ways of defining dual-band terminals. Depending on the configuration, Atoll processes dual-band terminal users differently in the Monte-Carlo simulation. •
•
The first one consists of defining main and secondary frequency bands. This enables you to give a higher priority to one frequency band in the Monte-Carlo simulation (the main frequency band will have the higher priority). A user with such a dual-band terminal will be connected to transmitters using the main frequency band if carriers on this frequency band are not overloaded. In case of overloading, he will be connected to transmitters using the secondary frequency band. The second consists of selecting "All" as main frequency band. This means that the terminal works on any frequency band without any priority. In this case, the user can be connected to transmitters using any frequency band.
In coverage predictions, both configurations give the same results. The priority of frequency bands is not taken into account.
686
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Select the type of HSPA Support the terminal has: None (i.e., R99 support only), HSDPA or HSPA (i.e., HSDPA and HSUPA). If the terminal supports HSDPA, you can define the HSDPA parameters under HSDPA: • •
•
UE Category: Select the HSDPA user equipment category of the terminal. MUD Factor: Enter a multi-user detection factor (MUD). MUD is based on an algorithm used to improve mobile receiver capacity. It reduces intra-cell interference and allows for higher Ec⁄Nt. MUD is modelled by a coefficient from 0 to 1; this factor is considered in calculating DL interference. If MUD is not supported, enter "0." Number of Reception Antenna Ports: Select the number of reception antenna ports available on the terminal for MIMO.
If the terminal supports HSUPA, you can define the HSUPA parameters under HSUPA: •
UE Category: Select the HSUPA user equipment category of the terminal.
7. Click OK.
9.2.10.8.3
Making Quality Predictions In Atoll, you can make several predictions to study the quality. In this section, the following quality predictions are explained: • • • •
"Making a Pilot Signal Quality Prediction" on page 687 "Studying Service Area (Eb⁄Nt) Downlink or Uplink" on page 688 "Studying the Effective Service Area" on page 690 "Creating a Quality Coverage Prediction Using Quality Indicators" on page 690. A table listing quality indicators (BER, BLER, etc.) to be analysed is available. Quality predictions proposed by Atoll depend on quality indicators specified in this table.
Making a Pilot Signal Quality Prediction A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is received sufficiently well to be added to the probe mobile active set. Atoll calculates the best pilot quality received on each pixel. Then, depending on the coverage prediction definition, it compares this value either to the Ec⁄I0 threshold defined for the selected mobility type, or to user-defined Ec⁄I0 thresholds. The pixel is coloured if the condition is fulfilled (in other words, if the best Ec⁄I0 is higher than the Ec⁄I0 mobility threshold or specified Ec⁄I0 thresholds). To make a pilot signal quality prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Pilot Quality Analysis and click OK. The Pilot Quality Analysis 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a "global" coverage prediction (e.g., a signal level coverage prediction). 6. Click the Conditions tab (see Figure 9.31). Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 682. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best (Main band)" carrier selected according to the carrier selection method defined for the site equipment. If you want the pilot signal quality prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box.
687
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
You can also select the Indoor coverage check box to add indoor losses.
Figure 9.31: 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 "Ec⁄I0 (dB)" is selected by default. Each pixel is displayed in a colour corresponding to the pilot signal quality. For information on defining display properties, see "Display Properties of Objects" on page 43. You can also set parameters to display the following results: • • • •
Where at least one transmitter is in the active set: Select "Unique" as the Display Type. Where at least one transmitter is in the active set, with information on the best server: Select "Discrete Value" as the Display Type and "Transmitter" as the Field. The pilot signal level: Select "Value Intervals" as the Display Type and "Ec (dBm)" as the Field. The pilot quality relative to the Ec⁄I0 threshold: Select "Value Intervals" as the Display Type and "Ec⁄I0 margin (dB)" as the Field.
8. Click the Result Export tab. If, on the Display tab, you have selected to display the results by value intervals, you can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Studying Service Area (Eb⁄Nt) Downlink or Uplink Atoll calculates the traffic channel quality (as defined by Eb⁄Nt) when using the maximum power allowed, i.e., the maximum traffic channel power allowed per cell for downlink and the maximum terminal power for uplink. In the coverage prediction, the downlink or uplink service area is limited by the maximum power allowed and by the pilot quality. If the received pilot quality is insufficient, Atoll will not display the traffic channel quality. The mobile handover status is taken in consideration to evaluate the downlink and uplink traffic channel quality (Eb⁄Nt). Atoll combines the signal from each transmitter in the probe mobile active set. To make a coverage prediction on service area (Eb/Nt) downlink or uplink: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears.
688
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
4. Select one of the following predictions and click OK: • •
Service Area Analysis (Eb/Nt) (DL) Service Area Analysis (Eb/Nt) (UL)
The coverage prediction Properties dialogue appears. 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab. Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. 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 682. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best (Main band)" carrier selected according to the carrier selection method defined for the site equipment. If you want the 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 also select the Indoor coverage check box to add indoor losses. You can select the Bearer downgrading check box if you want the service area (Eb⁄Nt) 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 Eb⁄Nt (dB)" is selected by default. The Field you choose determines which information the service area (Eb⁄Nt) 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 43. You can also set parameters to display the following results: • • •
The traffic channel quality relative to the Eb⁄Nt threshold: Select "Value Intervals" as the Display Type and "Eb⁄Nt Margin (dB)" as the Field. The power required to reach the Eb⁄Nt threshold: Select "Value Intervals" as the Display Type and "Required Power (dB)" as the Field. Where traffic channel quality exceeds the Eb⁄Nt threshold for each mobility type: On the Conditions tab, select "All" as the Mobility Type. The parameters on the Display tab are automatically set.
For a service area (Eb⁄Nt) (UL) coverage 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. Click the Result Export tab. If, on the Display tab, you have selected to display the results by value intervals, you can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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.
689
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Studying the Effective Service Area The effective service area is the intersection zone between the pilot reception area, and the uplink and downlink service areas. In other words, the effective service area prediction calculates where a service actually is available for the probe mobile. To make an effective service area prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Effective Service Area Analysis (Eb⁄Nt) (DL+UL) and click OK. The Effective Service Area Analysis (Eb⁄Nt) (DL+UL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab. Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 682. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best" carrier selected according to the carrier selection method defined for the site equipment. If you want the effective service area prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. You can also select the Indoor Coverage check box to add indoor losses. You can select the Bearer downgrading check box if you want the effective service area prediction to take into consideration circumstances when the R99 bearer is downgraded. When downgrading is enabled and if the selected service supports bearer downgrading, Atoll will consider only the lowest radio bearer. 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Creating a Quality Coverage Prediction Using Quality Indicators You can create a quality prediction based on a given quality indicators (BER, BLER, or FER). The coverage prediction will show for each pixel the measurement of the selected quality indicator. This type of coverage prediction is not available in the list of standard predictions; you can, however, use quality indicators in a prediction by first ensuring that the parameters of the quality indicators have been correctly set and then creating a coverage prediction, selecting display parameters that use these quality indicators. Before you define the quality prediction, you must ensure that the parameters of the quality indicators have been correctly set.
690
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
To check the parameters of the quality indicators: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Right-click Quality Indicators. The context menu appears. 4. Select Open Table from the context menu. The Quality Indicators table appears. For each quality indicator in the Name column, you can set the following parameters: • • • •
Used for Packet Services: Select the Used for Packet Services check box if the quality indicator is to be used for packet services. Used for Circuit Services: Select the Used for Circuit Services check box if the quality indicator is to be used for circuit services. Measured Parameter for Quality Indicator: From the list, select the parameter that will be measured to indicate quality. Interpolated Quality Indicator: Select the Interpolated Quality Indicator check box if you want Atoll to interpolate between two existing QI values. Clear the Interpolated Quality Indicator check box if you want Atoll to take the closest QI value.
5. Close the Quality Indicators table. 6. In the UMTS Network Settings folder, right-click the Reception Equipment folder. The context menu appears. 7. Select Open Table from the context menu. The Reception Equipment table appears. "Standard" is the default reception equipment type for all terminals. 8. Double-click the reception equipment type for which you want to verify the correspondence between the measured quality and the quality indicator. The reception equipment type’s 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 type’s Properties dialogue. Once you have ensured that the parameters of the quality indicators have been correctly set, you can use the measured quality to create a quality prediction. How you define a coverage prediction according to the measured quality indicator depends several parameters: • • • •
The settings made in the Quality Indicators table The service you want to study The quality indicator you want to use (BER, BLER, or FER) The coverage prediction you want to use (Pilot Quality Analysis, the Service Area Analysis Downlink, or Service Area Analysis Uplink).
In the following example, you will create a quality prediction showing BLER, for a user on foot, and with mobile internet access. To create a quality prediction showing BLER for a user on foot, and with mobile internet access: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Service Area Analysis (Eb⁄Nt) (DL) and click OK. The Service Area Analysis (Eb⁄Nt) (DL) Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name and Resolution of the service area (Eb⁄Nt) downlink prediction, and add some Comments. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. 6. Click the Conditions tab. Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. 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.
691
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• • •
© Forsk 2012
Service: Select "Mobile Internet Access" from the Service list. Mobility: Select "Pedestrian" from the Mobility list. Carrier: Select a specific carrier or "Best (Main band)" to have the carrier selected according to the carrier selection method defined for the site equipment.
If you want the service area (Eb⁄Nt) (DL) prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. You can also select the Indoor Coverage check box to add indoor losses. You can select the Bearer downgrading check box if you want the service area (Eb⁄Nt) 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 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the 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 (Eb⁄Nt) (provided when using the maximum traffic channel power allowed). Then, it calculates the corresponding BLER value from the quality graph (BLER=f(DL Eb⁄Nt)). The pixel is coloured if the condition is fulfilled (i.e., if BLER is evaluated as being higher than the specified threshold).
9.2.10.8.4
Studying Noise Atoll has several coverage predictions that enable you to study the downlink total noise, downlink noise rise or pilot pollution. In this section, the following noise predictions are explained: • • •
"Studying the Total Noise Level on the Downlink" on page 692 "Calculating Pilot Pollution" on page 693 "Studying Inter-technology Downlink Interference" on page 694.
Studying the Total Noise Level on the Downlink In the coverage by total noise level (DL) prediction, Atoll calculates and displays the areas where the downlink total noise or the downlink noise rise exceeds a set threshold. To make a downlink total noise or downlink noise rise prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Total Noise Level Analysis (DL) and click OK. The Total Noise Level Analysis (DL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab. Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
692
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
You must select a Terminal, and Service, as defined in "Service and User Modelling" on page 682. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best" carrier selected according to the carrier selection method defined for the site equipment You can also select the Indoor coverage check box to add indoor losses. 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. •
Coverage by total noise on the downlink: When making a prediction on the total noise level on the downlink, select one of the following in the Field list: • • •
•
Min. Noise Level Average Noise Level Max Noise Level
Coverage by noise rise on the downlink: When making a prediction on the noise rise on the downlink, select one of the following in the Field list: • • •
Min. Noise Rise Average Noise Rise Max Noise Rise
For information on defining display properties, see "Display Properties of Objects" on page 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Calculating Pilot Pollution A transmitter which fulfils all the criteria to enter a mobile’s active set but which is not admitted because the active set limit has already been reached is considered a polluter. In the Pilot Pollution Analysis prediction, Atoll calculates and displays the areas where the probe mobile is interfered by the pilot signal from polluter transmitters. To make a pilot pollution prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Pilot Pollution Analysis and click OK. The Pilot Pollution Analysis 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab. Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
693
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 682. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best" carrier selected according to the carrier selection method defined for the site equipment. If you want the 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 Analysis prediction, the Display Type "Value Intervals" and the Field "Number of Polluters" are selected by default. For information on defining display properties, see "Display Properties of Objects" on page 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Studying Inter-technology Downlink Interference In the inter-technology downlink noise prediction, Atoll calculates and displays the areas where the downlink noise or noise rise from external base stations and mobiles exceeds a set threshold. For more information on the modelling of inter-technology interference, see "Modelling Inter-technology Interference" on page 806. To make an inter-technology downlink noise or noise rise prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Inter-technology Interference Level Analysis (DL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab. 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. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal and a Service, as defined in "Service and User Modelling" on page 682. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best" carrier selected according to the carrier selection method defined for the site equipment. If you want the prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. 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 43.
694
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.2.10.8.5
Making a Handoff Status Coverage Prediction In the handoff status coverage prediction, Atoll calculates and displays the zones where a handoff can be made. For a handover to be possible, there must be a potential active transmitter, i.e., a transmitter that fulfils all the criteria to enter the mobile active set, and the service chosen by the user must be available. You can also use the handoff status coverage prediction to display the number of potential active transmitters. To make a handoff status coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Handoff Zones and click OK. The Handoff 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab. Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 682. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best (Main band)" carrier selected according to the carrier selection method defined for the site equipment. If you want the handoff status coverage prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. You can also select the Indoor Coverage check box to add indoor losses. 7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage prediction will display. To display the handoff status: a. Select "Discrete Values" from the Display Type list. b. Select "Status" from the Field list. Depending on the active set size of the terminal and the service capabilities in terms of soft handover, the coverage prediction can display the following values: • • • • • • •
No handoff: one cell in the mobile active set. Softer: two cells in the mobile active set belonging to the same site. Soft: two cells in the mobile active set, one from Site A and the other from Site B. Softer-Softer: three cells in the mobile active set, belonging to the same site. Softer-Soft: three cells in the mobile active set, two from Site A and the third one from Site B. Soft-Soft: three cells in the mobile active set, one from Site A, one from Site B and one from Site C. Not connected: no cell in the mobile active set.
695
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.2.10.8.6
Making an AS Analysis The Point Analysis window gives you information on reception for any point on the map. The AS Analysis view gives you information on the pilot quality (Ec⁄I0) (which is the main parameter used to define the mobile active set), the connection status, and the active set of the probe mobile. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service. Analysis is based on: • • •
The UL load percentage and the DL total power of cells for R99 bearer connection The available HSDPA power of cells for HSDPA bearer users The uplink reuse factor, the uplink load factor due to HSUPA, the maximum uplink load factor of cells and the number of HSUPA users in the cells in case of HSUPA bearer users.
You can make an AS analysis to verify a coverage prediction. Before you make the AS analysis, ensure the coverage prediction you want to use in the AS analysis is displayed on the map. For information on the criteria for belonging to the active set, see "Conditions for Entering the Active Set" on page 805. To make an AS analysis: 1. Click the Point Analysis button (
) on the toolbar. The Point Analysis window appears (see Figure 9.33).
2. Select the AS Analysis view at the top of the Point Analysis window. 3. At the top of the AS Analysis view, select "Cells Table" from Load conditions. 4. If you are making an AS analysis to verify a coverage prediction, you can recreate the conditions of the coverage prediction: a. Select the same Terminal, Service, and Mobility studied in the coverage prediction. b. Select the Carrier to be considered. You can make the AS analysis for a specific carrier or for the "Best" carrier selected according to the carrier selection method defined for the site equipment. c. Select the Bearer downgrading check box if bearer downgrading was selected in the coverage prediction. When downgrading is enabled and if the selected service supports bearer downgrading, Atoll will consider only the lowest radio bearer. d. Click the Options button ( • • •
) to display the Calculation Options dialogue.
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.
e. Click OK to close the Calculation Options dialogue. 5. Move the pointer over the map to make an active set analysis for the current location of the pointer. As you move the pointer, Atoll indicates on the map which is the best server for the current position (see Figure 9.32).
696
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Figure 9.32: Point analysis on the map Information on the current position is given on the AS Analysis view of the Point Analysis window. See Figure 9.33 for an explanation of the displayed information.
Figure 9.33: Point Analysis Tool - AS Analysis view The bar graph displays the following information: • • •
The pilot quality (Ec⁄I0) of all transmitters using the selected carrier (the colour of the bar corresponds to the colour of the transmitter on the map). The thresholds of the active set (Ec⁄I0 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, DL, HSDPA, and HSUPA.
If there is at least one successful connection (for pilot, DL, UL, HSDPA, or HSUPA), double-clicking the icons in the righthand frame will open a dialogue with additional information. 6. Click the map to leave the point analysis pointer at its current position. To move the pointer again, click the point analysis pointer on the map and drag it to a new position. 7. Click the Point Analysis button (
) on the toolbar again to end the point analysis.
9.2.10.9 HSDPA Quality and Throughput Analysis The HSDPA predictions allow you to study many HSDPA-related parameters, depending on the parameters defined. Each HSDPA bearer user is associated to an R99-dedicated channel A-DPCH in the uplink and downlink, and must first initiate a ADPCH connection in order to be able to use HSDPA channels. In the coverage prediction, the HSDPA service area is limited by the pilot quality and the A-DPCH quality. The parameters used as input for the HSDPA coverage predictions are the available HSDPA power, and the total transmitted power for each cell. If the coverage prediction is not based on a simulation, these values are taken from the cell properties. For information about the cell parameters, see "Creating or Modifying a Cell" on page 638. For information on the formulas used to calculate different throughputs, see the Technical Reference Guide.
697
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
To make an HSDPA coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select HSDPA Quality and Throughput Analysis and click OK. The HSDPA Quality and Throughput Analysis 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab. Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Mobility, as defined in "Service and User Modelling" on page 682. For an HSDPA coverage prediction, under Terminal, you must chose an HSDPA-capable terminal and, under Service, you must chose a service with HSDPA. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best (Main band)" carrier selected according to the carrier selection method defined for the site equipment. Under HSDPA radio bearer, select either "All" to consider all possible HSDPA radio bearers in the prediction or an HSDPA radio bearer index to calculate a prediction for a certain bearer. Display options available in the Display tab depend on what you have selected here. To model a dual-cell HSDPA user, select an HSDPA-capable Terminal, a Service with HSDPA, and "Best (Main band)" as the carrier. 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 Conditions tab, you can set the following parameters: •
To analyse the uplink and downlink A-DPCH qualities on the map: •
• •
To analyse the HS-SCCH quality or power: • •
•
The maximum DL A-DPCH quality relative to the Eb⁄Nt threshold: Select "Max DL A-DPCH Eb⁄Nt (dB)" as the Field. Atoll determines downlink A-DPCH quality at the receiver for the maximum traffic channel power allowed for the best server. The maximum UL A-DPCH quality relative to the Eb⁄Nt threshold: Select "Max UL A-DPCH Eb⁄Nt (dB)" as the Field. Atoll determines uplink A-DPCH quality at the receiver for the maximum terminal power allowed. The HS-SCCH power per HS-SCCH channel relative to the power threshold: Select "HS-SCCH Power (dBm)" as the Field. This display option is relevant only if HS-SCCH power is allocated dynamically. The HS-SCCH Ec⁄Nt per HS-SCCH channel relative to the Ec⁄Nt threshold: Select "HS-SCCH Ec⁄Nt (dBm)" as the Field. This display option is relevant only if HS-SCCH power is allocated statically.
To model fast link adaptation for a single HSDPA bearer user or for a defined number of HSDPA users: For a single HSDPA bearer user, Atoll considers one HSDPA bearer user on each pixel and determines the best HSDPA bearer that the user can obtain by considering the entire available HSDPA power of the cell. •
698
The HS-PDSCH Ec/Nt relative to the Ec⁄Nt threshold: Select "HS-PDSCH Ec/Nt" as the Field. Atoll calculates the best HS-PDSCH Ec⁄Nt on each pixel.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
The channel quality indicator (CQI) relative to the Ec⁄Nt threshold: Select "CQI" as the Field. Atoll displays either the CPICH CQI or the HS-PDSCH CQI, depending on the option selected under HSDPA on the Global Parameters tab of the UMTS Network Settings Properties dialogue (see "The Options of the Network Settings Properties Dialogue" on page 796).
If you are modelling a dual-cell HSDPA user, Atoll determines the best carrier and the secondary carrier according to the carrier selection criterion defined in the site equipment. The two carriers are taken into consideration to calculate the rates and the throughputs. • • •
• • •
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.).
In order to be covered, variable bit rate users have to obtain an HSDPA bearer with a RLC peak rate exceeding their minimum throughput demands. When the RLC peak rate of the best HSDPA bearer exceeds the user maximum throughput demand, the HSDPA bearer is downgraded until the RLC peak rate is lower than the maximum throughput demand. Dual-cell HSDPA users with variable bit rate services are not covered if they cannot obtain the minimum throughput demand on their best carrier. Atoll can consider several HSDPA bearer users per pixel. When the coverage prediction is not based on a simulation, this value is taken from the cell properties. Atoll considers the defined number of HSDPA bearer users on each pixel and determines the best HSDPA bearer that each user can obtain. The coverage prediction results displayed are the average results for one user. The available HSDPA power of the cell is shared between the HSDPA bearer users. If you are modelling a dual-cell HSDPA user, the following rates and throughputs are calculated for the two best carriers depending on the carrier selection criterion defined in the site equipment. You can display the following results: •
• •
The average MAC throughput per mobile relative to the threshold: Select "MAC Throughput per Mobile (kbps)" as the Field. Atoll calculates the average MAC throughput per mobile from the from the MAC throughput of each user. The average RLC throughput per mobile relative to the threshold: Select "RLC Throughput per Mobile (kbps)" as the Field. Atoll calculates the average RLC throughput per mobile from the RLC throughput of each user. The average application throughput per mobile relative to the threshold: Select "Application Throughput per Mobile (kbps)" as the Field. Using the RLC peak rate, the BLER, the HSDPA service scaling factor, and the throughput offset, Atoll calculates the average application throughput per mobile from the application throughput of each user.
If you have selected an HSDPA radio bearer index as the HSDPA Radio Bearer on the Conditions tab, you can display the following results: •
Where a certain RLC peak rate is available with different cell edge coverage probabilities: On the Conditions tab, do not take shadowing into consideration and select a specific HSDPA radio bearer index. On the Display tab, the Display Type "Value Intervals" based on the Field "Cell Edge Coverage Probability (%)" is selected by default.
When no value is defined in the Cells table for the total transmitted power and the number of HSDPA bearer users, Atoll uses the following default values: • •
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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately.
699
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
•
© Forsk 2012
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.2.10.10 HSUPA Quality and Throughput Analysis The HSUPA coverage prediction allows you to study several HSUPA-related parameters. Each HSUPA bearer user is associated with an R99-dedicated traffic channel in the downlink and uplink (i.e., the ADPCH-EDPCCH R99 bearer), and must first initiate this connection in order to be able to use HSUPA channels. In the coverage prediction, the HSUPA service area is limited by the pilot quality and ADPCH-EDPCCH quality. The parameters used as input for the HSUPA predictions are the uplink load factor the uplink reuse factor, the uplink load factor due to HSUPA and the maximum uplink load factor for each cell. If the coverage prediction is not based on a simulation, these values are taken from the cell properties. For information about the cell parameters, see "Creating or Modifying a Cell" on page 638. For information on the formulas used to calculate required E-DPDCH Ec/Nt, required terminal power, and different throughputs, see the Technical Reference Guide. To make an HSUPA coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select HSUPA Quality and Throughput Analysis and click OK. The HSUPA Quality and Throughput Analysis 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab. Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Mobility, as defined in "Service and User Modelling" on page 682. For an HSUPA coverage prediction, under Terminal, you must chose an HSUPA-capable terminal and, under Service, you must chose a service with HSUPA. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best (Main band)" carrier selected according to the carrier selection method defined for the site equipment. HSUPA Resources: Atoll can calculate the HSUPA coverage prediction in one of two ways: • •
For a single user: After allocating capacity to all R99 users, the entire remaining load will be allocated to a single HSUPA bearer user. Shared by HSUPA users defined or calculated per cell: After allocating capacity to all R99 users, the remaining load of the cell will be shared equally between all the HSUPA bearer users. When the coverage prediction is not based on a simulation, the number of HSUPA bearer users is taken from the cell properties. The displayed results of the coverage prediction will be for one user.
When no value is defined in the Cells table, Atoll uses the following default values: • • • • •
Uplink load factor = 50% Uplink reuse factor = 1 Uplink load factor due to HSUPA = 0% Maximum uplink load factor = 75% Number of HSUPA users = 1
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box.
700
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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 Ec⁄Nt relative to the threshold: Select "Required E-DPDCH Ec⁄Nt (dB)" as the Field. Atoll selects the best HSUPA bearer whose required E-DPDCH Ec⁄Nt does not exceed the maximum E-DPDCH Ec⁄Nt allowed. The required E-DPDCH Ec⁄Nt is a property of the selected HSUPA bearer. The power required for the selected terminal relative to the threshold: Select "Required Terminal Power (dBm)" as the Field. Atoll calculates the required terminal power from the required E-DPDCH Ec⁄Nt. The MAC Rate relative to the threshold: Select "MAC Rate (kbps)" as the Field. Atoll calculates the MAC rate from the transport block size of the selected HSUPA bearer. The RLC peak rate relative to the threshold: Select "RLC Peak Rate (kbps)" as the Field. Atoll displays the RLC peak rate that the selected HSUPA bearer can supply. The RLC peak rate is a property of the HSUPA bearer. The guaranteed RLC throughput relative to the threshold: Select "Min RLC Throughput (kbps)" as the Field. The average RLC throughput relative to the threshold: Select "Average RLC Throughput (kbps)" as the Field. Atoll calculates the average RLC throughput on the uplink using the early termination probabilities, defined in the terminal’s 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 terminal’s reception equipment, to model HARQ (Hybrid Automatic Repeat Request).
In order to be covered, variable bit rate users have to obtain an HSUPA bearer with a RLC peak rate exceeding their minimum throughput demands. When the RLC peak rate of the best HSUPA bearer exceeds the user maximum throughput demand, the HSUPA bearer is downgraded until the RLC peak rate is lower than the maximum throughput demand. 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
9.2.10.11 Printing and Exporting Coverage Prediction Results Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. •
•
•
Printing coverage prediction results: Atoll offers several options allowing you to customise and optimise the printed coverage prediction results. Atoll supports printing to a variety of paper sizes, including A4 and A0. For more information on printing coverage prediction results, see "Printing a Map" on page 84. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 59. Exporting coverage prediction results: In Atoll, you can export the coverage areas of a coverage prediction in raster or vector formats. In raster formats, you can export in BMP, TIF, JPEG 2000, ArcView© grid, or Vertical Mapper (GRD and GRC) formats. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 GB. In vector formats, you can export in ArcView©, MapInfo©, or AGD formats. For more information on exporting coverage prediction results, see "Exporting Coverage Prediction Results" on page 67.
9.2.10.12 Making a Multi-point Analysis In Atoll, you can carry out calculations on lists of points representing subscribers and analyse them. These analyses can be useful for verifying network QoS at subscriber locations in case of incidents (call drops, low data rates, etc.) reported by users. Moreover, some user equipment may feed back a number of network measurements at their locations. This may help verify network quality without the need for measurement campaigns at the expense of the operator.
701
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Two types of analyses are available: •
Active Set Analysis: A number of parameters are calculated for each point. These parameters include the best server, the active set, Ec⁄Io values for the active set, the connection status, and the obtained rates. The load conditions are fixed by the user, either read from the Cells table or from a traffic simulation. Shadowing margins are not used in these calculations, i.e., fixed at 0 dB.
•
Potential Server Analysis: A number of parameters are calculated for each point, not just for the best server but for all potential servers. These parameters include the path loss, RSCP, Ec⁄Io, DL Eb⁄Nt, and UL Eb⁄Nt. The load conditions are fixed by the user, either read from the Cells table or from a traffic simulation. The results provided by this analysis are the same as available for one point in the Details view of the Point Analysis tool. Shadowing margins are calculated for the cell edge coverage probability defined in the Properties dialogue of the Point Analysis tool. The Indoor Coverage check box in this dialogue is also taken into account.
You may choose to carry out either or both types of analyses as needed. For both analysis types, all the points are considered to have the same height, which is the receiver height defined in the Properties dialogue of the UMTS Network Settings folder, i.e., the receiver height at which path loss matrices are calculated. In this section, the following are explained: • • • •
9.2.10.12.1
"Creating a Multi-point Analysis Group" on page 702. "Adding New Analyses to Existing Multi-point Analysis Groups" on page 703. "Accessing Multi-point Analysis Results" on page 703. "Defining the Display Properties of Multi-point Analysis Results" on page 705.
Creating a Multi-point Analysis Group Atoll lets you create a multi-point analysis group for each list of points. An analysis group may contain one or more analyses carried out on one list of points. Analyses can be added to existing groups as required. To create a new multi-point analysis group: 1. Select the Network explorer. 2. Right-click the Multi-point Analysis folder. The context menu appears. 3. Select New from the context menu. The Analysis Group N Properties dialogue appears. 4. Click the General tab. The following options are available: • •
Name: The name of the analysis group. You can change the name of the analysis group if desired. Comments
5. Click the Conditions tab. The following options are available: •
Load Conditions: Select the load conditions to be used in the analysis. If you select "(Cells Table)," the calculations are not going to be based on load conditions taken from a simulation; Atoll will use the UL load factor and the DL total power defined in the cell properties. When you base an analysis on simulations, you would select the simulations from the Load Conditions list.
•
Results: Select the results that you wish to be calculated: • • •
All: Both types of the analyses below will be performed. Active Set Analysis: Only the active set analysis will be carried out. Potential Server Analysis: Only the potential server analysis will be carried out.
For more information on the two types of analyses, see "Making a Multi-point Analysis" on page 701. • •
Bearer Downgrading: Select the Bearer downgrading check box if you want to permit bearer downgrading. Carrier: Under Potential Server Analysis Options, select the carrier for which you want the analysis to be carried out. You can either select "Best" or one or more carrier numbers from the list. This option is only available when either All or Potential Server Analysis is selected in the Results list above. The "Best" carrier will depend on the carrier selection method defined for the site equipment.
6. Click the Points tab. Here you can create the list of points on which the analyses will be carried out. Each point in the list is defined by its X and Y coordinates, a Service, a Terminal, and a Mobility. You can: •
Import a list of points. To import a list of points: i.
702
Click the Actions button. The context menu appears.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
ii. Select Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 82. •
Copy and paste an existing list of points.
•
Create points in the list by editing the table. In the row marked with the New Row icon ( ), you can create one point per row by entering its X and Y coordinates and assigning it a service, a terminal, and a mobility. The coordinates must be in the format used by the display coordinate system of the document. For information on changing the coordinate system, see "Setting a Coordinate System" on page 121.
7. You can either run the analyses selected in the General tab immediately or you can create the analysis group and run the analyses later: •
•
9.2.10.12.2
Calculate: Click Calculate to run the selected analyses immediately. Once the calculations for the selected analyses are complete, an analysis (Analysis 0) will appear under the Analysis Group N in the Multi-point Analysis folder. For information on how to access the analysis results, see "Accessing Multi-point Analysis Results" on page 703. OK: Click OK to create the analysis group without running any analysis. Analysis Group N will appear under the Multi-point Analysis folder. For information on how to run analyses on an existing analysis group, see "Adding New Analyses to Existing Multi-point Analysis Groups" on page 703.
Adding New Analyses to Existing Multi-point Analysis Groups When you have created a multi-point analysis group corresponding to a list of points, you can re-examine this list of points with different calculation options by adding new analyses to the group. To add a new analysis to an existing multi-point analysis group: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Multi-point Analysis folder.
3. Right-click the multi-point analysis group. The context menu appears. 4. Select New from the context menu. The Analysis Group N Properties dialogue appears. 5. On the Conditions tab, the following options are available: •
Load Conditions: Select the load conditions to be used in the analysis. If you select "(Cells Table)," the calculations are not going to be based on load conditions taken from a simulation. Atoll will use the UL load factor and the DL total power defined in the cell properties. When you base an analysis on simulations, you would select the simulations from the Load Conditions list.
•
Results: Select the results that you wish to be calculated: • • •
All: Both types of the analyses below will be performed. Active Set Analysis: Only the active set analysis will be carried out. Potential Server Analysis: Only the potential server analysis will be carried out.
For more information on the two types of analyses, see "Making a Multi-point Analysis" on page 701. • •
Bearer Downgrading: Select the Bearer downgrading check box if you want to permit bearer downgrading. Carrier: Under Potential Server Analysis Options, select the carrier for which you want the analysis to be carried out. You can either select "Best" or one or more carrier numbers from the list. This option is only available when either All or Potential Server Analysis is selected in the Results list above. The "Best" carrier will depend on the carrier selection method defined for the site equipment.
6. Click Calculate. Once the calculations for the new analysis are complete, an analysis will appear under the Analysis Group N in the Multi-point Analysis folder. For information on how to access the analysis results, see "Accessing Multi-point Analysis Results" on page 703
9.2.10.12.3
Accessing Multi-point Analysis Results To access the active set analysis results: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Multi-point Analysis folder.
703
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
3. Click the Expand button (
) to expand the analysis group containing the analysis whose results you want to access.
4. Right-click the analysis. The context menu appears. 5. Select Active Set Analysis Results from the context menu. The Active Set Analysis Results dialogue appears. The results include the following information: • • • • • • • • •
Load Conditions: The load conditions that were used when creating the analysis. Bearer Downgrading: Whether bearer downgrading was allowed for the calculations or not. X and Y: The coordinates of users who attempt to connect. Service: The services assigned to the users. Terminal: The terminals assigned to the users. Mobility: The mobility types assigned to the users. Carrier: The carrier used for the mobile-transmitter connection. Dual-cell HSDPA users are connected to two carriers. Frequency Band: The frequency band used for the mobile-transmitter connection. DL and UL Total Requested Rate (kbps): For circuit and packet (R99) service users, the DL and UL total requested rates correspond to the DL and UL nominal rates of the R99 bearer associated to the service. For packet (HSDPA) service users, the uplink total requested rate corresponds to the nominal rate of ADPCH-UL64 R99 bearer and the downlink total requested rate is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate that the selected HSDPA radio bearers can provide. Here, the HSDPA user is treated as if he is the only user in the cell and then, Atoll determines the HSDPA bearer the user would obtain by considering the entire HSDPA power available of the cell. For HSUPA bearer users, the uplink total requested rate is equal to the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate of the requested HSUPA radio bearer. The requested HSUPA radio bearer is selected from the HSUPA bearers compatible with the user equipment. Here, the HSUPA user is treated as if he is the only user in the cell and then, Atoll determines the HSUPA bearer the user would obtain by considering the entire remaining load of the cell. The downlink total requested rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate that the requested HSDPA radio bearers can provide.
•
DL and UL Total Obtained Rate (kbps): For circuit and packet (R99) service users, the DL or UL total obtained rate is the same as the DL or UL total requested rate if he is connected without being downgraded. Otherwise, the total obtained rate is lower (it corresponds to the nominal rate of the selected R99 bearer). If the user was rejected, the total obtained rate is zero. For a packet (HSDPA) service user connected to an HSDPA bearer, the uplink total obtained rate equals the requested one and the downlink total obtained rate corresponds to the instantaneous rate; this is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearers after scheduling and radio resource control. If the user is delayed (he is only connected to an R99 radio bearer), uplink and downlink total obtained rates correspond to the uplink and downlink nominal rates of ADPCH-UL64 radio bearer. Finally, if the user is rejected either in the R99 part or in the HSDPA part, the uplink and downlink total obtained rates are zero. For connected packet (HSPA - Best Effort) service users and packet (HSPA - Variable Bit Rate) service users, on uplink, if the user is connected to an HSUPA bearer, the uplink total obtained rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the selected HSUPA radio bearer after noise rise scheduling. On downlink, if the user is connected to an HSDPA bearer, the downlink total obtained rate corresponds to the instantaneous rate. The instantaneous rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearers after scheduling and radio resource control. If the user is delayed, the downlink total obtained rate corresponds to the downlink nominal rate of ADPCHEDPCCH 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 minimum throughput demand defined for the service. If the user is rejected, the uplink and downlink total obtained rates are "0".
• • • • • • •
Mobile Total Power (dBm): The mobile total power corresponds to the total power transmitted by the terminal. Connection Status: The connection status indicates whether the user is connected or rejected. If connected, the connection status corresponds to the activity status. If rejected, the rejection cause is given. Best Server: The best server among the transmitters in the mobile active set. HO Status (Sites/No. Transmitters Act. Set): The HO status is the number of sites compared to the number of transmitters in the active set. AS1, AS2, AS3, AS4: The name of the cell that is the best server, the second-best server, and so on is given in a separate column for each cell in the active set. Ec/I0 AS1, AS2, AS3, AS4, (dB): Ec⁄I0 is given in a separate column for each cell in the active set. The Ec/I0 AS 1 column lists the Ec/I0 from the best server for the rejected mobiles as well. Active Compressed Mode: This field indicates whether active compressed mode is supported by the mobile or not.
6. Click Close.
704
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
To access the potential server analysis results: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Multi-point Analysis folder.
3. Click the Expand button (
) to expand the analysis group containing the analysis whose results you want to access.
4. Right-click the analysis. The context menu appears. 5. Select Potential Server Analysis Results from the context menu. The Potential Server Analysis Results dialogue appears. The results include the following information: • • • • • • • • • • • • • • • • • •
Load Conditions: The load conditions that were used when creating the analysis. Shadowing taken into account: Whether shadowing was taken into account for the calculations or not. Cell Edge Coverage Probability: Used to calculate the shadowing margin if shadowing was taken into account. Indoor Coverage: Whether the points were considered to be indoor for the calculations. In this case, indoor losses were used in the calculations. Bearer Downgrading: Whether bearer downgrading was allowed for the calculations or not. Carrier: The carrier(s) for which the calculations were made. X and Y: The coordinates of users who attempt to connect. Service: The services assigned to the users. Terminal: The terminals assigned to the users. Mobility: The mobility types assigned to the users. Transmitter: Potential servers of the users for which the remaining parameters were calculated. Distance (m): Distances from the potential servers. Path Loss (dB): Path losses corresponding to the potential servers. RSCP (dBm): Received Signal Code Powers corresponding to the potential servers. Ec/Io (dB): Ec/Io corresponding to the potential servers. Eb/Nt DL (dB): Downlink Eb/Nt corresponding to the potential servers. Eb/Nt UL (dB): Uplink Eb/Nt corresponding to the potential servers. Scrambling code: Scrambling codes corresponding to the potential servers.
6. Click Close.
9.2.10.12.4
Defining the Display Properties of Multi-point Analysis Results You can display the multi-point analysis results on the map according to different parameters. To define the display properties of multi-point analysis results: 1. Select the Network explorer. 2. Right-click the Multi-point Analysis folder. The context menu appears. 3. Select Properties from the context menu. The Multi-point Analysis Properties dialogue appears. 4. On the Display tab of the dialogue, define the display properties of multi-point analysis results. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 43. 5. Click OK.
9.2.11 Planning Neighbours You can set neighbours for each cell manually, or you can let Atoll automatically allocate neighbours, based on the parameters that you define. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as possible neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as possible neighbours all the active and filtered cells whose propagation zone intersects a rectangle containing the computation zone. If there is no focus zone, Atoll allocates neighbours only to the cells within the computation zone. The focus and computation zones are taken into account whether or not they are visible. In other words, the focus and computation zones will be taken into account whether or not their visibility check box in the Zones folder of the Geo explorer 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 Zone or Hot Spot for a Coverage Prediction Report" on page 673. For information on grouping transmitters in the explorer window, see "Grouping Data Objects" on page 89. Atoll supports the following neighbour types in a UMTS network: •
Intra-technology Neighbours: Intra-technology neighbours are cells defined as neighbours that also use UMTS. Intratechnology neighbours can be divided into: •
Intra-carrier Neighbours: Cells defined as neighbours which perform handover using the same carrier.
705
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• •
© Forsk 2012
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 706 "Defining Exceptional Pairs" on page 706 "Configuring Importance Factors for Neighbours" on page 706 "Allocating Neighbours Automatically" on page 707 "Checking Automatic Allocation Results" on page 711 "Allocating and Deleting Neighbours per Cell" on page 714 "Calculating the Importance of Existing Neighbours" on page 717 "Checking the Consistency of the Neighbour Plan" on page 718 "Exporting Neighbours" on page 719.
9.2.11.1 Importing Neighbours You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table. To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Network explorer. b. Right-click the Transmitters folder. The context menu appears. c. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 82.
9.2.11.2 Defining Exceptional Pairs In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs can be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Select the Network explorer. 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 cell’s 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. Click the Edit button on the bottom-right of the dialogue. The exceptional pair list becomes editable. b. Select the cell from the list in the Neighbours column. c. In the Status column, select one of the following: • •
Forced: The selected cell will always be a neighbour of the reference cell. Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair. 9. Click OK. You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table by right-clicking the Transmitters folder and selecting Neighbours > Intra-Technology > Exceptional Pairs.
9.2.11.3 Configuring Importance Factors for Neighbours You can define the relative importance of the factors that Atoll uses to evaluate possible intra-technology neighbours (intraand inter-carrier) and inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide).
706
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
To configure the importance factors for intra-technology neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. Select the Intra-carrier Neighbours tab. On the Intra-carrier Neighbours tab, you can set the following importance factors: • • •
•
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency Factor will be used if you select the Force adjacent transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 707. 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 707.
5. Select the Inter-carrier Neighbours tab. On the Inter-carrier Neighbours tab, you can set the following importance factors: • • •
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. 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 707.
6. Click OK. •
•
You can configure the same importance factors for inter-technology neighbours by selecting Neighbours > Inter-technology > Configure Importance from the Transmitters folder context menu. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual.
9.2.11.4 Allocating Neighbours Automatically Atoll can automatically allocate both intra- and inter-carrier neighbours in a UMTS network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. By setting an option in the atoll.ini file, you can prevent Atoll from allocating inter-carrier neighbours to cells located on sites whose equipment does not support the compressed mode. For more information, see the Administrator Manual. To automatically allocate intra-carrier UMTS neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Click the Intra-Carrier Neighbours tab. You can set the following parameters: • • •
Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour. Max. No. of Neighbours: Set the maximum number of intra-carrier neighbours that can be allocated to a cell. This value can be either set here for all transmitters, or specified for each transmitter in the Cells table. 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.
707
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
• • • • • • •
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 the minimum Ec⁄I0 which must be provided by reference cell A in an overlapping area. Reference cell A must also be the best server in terms of pilot quality in the overlapping area. Ec⁄I0 Margin: Enter the maximum difference of Ec⁄I0 between reference cell A and possible neighbour cell B in the overlapping area. DL Load Contributing to I0: You can let Atoll base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value). Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses in the calculations.
% Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cell’s coverage area must overlap the reference cell’s 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 cell’s 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 cell’s 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 706. Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new neighbours to the list.
6. Click Calculate. Atoll begins the process of allocating intra-carrier neighbours. Atoll first checks to see whether the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. • • • • • •
Cell: The name of the reference cell. Number: The total number of neighbours allocated to the reference cell. Maximum Number: The maximum number of neighbours that the reference cell can have. Neighbour: The cell that will be allocated as a neighbour to the reference cell. Importance (%): The importance. For information on defining neighbour importance, see "Configuring Importance Factors for Neighbours" on page 706. 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 cell’s 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 Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69.
708
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
At this point you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document: •
Click Compare. The list of automatically allocated neighbours (those whose Commit check box is selected) is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: • • • •
The document name and the neighbour allocation type The number of created neighbour relations (new neighbour relations proposed in the automatic allocation results compared to the existing neighbour relations) and the list of these relations The number of deleted neighbour relations (neighbour relations not proposed in the automatic allocation 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 cell’s Properties dialogue. To automatically allocate inter-carrier UMTS neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > 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. Ec⁄I0: Enter the minimum Ec⁄I0 which must be provided by reference cell A and possible neighbour B in an overlapping area. Possible neighbour B must also be the best server in terms of pilot quality in the overlapping area. Ec⁄I0 Margin: Enter the Ec⁄I0 margin relative to the Ec⁄I0 of the reference cell A. See the Technical Reference Guide for an explanation of how the Ec⁄I0 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 cell’s coverage area must overlap the reference cell’s 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 706. 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.
709
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is cleared, the Results table will be empty. The Results table contains the following information. • • • • • •
Cell: The name of the reference cell. Number: The total number of neighbours allocated to the reference cell. Maximum Number: The maximum number of neighbours that the reference cell can have. Neighbour: The cell that will be allocated as a neighbour to the reference cell. Importance (%): The importance. For information on defining neighbour importance, see "Configuring Importance Factors for Neighbours" on page 706. 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 cell’s 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 Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. At this point you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document: •
Click Compare. The list of automically allocated neighbours (those whose Commit check box is selected) is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: • • • •
The document name and the neighbour allocation type 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 cell’s Properties dialogue. •
•
•
•
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint on the forbidden neighbour will be ignored by the algorithm because the neighbour already exists. When the options Force exceptional pairs and Force symmetry are selected, Atoll considers the constraints between exceptional pairs in both directions in order to respect symmetry. On the other hand, if the neighbour relation is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event Viewer. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Saving a User Configuration" on page 101.
Atoll also enables you to automatically allocate neighbours to a single base station or transmitter: • •
9.2.11.4.1
"Allocating Neighbours to a New Base Station" on page 710 "Allocating Neighbours to a New Transmitter" on page 711.
Allocating Neighbours to a New Base Station When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects with the coverage area of the cells of the new base station.
710
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
To allocate neighbours to a new base station: 1. In the Network explorer, group the transmitters by site, as explained in "Grouping Data Objects" on page 89. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Neighbours > Intra-technology Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 707.
9.2.11.4.2
Allocating Neighbours to a New Transmitter When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new transmitters and other cells whose coverage area intersects the coverage area of the cells of the new transmitter. To allocate neighbours to a new transmitter: 1. Select the Network explorer. 2. In the Transmitters folder, right-click the new transmitter. The context menu appears. 3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 707.
9.2.11.5 Checking Automatic Allocation Results You can verify the results of automatic neighbour allocation in the following ways: • •
9.2.11.5.1
"Displaying Neighbour Relations on the Map" on page 711 "Displaying the Coverage of Each Neighbour of a Cell" on page 713.
Displaying Neighbour Relations on the Map You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Display Options from the context menu. The Neighbour Display dialogue appears. 4. Under Intra-technology Neighbours, select the Display links check box. 5. Click the Browse button (
) beside the Display links check box.
6. The Intra-technology Neighbour Display dialogue appears. 7. From the Display Type list, choose one of the following: • •
•
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 cell’s 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 cell’s neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors. 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 Type’s Data Table" on page 71.
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.
711
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
For information on changing display properties, see "Display Properties of Objects" on page 43. 8. Select the Add to legend check box to add the displayed neighbour links to the legend. 9. Click the Browse button ( ) next to Tip text and select the neighbour characteristics to be displayed in the tip text. This information will be displayed on each neighbour link. 10. Click OK to save your settings. 11. Under Advanced, select which neighbour links to display: • • •
Outwards non-symmetrical: Select the Outwards non-symmetrical check box to display neighbour relations where the selected cell is the reference cell and where the neighbour relation is not symmetric. Inwards non-symmetrical: Select the Inwards non-symmetrical check box to display neighbour relations where the selected cell is neighbour and where the neighbour relation is not symmetric. Symmetric links: Select the Symmetric links check box to display neighbour relations that are symmetric between the selected cell and the neighbour.
12. Click OK to save your settings. 13. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
14. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 15. Click the Edit Relations on the Map button (
) in the Radio Planning toolbar.
16. Select a transmitter to show its neighbour links: •
•
•
In the Transmitters folder of the Network explorer: Select the transmitter in the Transmitters folder. The selected transmitter is centred in the map and all its neighbours are indicated. Atoll displays the selected transmitter in the Neighbours table if it is open. On the map: Select the transmitter on the map. The neighbours of the selected transmitter are displayed on the map. 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 41). Atoll displays the selected transmitter in the Neighbours table if it is open. In the Neighbours table: Select the transmitter-neighbour relation you want to display by clicking in the left margin of the table row to select the entire row. The selected transmitter is centred in the map with the selected transmitter-neighbour relation (see Figure 9.34). The selected transmitter is also displayed in the Transmitters folder of the Network explorer.
Figure 9.34: Selecting a transmitters in the Neighbours table Atoll displays the following information (see Figure 9.35) for the selected cell: • • •
712
The symmetrical neighbour relations of the selected (reference) cell are indicated by a line. The outward neighbour relations are indicated with a line ending in an arrow pointing at the neighbour (e.g., see Site1_2(0)) in Figure 9.35.). 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 9.35.).
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
In Figure 9.35, neighbour links are displayed according to the neighbour. Therefore, the symmetrical and outward neighbour links are coloured the same as the corresponding neighbour transmitters and the inward neighbour link is coloured the same as the reference transmitter because it is neighbour of Site9_3(0) here.
Figure 9.35: Intra-carrier Neighbours of Site 22_3(0) - Display According to the Neighbour In Figure 9.36, neighbour links are displayed according to the neighbour carrier. You can view intra-carrier and intercarrier neighbour links. In Figure 9.36, all neighbour relations are symmetrical.
Figure 9.36: Intra-carrier and Inter-Carrier Neighbours of Site 14_3(0) You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
9.2.11.5.2
Displaying the Coverage of Each Neighbour of a Cell By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cell’s neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a "Coverage by transmitter" prediction, with the Display Type set to "Discrete Values" and the Field set to "Transmitter" (for information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by Transmitter" on page 669). 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Display Options from the context menu. The Neighbour Display dialogue appears.
713
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
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 cell’s 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 cell’s neighbours according to a value from the Intra-technology Neighbours table. Value Intervals: Select "Value Intervals" to colour the coverage area of a cell’s neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s 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 tip text. This information will be displayed on each coverage area. 9. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 11. Click the Edit Relations on the Map button (
) in the Radio Planning 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 41). Only intra-carrier neighbour coverage areas are displayed.
13. In order to restore colours and cancel the neighbour display, click the Edit Relations on the Map button ( Radio Planning toolbar.
) in the
9.2.11.6 Allocating and Deleting Neighbours per Cell Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of the Transmitter Properties dialogue. This section explains the following: • • •
"Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 714 "Allocating or Deleting Neighbours Using the Neighbours Table" on page 715 "Allocating or Deleting Neighbours on the Map" on page 716.
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 transmitter’s 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 transmitter’s 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 cell’s 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: • •
714
Max number inter-carrier Max number intra-carrier
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
To allocate a new neighbour: 1. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. 2. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon (
).
3. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Source to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: 1. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. 2. Click in the left margin of the table row containing the neighbour to select the entire row. 3. Right-click the neighbour in the Neighbour column. The context menu appears. 4. 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: 1. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. 2. Click in the left margin of the table row containing the neighbour to select the entire row. 3. Right-click the neighbour in the Neighbour column. The context menu appears. 4. 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: 1. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. 2. Click in the left margin of the table row containing the neighbour to select the entire row. 3. Press DEL to delete the neighbour. Allocating or Deleting Neighbours Using the Neighbours Table To allocate or delete UMTS neighbours using the Neighbours table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears. For information on working with data tables, see "Working with Data Tables" on page 69.
To allocate a neighbour: 1. In the row marked with the New Row icon (
), select a reference cell in the Cell column.
2. Select the neighbour in the Neighbour column. 3. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Source to "manual," and sets the Importance to "1." To create a symmetrical neighbour relation: 1. Click in the left margin of the table row containing the neighbour to select the entire row. 2. Right-click the neighbour in the Neighbour column. The context menu appears. 3. Select Make Symmetrical from the context menu. A symmetrical neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column. To make several neighbour relations symmetrical: 1. Click in the left margin of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. 2. Right-click the Neighbours table. The context menu appears. 3. Select Make Symmetrical from the context menu.
715
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
To take all exceptionnal pairs into consideration: 1. Right-click the Neighbours table. The context menu appears. 2. Select Force Exceptional Pairs from the context menu. You can add or delete some forced neighbours or some forbidden neighbours using the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table, select the exceptional pairs, right-click the table and select Force Exceptional Pairs in the context menu. To delete a symmetrical neighbour relation: 1. Click in the left margin of the table row containing the neighbour to select the entire row. 2. Right-click the Neighbours table. The context menu appears. 3. Select Delete Link and Symmetric Relation from the context menu. The symmetrical neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. To delete several symmetric neighbour relations: 1. Click in the left margin of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. 2. Right-click the Neighbours table. The context menu appears. 3. Select Delete Link and Symmetric Relation from the context menu. To delete a neighbour relation: 1. Click in the left margin of the table row containing the neighbour to select the entire row. 2. Press DEL to delete the neighbour. Allocating or Deleting Neighbours on the Map You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 711. To add a symmetrical neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters to the intra-technology neighbours list. To remove a symmetrical neighbour relation: 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. • •
716
If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric intertechnology neighbour relation.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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. •
•
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 41). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
9.2.11.7 Calculating the Importance of Existing Neighbours After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours in the AFP process. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Calculate Importance from the context menu. The Neighbour Importance Evaluation dialogue appears. 4. Select the Intra-carrier Neighbours tab. 5. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as possible neighbours. 6. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 706): • •
Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that neighbours are adjacent to their reference transmitters when calculating importance. Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.
7. Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: • • •
• •
• •
Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell and the neighbour. Min. Ec/Io: Enter the minimum Ec⁄Io which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage. Ec/Io Margin: Enter the Ec/Io margin to define the area of coverage overlapping between UMTS cells. DL Load Contributing to Io: Under DL Load Contributing to Io, select whether you want Atoll to base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value). Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell Edge Coverage Probability. Indoor Coverage: If desired, select the Indoor Coverage check box. Atoll will then calculate additional losses for indoor coverage.
8. Click OK to save your modifications and close the Coverage Conditions dialogue. 9. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 706): 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:
717
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• • •
• •
• •
© Forsk 2012
Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell and the neighbour. Min. Ec/Io: Enter the minimum Ec⁄Io which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage. Ec/Io Margin: Enter the Ec/Io margin to define the area of coverage overlapping between UMTS cells. DL Load Contributing to Io: Under DL Load Contributing to Io, select whether you want Atoll to base the interference ratio on the total power used as defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global Value). Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and enter a Cell 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. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. 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
Coverage: The amount of reference transmitter’s coverage area that the neighbour overlaps, in percentage and in square kilometres. Adjacency: The area of the reference transmitter, in percentage and in square kilometres, where the neighbour transmitter is best server or second best server. This information is not relevant for inter-carrier neighbours and is therefore not present on the Inter-carrier Neighbours tab. Distance: The distance in kilometres between the reference cell and the neighbour.
13. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
9.2.11.8 Checking the Consistency of the Neighbour Plan You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the intra-technology neighbour allocation plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Define the parameters of the audit: • •
718
Neighbourhood Type: Select whether you want to perform an audit on Intra-Carrier or Inter-Carrier neighbour relations. Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
• •
•
• • • •
Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Which cells having the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Lists > Max Number: Which cells having more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that must not be exceeded.
5. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: •
Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax:
•
Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax:
•
|CELL|
|CELL| |NUMBER| |MAX NUMBER|
Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Syntax:
|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:
•
Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
|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| You can perform an audit of the inter-technology neighbour allocation plan by selecting Neighbours > Inter-technology > Audit from the Transmitters folder context menu.
9.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. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears.
719
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
3. Select Neighbours > and then select the neighbour table containing the data you want to export from the context menu: • • • •
Intra-technology > Open Table: This table contains the data for the intra-technology (intra-carrier and inter-carrier) neighbours in the current Atoll document. Inter-technology > Open Table: This table contains the data for the inter-technology neighbours in the current Atoll document. Intra-technology > Exceptional Pairs: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document. Inter-technology > Exceptional Pairs: This table contains the data for the inter-technology exceptional pairs (forced and forbidden) in the current Atoll document.
4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files and Spreadsheets" on page 80.
9.2.12 Planning Scrambling Codes In UMTS, 512 scrambling codes are available, numbered from 0 to 511. Although UMTS scrambling codes are displayed in decimal format by default, they can also be displayed and calculated in hexadecimal format, in other words using the numbers 0 to 9 and the letters A to F. Atoll facilitates the management of scrambling codes by letting you create groups of scrambling codes and domains, where each domain is a defined set of groups. You can also assign scrambling codes manually or automatically to any cell in the network. Once allocation is completed, you can audit the scrambling codes, view scrambling code reuse on the map, and make an analysis of scrambling code distribution. The procedure for planning scrambling codes for a UMTS project is: •
Preparing for scrambling code allocation • • •
•
"Defining the Scrambling Code Format" on page 720 "Creating Scrambling Code Domains and Groups" on page 721 "Defining Exceptional Pairs for Scrambling Code Allocation" on page 721.
Allocating scrambling codes • •
"Automatically Allocating Scrambling Codes to UMTS Cells" on page 722 "Allocating Scrambling Codes to UMTS Cells Manually" on page 724.
•
"Checking the Consistency of the Scrambling Code Plan" on page 724.
•
Displaying the allocation of scrambling codes • • • • • •
"Using Find on Map to Display Scrambling Code Allocation" on page 725 "Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 726 "Grouping Transmitters by Scrambling Code" on page 726 "Displaying the Scrambling Code Allocation Histogram" on page 727 "Making a Scrambling Code Collision Zones Prediction" on page 727. "Making a Scrambling Code Collision Analysis" on page 728 • •
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.
9.2.12.1 Defining the Scrambling Code Format Scrambling codes can be displayed in decimal or hexadecimal format. The selected format is used to display scrambling codes in dialogues and tables such as in the Domains and Groups tables, the Cells table, and the Scrambling Code Allocation dialogue. The decimal format is the default format in Atoll. The accepted decimal values are from 0 to 511. The decimal format is also used, even if you have chosen the hexadecimal format, to store scrambling codes in the database and to display scrambling code distribution or the results of a scrambling code audit. The hexadecimal format uses the numbers 0 to 9 and the letters A to F for its base characters. In Atoll, hexadecimal values are indicated by a lower-case "h" following the value. For example, the hexadecimal value "3Fh" is "63" as a decimal value.
720
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
You can convert a hexadecimal value to a decimal value with the following equation, where A, B, and C are decimal values within the hexadecimal index ranges: 2
A × 16 + B × 16 + C
For example, the hexadecimal value "3Fh" would be calculated as shown below: 2
0 × 16 + 3 × 16 + 15 = 63
To define the scrambling code format for an Atoll document: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Right-click the Scrambling Codes folder. The context menu appears. 4. Select Format from the context menu and select either Decimal or Hexadecimal.
9.2.12.2 Creating Scrambling Code Domains and Groups Atoll facilitates the management of scrambling codes by letting you create domains, each containing groups of scrambling codes. The procedure for managing scrambling codes in a UMTS document consists of the following steps: 1. Creating a scrambling code domain, as explained in this section. 2. Creating groups, each containing a range of scrambling codes, and assigning them to a domain, as explained in this section. 3. Assigning a scrambling code domain to a cell or cells. If there is no scrambling code domain, Atoll will consider all 512 possible scrambling codes when assigning codes. To create a scrambling code domain: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Scrambling Codes folder.
4. Right-click Domains in the Scrambling Codes folder. The context menu appears. 5. Select Open Table from the context menu. The Domains table appears. 6. In the row marked with the New Row icon (
), enter a Name for the new domain.
7. Click in another cell of the table to create the new domain and add a new blank row to the table. 8. Double-click the domain to which you want to add a group. The domain’s Properties dialogue appears. 9. Under Groups, enter the following information for each group you want to create. • •
• • • •
Name: Enter a name for the new scrambling code group. Min.: Enter the lowest available primary scrambling code in this group’s 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 720). Max: Enter the highest available primary scrambling code in this group’s range. Step: Enter the separation interval between each primary scrambling code. Excluded: Enter the scrambling codes in this range that you do not want to use. Extra: Enter any additional scrambling codes (i.e., outside the range defined by the Min. and Max fields) you want to add to this group. You can enter a list of codes separated by either a comma, semi-colon, or a space. You can also enter a range of scrambling codes separated by a hyphen. For example, entering, "1, 2, 3-5" means that the extra scrambling codes are "1, 2, 3, 4, 5."
10. Click in another cell of the table to create the new group and add a new blank row to the table.
9.2.12.3 Defining Exceptional Pairs for Scrambling Code Allocation You can also define pairs of cells which cannot have the same primary scrambling code. These pairs are referred to as exceptional pairs. Exceptional pairs are used along with other constraints, such as neighbours, reuse distance, and domains, in allocating scrambling codes. To create a pair of cells that cannot have the same scrambling code: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears.
721
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
3. Select Primary Scrambling Codes > Exceptional Pairs. The Exceptional Separation Constraints table appears. For information on working with data tables, see "Working with Data Tables" on page 69. 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.
9.2.12.4 Allocating Scrambling Codes Atoll can automatically assign scrambling codes to the cells of a UMTS network according to set parameters. For example, it takes into account the definition of groups and domains of scrambling codes, the selected scrambling code allocation strategy (clustered, distributed per cell, distributed per site and one cluster per site), minimum code reuse distance, and any constraints imposed by neighbours. You can also allocate scrambling codes manually to the cells of a UMTS network. In this section, the following methods of allocating scrambling codes are described: • • •
"Defining Automatic Allocation Constraint Violation Costs" on page 722 "Automatically Allocating Scrambling Codes to UMTS Cells" on page 722 "Allocating Scrambling Codes to UMTS Cells Manually" on page 724.
Defining Automatic Allocation Constraint Violation Costs You can define the costs of the different types of constraints used in the automatic scrambling code allocation algorithm. To define the different constraint violation costs: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Primary Scrambling Codes > Constraint Costs. The Constraint Violation Costs dialogue appears. In this dialogue you can define the following costs of constraint violations for the automatic allocation process (the cost is a value from 0 to 1): • • • • •
Under Intra-technology Neighbours, you can set the constraint violation cost for 1st Order, 2nd Order, and 3rd Order neighbours. Under Distributed per Site Strategy, you can set the constraint violation cost for intra-technology neighbours that are 1st or 2nd Order Using the Same Cluster. Reuse Distance: Enter the maximum cost for reuse distance constraint violations. Exceptional Pair: Enter the cost for exceptional pair constraint violations. Common Inter-technology Neighbour: Enter the cost for inter-technology neighbour constraint violations.
4. Click OK. The constraint violation costs are stored and will be used in the automatic allocation. Automatically Allocating Scrambling Codes to UMTS Cells The allocation algorithm enables you to automatically allocate primary scrambling codes to cells in the current network. You can choose among several automatic allocation strategies. The actual automatic allocation strategies available will depend on your network and options selected in the atoll.ini file. For more information on the atoll.ini file, see the Administrator Manual. For more information on automatic allocation strategies, see the Technical Reference Guide. • • •
•
Clustered: The purpose of this strategy is to choose for a group of mutually constrained cells, scrambling codes among a minimum number of clusters. In this case, Atoll will preferentially allocate all the codes from the same cluster. Distributed per Cell Allocation: This strategy consists in using as many clusters as possible. Atoll will preferentially allocate codes from different clusters. One Cluster per Site: This strategy allocates one cluster to each base station, then, one code of the cluster to each cell of each base station. When all the clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses the clusters at another base station. Distributed per Site: This strategy allocates a group of adjacent clusters to each base station in the network, then, one cluster to each transmitter of the base station according to its azimuth and finally one code of the cluster to each cell of each transmitter. The number of adjacent clusters per group depends on the number of transmitters per base station you have in your network; this information is required to start allocation based on this strategy. When all the groups of adjacent clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses the groups of adjacent clusters at another base station.
To automatically allocate primary scrambling codes: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Primary Scrambling Codes > Automatic Allocation. The Primary Scrambling Codes dialogue appears.
722
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
Under Constraints, you can set the constraints on automatic scrambling code allocation. •
Existing Neighbours: Select the Existing Neighbours check box if you want to consider intra-carrier neighbour relations and then choose the neighbourhood level to take into account: Neighbours of a cell are referred to as the first order neighbours, neighbours’ neighbours are referred to as the second order neighbours and neighbours’ neighbours’ neighbours as the third order neighbours. First Order: No cell will be allocated the same scrambling code as its neighbours. Second Order: No cell will be allocated the same scrambling code as its neighbours or its second order neighbours. Third Order: No cell will be allocated the same scrambling code as its neighbours or its second order neighbours or its third order neighbours. Atoll can only consider neighbour relations if neighbours have already been allocated. For information on allocating neighbours, see "Planning Neighbours" on page 705. 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 793
•
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 cell’s 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. Ec⁄I0: Enter the minimum Ec⁄I0 which must be provided by reference cell A in an area with overlapping coverage. Reference cell A must also be the best server in terms of pilot quality in the area with overlapping coverage. Ec⁄I0 Margin: Enter the maximum difference of Ec⁄I0 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.
• •
From the Strategy list, you can select an automatic allocation strategy: • • • •
• •
Exceptional Pairs: Select the Exceptional Pairs check box, if you want to the automatic allocation process to consider the exceptional pair constraints. Clustered Distributed per Cell One Cluster per Site Distributed per Site
Carrier: Select the Carrier on which you want to run the allocation. You may choose one carrier (Atoll will assign primary scrambling codes to transmitters using the selected carrier) or all of them. No. of Codes per Cluster: According to 3GPP specifications, the number of codes per cluster is 8. If you want, you can change the number of codes per cluster. When the allocation is based on a distributed strategy (Distributed per Cell or Distributed per Site), this parameter can also be used to define the interval between the primary scrambling codes assigned to cells on a same site.
723
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
The defined interval is applied by setting an option in the atoll.ini file. For more information about setting options in the atoll.ini file, see the Administrator Manual. •
•
•
Use a Max of Codes: Select the Use a Max of Codes check box to make Atoll use the maximum number of codes. For example, if there are two cells using the same domain with two scrambling codes, Atoll will assign the remaining code to the second cell even if there are no constraints between these two cells (for example, neighbour relations, reuse distance, etc.). If you do not select this option, Atoll only checks the constraints, and allocates the first ranked code in the list. Delete Existing Codes: Select the Delete Existing Codes check box if you want Atoll to delete currently allocated scrambling codes and recalculate all scrambling codes. If you do not select this option, Atoll will keep currently allocated scrambling codes and will only allocate scrambling codes to cells that do not yet have codes allocated. Allocate Carriers Identically: Select the Allocate Carriers Identically check box if you want Atoll to allocate the same primary scrambling code to each carrier of a transmitter. If you do not select this option, Atoll allocates scrambling codes independently for each carrier.
4. Click Calculate. Atoll begins the process of allocating scrambling codes. Once Atoll has finished allocating scrambling codes, the codes are visible under Results. Atoll only displays newly allocated scrambling codes. 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. Cluster: The cluster the scrambling code belongs to.
5. Click Commit. The primary scrambling codes are committed to the cells. You can save automatic scrambling code allocation parameters in a user configuration. For information on saving automatic scrambling code allocation parameters in a user configuration, see "Saving a User Configuration" on page 101.
•
•
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 transmitter’s context menu. If you need to allocate scrambling codes to all the cells on group of transmitters, you can allocate them automatically by selecting Primary Scrambling Codes > Automatic Allocation from the transmitter group’s context menu.
Allocating Scrambling Codes to UMTS Cells Manually When you allocate scrambling codes to a large number of cells, it is easiest to let Atoll allocate scrambling codes automatically, as described in "Automatically Allocating Scrambling Codes to UMTS Cells" on page 722. However, if you want to add a primary scrambling code to one cell or to modify the primary scrambling code of a cell, you can do it by accessing the properties of the cell. To allocate a scrambling code to a UMTS cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate a scrambling code. The context menu appears. 2. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 3. Select the Cells tab. 4. Enter a Primary Scrambling Code in the cell’s column. 5. Click OK.
9.2.12.5 Checking the Consistency of the Scrambling Code Plan Once you have completed allocating scrambling codes, you can verify whether the allocated scrambling codes respect the specified constraints by performing an audit of the plan. The scrambling code audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Primary Scrambling Codes > Audit. The Code and Cluster Audit dialogue appears.
724
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
4. In the Code and Cluster Audit dialogue, select the allocation criteria that you want to check: • •
No. of Codes per Cluster: Enter the number of scrambling codes per cluster. Neighbours: Select Neighbours to check scrambling code constraints between cells and their neighbours and then choose the neighbourhood level to take into account: • • •
First Order: Atoll will check that no cell has the same scrambling code as any of its neighbours. Second Order Neighbours: Atoll will check that no cell has the same scrambling code as any of its neighbours or any of the neighbours of its neighbours. Third Order Neighbours: Atoll will check that no cell has the same scrambling code as any of its neighbours or any of the neighbours of its neighbours or any of the neighbours of its second order neighbours.
The report will list the cells and the neighbours that do not meet any of these constraints. In addition, it will indicate the allocated primary scrambling code and the neighbourhood level. •
•
•
• •
•
Neighbours in Different Clusters: If you select the Neighbours in different clusters check box, Atoll will check that neighbour cells have scrambling codes from different clusters. The report will list any neighbour cells that do have scrambling codes from the same cluster. Domain Compliance: If you select the Domain Compliance check box, Atoll will check if allocated scrambling codes belong to domains assigned to cells. The report will list any cells with scrambling codes that do not belong to domains assigned to the cell. Site Domains Not Empty: If you select the Site Domains Not Empty check box, Atoll will check for and list base stations for which the allocation domain (i.e., the list of possible scrambling codes) is not consistent with the "One cluster per site" strategy. If there is a base station with N cells, Atoll will check that the domains assigned to the cells contain at least one cluster consisting of N codes. If you plan to automatically allocate scrambling codes using the "One Cluster per Site" strategy, you can perform this test beforehand to check the consistency of domains assigned to cells of each base station. One Cluster per Site: If you select the One Cluster per Site check box, Atoll will check for and list base stations whose cells have scrambling codes coming from more than one cluster. Distance: If you select the Distance check box and set a reuse distance, Atoll will check for and list the cell pairs that do not respect the reuse distance condition. For any cell pair, Atoll uses the lowest of the reuse distance values defined in the properties of the two cells and the value that you set in the Code and Cluster Audit dialogue. 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.
9.2.12.6 Displaying the Allocation of Scrambling Codes Once you have completed allocating scrambling codes, you can verify several aspects of scrambling code allocation. You have several options for displaying scrambling codes: • • • • • •
"Using Find on Map to Display Scrambling Code Allocation" on page 725 "Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 726 "Grouping Transmitters by Scrambling Code" on page 726 "Displaying the Scrambling Code Allocation Histogram" on page 727 "Making a Scrambling Code Collision Zones Prediction" on page 727. "Making a Scrambling Code Collision Analysis" on page 728
Using Find on Map to Display Scrambling Code Allocation In Atoll, you can search for scrambling codes and scrambling code groups using the Find on Map tool. Results are displayed in the map window in red. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Scrambling codes and scrambling code groups and any potential problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 669. To find scrambling codes or scrambling code groups using the Find on Map tool: 1. Click Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "Scrambling Code." 3. Select what you what you want to search for: • •
Scrambling code: If you want to find a scrambling code, select Scrambling code and select it from the list. SC Group: If you want to find a scrambling code group, select SC group and select it from the list.
4. Select the carrier you want to search on from the For carrier list, or select "(All)" to search in all carriers.
725
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
5. Click Search. Transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match the search criteria are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Find on Map window. Displaying Scrambling Code Allocation Using Transmitter Display Settings You can use the display characteristics of transmitters to display scrambling code-related information. To display scrambling code-related information on the map: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties 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 transmitter’s 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 transmitter’s cell, select "Discrete values" as the Display Type and "Cells: Scrambling Code Domain" as the Field.
You can display the following information in the transmitter label or tip text by clicking the Label or Tip Text Browse button ( • • •
):
Primary scrambling code: To display the primary scrambling code of a transmitter’s cell in the transmitter label or tip text, "Cells: Primary Scrambling Code" from the Label or Tip Text Field Definition dialogue. Scrambling code domain: To display the primary scrambling code domain of a transmitter’s cell in the transmitter label or tip text, "Cells: Scrambling Code Domain" from the Label or Tip Text Field Selection dialogue. Scrambling code reuse distance: To display the scrambling code reuse distance of a transmitter’s cell in the transmitter label or tip text, "Cells: SC Reuse Distance" from the Label or Tip Text Field Selection dialogue.
5. Click OK. For information on display options, see "Display Properties of Objects" on page 43. Grouping Transmitters by Scrambling Code You can group transmitters in the Network explorer by their primary scrambling code, their scrambling code domain, or by their scrambling code reuse distance. To group transmitters by scrambling code: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available Fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: • • •
Scrambling Code Domain Primary Scrambling Code SC Reuse Distance
7. Click to add the parameter to the Grouping Fields list. The selected parameter is added to the list of parameters on which the transmitters will be grouped. 8. If you do not want the transmitters to be sorted by a certain parameter, select it in the Grouping Fields list and click . The selected parameter is removed from the list of parameters on which the transmitters will be grouped. 9. Arrange the parameters in the Grouping Fields list in the order in which you want the transmitters to be grouped: a. Select a parameter and click
to move it up to the desired position.
b. Select a parameter and click
to move it down to the desired position.
10. Click OK to save your changes and close the Group dialogue.
726
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
If a transmitter has more than one cell, Atoll cannot arrange the transmitter by cell. Transmitters that cannot be grouped by cell are arranged in a separate folder under the Transmitters folder. Displaying the Scrambling Code Allocation Histogram You can use a histogram to analyse the use of allocated scrambling codes in a network. The histogram represents the scrambling codes or scrambling code clusters as a function of the frequency of their use. To display the scrambling code histogram: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Primary Scrambling Codes > Code Distribution. The Distribution Histograms dialogue appears. Each bar represents a scrambling code or a cluster, its height depending on the frequency of its use. 4. Select Scrambling Codes to display scrambling code use and Clusters to display scrambling code cluster use. 5. Move the pointer over the histogram to display the frequency of use of each scrambling code or cluster. The results are highlighted simultaneously in the Zoom on selected values list. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. Making a Scrambling Code Collision Zones Prediction You can make a scrambling code collision zone prediction to view areas covered by cells using the same scrambling code. Atoll checks on each pixel if one or more cell whose Ec/Io is higher than the threshold defined in the user’s mobility type has the same scrambling code as the user’s best serving cell. If so, Atoll considers that there is scrambling code collision. To make a scrambling code collision zone prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Scrambling Code Collision 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab. Select "(Cells Table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and the DL total power defined in the cell properties. 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 682. You must also select which Carrier is to be considered. If you want the scrambling code collision zone prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. You can also select the Indoor Coverage check box to add indoor losses. 7. Click the Display tab. For a scrambling code collision zone prediction, the Display Type "Discrete Values" based on the Field "Transmitter" is selected by default. Each pixel where there is scrambling code collision is displayed with the same colour as that
727
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
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 43. You can also set parameters to display the following results: •
•
The number of interferers for each transmitter: Select "Value Intervals" as the Display Type and "No. of Interferers per Transmitter" as the Field. In the explorer window, the coverage prediction results are arranged by interfered transmitter. The total number of interferers on one pixel: Select "Value Intervals" as the Display Type and "No. of Interferers" as the Field. In the explorer window, the coverage prediction results are arranged according to the number of interferers.
8. Click the Calculate button ( ) in the Radio Planning toolbar to calculate the scrambling code collision zone prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Making a Scrambling Code Collision Analysis The SC Collisions tab of the Point Analysis window gives you information on reception for any point on the map where there is scrambling code collision. Scrambling code collision occurs when one or more cell whose Ec/Io is higher than the threshold defined in the user’s mobility type has the same scrambling code as the user’s best serving cell. When there is scrambling code collision, Atoll displays the pilot quality (Ec⁄I0) received from interfered and interferer transmitters. The analysis is based on the UL load percentage and the DL total power of each cell. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility, and a service. You can make a scrambling code collision analysis to verify a scrambling code collision zone prediction. In this case, before you make the scrambling code collision analysis, ensure the coverage prediction you want to use in the scrambling code collision analysis is displayed on the map. To make a scrambling code collision analysis: 1. Click the Point Analysis button (
) on the toolbar. The Point Analysis window appears.
2. At the top of the Point Analysis window, select the SC Collisions view. 3. At the top of the SC Collisions view, select "Cells Table" from Load conditions. 4. If you are making a scrambling code collision analysis to verify a coverage prediction, you can recreate the conditions of the coverage prediction: a. Select the same Terminal, Service, and Mobility studied in the coverage prediction. b. Select the Carrier studied in the coverage prediction. c. Click the Options button ( • • •
) to display the Calculation Options dialogue. You can change the following:
Change the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and, select "Ec⁄I0" from the Shadowing Margin list. Select the Indoor Coverage check box to add indoor losses.
d. Click OK to close the Properties dialogue. If you are making a scrambling code collision analysis to make a prediction on a defined point, you can use the instructions in this step to define a user.
5. Move the pointer over the map to make a scrambling code collision analysis for the current location of the pointer. 6. 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 (
728
) on the toolbar again to end the point analysis.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9.3 Studying Network Capacity A UMTS network automatically regulates power on both uplink and downlink with the objective of minimising interference and maximising network capacity. In the case of HSDPA, the network uses A-DCH power control in the uplink and downlink and a fast link adaptation (in other words, the selection of an HSDPA bearer) in the downlink. Atoll can simulate these network regulation mechanisms, thereby enabling you to study the capacity of the UMTS network. In Atoll, a simulation is based on a realistic distribution of R99 and HSDPA users at a given point in time. The distribution of users at a given moment is referred to as a snapshot. Based on this snapshot, Atoll calculates various network parameters such as the active set for each mobile, the required power of the mobile, the total DL power and DL throughput per cell, and the UL load per cell. Simulations are calculated in an iterative fashion. When several simulations are performed at the same time using the same traffic information, the distribution of users will be different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snapshot to another. To create snapshots, services and users must be modelled. As well, certain traffic information in the form of traffic maps must be provided. Once services and users have been modelled and traffic maps have been created, you can make simulations of the network traffic. In this section, the following are explained: • • • •
"Defining Multi-service Traffic Data" on page 729 "Creating a Traffic Map" on page 729 "Calculating and Displaying Traffic Simulations" on page 739 "Analysing the Results of a Simulation" on page 760.
9.3.1 Defining Multi-service Traffic Data The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: •
•
•
•
R99 radio bearers: Bearer services are used by the network for carrying information. The R99 Radio Bearer table lists all the available radio bearers. You can create new R99 radio bearers and modify existing ones by using the R99 Radio Bearer table. For information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 798. Services: Services are the various services, such as voice, mobile internet access, etc., available to subscribers. These services can be either circuit-switched or packet-switched. For information on modelling end-user services, see "Modelling UMTS HSPA Services" on page 682. 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. Ec⁄I0 requirements and Eb⁄Nt targets per radio bearer and per link (uplink or downlink) are largely dependent on mobile speed. For information on creating a mobility type, see "Creating a UMTS HSPA Mobility Type" on page 685. Terminals: In UMTS, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a car’s on-board navigation device. For information on creating a terminal, see "Modelling UMTS HSPA Terminals" on page 685.
9.3.2 Creating a Traffic Map The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atoll provides three types of traffic maps for UMTS projects. • • •
Sector traffic map User profile traffic map User density traffic map (number of users per km2)
These maps can be created using different types of traffic data sources as follows: •
Sector traffic maps can be used if you have live traffic data from the OMC (Operation and Maintenance Centre). The OMC (Operations and Maintenance Centre) collects data from all cells in a network. This includes, for example, the number of users or the throughput in each cell and the traffic characteristics related to different services. Traffic is spread over the best server coverage area of each transmitter and each coverage area is assigned either the throughputs in the uplink and in the downlink or the number of users per activity status or the total number of users (including all activity statuses). For more information, see "Creating a Sector Traffic Map" on page 730.
•
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
729
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
page 733, "Importing a User Profile Environment Based Traffic Map" on page 735, and "Creating a User Profile Environment Based Traffic Map" on page 735. •
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 736, "Creating a User Density Traffic Map" on page 737, "Converting 2G Network Traffic" on page 738 and "Exporting Cumulated Traffic" on page 738.
9.3.2.1 Creating a Sector Traffic Map This section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands in the uplink and in the downlink, the number of users per activity status, or the total number of users including all activity statuses. A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by Transmitter" on page 669. To create a sector traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector Traffic Map. 5. Select the type of traffic information you want to input. You can choose between Uplink and Downlink Throughputs, Total Number of Users (All Activity Statuses) or Number of Users per Activity Status. 6. Click the Create button. The Sector Traffic Map dialogue appears. You can also import a traffic map from a file by clicking the Import button. You can import AGD (Atoll Geographic Data) format files that you have exported from an other Atoll document. 7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter. 8. Enter the data required in the Sector Traffic Map dialogue: • • •
If you have selected Uplink and Downlink Throughputs, enter the throughput demands in the uplink and downlink for each sector and for each listed service. If you have selected Total Number of Users (All Activity Statuses), enter the number of connected users for each sector and for each listed service. If you have selected Number of Users per Activity Status, enter the number of inactive users, the number of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each service. You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 82.
9. Click OK. The Sector Traffic Map Properties dialogue appears. 10. Select the Traffic tab. 11. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must equal 100. 12. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must equal 100. 13. Under Clutter Distribution, for each clutter class, enter: • •
A weight to spread the traffic over the vector. The percentage of indoor users. An additional loss will be counted for indoor users during Monte-Carlo simulations.
14. Click OK. Atoll creates the traffic map in the Traffic Maps folder. You can modify the sector traffic map after it has been created.
730
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
To modify the sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Traffic Maps folder.
3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 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 669. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Traffic Maps 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 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 738.
9.3.2.2 Creating a User Profile Traffic Map The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There might also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create user profile traffic maps. A user profile models the behaviour of different subscriber categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for circuit-switched calls) or uplink and downlink volume (for packet-switched calls). Environment classes are used to describe the distribution of subscribers on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km²). The sections "Importing a User Profile Traffic Map" on page 733, "Importing a User Profile Environment Based Traffic Map" on page 735 and "Creating a User Profile Environment Based Traffic Map" on page 735 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 731 "Modelling Environments" on page 732.
Modelling User Profiles You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user can be considered a business user during the day, with video conferencing and voice, but no web
731
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Traffic Parameters folder.
3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles New Element Properties dialogue appears. 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 UMTS HSPA Services" on page 682. Terminal: Select a terminal from the list. For information on terminals, see "Modelling UMTS HSPA Terminals" on page 685. Calls/Hour: For circuit-switched services, enter the average number of calls per hour for the service. The number of calls per hour is used to calculate the activity probability. For circuit-switched services, one call lasting 1000 seconds presents the same activity probability as two calls lasting 500 seconds each. For packet-switched services, the Calls/Hour value is defined as the number of sessions per hour. A session is like a call in that it is defined as the period of time between when a user starts using a service and when he stops using a service. In packet-switched services, however, he may not use the service continually. For example, with a webbrowsing service, a session starts when the user opens his browsing application and ends when he quits the browsing application. Between these two events, the user might be downloading web pages and other times he may not be using the application, or he might be browsing local files, but the session is still considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and not by the time. In order for all the services defined for a user profile to be taken into account during traffic scenario elaboration, the sum of activity probabilities must be lower than 1.
• • •
Duration: For circuit-switched services, enter the average duration of a call in seconds. For packet-switched services, this field is left blank. UL Volume: For packet-switched services, enter the average uplink volume per session in kilobytes. DL Volume: For packet-switched services, enter the average downlink volume per session in kilobytes.
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. Select the Network explorer. 2. Click the Expand button (
) to expand the Traffic 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. 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: •
732
User: Select a user profile.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
• •
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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
For example: An area of 10 km² with a subscriber density of 100/km². Therefore, in this area, there are 1000 subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in the Building clutter class. 10. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss.
9.3.2.2.1
Importing a User Profile Traffic Map User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscribers⁄km, or polygons with a number of subscribers⁄km²) with a user profile, mobility type, and traffic density assigned to each vector. To import a user profile traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile densities from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Density Traffic Map" on page 737. 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 map’s properties dialogue appears. 11. Select the Traffic tab (see Figure 9.37). Under Traffic fields, you can specify the user profiles to be considered, their mobility type (km⁄h), and their density. If the file you are 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.
733
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Figure 9.37: Traffic map properties dialogue - Traffic tab Define each of the following: •
•
•
User profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points. When you import user profile or mobility information from the file, the values in the file must be exactly the same as the corresponding names in the Traffic Parameters folder in the Parameters explorer. If the imported user profile or mobility does not match, Atoll will display a warning.
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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
13. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss. 14. Click OK to finish importing the traffic map.
734
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9.3.2.2.2
Importing a User Profile Environment Based Traffic Map Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 735. 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 map’s 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 Traffic Parameters in the Parameters explorer. For more information, see "Modelling Environments" on page 732. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 43.
9.3.2.2.3
Creating a User Profile Environment Based Traffic Map Atoll enables you to create a user profile environment traffic map based on by drawing it in the map window. To draw a traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 9.38).
Draw Map
Delete
Figure 9.38: 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.
735
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
9.3.2.2.4
© Forsk 2012
Displaying Statistics on a User Profile Environment Traffic Map You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Traffic Maps folder.
3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears. The Statistics window lists the surface (Si in km²) and the percentage of surface (% of i) for each environment class "i" S
i - × 100 within the focus zone. The percentage of surface is given by: % of i = -------------
Sk k
You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.
9.3.2.3 Creating User Density Traffic Maps (No. Users/km2) User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit of surface, i.e., the density of users, as input. This can be either the density of users per activity status or the density of users including all activity statuses. In this section, the following ways of creating a user density traffic map are explained: • •
"Importing a User Density Traffic Map" on page 736 "Creating a User Density Traffic Map" on page 737.
User density traffic maps can be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. for more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 738.
9.3.2.3.1
Importing a User Density Traffic Map The user density traffic map defines the density of users per pixel. For a traffic density of X users per km², Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined on the Traffic tab of the traffic map’s properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select 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.
736
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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 737. 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 map’s 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. 16. Click OK. Atoll creates the traffic map in the Traffic Maps folder.
9.3.2.3.2
Creating a User Density Traffic Map Atollenables you to create a user density traffic map by drawing it in the map window. To draw a user density traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (Number of users per km2). 5. Select the type of traffic information you input: • • • • •
All Activity Statuses: Select All Activity Statuses if the map you are drawing provides a density of users with any activity status. Active in Uplink: Select Active in Uplink if the map you are drawing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are drawing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are drawing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are drawing provides a density of inactive users.
6. Click the Create button. The traffic map’s 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 Maps 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 Editor toolbar to draw contours. For more information on editing contours, see "Editing Polygons, Lines, and Points" on page 61.
737
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
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.
9.3.2.3.3
Creating User Density Traffic Maps from Sector Traffic Maps You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. To create user density traffic maps from a sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Traffic Maps folder.
3. Right-click the sector traffic map from which you want to create user density traffic maps. The context menu appears. 4. Select Create density maps from the context menu. Atoll creates as many user density traffic maps as the number of services present in the sector traffic map. The user density map files use the resolution of the coverage prediction used for the sector traffic map and are embedded in the document.
9.3.2.4 Converting 2G Network Traffic Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km² for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as user density traffic maps into your UMTS document. These maps can then be used in traffic simulations like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 738, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 736. To import a 2G traffic map into a UMTS document: 1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 438. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 738. 3. Import the traffic exported in step 2 in your UMTS document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 736.
9.3.2.5 Exporting Cumulated Traffic Atollallows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user densities. The cumulated traffic is exported in 32-bit BIL, ArcView© Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Select the Geo explorer. 2. Right-click the Traffic Maps 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.
738
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
You must enter a resolution before exporting. If you do not enter a resolution, it remains at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic data to be exported. • •
• •
Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal. Service: Select the service that will be exported, select "All circuit services" to export traffic using any circuit service, "All packet services" to export traffic using any packet service, or select the specific type of service: HSDPA, HSUPA, mobile internet access, multimedia messaging service, video conferencing, or voice. Mobility: Select the mobility type that will be exported or select "All" to export all mobility types. Activity: Select one of the following: • • • • •
All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status. Uplink: Select Uplink to export mobiles active in the uplink only. Downlink: Select Downlink to export mobiles active in the downlink only. Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity. Inactive: Select Inactive to export only inactive mobiles.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the cumulated traffic. 10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
9.3.3 Exporting a Traffic Map To export a traffic map: 1. Select the Geo explorer. 2. Click the Expand button (
) to expand the Traffic Maps folder.
3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save. If you are exporting a raster traffic map, you have to define: •
The Export Region: • • •
•
Entire Project Area: Saves the entire traffic map. Only Pending Changes: Saves only the modifications made to the map. Computation Zone: Saves only the part of the traffic map inside the computation zone.
An export Resolution.
9.3.4 Calculating and Displaying Traffic Simulations Once you have modelled the network services and users and have created traffic maps, you can create simulations. The simulation process consists of two steps: 1. Obtaining a realistic user distribution: Atoll generates a user distribution using a Monte-Carlo algorithm; this user distribution is based on the traffic database and traffic maps and is weighted by a Poisson distribution between simulations of the same group. Each user is assigned a service, a mobility type, and an activity status by random trial, according to a probability law that uses the traffic database. The user activity status is an important output of the random trial and has direct consequences on the next step of the simulation and on the network interferences. A user can be either active or inactive. Both active and inactive users consume radio resources and create interference. Then, Atoll randomly assigns a shadowing error to each user using the probability distribution that describes the shadowing effect. Finally, another random trial determines user positions in their respective traffic zone (possibly according to the clutter weighting and the indoor ratio per clutter class). 2. Modelling network power control: Atoll uses a power control algorithm for R99 users, and an algorithm mixing A-DPCH power control and fast link adaptation for HSDPA users and an additional loop modelling noise rise scheduling
739
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
for HSUPA users. The power control simulation algorithm is described in "The Power Control Simulation Algorithm" on page 740.
9.3.4.1 The Power Control Simulation Algorithm The power control algorithm (see Figure 9.39) simulates the way a UMTS network regulates itself by using uplink and downlink power controls in order to minimise interference and maximise capacity. HSDPA users (i.e., Packet (HSDPA - Best Effort), Packet (HSPA - Best Effort), Packet (HSDPA - Variable Bit Rate), Packet (HSPA - Variable Bit Rate) and Packet (HSPA Constant Bit Rate) service users) are linked to the A-DPCH radio bearer (an R99 radio bearer). Therefore, the network uses an A-DPCH power control on UL and DL and then performs fast link adaptation on DL in order to select an HSDPA radio bearer. For HSUPA users (i.e., Packet (HSPA - Best Effort), Packet (HSPA - Variable Bit Rate) and Packet (HSPA - Constant Bit Rate) service users), the network first uses an E-DPCCH/A-DPCH power control on UL and DL, checks that there is an HSDPA connection on downlink and then carries out noise rise scheduling in order to select an HSUPA radio bearer on uplink. Atoll simulates these network regulation mechanisms for each user distribution. During each iteration of the algorithm, all the mobiles (i.e., Circuit (R99), Packet (R99), Packet (HSDPA - Best Effort), Packet (HSPA - Best Effort), Packet (HSDPA - Variable Bit Rate), Packet (HSPA - Variable Bit Rate), and Packet (HSPA - Constant Bit Rate) service users) selected during the user distribution generation attempt to connect one by one to network transmitters. The process is repeated until the network is balanced, i.e., until the convergence criteria (on UL and DL) are satisfied. Initialisation
R99 part
Mi Best Server Determination
Mi Active Set Determination
For HSDPA users, this part of the algorithm is performed for the A-DPCH bearer (R99 bearer) For HSUPA users, this part is performed for the E-DPCCH/ADPCH bearer (R99 bearer)
For each R99, HSDPA and HSUPA mobile, Mi
UL Power Control
DL Power Control
UL and DL Interference Update
Congestion and Radio Resource Control
HSDPA part For each HSDPA and HSUPA mobile, Mi
Fast Link Adaptation
Mobile Scheduling
Radio Resource Control
HSUPA part Admission Control For each HSUPA mobile, Mi Noise Rise Scheduling
Radio Resource Control
Convergence Study
Figure 9.39: Schematic view of simulation algorithm As shown in Figure 9.39, the simulation algorithm is divided in three parts. All users are evaluated by the R99 part of the algorithm. HSDPA and HSUPA bearer users, unless they have been rejected during the R99 part of the algorithm, are then evaluated by the HSDPA part of the algorithm. Finally, HSUPA bearer users, unless they have been rejected during the R99 or HSDPA parts of the algorithm, are then evaluated by the HSUPA part of the algorithm. Description of the R99 Portion of the Simulation The R99 part of the algorithm simulates power control, congestion and radio resource control performed for R99 bearers for all users. Atoll considers each user in the order established during the generation of the user distribution and determines his best server and his active set. Atoll first calculates the required terminal power in order to reach the Eb⁄Nt threshold requested by the R99 bearer on UL, followed by the required traffic channel power in order to reach the Eb⁄Nt threshold requested by the R99 bearer on DL. After calculating power control, Atoll updates the cell load parameters. Atoll then carries out congestion and radio resource control, verifying the cell UL load, the total power transmitted by the cell, the number of channel elements, the Iub throughput and OVSF codes consumed by the cell. In dual-cell HSDPA, A-DPCH is only transmitted on one of the two carriers (called the anchor carrier). Therefore, dual-cell HSDPA users consume the same amount of R99 resources as single-cell HSDPA users. The R99 bearer is allocated to dual-cell HSDPA users on their best serving cell.
740
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
At this point, users can be either connected or rejected. They are rejected if: •
The signal quality is not sufficient: • • •
•
On the downlink, the pilot quality is not high enough (no cell in the user active set): the status is "Ec⁄I0 < (Ec⁄I0)min" On the downlink, the power required to reach the user is greater than the maximum allowed: the status is "Ptch > PtchMax" On the uplink, there is not enough power to transmit: the status is "Pmob > PmobMax"
Even if constraints above are respected, the network can be saturated: • • • • •
The maximum uplink load factor is exceeded (at admission or congestion): the status is either "Admission Rejection" or "UL Load Saturation" There are not enough channel elements on site: the status is "Ch. Elts Saturation" The maximum Iub backhaul throughput on site is exceeded: the status is "Iub Throughput Saturation" There is not enough power for cells: the status is "DL Load Saturation" There are no more OVSF codes available: the status is "OVSF Code Saturation"
Description of the HSDPA Portion of the Simulation In the HSDPA part, Atoll processes all HSDPA bearer users, i.e., Packet (HSDPA - Best Effort), Packet (HSPA - Best Effort), Packet (HSDPA - Variable Bit Rate), Packet (HSPA - Variable Bit Rate) and Packet (HSPA - Constant Bit Rate) service users. The HSDPA part of the algorithm simulates fast link adaptation, the scheduling of HSDPA bearer users, and radio resource control on downlink. For dual-cell HSDPA users, fast link adaptation is done once for each carrier. For a dual-cell HSDPA user, the first carrier is the one selected in the R99 part according to the carrier selection method chosen in the site equipment, and the second carrier is the one that provides the best CQI. Therefore, dual-cell HSDPA users have two HSDPA bearers (possibly different ones depending on the available HSDPA power in each cell), and consume HSDPA resources in both cells. Their throughputs are the sum of the throughputs provided by the two HSDPA bearers. HSDPA bearer selection is based on look-up tables, available by double-clicking the corresponding entry in the Reception Equipment table, found in the Terminals context menu. HSDPA bearer selection depends on reported CQI, UE and cell capabilities as detailed in the following diagramme.
[ Figure 9.40: HSDPA bearer selection The HSDPA and HS-SCCH powers of a cell are evaluated before calculating HS-PDSCH Ec⁄Nt. The available HSDPA power (the power dedicated to HS-SCCH and HS-PDSCH of HSDPA bearer users) of a cell can be either fixed (statically allocated) or dynamically allocated. If it is dynamically allocated, the power allocated to HSDPA depends on how much power is required to serve R99 traffic. In other words, the power available after all common channels (including the power for downlink HSUPA channels) and all R99 traffic have been served is allocated to HS-PDSCH and HS-SCCH of HSDPA bearer users. Similarly, the power per HS-SCCH can be either fixed or dynamically allocated in order to attain the HS-SCCH Ec⁄Nt threshold. Using the HS-SCCH and HSDPA powers, Atoll evaluates the HS-PDSCH power (the difference between the available HSDPA power and the HS-SCCH power), calculates the HS-PDSCH Ec⁄Nt and, from that, the corresponding CQI (from the graph CQI=f(HS-PDSCH Ec⁄Nt) defined for the terminal reception equipment and the user mobility). Then, Atoll reads the best HSDPA bearer associated to this CQI (i.e., it reads the Best Bearer=f(HS-PDSCH CQI) from the table defined for the terminal reception equipment and the user mobility) and checks if it is compatible with the user equipment and cell capabilities. If compatible, Atoll selects the HSDPA bearer. Otherwise, it downgrades the HSDPA bearer to a lower one until the selected HSDPA bearer is compatible with the user equipment and cell capabilities. For Best Effort service users, the selected HSDPA bearer is the best HSDPA bearer that the user can obtain. For Variable Bit Rate service users, Atoll downgrades the HSDPA bearer to a lower one if the associated RLC peak rate exceeds the maximum throughput demand defined for the service. Downgrading occurs until the RLC peak rate of the selected HSDPA bearer is lower than the maximum throughput demand. Additionally, the selected HSDPA bearer must provide a RLC peak rate higher than the minimum throughput demand defined for the service. For Packet (HSPA - Constant Bit Rate) service users, HS-SCCH-less operation (i.e., HS-DSCH transmissions without any accompanying HS-SCCH) is performed. In this case, the UE is not informed about the transmission format and has to revert to blind decoding of the transport format used on the HS-DSCH. Complexity of blind detections in the UE is decreased by limiting the transmission formats that can be used (i.e., the HSDPA bearers available). Therefore, only HSDPA bearers using QPSK modulation and a maximum of two HS-PDSCH channels can be selected and allocated to the user. Additionally, the selected HSDPA bearer must provide a RLC peak rate higher than the minimum throughput demand defined for the service. Two CQI values are calculated for dual-cell HSDPA users, one for each carrier, and two HSDPA bearers are determined. 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 scheduler manages the maximum number of users within each cell and
741
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
shares the cell’s 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 minimum throughput demand defined for the service. To achieve the highest cell capacity, the scheduler can hold several packets over a TTI (Transmission Time Interval). Atollmodels this "intelligent scheduling" by allowing several Packet (HSPA - Constant Bit Rate) service users to share the same HSDPA bearer. Then, Atoll calculates the HSDPA bearer consumption for each user and takes into account this parameter when it determines the resources consumed by the user (i.e., the HSDPA power used, the number of OVSF codes, and the Iub backhaul throughput). Atoll checks if enough codes and Iub backhaul throughput are available for the user (taking into account the maximum number of OVSF codes defined for the cell and the maximum Iub backhaul throughput allowed on the site in the downlink). If not, Atoll allocates a lower HSDPA bearer ("downgrading") which needs fewer OVSF codes and consumes lower Iub backhaul 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 minimum throughput demand: the status is "HSDPA Resource Saturation" The HS-SCCH signal quality is not sufficient: the status is "HSDPA Resource Saturation" There are no more OVSF codes available: the status is "HSDPA Resource Saturation" The maximum Iub backhaul throughput allowed on the site in the downlink is exceeded: the status is "HSDPA Resource Saturation"
After processing the Packet (HSPA - Constant Bit Rate) service users, Atoll processes the remaining HSDPA bearer users (i.e., Packet (HSDPA - Variable Bit Rate), Packet (HSPA - Variable Bit Rate), Packet (HSDPA - Best Effort) and Packet (HSPA - Best Effort) service users) without exceeding the maximum number of users within each cell. Variable Bit Rate service users have the highest priority and are managed before Best Effort service users. For each type of service, the scheduler ranks the users according to the selected scheduling technique: •
• •
Max C/I: "n" users (where "n" corresponds to the maximum number of HSDPA 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 cell’s 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 if enough codes and Iub backhaul throughput are available for the user (taking into account the maximum number of OVSF codes defined for the cell and the maximum Iub backhaul throughput allowed on the site in the downlink). If not, Atoll allocates a lower HSDPA bearer ("downgrading") which needs fewer OVSF codes and consumes lower Iub backhaul throughput. For Variable Bit Rate services, if no OVSF codes are available, the user is rejected. At the same time, if the maximum Iub backhaul throughput allowed on the site in the downlink is still exceeded, the user is rejected. At this point, Variable 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 minimum throughput demand: the status is "HSDPA Resource Saturation" There are no more HS-SCCH channels available: the status is "HS-SCCH Channels Saturation" The HS-SCCH signal quality is not sufficient: the status is "HSDPA Resource Saturation" There are no more OVSF codes available: the status is "HSDPA Resource Saturation" The maximum Iub backhaul throughput allowed on the site in the downlink is exceeded: the status is "HSDPA Resource Saturation"
For Best Effort services, if no OVSF codes are available, the user is delayed. At the same time, if the maximum Iub backhaul throughput allowed on the site in the downlink is still exceeded even by using the lowest HSDPA bearer, the user is delayed. At this point, Best Effort 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: • • • • •
742
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 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Description of the HSUPA Portion of the Simulation In the HSUPA part, Atoll processes Packet (HSPA - Best Effort) service users, Packet (HSPA - Variable Bit Rate) service users and Packet (HSPA - Constant Bit Rate) service users who are connected to an HSDPA bearer or were delayed in the previous step. It manages the maximum number of users within each cell. Packet (HSPA - Constant Bit Rate) service users have the highest priority and are processed first, in the order established during the generation of the user distribution. Then, Atoll considers Packet (HSPA - Variable Bit Rate) service users in the order established during the generation of the user distribution and lastly, it processes Packet (HSPA - Best Effort) service users in the order established during the generation of the user distribution. The HSUPA part of the algorithm simulates an admission control on the HSUPA bearer users followed by noise rise scheduling and radio resource control. Atoll first selects a list of HSUPA bearers that are compatible with the user equipment capabilities for each HSUPA bearer user. For Packet (HSPA - Constant Bit Rate) service users, the list is restricted to HSUPA bearers that provide a RLC peak rate higher than the minimum throughput demand. Then, during admission control, Atoll checks that the lowest compatible bearer in terms of the required E-DPDCH Ec⁄Nt does not require a terminal power higher than the maximum terminal power allowed. Then, Atoll performs the noise rise scheduling on Packet (HSPA - Constant Bit Rate) service users, followed by a radio resource control. The noise rise scheduling algorithm attempts to evenly share the remaining cell load between the users admitted in admission control; in terms of HSUPA, each user is allocated a right to produce interference. The remaining cell load factor on uplink depends on the maximum load factor allowed on uplink and how much uplink load is produced by the served R99 traffic. From this value, Atoll calculates the maximum E-DPDCH Ec⁄Nt allowed and can select an HSUPA bearer. The HSUPA bearer is selected based on the values in a look-up table, and depends on the maximum E-DPDCH Ec⁄Nt allowed and on UE capabilities. You can open the HSUPA Bearer Selection table by clicking the Expand button ( ) to expand the UMTS Network Settings folder in the Parameters explorer, and then rightclicking the Reception Equipment folder and selecting Open Table from the context menu. Atoll selects the best HSUPA bearer from the HSUPA compatible bearers, in other words, the HSUPA bearer with the highest potential throughput where the required E-DPDCH Ec/Nt is lower than the maximum E-DPDCH Ec⁄Nt allowed and the required terminal power is lower than the maximum terminal power. In this section, the potential throughput refers to the ratio between the RLC peak rate and the number of retransmissions. When several HSUPA bearers are available, Atoll selects the one with the lowest required E-DPDCH Ec⁄Nt. Several Packet (HSPA - Constant Bit Rate) service users can share the same HSUPA bearer. Atoll calculates the HSUPA bearer consumption for each user and takes into account this parameter when it determines the resources consumed by each user (i.e., the terminal power used, the number of channel elements and the Iub backhaul throughput). Finally, Atoll carries out radio resource control on Packet (HSPA - Constant Bit Rate) service users. Atoll checks to see if enough channel elements and Iub backhaul throughput are available for the HSUPA bearer assigned to the user (taking into account the maximum number of channel elements defined for the site and the maximum Iub backhaul throughput allowed on the site in the uplink). If not, Atoll allocates a lower HSUPA bearer ("downgrading") which needs fewer channel elements and consumes lower Iub backhaul throughput. If no channel elements are available, the user is rejected. On the same hand, if the maximum Iub backhaul throughput allowed on the site in the uplink is still exceeded even by using the lowest HSUPA bearer, the user is rejected. At this point, Packet (HSPA - Constant Bit Rate) service users can be either connected, or rejected. They are rejected if: • • • • •
The maximum number of HSUPA users per cell is exceeded: the status is "HSUPA Scheduler Saturation". The terminal power required to obtain the lowest compatible HSUPA bearer exceeds the maximum terminal power in the admission control: the status is "Pmob > PmobMax". The lowest compatible HSUPA bearer they can obtain does not provide a RLC peak rate higher than the minimum throughput demand: the status is "HSUPA Admission Rejection". There are no more channel elements available: the status is "Ch. Elts Saturation" The maximum Iub backhaul throughput allowed on the site in the uplink is exceeded: the status is "Iub Throughput Saturation".
Then, Atoll processes Packet (HSPA - Variable Bit Rate) service users. For these users, the list of compatible bearers is restricted to HSUPA bearers that provide a RLC peak rate between the maximum and the minimum throughput demands. Atoll performs a new noise rise scheduling and distributes the remaining cell load factor available after all Packet (HSPA Constant Bit Rate) service users have been served. From this value, Atoll selects an HSUPA bearer for each Packet (HSPA Variable Bit Rate) service user. Finally, Atoll carries out radio resource control on Packet (HSPA - Variable 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.
743
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
At this point, Packet (HSPA - Variable 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 minimum throughput demand: the status is "HSUPA Admission Rejection". There are no more channel elements available: the status is "Ch. Elts Saturation". The maximum Iub backhaul throughput allowed on the site in the uplink is exceeded: the status is "Iub Throughput Saturation".
Then, Atoll processes Packet (HSPA - Best Effort) service users. It performs a new noise rise scheduling and distributes the remaining cell load factor available after all Packet (HSPA - Constant Bit Rate) and Packet (HSPA - Variable Bit Rate) service users have been served. From this value, Atoll selects an HSUPA bearer for each Packet (HSPA - Best Effort) service user. Then, Atoll checks that each Packet (HSPA - Best Effort) service user has obtained the average requested rate (defined in the properties of the service). Finally, Atoll carries out radio resource control, verifying whether enough channel elements and Iub backhaul throughput are available for the HSUPA bearer assigned to the user (taking into account the maximum number of channel elements defined for the site and the maximum Iub backhaul throughput allowed on the site in the uplink). If not, Atoll allocates a lower HSUPA bearer ("downgrading") which needs fewer channel elements and consumes lower Iub backhaul throughput. If no channel elements are available, the user is rejected. On the same hand, if the maximum Iub backhaul throughput allowed on the site in the uplink is still exceeded even by using the lowest HSDPA bearer, the user is rejected. At this point, Packet (HSPA - Best Effort) service users can be either connected, or rejected. They are rejected if: • • • •
The maximum number of HSUPA users per cell is exceeded: the status is "HSUPA Scheduler Saturation". The terminal power required to obtain the lowest compatible HSUPA bearer exceeds the maximum terminal power in the admission control: the status is "Pmob > PmobMax". There are no more channel elements available: the status is "Ch. Elts Saturation" The maximum Iub backhaul throughput allowed on the site in the uplink is exceeded: the status is "Iub Throughput Saturation".
Bearer Downgrading If you select the option "Bearer Downgrading," when creating a simulation, R99, HSDPA and HSUPA service users can be downgraded under certain circumstances. When the downgrading is allowed, Atoll does not reject R99, HSDPA and HSUPA users directly; it downgrades them first. The R99 to R99 bearer downgrading occurs when: •
The cell resources are insufficient when the user is admitted •
•
The cell resources are insufficient during congestion control • • • • •
•
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
The user maximum connection power is exceeded during power control: • •
On the downlink, the maximum traffic channel power is exceeded On the uplink, the maximum terminal power is exceeded
For all these reasons, the user’s 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.
744
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9.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. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name and Comments for this simulation or group of simulations. 5. Under Execution on the General tab, you can set the following parameters: • •
Number of simulations: Enter the number of simulations to be carried out. All simulations created at the same time are grouped together in a folder in the Network explorer. Information to retain: You can select the level of detail that will be available in the output: •
Only the Average Simulation and Statistics: None of the individual simulations are displayed or available in the group. Only an average of all simulations and statistics is available. Some calculation and display options available for coverage predictions are not available when the option "Only the Average Simulation and Statistics" is selected.
•
• •
No Information About Mobiles: All the simulations are listed and can be displayed. For each of them, a properties window containing simulation output, divided among four tabs — Statistics, Sites, Cells, and Initial Conditions — is available. Standard Information About Mobiles: All the simulations are listed and can be displayed. The properties window for each simulation contains an additional tab with output related to mobiles. Detailed Information About Mobiles: All the simulations are listed and can be displayed. The properties window for each simulation contains additional mobile-related output on the Mobiles and Mobiles (Shadowing Values) tabs. When you are working on very large radio-planning projects, you can reduce memory consumption by selecting Only the Average Simulation and Statistics under Information to retain.
6. Under Load constraints on the General tab, you can set the constraints that Atoll must respect during the simulation: • • • • •
Number of CEs: Select the Number of CEs check box if you want Atoll to respect the number of channel elements defined for each site. Iub throughputs: Select the Iub throughputs check box if you want Atoll to respect the maximum Iub backhaul throughputs defined for each site. Number of codes: Select the Number of codes check box if you want Atoll to respect the number of OVSF codes available each cell. UL load factor: If you want the UL load factor to be considered in the simulation, select the UL load factor check box. Max UL load factor: If you want to enter a global value for the maximum uplink cell load factor, click the button (
• •
) beside the box and select Global value. Then, enter a maximum uplink cell load factor. If you want to use the
maximum uplink cell load factor as defined in the properties for each cell, click the button ( ) beside the box and select Defined per cell. DL load (% Pmax): If you want the DL load to be considered in the simulation, select the DL load (% Pmax) check box and enter a maximum downlink cell load in the Max DL load box. Max DL load (% Pmax): If you want to enter a global value for the maximum downlink cell load, as a percentage of the maximum power, click the button ( ) beside the box and select Global value. Then, enter a maximum downlink cell load, as a percentage of the maximum power. If you want to use the maximum downlink cell load factor as defined in the properties for each cell, click the button (
) beside the box and select Defined per cell.
7. Under Bearer negotiation on the General tab, check the Bearer downgrading check box if you want to permit bearer downgrading during the simulation. When a constraint is not respected, user radio bearers with services supporting bearer downgrading are downgraded. If the constraint is still not satisfied after downgrading, users are rejected. If downgrading is not selected, users will be rejected immediately, starting with users with the lowest service priority, if a constraint can not be respected.
745
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
8. On the Traffic tab, enter the following: •
Global scaling factor: If desired, enter a scaling factor to increase user density. The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps).
•
Select traffic maps to be used: Select the traffic maps you want to use for the simulation. You can select traffic maps of any type. However, if you have several different types of traffic maps and want to make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 729.
9. Click the Advanced tab. 10. Under Generator initialisation, enter an integer as the generator initialisation value. If you enter "0", the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value. Using the same generated user and shadowing error distribution for several simulations can be useful when you want to compare the results of several simulations where only one parameter changes. 11. Under Convergence, enter the following parameters: • • •
Max number of iterations: Enter the maximum number of iterations that Atoll should run to make convergence. UL convergence threshold: Enter the relative difference in terms of interference and connected users on the uplink that must be reached between two iterations. DL convergence threshold: Enter the relative difference in terms of interference and connected users on the downlink that must be reached between two iterations.
12. Once you have defined the simulation, you can calculate it immediately or you can save it to calculate it later: • •
Calculate: Click Calculate to save the defined simulation and calculate it immediately. OK: Click OK to save the defined simulation without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
All simulations created at the same time are grouped together in a folder in the Network explorer. You can now use the completed simulations for specific UMTS and HSDPA coverage predictions (see "Making Coverage Predictions Using Simulation Results" on page 761) or for an AS analysis using the Point Analysis window (see "Making an AS Analysis of Simulation Results" on page 760).
9.3.4.3 Displaying the Traffic Distribution on the Map Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to service, activity status, pilot signal strength, or soft handover gain. You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 43. In this section are the following examples of traffic distribution: • • •
"Displaying the Traffic Distribution by Handover Status" on page 746 "Displaying the Traffic Distribution by Connection Status" on page 747 "Displaying the Traffic Distribution by Service" on page 748. 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 Windows" on page 38.
9.3.4.3.1
Displaying the Traffic Distribution by Handover Status In this example, the traffic distribution is displayed by the handover status.
746
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
To display the traffic distribution by the handover status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "HO Status (Sites/No. Transmitters Act. Set)" as the Field. 5. Click OK. The traffic distribution is now displayed by handover status (see Figure 9.41).
Figure 9.41: Displaying the traffic distribution by handover status
9.3.4.3.2
Displaying the Traffic Distribution by Connection Status In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Connection Status" as the Field. 5. Click OK. The traffic distribution is now displayed by connection status (see Figure 9.42).
Figure 9.42: Displaying the traffic distribution by connection status
747
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
9.3.4.3.3
© Forsk 2012
Displaying the Traffic Distribution by Service In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 9.43).
Figure 9.43: Displaying the traffic distribution by service
9.3.4.4 Displaying the User Active Set on the Map Atoll enables you to display on the map the active set for each user generated by a simulation. To display the active set for a user: •
On the map, click and hold the icon of the user whose best and second-best servers you want to display. The servers in the user’s active set are connected to the user with lines the same colour as the serving transmitter. The best server is indicated with the number "1", the second-best with number "2" and so on. Figure 9.44 shows a user with three servers in his active set.
Figure 9.44: The active set of a user
9.3.4.5 Displaying the Results of a Single Simulation After you have created a simulation, as explained in "Creating Simulations" on page 745, you can display the results. To access the results of a single simulation: 1. Select the Network explorer. 2. Click the Expand button (
748
) to expand the Simulations folder.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
3. Click the Expand button ( want to access.
) to expand the folder of the simulation group containing the simulation whose results you
4. Right-click the simulation. The context menu appears. 5. Select Properties from the context menu. The simulation properties dialogue appears. One tab gives statistics of the results of the simulation. Other tabs in the simulation properties dialogue contain simulation results as identified by the tab title. A final tab lists the initial conditions of the simulation. The amount of detail available when you display the results depends on the level of detail you selected from the Information to retain list on the General tab of the properties dialogue for the group of simulations. For more information on the different options, see step 5. of "Creating Simulations" on page 745. The Statistics tab: The Statistics tab contains the following two sections: •
Demand: Under Demand, you will find data on the connection requests: • • •
•
Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; power control has not yet finished. The result depends on the traffic description and traffic input. During the first random trial, each user is assigned a service and an activity status. The number of users per activity status and the UL and DL rates that all active users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and UL and DL rates) is given.
Results: Under Results, you will find data on connection results: • •
• •
•
•
The number of iterations that were run in order to converge. The number and the percentage of rejected users is given along with the reason for rejection. These figures include rejected users only. These figures are determined at the end of the simulation and depend on the network design. The number and the percentage of delayed users is given along with the reason for delay. The number and percentage of R99 bearer users connected to a cell, the number of users per frequency band for a dual-band network, the number of users per activity status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPA and HSUPA bearer users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm. These data are also given per service. The total number and the percentage of connected users with an HSDPA bearer, the number of users per frequency band for a dual-band network, the number of users per activity status, and the DL total rate that they generate. Packet (HSDPA - Best Effort), Packet (HSPA - Best Effort), Packet (HSDPA - Variable Bit Rate), Packet (HSPA - Variable Bit Rate), and Packet (HSPA - Constant Bit Rate) service users are considered because they all request an HSDPA bearer. The total number of connected HSUPA bearer users and the percentage of users with an HSUPA bearer, the number of users per frequency band for a dual-band network, the number of users per activity status, and the UL total rate they generate. Only Packet (HSPA - Best Effort), Packet (HSPA - Variable Bit Rate) 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. 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 users for HS Channels in the downlink.
749
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• • • •
© Forsk 2012
Nb of Recommended E1/T1/Ethernet Link: The number of E1/T1/Ethernet links required to provide the total Iub backhaul throughput. Instantaneous HSDPA Rate (kbps): The Instantaneous HSDPA Rate (kbps). Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps). DL and UL Throughput for Each Service: The throughput in kbits⁄s for each service. The result is detailed on the downlink and uplink only when relevant.
The Cells tab: The Cells tab contains the following information, per site, transmitter, and carrier: • • • • •
• • • • • •
• •
Max Power (dBm): The maximum power as defined in the cell properties. Pilot Power (dBm): The pilot power as defined in the cell properties. SCH power (dBm): The SCH power as defined in the cell properties. Other CCH power (dBm): The power of other common channels. It includes the other CCH power and the DL HSUPA power as defined in the cell properties. Available HSDPA Power (dBm): The available HSDPA power as defined in the cell properties. This is the power available for the HS-PDSCH and HS-SCCH. The value is either fixed by the user when the HSDPA power is allocated statically, or by a simulation when the option HSDPA Power Dynamic Allocation is selected. AS Threshold (dB): The active set threshold as defined in cell properties Gain (dBi): The gain as defined in the antenna properties for that transmitter. Reception Losses (dB): The reception losses as defined in the transmitter properties. Transmission Losses (dB): The transmission losses as defined in the transmitter properties. Noise Figure (dB): The noise figure as defined in the transmitter properties Total Transmitted R99 Power (dBm): The total transmitted R99 power is the power transmitted by the cell on common channels (Pilot, SCH, other CCH), HSUPA channels (E-AGCH, E-RGCH, and E-HICH) and R99 traffic-dedicated channels. Transmitted HSDPA Power (dBm): The HSDPA power transmitted by the cell on HSDPA channels. It corresponds to the HSDPA power used to serve HSDPA bearer users. Total Transmitted Power (dBm): The total transmitted power of the cell is the sum of the total transmitted R99 power and the transmitted HSDPA power. If HSDPA power is allocated dynamically, the total transmitted power cannot exceed the maximum power minus the power headroom. When the constraint "DL load" is set and HSDPA power is statically allocated, the total transmitted power cannot exceed the maximum DL load (defined either in the cell properties, or in the simulation). On the other hand, if HSDPA power is allocated dynamically, the control is carried out on the R99 transmitted power, which cannot exceed the maximum DL load.
•
• • •
•
• •
• • •
• •
750
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). 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.).
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
•
•
•
• •
• • • • • •
•
•
• • • •
•
Min. HSDPA RLC Peak Rate (kbps): The minimum HSDPA RLC peak rate corresponds to the lowest of RLC peak rates obtained by HSDPA bearer users connected to the cell. For dual-cell HSDPA users, this is the lower of the two minimum HSDPA RLC peak rates. Max HSDPA RLC Peak Rate (kbps): The maximum HSDPA RLC peak rate corresponds to the highest of RLC peak rates obtained by HSDPA bearer users connected to the cell. For dual-cell HSDPA users, this is the higher of the two maximum HSDPA RLC peak rates. Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA rate (kbps) is the average number of kbits per second that the cell supports on downlink to provide one connected user with an HSDPA bearer. The HSDPA throughput of dual-cell HSDPA users is the sum of their HSDPA throughputs on both cells. Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate (kbps) is the number of kbits per second that the cell supports on downlink to provide simultaneous connected users with an HSDPA bearer. The HSDPA rate of dual-cell HSDPA users is the sum of their HSDPA rates on both cells. Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that the cell carries. The HSDPA throughput of dual-cell HSDPA users is the sum of their HSDPA throughputs on both cells. No. of Simultaneous HSDPA Users: The number of simultaneous HSDPA users corresponds to the number of HSDPA bearer users that the cell supports at one time, i.e. within one time transmission interval. All these users are connected to the cell at the end of the HSDPA part of the simulation; they have a connection with the R99 bearer and an HSDPA bearer. Dual-cell HSDPA users are considered once in each cell they are connected to. No. of HSDPA Users: The number of HSDPA users including the connected and delayed HSDPA bearer users. Dualcell HSDPA users are considered once in each cell they are connected to. No. of HSUPA Users: The number of HSUPA bearer users connected to the cell. HSUPA Application Throughput (kbps): This is the net HSUPA throughput without coding (redundancy, overhead, addressing, etc.). HSUPA UL Load Factor (%): The uplink cell load contribution due to HSUPA traffic. No. of Codes (512 Bits): The number of 512-bit OVSF codes used per cell. The types of handover as a percentage: Atoll estimates the percentages of handover types for each transmitter. Atoll only lists the results for the following handover status, no handover (1⁄1), softer (1⁄2), soft (2⁄2), softer-soft (2⁄3) and soft-soft (3⁄3) handovers; the other handover status (other HO) are grouped. R99 UL and DL Throughput (kbps): The uplink and downlink R99 throughputs represent the numbers of kbits per second delivered by the cell respectively on uplink and on downlink to supply users with a R99 bearer. All the radio links in the cell, i.e., links due to handover, are taken into account in the throughput calculation. R99 UL and DL Throughput Without HO (kbps): The uplink and downlink R99 throughputs represent the numbers of kbits per second delivered by the cell respectively on uplink and on downlink to supply users with a R99 bearer. Only the links with the best server are taken into account in the calculation of throughput. Min TCH Pwr (dBm): The minimum power allocated to a traffic channel to supply services. Max TCH Pwr (dBm): The maximum power allocated to a traffic channel to supply services. Avg TCH Pwr (dBm): The average power allocated to a traffic channel to supply services. Non-connected users: The number of rejected and delayed users per cell. Rejected users are sorted by the following values: Pmob > PmobMax, Ptch > PtchMax, Ec⁄Io < (Ec⁄Io)min., UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Code Saturation, Admission Rejection, HSDPA Scheduler Saturation, HSDPA Resource Saturation, HSUPA Admission Rejection, HSUPA Scheduler Saturation and Iub Throughput Saturation. Delayed users are regrouped under HSDPA Delayed. Connection Success Rate (%) For Each Service: For each service, the connection success rate gives the ratio of connected users over the total number of users of that service in the cell.
The Mobiles tab: The Mobiles tab contains the following information: The Mobiles tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 745, you select either "Standard information about mobiles" or "Detailed information about mobiles" under Information to Retain. • • • • • • • • •
X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second random trial). Service: The service assigned during the first random trial during the generation of the user distribution. Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal and the user profile. User Profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal and the user profile. Mobility: The mobility type assigned during the first random trial during the generation of the user distribution. Activity Status: The activity status assigned during the first random trial during the generation of the user distribution. Carrier: The carrier used for the mobile-transmitter connection. Dual-cell HSDPA users are connected to two carriers. Details can be displayed per carrier by selecting Actions > Detailed Display. Frequency Band: the frequency band used for the mobile-transmitter connection. DL and UL Total Requested Rate (kbps): For circuit and packet (R99) service users, the DL and UL total requested rates correspond to the DL and UL nominal rates of the R99 bearer associated to the service.
751
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
For packet (HSDPA) service users, the uplink total requested rate corresponds to the nominal rate of ADPCH-UL64 R99 bearer and the downlink total requested rate is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate that the selected HSDPA radio bearers can provide. Here, the HSDPA user is treated as if he is the only user in the cell and then, Atoll determines the HSDPA bearer the user would obtain by considering the entire HSDPA power available of the cell. For HSUPA bearer users, the uplink total requested rate is equal to the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate of the requested HSUPA radio bearer. The requested HSUPA radio bearer is selected from the HSUPA bearers compatible with the user equipment. Here, the HSUPA user is treated as if he is the only user in the cell and then, Atoll determines the HSUPA bearer the user would obtain by considering the entire remaining load of the cell. The downlink total requested rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate that the requested HSDPA radio bearer can provide. The requested HSDPA bearer is determined as explained in the previous paragraph. •
DL and UL Total Obtained Rate (kbps): For circuit and packet (R99) service users, the DL or UL total obtained rate is the same as the DL or UL total requested rate if he is connected without being downgraded. Otherwise, the total obtained rate is lower (it corresponds to the nominal rate of the selected R99 bearer). If the user was rejected, the total obtained rate is zero. For a packet (HSDPA) service user connected to an HSDPA bearer, the uplink total obtained rate equals the requested one and the downlink total obtained rate corresponds to the instantaneous rate; this is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearers after scheduling and radio resource control. If the user is delayed (he is only connected to an R99 radio bearer), uplink and downlink total obtained rates correspond to the uplink and downlink nominal rates of ADPCH-UL64 radio bearer. Finally, if the user is rejected either in the R99 part or in the HSDPA part, the uplink and downlink total obtained rates are zero. For connected packet (HSPA - Best Effort) service users and packet (HSPA - Variable Bit Rate) service users, on uplink, if the user is connected to an HSUPA bearer, the uplink total obtained rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the selected HSUPA radio bearer after noise rise scheduling. On downlink, if the user is connected to an HSDPA bearer, the downlink total obtained rate corresponds to the instantaneous rate. The instantaneous rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearers after scheduling and radio resource control. If the user is delayed, the downlink total obtained rate corresponds to the downlink nominal rate of ADPCHEDPCCH 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 minimum throughput demand 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 HSDPA and HSPA bearer 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): Ec⁄I0 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 745, you select "Detailed information about mobiles" under Information to Retain: •
DL and UL Requested RLC Peak Rates (kbps): For HSUPA bearer users (i.e., packet (HSPA - Best Effort), packet (HSPA - Variable Bit Rate) and packet (HSPA - Constant Bit Rate) service users), the requested uplink RLC peak rate is the rate of the requested HSUPA radio bearer. If the user is connected to an HSDPA bearer in the downlink, the downlink requested RLC peak rate is the rate that the requested HSDPA radio bearer can provide. Downlink and uplink requested RLC peak rates are not calculated for circuit and packet (R99) service users. For packet (HSDPA - Best Effort) and packet (HSDPA - Variable Bit Rate) 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.
•
752
DL and UL Obtained RLC Peak Rate (kbps): For connected packet (HSPA - Best Effort) service users and packet (HSPA - Variable Bit Rate) service users, 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
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Bit Rate) service user, the uplink and downlink obtained RLC peak rates are the uplink and downlink minimum throughput demands defined for the service. Downlink and uplink obtained RLC peak rates are not calculated for circuit and packet (R99) service users. For a packet (HSDPA) service user connected to an HSDPA bearer, the downlink obtained RLC peak rate is the rate provided by the selected HSDPA radio bearer after scheduling and radio resource control. The uplink obtained RLC peak rate is not calculated. •
• •
• • •
• • •
• •
•
HSDPA Application Throughput (kbps): The HSDPA application throughput is the net HSDPA throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the instantaneous HSDPA rate (i.e., the DL obtained rate), the BLER, the HSDPA service scaling factor and the throughput offset. Served HSDPA Power (dBm): This is the HSDPA power required to provide the HSDPA bearer user with the downlink obtained rate. Required HSDPA Power (dBm): The required HSDPA power is the HSDPA power required to provide the HSDPA bearer user with the downlink requested rate. If the HSDPA bearer allocated to the user is the best one, the required HSDPA power corresponds to the available HSDPA power of the cell. On the other hand, if the HSDPA has been downgraded in order to be compliant with cell and UE capabilities, the required HSDPA power will be lower than the available HSDPA power of the cell. No. of HSUPA Retransmissions (Required): The maximum number of retransmissions in order to have the requested HSUPA radio bearer with a given BLER. No. of HSUPA Retransmissions (Obtained): The maximum number of retransmissions in order to have the obtained HSUPA radio bearer with a given BLER. HSUPA Application Throughput (kbps): The HSUPA application throughput is the net HSUPA throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the UL obtained rate, the BLER, the HSUPA service scaling factor and the throughput offset. Cell TCH Power AS1, AS2, AS3, AS4 (DL) (dBm): The cell power transmitted on the downlink is given for each link between the mobile and a transmitter in the active set. DL Ntot AS1, AS2, AS3, AS4 (dBm): The total noise on the downlink for each link between the mobile and a transmitter in the \active set. Load Factor AS1, AS2, AS3, AS4 (DL) (%): The load factor on the downlink for each link between the mobile and a transmitter in the active set. It corresponds to the ratio between the total interference on the downlink and total noise at the terminal. Noise Rise AS1, AS2, AS3, AS4 (DL) (dB): The noise rise on the downlink for each link between the mobile and a transmitter in the active set. Reuse Factor AS1, AS2, AS3, AS4 (DL): The DL reuse factor for each link between the mobile and a transmitter in the active set. It is calculated from the interference received at the terminal from the intra cell area and the total interference received at the terminal from all the transmitters (intra and extra-cell and inter-carrier). Iintra AS1, AS2, AS3, AS4 (DL) (dBm): The intra-cell interference for each cell (I) of the active set. DL (ic ) − Fortho × P DL (ic ) − PSCH I int ra = P DL tot tot LT i i
•
Iextra AS1, AS2, AS3, AS4 (DL) (dBm): The extra-cell interference for each cell (I) of the active set. I extra = DL
• • • • • • • • • • • •
(ic ) − Fortho × P DL (ic ) − PSCH P DL tot tot LT Tx ,i∉Tx
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.
753
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
The Mobiles (Shadowing Values) tab: The Mobiles (Shadowing Values) tab contains information on the shadowing margin for each link between the receiver and up to ten closest potential transmitters: The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 745, you select "Detailed information about mobiles" under Information to Retain. • • • • •
Name: The name assigned to the mobile. Value at Receiver (dB): The value of the shadowing margin at the receiver. Clutter: The clutter class on which the mobile is located. Path To: The name of the potential transmitter. Value (dB): The shadowing value for the potential link in the corresponding Path To column. These values depend on the model standard deviation per clutter type on which the receiver is located and are randomly distributed on a gaussian curve.
The Initial Conditions tab: The Initial Conditions tab contains the following information: •
The global transmitter parameters: • • • • • • •
•
The input parameters specified when creating the simulation: • • • • • •
•
The spreading width Whether the power values on the downlink are absolute or relative to the pilot The default uplink soft handover gain Whether the MRC in softer/soft is defined or not The methods used to calculate I0 and Nt Parameters for compressed mode The methods used to calculate Nt and CQI for HSDPA. The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink convergence thresholds The simulation constraints such as maximum power, the maximum number of channel elements, the maximum Iub throughputs, the uplink load factor and the maximum load The name of the traffic maps used.
The parameters related to the clutter classes, including the default values.
9.3.4.6 Displaying the Average Results of a Group of Simulations After you have created a group of simulations, as explained in "Creating Simulations" on page 745, you can display the average results of the group. If you want to display the results of a single simulation of a group, see "Displaying the Results of a Single Simulation" on page 748. To access the averaged results of a group of simulations: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Traffic Parameters folder.
3. Right-click the group of simulations whose results you want to access. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation. The Statistics tab: The Statistics tab contains the following two sections: •
Request: Under Request, you will find data on the connection requests: • • •
•
Results: Under Results, you will find data on the connection results: • •
754
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.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
• •
•
•
The number and the percentage of delayed users is given along with the reason for delay. The number and percentage of R99 bearer users connected to a cell, the number of users per frequency band for dual-band networks, the number of users per activity status, and the total UL and DL rates they generate. These figures include R99 users as well as HSDPA and HSUPA bearer users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm. These data are also given per service. The total number and the percentage of connected users with an HSDPA bearer, the number of users per frequency band for dual-band networks, the number of users per activity status, and DL total rate that they generate. Packet (HSDPA - Best Effort), Packet (HSPA - Best Effort), Packet (HSDPA - Variable Bit Rate), Packet (HSPA - Variable Bit Rate), 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 - Best Effort), Packet (HSPA - Variable Bit Rate) 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). DL and UL Throughput for Each Service: The throughput in kbits⁄s for each service.
The Cells (Average) and Cells (Standard Deviation) tabs: The Cells (Average) and Cells (Standard Deviation) tabs contains the following average and standard deviation information, respectively, per site, transmitter, and carrier: • • • • •
• • • • • •
•
Max Power (dBm): The maximum power as defined in the cell properties. Pilot Power (dBm): The pilot power as defined in the cell properties. SCH power (dBm): The SCH power as defined in the cell properties. Other CCH power (dBm): The power of other common channels. It includes the other CCH power and the DL HSUPA power as defined in the cell properties. Available HSDPA Power (dBm): The available HSDPA power as defined in the cell properties. This is the power available for the HS-PDSCH and HS-SCCH. The value is either fixed by the user when the HSDPA power is allocated statically, or by a simulation when the option HSDPA Power Dynamic Allocation is selected. AS Threshold (dB): The active set threshold as defined in cell properties Gain (dBi): The gain as defined in the antenna properties for that transmitter. Reception Losses (dB): The reception losses as defined in the transmitter properties. Transmission Losses (dB): The transmission losses as defined in the transmitter properties. Noise Figure (dB): The noise figure as defined in the transmitter properties Total Transmitted R99 Power (dBm): The total transmitted R99 power is the power transmitted by the cell on common channels (Pilot, SCH, other CCH), HSUPA channels (E-AGCH, E-RGCH, and E-HICH) and R99 traffic-dedicated channels. Transmitted HSDPA Power (dBm): The HSDPA power transmitted by the cell on HSDPA channels. It corresponds to the HSDPA power used to serve HSDPA bearer users.
755
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
•
© Forsk 2012
Total Transmitted Power (dBm): The total transmitted power of the cell is the sum of the total transmitted R99 power and the transmitted HSDPA power. If HSDPA power is allocated dynamically, the total transmitted power cannot exceed the maximum power minus the power headroom. When the constraint "DL load" is set and HSDPA power is statically allocated, the total transmitted power cannot exceed the maximum DL load (defined either in the cell properties, or in the simulation). On the other hand, if HSDPA power is allocated dynamically, the control is carried out on the R99 transmitted power, which cannot exceed the maximum DL load.
•
• • •
• •
• •
• • •
• •
•
•
•
•
• •
• • • •
756
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. For dual-cell HSDPA users, this is the lower of the two minimum HSDPA RLC peak rates. Max HSDPA RLC Peak Rate (kbps): The maximum HSDPA RLC peak rate: It corresponds to the highest of RLC peak rates obtained by HSDPA bearer users connected to the cell. For dual-cell HSDPA users, this is the higher of the two maximum HSDPA RLC peak rates. Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA rate (kbps) is the average number of kbits per second that the cell supports on downlink to provide one connected user with an HSDPA bearer. The HSDPA throughput of dual-cell HSDPA users is the sum of their HSDPA throughputs on both cells. Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate (kbps) is the number of kbits per second that the cell supports on downlink to provide simultaneous connected users with an HSDPA bearer. The HSDPA rate of dual-cell HSDPA users is the sum of their HSDPA rates on both cells. Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that the cell carries. The HSDPA throughput of dual-cell HSDPA users is the sum of their HSDPA throughputs on both cells. No. of Simultaneous HSDPA Users: The number of simultaneous HSDPA users corresponds to the number of HSDPA bearer users that the cell supports at a time, i.e. within one time transmission interval. All these users are connected to the cell at the end of the simulation HSDPA part; they have a connection with the R99 bearer and an HSDPA bearer. Dual-cell HSDPA users are considered once in each cell they are connected to. No. of HSDPA Users: The number of HSDPA users include the connected and delayed HSDPA bearer users. Dualcell HSDPA users are considered once in each cell they are connected to. No. of HSUPA Users: The number of HSUPA bearer users connected to the cell. HSUPA Application Throughput (kbps): This is the net HSUPA throughput without coding (redundancy, overhead, addressing, etc.). HSUPA UL Load Factor (%): The uplink cell load caused by HSUPA traffic.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
• •
•
•
• • • •
•
No. of Codes (512 Bits): The number of OVSF codes used per cell. The types of handover as a percentage: Atoll estimates the percentages of handover types for each transmitter. Atoll only lists the results for the following handover status, no handover (1⁄1), softer (1⁄2), soft (2⁄2), softer-soft (2⁄3) and soft-soft (3⁄3) handovers; the other handover status (other HO) are grouped. R99 UL and DL Throughput (kbps): The uplink and downlink R99 throughputs represent the numbers of kbits per second delivered by the cell respectively on uplink and on downlink to supply users with a R99 bearer. All the radio links in the cell, i.e., links due to handover, are taken into account in the throughput calculation. R99 UL and DL Throughput Without HO (kbps): The uplink and downlink R99 throughputs represent the numbers of kbits per second delivered by the cell respectively on uplink and on downlink to supply users with a R99 bearer. Only the links with the best server are taken into account in the calculation of throughput. Min TCH Pwr (dBm): The minimum power allocated to a traffic channel to supply services. Max TCH Pwr (dBm): The maximum power allocated to a traffic channel to supply services. Avg TCH Pwr: The average power allocated to a traffic channel to supply services. Non-connected users: The number of rejected and delayed users per cell. Rejected users are sorted by the following reasons: Pmob > PmobMax, Ptch > PtchMax, Ec⁄Io < (Ec⁄Io)min., UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Code Saturation, Admission Rejection, HSDPA Delayed, HSDPA Scheduler Saturation, HSDPA Resource Saturation, HSUPA Admission Rejection, HSUPA Scheduler Saturation and Iub Throughput Saturation. Delayed users are regrouped under HSDPA Delayed. Connection Success Rate (%) For Each Service: For each service, the connection success rate gives the ratio of connected users over the total number of users of that service in the cell.
The Initial Conditions tab: The Initial Conditions tab contains the following information: •
The global transmitter parameters: • • • • • • •
•
The input parameters specified when creating the group of simulations: • • • • • •
•
The spreading width Whether the power values on the downlink are absolute or relative to the pilot The default uplink soft handover gain Whether the MRC in softer/soft is defined or not The methods used to calculate I0 and Nt Parameters for compressed mode The methods used to calculate Nt and CQI for HSDPA. The maximum number of iterations The global scaling factor The generator initialisation value The uplink and downlink convergence thresholds The simulation constraints such as maximum power, the maximum number of channel elements, the uplink load factor and the maximum load The name of the traffic maps used.
The parameters related to the clutter classes, including the default values.
9.3.4.7 Updating Cell Values With Simulation Results After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 745, you can update values for each cell with the results calculated during the simulation. The following values are updated: • • • • • • •
Total Transmitted Power UL Load Factor UL Reuse Factor Available HSDPA Power Number of HSDPA Users UL Load Factor due to HSUPA Number of HSUPA Users.
To update cell values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Select the Network explorer. b. Click the Expand button (
) to expand the Traffic 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.
757
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
To display the results for a single simulation: a. Select the Network explorer. b. Click the Expand button (
) to expand the Traffic Parameters folder.
c. Click the Expand button ( you want to access.
) to expand the folder of the simulation group containing the simulation whose results
d. Select Properties from the context menu. The simulation properties dialogue appears. 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.
9.3.4.8 Adding New Simulations to an Atoll Document When you have created a simulation or group of simulations, you can re-examine the same conditions by adding new simulations to the Atoll document. In Atoll, there are the following ways of adding new simulations: •
Adding to a group: When you add one or more simulations to an existing group of simulations, Atoll reuses the same input (radio, traffic, and simulation parameters) as those used to generate the group of simulations. It then generates a new user distribution and performs the power control simulation. To add a simulation to a group of simulations, see "Adding a Simulation to a Group of Simulations" on page 758.
•
Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution (users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shadowing error distribution between simulations is different. Traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) might or might not be taken into account. Finally, radio data modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during the power control (or rate/power control) simulation. To replay a group of simulations, see "Replaying a Simulation or Group of Simulations" on page 759.
•
Using the Generator Initialisation Number: When you create groups of simulations using the same generator initialisation number (which must be an integer other than 0) Atoll generates the same user and shadowing error distributions (user with a service, a mobility, an activity status and a shadowing error) in all groups using the same number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers allowed, Eb⁄Nt thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during the power control simulation. By creating and calculating one group of simulations, making a change to the network and then creating and calculating a new group of simulations using the same generator initialisation number, you can see the difference your parameter changes make. To create a new simulation to a group of simulations using the generator initialisation number, see "Creating a New Simulation or Group of Simulations Using the Generator Initialisation Number" on page 759.
•
Duplicating a Group: When you duplicate a group, Atoll creates a group of simulations with the same simulation parameters as those used to generate the group of simulations. You can then modify the simulation parameters before calculating the group. To duplicate a group of simulations, see "Duplicating a Simulation or Group of Simulations" on page 760.
Adding a Simulation to a Group of Simulations To add a simulation to an existing group of simulations: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Simulations folder.
3. Right-click the group of simulations to which you want to add a simulation. The context menu appears. 4. Select New from the context menu. The properties dialogue of the group of simulations appears.
758
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
When adding a simulation to an existing group of simulations, the parameters originally used to calculate the group of simulations are used for the new simulations. Consequently, few parameters can be changed for the added simulation. 5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations. 6. Under Execution on the General tab, you can set the following parameter: •
Number of Simulations: Enter the number of simulations to added to this group of simulations.
7. Once you have added the simulation, you can calculate it immediately or you can save it to calculate it later: • •
Calculate: Click Calculate to save the defined simulation and calculate it immediately. OK: Click OK to save the defined simulation without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Replaying a Simulation or Group of Simulations To replay an existing simulation or group of simulations: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Simulations folder.
3. Right-click the group of simulations you want to replay. The context menu appears. 4. Select Replay from the context menu. The properties dialogue of the group of simulations appears. When replaying an existing group of simulations, some parameters originally used to calculate the group of simulations are reused for the replayed group. Consequently, few parameters can be changed for the replayed group. 5. On the General tab of the dialogue, you can set the following parameters: • • •
Select the level of detail as explained in "Creating Simulations" on page 745 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 745 that Atoll must respect during the simulation. Under Bearer Negotiation, check the Bearer downgrading check box if you want to permit bearer downgrading during the simulation.
6. On the Source Traffic tab of the dialogue, select the Refresh Traffic Parameters check box if you want to take into account traffic parameter changes (such as maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) in the replayed simulation. 7. On the Advanced tab, you can set the following parameters: • • •
Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make convergence. UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the uplink that must be reached between two iterations. DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on the downlink that must be reached between two iterations.
8. Click Calculate. Atoll immediately begins the simulation. Creating a New Simulation or Group of Simulations Using the Generator Initialisation Number To create a new simulation or group of simulations using the generator initialisation number: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. 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.
759
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
6. For information on setting other parameters, see "Creating Simulations" on page 745. 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 760. Duplicating a Simulation or Group of Simulations To duplicate an existing simulation or group of simulations: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Simulations folder.
3. Right-click the simulation or group of simulations you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The properties dialogue for the duplicated group of simulations appears. You can change the parameters for the duplicated simulation or group of simulations as explained in "Creating Simulations" on page 745.
9.3.4.9 Estimating a Traffic Increase When you create a simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increased traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to "2" is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a simulation or group of simulations by: • •
Creating a new simulation or group of simulations as described in "Creating Simulations" on page 745. Duplicating an existing simulation or group of simulations as described in "Adding New Simulations to an Atoll Document" on page 758.
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).
9.3.5 Analysing the Results of a Simulation In Atoll, you have several methods available to help you analyse simulation results. You can make an active set analysis of a real-time probe user or you can make a prediction where each pixel is considered as a probe user with a defined terminal, mobility, and service. The analyses are based on a single simulation or on an averaged group of simulations. You can find information on the analysis methods in the following sections: • •
"Making an AS Analysis of Simulation Results" on page 760 "Making Coverage Predictions Using Simulation Results" on page 761.
9.3.5.1 Making an AS Analysis of Simulation Results The Point Analysis window gives you information on reception for any point on the map. The AS Analysis view gives you information on the pilot quality (Ec⁄I0) (which is the main parameter used to define the mobile active set), the connection status, and the active set of the probe mobile. Analysis is based on the UL load percentage and the DL total power of cells. In this case, these parameters can be either outputs of a given simulation, or average values calculated from a group of simulations. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service. For information on the criteria for belonging to the active set, see "Conditions for Entering the Active Set" on page 805. Before you make an AS analysis: • •
Ensure the simulation or group of simulations you want to use in the AS analysis is displayed on the map. Replay the simulation or group of simulations you want to use if you have modified radio parameters since you made the simulation. The AS analysis does not take possible network saturation into account. Therefore, there is no guarantee that a simulated mobile with the same receiver characteristics can verify the point analysis, simply because the simulated network can be saturated.
760
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
To make an AS analysis of simulation results: 1. Click the Point Analysis button (
) on the toolbar. The Point Analysis window appears. (see Figure 9.14).
2. Select the AS Analysis view at the top of the Point Analysis window. 3. At the top of the AS Analysis view, select the simulation or group of simulations you want to base the AS analysis on from the Load Conditions list. 4. Select the Terminal, Service, and Mobility. 5. Click the Options button (
) to display the Calculation Options dialogue.
6. Select or clear the following options: • • •
Whether shadowing is to be taken into account (and, if so, the cell edge coverage probability). Whether indoor coverage is to be taken into account. Whether downgrading is allowed.
7. Click OK to close the Calculation Options dialogue. 8. Move the pointer over the map to make an active set analysis for the current location of the pointer. As you move the pointer, Atoll indicates on the map which is the best server for the current position (see Figure 9.32 on page 697). Information on the current position is given on the AS Analysis view of the Point Analysis window. See Figure 9.33 on page 697 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.
9.3.5.2 Making Coverage Predictions Using Simulation Results When no simulations are available, Atoll uses the UL load factor, the DL total power, the UL reuse factor, the available HSDPA power, the number of HSDPA users, the number of HSUPA users, and the UL load factor due to HSUPA defined for each cell to make coverage predictions. For information on cell properties, see "Creating or Modifying a Cell" on page 638; for information on modifying cell properties, see "Cell Definition" on page 633. Once you have made simulations, Atoll can use this information instead of the defined parameters in the cell properties to make coverage predictions where each pixel is considered as a probe user with a terminal, mobility, profile, and service. For each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a group of simulations, choosing either an average analysis of all simulations in the group or a statistical analysis based on a defined probability. To be able to base a coverage prediction on a simulation or group of simulations, the simulation must have converged. The coverage predictions that can use simulation results are: •
Coverage predictions on the pilot or on a service: • • • •
•
Coverage predictions on noise and interference: • •
•
Coverage by Total Noise Level (DL): For information on making a coverage by total noise level, see "Studying the Total Noise Level on the Downlink" on page 692. Pilot Pollution Analysis: For information on making a coverage by pilot polluter, see "Calculating Pilot Pollution" on page 693.
A handover status coverage prediction to analyse macro-diversity performance: •
•
Pilot Quality Analysis: For information on making a pilot quality analysis, see "Making a Pilot Signal Quality Prediction" on page 687. Service Area Analysis Downlink: For information on making a coverage prediction on the downlink service area, see "Studying Service Area (Eb⁄Nt) Downlink or Uplink" on page 688. Service Area Analysis Uplink: For information on making a coverage prediction on the uplink service area, see "Studying Service Area (Eb⁄Nt) Downlink or Uplink" on page 688. Effective Service Area Analysis (Eb/Nt) (DL+UL): For information on making a effective service area analysis, see "Studying the Effective Service Area" on page 690.
Handoff Zones: For information on making a Handoff Zones, see "Making a Handoff Status Coverage Prediction" on page 695.
An HSDPA prediction to analyse A-DPCH qualities, HS-SCCH power or quality per HS-SCCH channel and to model fast link adaptation.
761
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• •
© Forsk 2012
HSDPA Quality and Throughput Analysis: For information on making an HSDPA coverage prediction, see "HSDPA Quality and Throughput Analysis" on page 697.
An HSUPA predictions prediction to analyse the required E-DPDCH Ec/Nt, the required terminal power, and the obtained HSUPA bearer. •
HSUPA Quality and Throughput Analysis: For information on making an HSUPA coverage prediction, see "HSUPA Quality and Throughput Analysis" on page 700.
The procedures for the coverage predictions assume that simulation results are not available. When no simulations are available, you select "(Cells Table)" from the Load Conditions list, on the Conditions tab. However, when simulations are available you can base the coverage prediction on one simulation or a group of simulations. To base a coverage prediction on a simulation or group of simulations, when setting the parameters: 1. Click the Conditions tab. 2. From the Load Conditions list, select the simulation or group of simulations on which you want to base the coverage prediction. 3. If you select a group of simulations from the Load Conditions list, select one of the following: •
•
All: 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.
9.4 Optimising Network Parameters Using the ACP Atoll Automatic Cell Planning (ACP) enables radio engineers designing UMTS networks to automatically calculate the optimal network settings in terms of network coverage and quality. The ACP can also be used to add sites from a list of candidate sites or to remove unnecessary sites or sectors. Atoll ACP can also be used in co-planning projects where networks using different radio access technologies must be taken into consideration when calculating the optimal network settings. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and cell pilot power. ACP can also be used during the initial planning stage of a UMTS network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP not only takes transmitters into account in optimisations but also any repeaters and remote antennas. Atoll ACP can also be used to measure and optimise the EMF exposure created by the network. This permits the optimisation of power and antenna settings to reduce excessive EMF exposure in existing networks and optimal site selection for new transmitters. ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have defined the objectives and the network parameters to be optimised, Atoll ACP uses an efficient global search algorithm to test many network configurations and propose the reconfigurations that best meet the objectives. The ACP presents the changes ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the suggested changes. The ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 6: Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how you can view the results of an optimisation. In this section, only the concepts specific to UMTS networks are explained: • • •
"UMTS Optimisation Objectives" on page 762 "UMTS Quality Parameters" on page 762 "The UMTS Quality Analysis Maps" on page 763.
9.4.1 UMTS Optimisation Objectives ACP optimises the network using user-defined objectives to evaluate the quality of the network reconfiguration. The objectives are dependent on the technology used by the project and are consistent with the corresponding coverage predictions in Atoll. In projects using UMTS, either alone, or in a co-planning or multi-RAT project, the following objectives are used: • •
RSCP Ec/Io
You define the optimisation objectives using the Objectives tab of the ACP Setup dialogue. For information on setting objective parameters, see "Setting Objective Parameters" on page 242 of Chapter 6: Automatic Cell Planning.
9.4.2 UMTS Quality Parameters When you create an optimisation setup, you define how the ACP evaluates the objectives. The quality parameters are technology dependent. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configu-
762
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
ration. 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. In projects using UMTS, either alone, or in a co-planning or multi-RAT project, the following quality parameters are used: • • •
Overlap RSCP Ec/Io
To define the quality parameters for UMTS: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233 in Chapter 6: Automatic Cell Planning. 2. Click the Objectives tab. 3. Under Criteria, in the left-hand pane, under Parameters, expand UMTS. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own maps. However, if you have saved the display options of an ACP map as default, or if you are using a configuration file for ACP, these defined ranges and colours will be used as the default, overriding the settings in the selected coverage prediction. For information on setting ACP map display options as the default, see "Changing the Display Properties of ACP Predictions" on page 284. For information on saving a configuration file, see "Configuring Default Settings" on page 231. If you want to use a coverage prediction, the coverage prediction must have already been calculated.
4. Click Overlap. In the right-hand pane, you can define how the ACP will evaluate overlapping coverage. 5. Select what the objective evaluation will be based on from the Base prediction settings on list: • •
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, define an Overlap threshold margin and a Minimum signal level. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate overlapping coverage using the same parameters that were used to calculate the coverage prediction.
6. Under UMTS in the left-hand pane under Parameters, select RSCP. 7. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate RSCP using the same parameters that were used to calculate the coverage prediction.
8. Under UMTS in the left-hand pane under Parameters, select Ec⁄Io. 9. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box. When selected, the shadowing margin will be taken into account using the defined Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Macro diversity is also taken into account during Ec⁄Io calculation. Select a Service and a Terminal. The service and terminal specified are used during the calculation of Ec⁄Io through gain and losses (i.e., the service body loss, the gain and loss of the terminal antenna, and terminal noise factor). Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate Ec⁄Io using the same parameters that were used to calculate the coverage prediction.
9.4.3 The UMTS Quality Analysis Maps The quality analysis maps enable you to display the RSCP and Ec⁄Io quality maps in the Atoll map window. These maps are the same as those displayed on the Quality tab of the optimisation’s Properties dialogue. The quality analysis maps are the equivalent of maps created by different Atoll coverage predictions: •
The RSCP maps correspond to the Atoll coverage by signal level in UMTS. For information on the coverage by signal level, see "Studying Signal Level Coverage" on page 658.
763
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
•
© Forsk 2012
The overlapping zones maps correspond to the Atoll overlapping zones coverage prediction. For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 670.
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 analysis. ACP generated maps are generated using the entire set of proposed changes. They do not take into account the change subset defined on the Change Details tab. Multiple carriers are not supported by ACP; the maps are only provided for the requested carrier. Even after committing the optimisation results, differences can remain between the ACP maps and the maps resulting from Atoll coverage predictions.
You can view the exact RSCP and Ec⁄Io values on any pixel by letting the pointer rest over the pixel. The RSCP or Ec⁄Io value is then displayed in tip text. For the overlapping zones map, you can set the best server threshold on the User Preferences tab of the ACP Properties dialogue (see "Configuring Default Settings" on page 231) or by setting the CellOverlap parameter in the acp.ini file. For each network quality coverage prediction, ACP offers a map showing the initial network state, the final network state, and a map showing the changes between the initial and final state.
9.5 Verifying Network Capacity An important step in the process of creating a UMTS HSPA network is verifying the capacity of the network. This is done using measurements of the strength of the pilot signal in different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: • • • • • • •
"Importing a Drive Test Data Path" on page 764 "Displaying Drive Test Data" on page 767 "Defining the Display of a Drive Test Data Path" on page 767 "Network Verification" on page 768 "Exporting a Drive Test Data Path" on page 775 "Extracting CW Measurements from Drive Test Data" on page 775 "Printing and Exporting the Drive Test Data Window" on page 775.
9.5.1 Importing a Drive Test Data Path In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, commas, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: • •
The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells). In UMTS networks, a cell is identified by its scrambling code. Therefore, you must indicate during the import process which columns contain the scrambling code of cells and the scrambling code format (decimal or hexadecimal) used in the file. Because a scrambling code can belong to several groups, you can also indicate from which group the scrambling code has been selected.
You can import a single drive test data file or several drive test data files at the same time. If you regularly import drive test data files of the same format, you can create an import configuration. The import configuration contains information that defines the structure of the data in the drive test data file. By using the import configuration, you will not need to define the data structure each time you import a new drive test data file. To import one or several drive test data files: 1. Select the Network explorer. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. You can import one or several files. Select the file or files you want to open.
764
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import. 5. Click Open. The Import of Measurement Files dialogue appears. Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue. 6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Import configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Import configuration, select an import configuration from the Import configuration list. b. Continue with step 10. •
•
When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. If several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters: • • •
Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement Conditions, • •
Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document.
8. Click the Setup tab (see Figure 9.45).
765
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Figure 9.45: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal Symbol used in the file. b. Click the Setup button to link file columns and internal Atoll fields. The Drive Test Data Setup dialogue appears. c. Under Measurement point position, select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in the drive test data file. You can also identify the columns containing the XY coordinates of each point in the drive test data file by selecting them from the Field row of the table on the Setup tab.
d. If you are importing data using Scrambling Codes as cell identifiers: i.
Select By Scrambling Code under Transmitter Identification.
i.
In the Scrambling Code Identifier box, enter a string that is found in the column names identifying the scrambling code of scanned cells. For example, if the string "SC" is found in the column names identifying the scrambling code of scanned cells, enter it here. Atoll will then search for columns with this string in the column name.
ii. From the SC Format list, select the scrambling code format, either "Decimal" or "Hexadecimal." iii. In the Scrambling Code Group Identifier box, enter a string that must be found in the column names identifying the scrambling code group of scanned cells. For example, if the string "SC_Group" is found in the column names identifying the scrambling code group of scanned cells, enter it here. Atoll will then search for columns with this string in the column name. If there is no scrambling code group information contained in the drive test data file, leave the Scrambling Code Group Identifier box empty. e. If you are importing data using Cell ID as cell identifiers: i.
Select By Cell ID under Transmitter Identification.
ii. In the Cell ID Identifier box, enter a string found in the column name identifying the cell Ids of scanned cells. For example, if the string "Cell_ID" is found in the column names identifying the Cell_ID of scanned cells, enter it here. Atoll will then search for the column with this string in the column name. f. Click OK to close the Drive Test Data Setup dialogue.
766
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
•
If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Setup dialogue, Atoll should recognise all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "". If a column is marked with "", it will not be imported. The data in the file must be structured so that the columns identifying the scrambling code group and the scrambling code are placed before the data columns for each cell. Otherwise Atoll will not be able to properly import the file.
9. If you want to save the definition of the data structure so that you can use it again, you can save it as an import configuration: a. On the Setup tab, under Import configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll’s installation folder. If you cannot write into that folder, you can click the Browse button to choose a different location. c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for example, "*.csv"). d. Click OK. Atoll will now select this import configuration automatically every time you import a drive test data path file with the selected extension. If you import a file with the same structure but a different extension, you will be able to select this import configuration from the Configuration list. • •
•
You do not have to complete the import procedure to save the import configuration and have it available for future use. When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking the Expand button ( ) in front of the file under Import configuration to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Import configuration and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The mobile data are imported into the current Atoll document.
9.5.2 Displaying Drive Test Data When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see information about the active set at that location. To display information about a single drive test data point: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Drive Test Data folder.
3. Select the display check box beside the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want active set information. Atoll displays an arrow pointing towards the serving cells (see Figure 9.50 on page 773), 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 44.
9.5.3 Defining the Display of a Drive Test Data Path You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to manage permanent labels on the map, tip text and the legend. In other words, the display of measurement paths can be defined in the same way as for sites, transmitters, etc.
767
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
To display the Display tab of a drive test data path’s Properties dialogue: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Drive Test Data folder.
3. Right-click the drive test data path whose display you want to manage. The context menu appears. 4. Select Properties from the context menu, 5. Click the Display tab. Each point can be displayed by a unique attribute or according to: • •
a text or integer attribute (discrete value) a numerical value (value interval).
In addition, you can display points by more than one criterion at a time using the Advanced option in the Display Type list. When you select Advanced from the Display Type list, a dialogue opens in which you can define the following display for each single point of the measurement path: • • •
a symbol according to any attribute a symbol colour according to any attribute a symbol size according to any attribute
You can, for example, display a signal level in a certain colour, choose a symbol type for Transmitter 1 (a circle, triangle, cross, etc.) and a symbol size according to the altitude. • • •
•
Fast Display forces Atoll to use the lightest symbol to display the points. This is particularly useful when you have a very large number of points. You can not use Advanced Display if the Fast Display check box has been selected. You can sort drive test data paths in alphabetical order in the Network explorer by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can save the display settings (such as colours and symbols) of a drive test data path in a user configuration file to make them available for use on another drive test data path. To save or load the user configuration file, click the Actions button on the Display tab of the path properties dialogue and select Save or Load from the Display Configuration submenu.
9.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 768 "Predicting Signal Level on Drive Test Data Points" on page 770 "Predicting Signal Level on Drive Test Data Points" on page 770 "Displaying Statistics Over a Drive Test Data Path" on page 772 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 773 "Analysing Data Variations Along the Path" on page 773.
9.5.4.1 Filtering Incompatible Points Along Drive Test Data Paths When using a drive test data path, some measured points may present values that are too far outside of the median values to be useful in calibration. As well, test paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from the more lightly populated region between the two. In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter classes where the incompatible points are located, or by filtering out points according to their properties. To filter out incompatible points by clutter class: 1. Select the Network explorer. 2. In the Network explorer, right-click the Drive Test Data on which you want to filter out incompatible points: •
768
All drive test data measurements: Right-click the Drive Test Data folder.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
Only one drive test data path: Click the Expand button ( ) to expand the Drive Test Data folder and right-click the drive-test data path on which you want to filter out incompatible points.
The context menu appears. 3. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 4. In the Clutter classes window, under Filter, clear the check boxes of the clutter classes you want to filter out. Only the clutter classes whose check box is selected will be taken into account. 5. If you want to keep the measurement points inside the focus zone, select the Use focus zone to filter check box. 6. If you want to permanently remove the measurement points outside the filter, select the Delete points outside filter check box. If you permanently delete measurement points and later want to use them, you will have to re-import the original measurement data. To filter out incompatible points using a filter: 1. Select the Network explorer. 2. In the Network explorer, right-click the Drive Test Data on which you want to filter out incompatible points: • •
All drive test data measurements: Right-click the Drive Test Data folder. Only one drive test data path: Click the Expand button ( ) to expand the Drive Test Data folder and right-click the drive-test data path on which you want to filter out incompatible points.
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.46).
Figure 9.46: The Filter dialogue - Advanced tab b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the following table: Formula
Data are kept in the table only if
=X
value equal to X (X can be a number or characters)
X
value not equal to X (X can be a number or characters)
X
numerical value is greater than X
769
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Formula
Data are kept in the table only if
=X
numerical value is greater than or equal to X
*X*
text objects which contain X
*X
text objects which end with X
X*
text objects which start with X
7. Click OK to filter the data according to the criteria you have defined. Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering" on page 96. 8. Click OK to apply the filter and close the dialogue. You can update heights (of the DTM, and clutter heights) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones by selecting Refresh Geo Data from the context menu of the Drive Test Data Paths folder.
9.5.4.2 Predicting Signal Level on Drive Test Data Points To predict the signal level on drive test data points: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to create the point prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Point predictions, select Point Signal Level and click OK. The Point Signal Level Properties dialogue appears (see Figure 9.47).
Figure 9.47: Point Signal Level Properties Dialogue The errors between measured and predicted signal levels can be calculated and added to the drive test data table. 6. If you want to calculate errors between measured and predicted signal levels, under Select signal levels for error calculations, select the names of the columns representing measured signal level values in the drive test data table for which you want to calculate the errors (see Figure 9.48). If you do not want to add this information to the drive test data table, continue with step 7.
Figure 9.48: Selecting Measured Signal Levels for which Errors will be Calculated
770
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
7. Click OK. A new point prediction is created for the selected drive test data path. 8. Right-click the drive test data path. The context menu appears. 9. Select Calculations > Calculate All the Predictions from the context menu. If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the drive test data table for the predicted point signal level from the serving cell and the errors between the measured and predicted values.
Figure 9.49: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations) New columns are also added for the predicted point signal level from each neighbour cell and the errors between the predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Data Variations Along the Path" on page 773. The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main matrix. For more information on propagation models, see Chapter 5: Working with Calculations in Atoll.
9.5.4.3 Creating Coverage Predictions on Drive Test Data Paths You can create the following coverage predictions for all transmitters on each point of a drive test data path: • • • •
Coverage by Signal Level Pilot Quality Analysis Service Area Analysis (Eb⁄Nt) (DL) Service Area Analysis (Eb⁄Nt) (UL)
To create a coverage prediction along a drive test data path: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Drive Test Data folder.
3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Standard Predictions, select one of the following coverage predictions and click OK: •
Coverage by Signal Level: Click the Conditions tab. •
•
At the top of the Conditions tab, you can set the range of signal level to be calculated. Under Server, you can select whether to calculate the signal level from all transmitters, or only the best or second-best signal. If you choose to calculate the best or second-best signal, you can enter a Margin. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. Finally, you can select the Carrier to be studied.
Pilot Quality Analysis (Ec⁄I0): Click the Conditions tab. •
•
• • •
On the Conditions tab, you can select which simulation to study in the Load Conditions list. Or you can select a group of simulations and either select All to perform an average analysis of all simulations in the group based on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simulations. If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from Load conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the DL total power defined in the cell properties. You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 682. 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.
771
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
•
© Forsk 2012
Service Area Analysis (Eb⁄Nt) (DL): Click the Conditions tab. •
•
• • • •
On the Conditions tab, you can select which simulation to study in the Load Conditions list. Or you can select a group of simulations and either select All to perform an average analysis of all simulations in the group based on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simulations. If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from Load conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the DL total power defined in the cell properties. You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 682. 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.
Service Area Analysis (Eb⁄Nt) (UL): Click the Conditions tab. •
•
• • •
On the Conditions tab, you can select which simulation to study in the Load Conditions list. Or you can select a group of simulations and either select All to perform an average analysis of all simulations in the group based on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simulations. If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from Load conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the DL total power defined in the cell properties. You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 682. 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 Predictions from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Working with Calculations in Atoll). You can display the information in these new columns in the Drive Test Data window. For more information on the Drive Test Data window, see "Analysing Data Variations Along the Path" on page 773.
9.5.4.4 Displaying Statistics Over a Drive Test Data Path Assuming some predictions have been calculated along a drive test data path, you can display the statistics between the measured and the predicted values on a specific measurement path. To display the statistics for a specific drive test data path: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Drive Test Data folder.
3. Right-click the drive test data from which you want to display comparative statistics. The context menu appears. 4. Select Display Statistics from the context menu. The Measurement and Prediction Fields Selection dialogue appears. 5. Select one or more transmitters from the For the following transmitters list. 6. Select the fields that you want to use for predictions from the Select the predicted values list. Only one type of value can be compared at a time (signal level or quality). 7. Select the fields that you want to use for predictions the Select the measured values list. Only one type of value can be compared at a time (signal level or quality). The measured and the selected values have to match up. 8. Enter the minimum and maximum Measured Values. Statistics are done with drive test data points where the measured values are within this specified range. 9. Click OK. Atoll opens a dialogue in which the global statistics between measurements and predictions are given over all the filtered (or not) points of the current drive test data path through the mean error, its standard deviation, the root mean square and the error correlation factor. The statistics are also given per clutter class.
772
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9.5.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter You can extract a specific field for a specific transmitter on each point of an existing drive test data path. The extracted information will be added to a new column in the table for the drive test data. To extract a field from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Drive Test Data folder.
3. Right-click the drive test data from which you want to extract a field. The context menu appears. 4. Select Focus on a Transmitter from the context menu. The Field Select for a Given Transmitter dialogue appears. 5. Select a transmitter from the On the Transmitter list. 6. Click the For the Fields list. The list opens. 7. Select the check box beside the field you want to extract for the selected transmitter. Atoll can display the best server and up to six other servers in the active set. If you want to display for example, the point signal level, remember to select the check box for the point signal level for all servers in the For the Fields list. The new column will then display the point signal level for the selected transmitter for all servers if a value exists. 8. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitters and with the selected values.
9.5.4.6 Analysing Data Variations Along the Path In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use the Drive Test Data window to see which cell is the serving cell for a given test point. To analyse data variations using the Drive Test Data window. 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Drive Test Data folder.
3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 9.50).
Figure 9.50: 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.51).
773
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Figure 9.51: The Drive Test Data window 6. In the Display Parameters dialogue: • • •
Select the check box next to any field you want to display in the Drive Test Data window. If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new colour from the palette that appears. Click OK to close the Display Parameters dialogue. You can change the display status or the colour of more than one field at a time. You can select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field you want to import. You can select non-contiguous fields by pressing CTRL and clicking each field. You can then change the display status or the colour by right-clicking on the selected fields and selecting the choice from the context menu. The selected fields are displayed in the Drive Test Data window.
7. You can display the data in the drive test data path in two ways: • •
Click the values in the Drive Test Data window. Click the points on the drive test data path in the map window.
The drive test data path appears in the map window as an arrow pointing towards the serving cell, with a number identifying the best server (see Figure 9.50 on page 773). 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 44. 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.
774
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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.50 on page 773).
9.5.5 Exporting a Drive Test Data Path You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Drive Test Data folder.
3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.
9.5.6 Extracting CW Measurements from Drive Test Data You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Drive Test Data folder.
3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears. 5. Under Extract CW Measurements: a. Select one or more transmitters from the For the following transmitters list. b. Select the field that contains the information that you want to export to CW measurements from the Select the measured signal levels list. 6. Under Extraction Parameters of CW Measurement Paths: a. Enter the Min. number of points to extract per measurement path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured Signal Levels. CW measurements are created with drive test data points where the signal levels are within this specified range. 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.
9.5.7 Printing and Exporting the Drive Test Data Window You can print or export the contents of the Drive Test Data window, using the context menu in the Drive Test Data window. To print or export the contents of the Drive Test Data window: 1. Select the Network explorer. 2. Click the Expand button (
) to expand the Drive Test Data folder.
3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 9.50 on page 773). 5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 773. 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.
775
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
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.6 Co-planning UMTS Networks with Other Networks Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a UMTS and a GSM network for the same area in Atoll, and then work with Atoll’s co-planning features to study the mutual impacts of the two networks. Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other network’s Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In addition, you can optimise the settings of the two networks using Atoll’s Automatic Cell Planning (ACP) module. In this section, the following are explained: • • • • • •
"Switching to Co-planning Mode" on page 776 "Working with Coverage Predictions in a Co-Planning Project" on page 778 "Performing Inter-technology Neighbour Allocation" on page 782 "Creating a UMTS Sector From a Sector in the Other Network" on page 793 "Using ACP in a Co-planning Project" on page 794 "Ending Co-planning Mode" on page 795.
9.6.1 Switching to Co-planning Mode Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a UMTS Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, the UMTS document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems.
To switch to co-planning mode: 1. Open the main document. •
Select File > Open or File > New > From an Existing Database.
2. Link the other document with the open main document. a. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document. b. Select Document > Link > Link With. The Link With dialogue appears. c. Select the document to be linked. d. Click Open. The selected document is opened in the same Atoll session as the main document and the two documents are linked. The explorer window of the main document now contains a folder named Transmitters in [linked document], where [linked document] is the name of the linked document and another folder named Predictions in [linked document].
776
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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 Atoll’s co-planning features are now available. When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll syncronises the display for the following: • • • •
Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.
Displaying Both Networks in the Same Atoll Document After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 776, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the explorer window of the linked document to the explorer window of the main document (e.g., you can display GSM sites and measurement paths in a UMTS document). To display sites from the linked document in the main document: 1. Click the linked document’s map window. The linked document’s map window becomes active and the explorer window shows the contents of the linked document. 2. Select the Network explorer. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In from the context menu, and select the name of the main document from the submenu that opens. The Sites folder of the linked document is now available in the main document. The explorer window of the main document now contains a folder named Sites in [linked document], where [linked document] is the name of the linked document. If you want the Sites folder of the linked document to appear in the main document automatically, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual. The same process can be used to link other folders in one document, folders such as CW Measurements, Drive Test Data, Clutter classes, Traffic Maps, and DTM, etc., in the other document. Once the folders are linked, you can access their properties and the properties of the items in the folders from either of the two documents. Any changes you make in the linked document are taken into account in the both the linked and main documents. However, the only changes in the working document that are taken into account in the linked document are changes made to the linked folders (e.g., the Transmitters and Predictions folders). If you close the linked document, Atoll displays a warning icon ( ) in the main document’s explorer window, and the linked items are no longer accessible from the main document. You can load the linked document in Atoll again by right-clicking the linked item in the explorer window of the main document, and selecting Open Linked Document. The administrator can create and set a configuration file for the display parameters of linked and main document transmitters in order to enable you to distinguish them on the map and to be able to select them on the map using the mouse. If such a configuration file has not been set up, you can choose different symbols, sizes and colours for the linked and the main document transmitters. For more information on folder configurations, see "Folder Configurations" on page 105. You can also set the tip text to enable you to distinguish the objects and data displayed on the map. For more information on tip text, see "Defining the Object Type Tip Text" on page 46. 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 Windows" on page 39. Figure 9.52 shows an example of UMTS transmitters with labels, and GSM transmitter data displayed in tip text.
777
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
Figure 9.52: GSM and UMTS Transmitters displayed on the map
9.6.2 Working with Coverage Predictions in a Co-Planning Project Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: • •
"Updating Coverage Predictions" on page 778 "Analysing Coverage Predictions" on page 779.
9.6.2.1 Updating Coverage Predictions You can access the properties of the coverage predictions in the linked Predictions folder in the main document’s explorer window. After modifying the linked coverage prediction properties, you can update them from the main document. To update a linked coverage prediction: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button (
) in the Radio Planning toolbar.
When you click the Calculate button, Atollfirst calculates uncalculated and invalid path loss matrices and then unlocked coverage predictions in the main and linked Predictions folders. When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions" on page 218. 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.
778
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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.6.2.2 Analysing Coverage Predictions In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tip text to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following are explained: • • • • •
9.6.2.2.1
"Co-Planning Coverage Analysis Process" on page 779 "Displaying the Legend Window" on page 779 "Comparing Coverage Prediction Results Using Tip Text" on page 779 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 780 "Studying Differences Between Coverage Areas" on page 781.
Co-Planning Coverage Analysis Process The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes. The recommended process for analysing coverage areas, and the effect of parameter modifications in one network on the other, is as follows: 1. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the main document. For more information, see "Making a Coverage Prediction by Transmitter" on page 669 and "Studying Signal Level Coverage" on page 658. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tip text contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage prediction’s 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 777. 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 780 and "Studying Differences Between Coverage Areas" on page 781. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.
9.6.2.2.2
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: •
9.6.2.2.3
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction in the main and linked Predictions folders, identified by the name of the coverage prediction.
Comparing Coverage Prediction Results Using Tip Text You can compare coverage predictions by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. Atoll displays information for all displayed coverage predictions in both the working and the linked
779
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Analysing Coverage Predictions" on page 779). To get coverage prediction results in the form of tip text: •
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 9.22). The tip text for the working document is on top and the tip text for the linked document, with the linked document identified by name is on the bottom.
Figure 9.53: Comparing coverage prediction results using tip text
9.6.2.2.4
Comparing Coverage Areas by Overlaying Coverage Predictions You can compare the coverage areas of the main and linked documents by overlaying coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 3. Click the Expand button (
) to expand the Predictions folder.
4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is dislayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 43. 9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The coverage prediction is dislayed on the map. 11. Right-click the coverage prediction. The context menu appears. 12. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 13. Modify the display parameters of the coverage prediction. 14. Calculate the two coverage predictions again, if needed. Figure 9.54 and Figure 9.55 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 Windows" on page 39.
780
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
Figure 9.54: UMTS coverage by transmitter – pink contours with no interior
Figure 9.55: GSM coverage by transmitter – high transparency with full interior coloured by BCCH, with BCCH/BSIC information available in tip text
9.6.2.2.5
Studying Differences Between Coverage Areas You can compare coverage predictions to find differences in coverage areas. To compare coverage predictions: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 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 coverage prediction in the linked document you want to compare with the coverage prediction of the main document. The Comparison Properties dialogue opens. 6. Select the display parameters of the comparison and add a comment if you want. 7. Click OK.
781
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
The two coverage predictions are compared and a comparison coverage prediction is added to the main document’s Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 677.
9.6.3 Performing Inter-technology Neighbour Allocation Atoll enables you to carry out inter-technology neighbour planning. For example, you can study handovers between a UMTS and a GSM network in Atoll by allocating neighbour GSM sectors to UMTS cells. In this section, the following are explained: • • • • • • • • •
"Setting Inter-technology Exceptional Pairs" on page 782 "Displaying Inter-technology Exceptional Pairs on the Map" on page 783 "Adding and Removing Inter-technology Exceptional Pairs on the Map" on page 783 "Configuring Importance Factors for Inter-technology Neighbours" on page 784 "Allocating Inter-technology Neighbours Automatically" on page 784 "Displaying Inter-technology Neighbours on the Map" on page 786 "Allocating and Deleting Inter-technology Neighbours per Cell" on page 787 "Calculating the Importance of Existing Inter-technology Neighbours" on page 790 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 792.
In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Coplanning Mode" on page 776.
9.6.3.1 Setting Inter-technology Exceptional Pairs You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Exceptional Pairs from the context menu. The Inter-technology Neighbours Exceptional Pairs table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list. c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. d. Atoll fills the Number and Distance (m) fields automatically. In GSM, neighbours and exceptional pairs are allocated by transmitter (i.e., by sector). You can access a cell’s inter-technology neighbours and exceptional pairs by using its Properties dialogue. To open a cell’s Properties dialogue: 1. Select the Network explorer. 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 cell’s Properties dialogue appears. 5. Click the Inter-technology Neighbours tab. In GSM, the Inter-technology Neighbours tab is found on the transmitter’s Properties dialogue.
782
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9.6.3.2 Displaying Inter-technology Exceptional Pairs on the Map You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table. To display exceptional pairs defined between the main and the linked documents: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Display Options from the context menu. The Neighbour Display dialogue appears. 5. Under Inter-technology Neighbours, select the Display Links check box. 6. Under Advanced, select which exceptional pair links to display: •
•
•
Outwards Non-Symmetric: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Selecting this option displays an exceptional pair link for each transmitter/cell in the linked document that has an exceptional pair defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric Links: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines.
7. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
8. Select Forced Neighbours or Forbidden Neighbours from the menu. The exceptional pair of a cell will be displayed when you select a transmitter. 9. Click the Edit Relations on the Map button ( ) in the Radio Planning toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Visual Management button again. 10. Click a transmitter on the map to show its exceptional pair links. When there is more than one cell on the transmitter, 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 41). 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.
9.6.3.3 Adding and Removing Inter-technology Exceptional Pairs on the Map You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-technology Exceptional Pairs on the Map" on page 783. 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.
783
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
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. 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 41).
9.6.3.4 Configuring Importance Factors for Inter-technology Neighbours You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Inter-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: • •
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. The Adjacency factor is not used when calculating the importance of inter-technology neighbours.
•
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 784.
5. Click OK.
9.6.3.5 Allocating Inter-technology Neighbours Automatically Atoll can automatically determine handover relations between networks of different technologies, for example, UMTS and GSM. In this case, inter-technology handovers from UMTS to GSM may occur when the UMTS coverage is not continuous. The network’s overall coverage is extended by a UMTS-to-GSM handover. Atoll can automatically determine neighbours in the linked document for cells in the main document and vice versa. Inter-technology neighbours are stored in the database.
784
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
By setting an option in the atoll.ini file, you can prevent Atoll from allocating inter-technology neighbours to cells located on sites whose equipment does not support the compressed mode. For more information, see the Administrator Manual. To automatically allocate neighbours in the linked document for cells in the main document: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > 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 a distance criterion and continue with step 9. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour allocation on coverage conditions. a. Click the Define button to change the coverage conditions for the cells in the main document. The UMTS Coverage Conditions dialogue appears. In the UMTS Coverage Conditions dialogue, you can change the following parameters: • • • • • • • •
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.
785
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
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 cell’s coverage area that the neighbour’s coverage area should also cover to be considered as a neighbour. 9. Under Calculation Options, define the following: • •
• •
CDMA Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers; Atoll will allocate neighbours to cells using the selected carriers. Force co-site as neighbours: Selecting the Force co-site as neighbours check box will include the co-site transmitters/cells in the neighbour list of the UMTS cell. The check box is automatically selected when the neighbour allocation is based on distance. Force exceptional pairs: Selecting the Force exceptional pairs check box will apply the inter-technology exceptional pair criteria on the neighbours list of the UMTS cell. Delete existing neighbours: Selecting the Delete existing neighbours check box will delete all existing neighbours in the neighbours list and perform a clean neighbour allocation. If the Delete existing neighbours check box is not selected, Atoll keeps the existing neighbours in the list.
10. Click the Calculate button to start calculations. 11. Once the calculations finish, Atoll displays the list of neighbours in the Results section. The results include the names of the neighbours, the number of neighbours of each cell, and the reason they are included in the neighbours list. The reasons include: Reason
Description
When
Exceptional Pair
Neighbour relation is defined as an exceptional pair.
Force exceptional pairs is selected
Co-site
The neighbour is located at the same site as the reference cell.
Force co-site as neighbours is selected
Distance
The neighbour is within the maximum distance from the reference cell.
Use coverage overlapping is not selected
% of covered area and overlapping area
Neighbour relation that fulfils coverage conditions.
Use coverage overlapping is selected
Existing
The neighbour relation existed before running the automatic allocation.
Reset is not selected
12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: •
Click Compare. The list of automatically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt which appears at the end of the comparison. This file lists: • • • •
The document name and the neighbour allocation type, 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.6.3.6 Displaying Inter-technology Neighbours on the Map You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios. To display neighbours in the linked document for cells in the main document: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears.
786
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
3. Select Neighbours > Inter-technology > Display Options from the context menu. The Neighbour Display dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select the neighbour links to display: •
•
•
Outwards Non-Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric Links: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines.
6. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
7. Select Neighbours as the type of neighbour links to display. 8. Click the Edit Relations on the Map button ( ) in the Radio Planning toolbar. Neighbours are now displayed on the map. Neighbours are displayed until you click the Edit Relations on the Map button again. 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, 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 41). If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intratechnology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.
9.6.3.7 Allocating and Deleting Inter-technology Neighbours per Cell Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Inter-technology Neighbours table. This section explains the following: • •
"Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 788. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 788.
787
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
•
© Forsk 2012
"Allocating and Removing Inter-technology Neighbours on the Map" on page 789.
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 transmitter’s Properties dialogue: 1. On the main document’s map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitter’s 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 cell’s Properties dialogue appears. 5. Click the Inter-technology Neighbours tab. 6. If desired, you can enter the Maximum Number of Neighbours. To allocate a new neighbour: 1. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. 2. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon (
).
3. Click elsewhere in the table to complete creating the new neighbour. 4. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, and sets the Source to "manual." To create a symmetric neighbour relation: 1. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. 2. Click in the left margin of the table row containing the neighbour to select the entire row. 3. Right-click the neighbour in the Neighbour column. The context menu appears. 4. 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: 1. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. 2. Click in the left margin of the table row containing the neighbour to select the entire row. 3. Right-click the neighbour in the Neighbour column. The context menu appears. 4. 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: 1. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. 2. Click in the left margin of the table row containing the neighbour to select the entire row. 3. Press DEL to delete the neighbour. In GSM, the Inter-technology Neighbours tab is available in each transmitter’s Properties dialogue. Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Open Table from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour.
788
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
To allocate an inter-technology neighbour: 1. In the row marked with the New Row icon (
), select a reference cell in the Cell column.
2. Select the neighbour in the Neighbour column. 3. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. 4. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Source to "manual." To create a symmetric neighbour relation: 1. Right-click the neighbour in the Neighbour column. The context menu appears. 2. 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: 1. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. 2. Right-click the Neighbours table. The context menu appears. 3. Select Make Symmetrical from the context menu. To take all exceptionnal pairs into consideration: 1. Right-click the Neighbours table. The context menu appears. 2. Select Force Exceptional Pairs from the context menu. You can add or delete either forced neighbours or forbidden neighbours using the Exceptional Pairs of Inter-technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu. To delete a symmetric neighbour relation: 1. Click in the left margin of the table row containing the neighbour to select the entire row. 2. Right-click the Neighbours table. The context menu appears. 3. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. To delete several symmetric neighbour relations: 1. Click in the left margin of the table rows containing the neighbours to select entire rows. You can select contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. 2. Right-click the Neighbours table. The context menu appears. 3. Select Delete Link and Symmetric Relation from the context menu. To delete a neighbour: 1. Click in the left margin of the table row containing the neighbour to select the entire row. 2. Press DEL to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector). Allocating and Removing Inter-technology Neighbours on the Map You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-technology Neighbours on the Map" on page 786. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter.
789
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter. T remove an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the list of inter-technology neighbours of the other transmitter. To add an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. There can be two cases: • •
If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric intertechnology 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. 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 41).
9.6.3.8 Calculating the Importance of Existing Inter-technology Neighbours After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing inter-technology neighbours: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Calculate Importance from the context menu. The Neighbour Importance Evaluation dialogue appears. 5. Select the Inter-technology Neighbours tab. 6. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as possible neighbours. 7. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance. 8. Clear the Use Overlapping Coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 10. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour importance calculation on coverage conditions.
790
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for cells in the main document. The UMTS Coverage Conditions dialogue appears. In the UMTS Coverage Conditions dialogue, you can change the following parameters: • • • • • • • •
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. 10. If you cleared the Use Overlapping Coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated. 11. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information.
791
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• • • •
© Forsk 2012
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: If you calculated neighbour importance using inter-site distance, Atoll gives the distance in kilometres between the reference cell and the neighbour.
•
Coverage: If you calculated neighbour importance using coverage overlapping, Atoll gives the amount of reference transmitter’s coverage area that the neighbour overlaps, in percentage and in square kilometres.
12. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
9.6.3.9 Checking the Consistency of the Inter-technology Neighbour Plan You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Inter-technology > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Neighbours tab. 5. Define the parameters of the audit: • • •
•
• • • •
Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Which cells having the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Lists > Max Number: Which cells having more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that should not be exceeded.
6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: •
Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax:
•
Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax:
•
|CELL|
|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| 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.
792
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax:
•
Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Distance Between Neighbours > Y: X; total number of neighbours in the audited neighbour plan that are located at a distance greater than Y. Syntax:
|CELL| |NEIGHBOUR| |DISTANCE|
9.6.4 Creating a UMTS Sector From a Sector in the Other Network You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main document’s map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new UMTS transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document. To update the display settings of the new sector: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder of the main document. The context menu appears. 4. Select Update Folder Configuration from the context menu.
Figure 9.56: New sector – Before and after applying the configuration The azimuths and mechanical tilts of secondary antennas or remote antennas are not included when you select Update Folder Configuration and have to be set up manually.
793
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
9.6.5 Using ACP in a Co-planning Project Atoll ACP enables you to automatically calculate the optimal network settings in terms of network coverage and capacity in co-planning projects where networks using different technologies, for example, UMTS and GSM, must both be taken into consideration. When you run an optimisation setup in a co-planning environment, you can display the sites and transmitters of both networks in the document in which you will run the optimisation process, as explained in "Switching to Co-planning Mode" on page 776. 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 794 "Importing the Other Network into the Setup" on page 794.
9.6.5.1 Creating a New Co-planning Optimisation Setup Once you have displayed both networks in the main document as explained in "Switching to Co-planning Mode" on page 776, you can create the new co-planning optimisation setup. To create a new co-planning optimisation setup: 1. Click the main document’s map window. 2. Select the Network explorer. 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 234. 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.
9.6.5.2 Importing the Other Network into the Setup Once you have created the co-planning optimisation setup, you must import the linked network. To import the linked network: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Click the Expand button (
) to expand the ACP - Automatic Cell Planning folder.
4. Right-click the setup you created in "Creating a New Co-planning Optimisation Setup" on page 794. The context menu appears. 5. Select Import Project from the context menu and select the name of the linked document you want to import into the newly created setup.
The setup has been modified to include the linked network.
794
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
You can modify the parameters for the optimisation setup by right-clicking it in the Network explorer and selecting Properties from the context menu. For information on the parameters available, see "Defining Optimisation Parameters" on page 234. After defining the co-planning optimisation setup: •
Right-click the setup in the ACP - Automatic Cell Planning folder and select Run from the context menu to run the optimisation. For information on running the optimisation, see "Running an Optimisation Setup" on page 267. For information on the optimisation results, see "Viewing Optimisation Results" on page 270.
9.6.6 Ending Co-planning Mode once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents. To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select Document > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.
9.7 Advanced Configuration In this section, the following advanced configuration options are explained: • • • • • • • • • •
"Modelling Inter-Carrier Interference" on page 795 "Defining Frequency Bands" on page 796 "The Global Network Settings" on page 796 "Radio Bearers" on page 798 "Site Equipment" on page 799 "Receiver Equipment" on page 801 "Multiple Input Multiple Output Systems" on page 804 "Conditions for Entering the Active Set" on page 805 "Modelling Shadowing" on page 805 "Modelling Inter-technology Interference" on page 806.
9.7.1 Modelling Inter-Carrier Interference If you want Atoll to take into account the interference between two carriers, you must create a carrier pair with an interference reduction factor. Atoll will take the interference reduction factor into account on both the uplink and the downlink. To create a pair of carriers with an interference reduction factor: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Frequencies folder.
4. Right-click the Intra-technology Interference Reduction Factors folder. The context menu appears. 5. Select Open Table from the context menu. The Inter-Carrier Interference Reduction Factor table appears. 6. For each carrier pair for which you want define inter-carrier interference: a. Enter the first carrier of the pair in the 1st Carrier column. b. Enter the second carrier of the pair in the 2nd Carrier column. c. Enter an interference reduction factor in the Reduction Factor (dB) column. When Atoll is calculating interference, it subtracts the interference reduction factor from the calculated interference. If the interference reduction factor is set to "0," Atoll assumes that the carriers in the defined pair generate as much interference as cells with the same carrier interference. The interference reduction factor must be a positive value.
795
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
For every pair of carriers that is not defined, Atoll assumes that there is no inter-carrier interference. d. Press ENTER to create the carrier pair and to create a new row in the table.
9.7.2 Defining Frequency Bands To define frequency bands: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Frequencies folder.
4. In the Frequencies folder, right-click Bands. The context menu appears. 5. Select Open Table from the context menu. The Frequency Bands table appears. 6. In the Frequency Bands table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each frequency band, enter: • • • •
Name: Enter a name for the frequency, for example, "Band 2100." This name will appear in other dialogues when you select a frequency band. Average Frequency (MHz): Enter the average frequency. First Carrier: Enter the number of the first carrier in this frequency band. Last Carrier: Enter the number of the last carrier in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First Carrier field. When you have more than one frequency band, the carriers must be numbered sequentially, contiguously (i.e., you cannot skip numbers in a range of carriers, and the range of carriers in one band cannot overlap the range of carriers in another), and uniquely (i.e., you can only use each number once). For example: Band 2100: First carrier: 0; Last carrier 1 and Band 900: First carrier: 2 and Last carrier: 2
7. When you have finished adding frequency bands, click the Close button (
).
9.7.3 The Global Network Settings In the Network Settings Properties dialogue, you can define many calculation parameters that are used in predictions and in Monte Carlo simulations. This section explains the options available in the Network Settings Properties dialogue, and explains how to access the dialogue: • •
"The Options of the Network Settings Properties Dialogue" on page 796 "Modifying Global Network Settings" on page 797.
9.7.3.1 The Options of the Network Settings Properties Dialogue The Network Settings Properties dialogue has two tabs: the Global Parameters Tab and the Calculation Parameters tab. • •
9.7.3.1.1
"The Global Parameters Tab" on page 796 "The Calculation Parameters Tab" on page 797
The Global Parameters Tab The Global Parameters tab has the following options:
796
•
DL Powers: Under DL Powers, you can define whether the power values on the downlink are Absolute or offset from the pilot (Pilot Offset). The power values affected are the synchronisation channel, other common channel, HS-SCCH, and HSUPA powers defined in the cell properties, as well as the minimum and maximum traffic channel powers per R99 radio bearer. Atollautomatically converts the power values defined in the cell properties (i.e., synchronisation channel, other common channel, HS-SCCH, and HSUPA powers) when you change the option. On the other hand, the values for the minimum and maximum traffic channel powers have to be modified manually.
•
DL Load: Under DL Load, you can define whether the total power values on the downlink are Absolute or a percentage of the maximum power (% Pmax). Atollautomatically converts the total power values when you change the option.
•
Interferences: Under Interferences, you can define the method used to calculate interference on the downlink (I0 and Nt):
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
•
•
•
Handoff: Under Handoff, you can define the parameters used to model soft handoff on the uplink. •
•
•
I0: You can select "Total noise" and Atoll will calculate I0 using the noise generated by all transmitters plus thermal noise or you can select "Without pilot" and Atoll will calculate I0 using the total noise less the pilot signal and orthogonal part of traffic channels and other common channels. Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus thermal noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the signal of the studied cell. Default UL Macro-Diversity Gain: You can set a default value for the uplink gain due to macro-diversity on soft and soft-soft handovers. If you clear the Shadowing taken into account check box on the Conditions tab when defining a coverage prediction or during a point analysis, Atoll uses this value. If you select the Shadowing taken into account check box on the Conditions tab, Atoll calculates the UL macro-diversity gain, based on the standard deviation value of Eb⁄Nt on the uplink defined per clutter class. +MRC (maximal ratio combining) in Softer/Soft: If you select the +MRC in Softer/Soft check box, Atoll selects the serving cell during a softer/soft handover by recombining the signal of co-site transmitters and multiplying the resulting signal by the rake efficiency factor and then comparing this value to the signal received at transmitters located on the other sites of the active set. Atoll chooses the greatest value and multiplies it by the macro-diversity gain.
Compressed Mode: Under Compressed Mode, you can define the parameters related to compressed mode. Compressed mode is used when a mobile supporting compressed mode is connected to a cell located on a site with a compressed-mode-capable equipment and either the pilot RSCP, or the received Ec⁄I0, or both of them are lower than the defined activation thresholds. • •
Pilot RSCP Activation Threshold: You can select the RSCP Active check box and enter a Pilot RSCP Activation Threshold. Ec⁄I0 Activation Threshold: You can select the Ec⁄I0 Active check box and enter a Ec⁄I0 Activation Threshold. You must select either the RSCP Active check box or the Ec⁄I0 Active check box or both.
•
•
HSDPA: Under HSDPA, you can define how total noise is calculated and how the CQI (Channel Quality Indicator) is evaluated for HSDPA. •
•
9.7.3.1.2
Eb⁄Nt UL and DL Target Increase: When compressed mode is activated, Eb⁄Nt requirements in UL and DL are increased. In order to take this into account, Atoll adds UL and DL Eb⁄Nt target increase values to the UL and DL Eb⁄Nt requirements set for each radio bearer.
Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus thermal noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the signal of the studied cell. CQI: You can select “Based on CPICH quality” and Atoll will measure the CQI based on the pilot Ec⁄Nt or you can select “Based on HS-PDSCH quality” and Atoll will measure the CQI based on the HS-PDSCH Ec⁄Nt. Depending on the option selected, you will have to define either a CQI=f(CPICH Ec/Nt) graph, or a CQI=f(HS-PDSCH Ec/Nt) graph in the Properties dialogue of the terminal equipment. The calculated CQI will be used to determine the best bearer.
The Calculation Parameters Tab The Calculation Parameters tab has the following options: •
Calculation limitation: Under Calculation limitation, you can define the following data: •
•
Min. interferer reception threshold: This value is used by Atoll to limit the influence of interferers in calculations. The performance of UMTS-specific coverage predictions and Monte Carlo simulations can be improved by setting a high minimum interferer reception threshold. This value is used as a filter criterion on the signal level received from interferers. Atoll will discard all interferers with a signal level lower than this value. • Min. pilot RSCP threshold: The minimum pilot RSCP threshold. The value is used as a filter criterion on the received pilot signal level when calculating UMTS-specific predictions. Atoll does not display any result on the pixel if the pilot signal level received from the best server is lower than the defined min. pilot RSCP threshold. Receiver: Under Receiver, you can enter the Height of the receiver.
9.7.3.2 Modifying Global Network Settings You can change global network settings in the Network Settings Properties dialogue. To change global network settings: 1. Select the Parameters explorer. 2. Right-click the Network Settings folder. The context menu appears.
797
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
3. Select Properties from the context menu. The Network Settings Properties dialogue appears. 4. Modify the parameters described in "The Options of the Network Settings Properties Dialogue" on page 796. 5. Click OK.
9.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 798 "Defining HSDPA Radio Bearers" on page 798 "Defining HSUPA Radio Bearers" on page 799.
9.7.4.1 Defining R99 Radio Bearers Bearer services are used by the network for carrying information. The R99 Radio Bearer table lists all the available radio bearers. You can create new R99 radio bearers and modify existing ones by using the R99 Radio Bearer table. Only the following R99 radio bearer parameters are used in predictions: • •
Max TCH Power (dBm) The type of bearer.
To create or modify an R99 radio bearer: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Radio Bearers folder.
4. Right-click the R99 Radio Bearers folder. The context menu appears. 5. Select Open Table from the context menu. The R99 Radio Bearers table appears. 6. In the R99 Radio Bearers table, you can enter or modify the following fields: • • • • •
• • •
Name: You can modify the name of the bearer. If you are creating a new R99 radio bearer, enter a name in the row marked with the New Row icon ( ). Nominal Uplink Rate (Kbps): Enter or modify the nominal uplink rate in kilobytes per second. Nominal Downlink Rate (Kbps): Enter or modify the nominal downlink rate in kilobytes per second. Type: Select or modify the service type. There are four classes: Conversational, Streaming, Interactive, and Background. This field corresponds to the QoS (quality of service) class or traffic class that the bearer will belong to. UL DPCCH/DPCH Power Ratio: Enter or modify the uplink DPCCH (Dedicated Physical Control Channel)/DPCH (Dedicated Physical Channel) power ratio. The DPCH power is the combination of the DPCCH and the DPDCH (Dedicated Physical Data Channel) power. DL DPCCH/DPCH Power Ratio: Enter or modify the downlink DPCCH (Dedicated Physical Control Channel)/DPCH (Dedicated Physical Channel) power ratio. Min. TCH Power (dBm): Enter or modify the minimum traffic channel power. The minimum and maximum traffic channel power make up the dynamic range for downlink power control. Max TCH Power (dBm): Enter or modify the maximum traffic channel power. The maximum and minimum traffic channel powers can be either absolute values or values relative to the pilot power; this depends on the option defined on the Global Parameters tab of the UMTS Network Settings Properties dialogue. These values have to be manually modified when the option is changed.
• •
DL Spreading Factor (Active Users): Enter or modify the downlink spreading factor for active users. This parameter is used to estimate the number of OVSF codes required by an active user using the R99 radio bearer. DL Spreading Factor (Inactive Users): Enter or modify the downlink spreading factor for inactive users. This parameter is used to estimate the number of OVSF codes required by an inactive user with the R99 radio bearer.
9.7.4.2 Defining HSDPA Radio Bearers In each cell, the scheduler selects the HSDPA resource per UE and per TTI. This HSDPA resource is called a TFRC (Transport Format Resource Combination) and is the set of parameters such as the transport format, the modulation scheme, and the number of used HS-PDSCH channels. In Atoll, the TFRC are referred to as HSDPA radio bearers. During a simulation, and for the HSDPA coverage prediction, Atoll selects a suitable HSDPA radio bearer and uses its RLC peak rate. The HSDPA radio bearer selection is based on UE capabilities (maximum number of HS-PDSCH channels, transport block size, modulation supported), cell capabilities (HSPA or HSPA+, MIMO system used, maximum number of HS-PDSCH channels), and reported CQI.
798
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
The HSDPA Radio Bearers table lists the available HSDPA radio bearers. They can be classified into two categories: • •
HSDPA bearers using QPSK and 16QAM modulations. They can be selected for users connected to HSPA and HSPA+ capable cells. HSDPA bearers using 64QAM modulation (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+). These HSDPA bearers can be allocated to users connected to cells with HSPA+ capabilities only.
You can create new HSDPA radio bearers and modify existing ones by using the HSDPA Radio Bearers table. To open the HSDPA Radio Bearers table: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Radio Bearers folder.
4. Right-click the HSDPA Radio Bearers folder. The context menu appears. 5. Select Open Table from the context menu. The HSDPA Radio Bearers table appears with the following information: • • • • •
Radio Bearer Index: The bearer index number. Transport Block Size (Bits): The transport block size in bits. Number of Used HS-PDSCH Channels: The number of HS-PDSCH channels used. RLC Peak Rate (bps): The RLC peak rate represents the peak rate without coding (redundancy, overhead, addressing, etc.). Modulation: The modulation used. You can choose between QPSK, 16QAM or 64QAM.
9.7.4.3 Defining HSUPA Radio Bearers In each cell, the scheduler selects the HSUPA resource per UE, per Node B, and per user service. This HSUPA resource is called a TFC (Transport Format Combination) and requires a defined ratio of E-DPDCH power over DPCCH power. This ratio is modelled as the required E-DPDCH Ec⁄Nt. The combination of the TFC and the power offset is modelled in Atoll as HSUPA radio bearers. During a simulation, and for the HSUPA coverage prediction, Atoll selects a suitable HSUPA radio bearer. The HSUPA radio bearer selection is based on UE capabilities (maximum number of E-DPDCH codes, smallest spreading factor, TTI length, and modulation supported), cell capabilities (HSPA or HSPA+), and the required E-DPDCH Ec⁄Nt. The HSUPA Radio Bearers table lists the available HSUPA radio bearers. They can be classified into two categories: • •
HSUPA bearers using QPSK modulation. They can be selected for users connected to HSPA and HSPA+ capable cells. HSUPA bearers using 16QAM modulation (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+). These HSUPA bearers can be allocated to users connected to cells with HSPA+ capabilities only.
To open the HSUPA Radio Bearers table: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Radio Bearers folder.
4. Right-click the HSUPA Radio Bearers folder. The context menu appears. 5. Select Open Table from the context menu. The HSUPA Radio Bearers table appears with the following information: • • • • • • •
Radio Bearer Index: The bearer index number. TTI Duration (ms): The TTI duration in ms. The TTI can be 2 or 10 ms. Transport Block Size (Bits): The transport block size in bits. Number of E-DPDCH Codes: The number of E-DPDCH channels used. Min. Spreading Factor: The minimum spreading factor used. RLC Peak Rate (bps): The RLC peak rate represents the peak rate without coding (redundancy, overhead, addressing, etc.). Modulation: The modulation used. You can choose between QPSK or 16QAM.
9.7.5 Site Equipment In this section, the following are described: • • •
"Creating Site Equipment" on page 800 "Defining Resource Consumption per UMTS Site Equipment and R99 Radio Bearer" on page 801 "Defining Resource Consumption per UMTS Site Equipment and HSUPA Radio Bearer" on page 801.
799
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
9.7.5.1 Creating Site Equipment To create a new piece of UMTS site equipment: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Radio Resource Management folder.
4. Right-click Site Equipment. The context menu appears. 5. Select Open Table from the context menu. The Site Equipment table appears. 6. In the Equipment table, each row describes a piece of equipment. For information on working with data tables, see "Working with Data Tables" on page 69. For the new piece of UMTS equipment you are creating, enter the following: • • •
•
Name: The name you enter will be the one used to identify this piece of equipment. Manufacturer: The name of the manufacturer of this piece of equipment. MUD factor: Multi-User Detection (MUD) is a technology used to decrease intra-cell interference in the uplink. MUD is modelled by a coefficient from 0 to 1; this factor is considered in the UL interference calculation. In case MUD is not supported by equipment, enter 0 as value. Rake factor: The rake receiver efficiency factor enables Atoll to model the rake receiver on UL. Atoll uses this factor to calculate the uplink SHO gain and uplink signal quality in simulations, point-to-point handover analysis and coverage predictions. This parameter is considered in the uplink for softer and softer-softer handovers; it is applied to the sum of signals received on the same site. The factor value can be from 0 to 1. It models losses due to the imperfection of signal recombination. The rake receiver efficiency factor used to model the recombination in downlink can be set in terminal properties.
•
Carrier selection: Carrier selection refers to the carrier selection method used during the transmitter admission control in the mobile active set. The selected strategy is used in simulations when no carrier is specified in the properties of the service (all the carriers can be used for the service) or when the carrier specified for the service is not used by the transmitter. On the other hand, the specified carrier selection mode is always taken into account in predictions (AS analysis and coverage predictions). Choose one of the following: • • • •
•
• •
Min. UL Load Factor: The carrier with the minimum UL noise (carrier with the lowest UL load factor) is selected. Min. DL Total Power: The carrier with the minimum DL total power is selected. Random: The carrier is randomly chosen. Sequential: Carriers are sequentially loaded. The first carrier is selected as long as it is not overloaded. Then, when the maximum uplink load factor is reached, the second carrier is chosen and so on.
Downlink and Uplink Overhead Resources for Common Channels/Cell: The uplink and downlink overhead resources for common channels/cell correspond to the numbers of channel elements that a cell uses for common channels in the uplink and downlink. This setting is also used for OVSF code allocation; it indicates the number of OVSF codes to be allocated to control channels per cell. AS restricted to neighbours: Select this option if you want the other transmitters in the active set to belong to the neighbour list of the best server. Compressed Mode: If you select this option, cells located on sites with this equipment are able to manage compressed mode when radio conditions require it. Compressed mode is generally used to prepare the hard handover of users with single receiver terminals. By setting an option in the atoll.ini file, you can prevent Atoll from allocating inter-carrier and inter-technology neighbours to cells located on sites whose equipment does not support the compressed mode. For more information, see the Administrator Manual.
• •
•
Overhead Iub Throughput/Cell (kbps): The overhead Iub throughput per cell corresponds to the Iub throughput required by the cell for common channels in the downlink. HSDPA Iub Backhaul Overhead (%): The HSDPA Iub backhaul overhead corresponds to the percentage of the HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corresponds to the Iub backhaul throughput required by the HSDPA user for HS Channels in the downlink. Throughput Supported per E1/T1/Ethernet Link (kbps): The throughput supported per E1/T1/Ethernet link corresponds to the throughput carried by an E1/T1/Ethernet link. This parameter is used to calculate the required Iub capacity, i.e. the number of E1/T1/Ethernet links required to provide the total throughput.
7. Click the Close button (
800
) to close the table.
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
9.7.5.2 Defining Resource Consumption per UMTS Site Equipment and R99 Radio Bearer The number of channel elements and the Iub backhaul throughput consumed by an R99 bearer user depend on the site equipment, on the R99 radio bearer, and on the link direction (up or down). The number of channel elements and the Iub backhaul throughput consumed can be defined for UMTS simulations. To define channel element and Iub backhaul throughput consumption during UMTS simulations: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Radio Resource Management folder.
4. Right-click R99 Resource Consumption. The context menu appears. 5. Select Open Table from the context menu. The R99 Resource Consumption table appears. 6. For each equipment-R99 radio bearer pair, enter in the R99 Resource Consumption table the number of UL and DL channel elements and the UL and DL Iub backhaul throughputs that Atoll will consume during the power control simulation.
9.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. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Radio Resource Management folder.
4. Right-click HSUPA Resource Consumption. The context menu appears. 5. Select Open Table from the context menu. The HSUPA Resource Consumption table appears. 6. For each equipment-HSUPA radio bearer pair, enter in the HSUPA Resource Consumption table the number of UL channel elements and the UL Iub backhaul throughput that Atoll will consume during the power control simulation.
9.7.6 Receiver Equipment In this section, the following are described: • • •
"Creating or Modifying Reception Equipment" on page 801 "HSDPA UE Categories" on page 803 "HSUPA UE Categories" on page 803.
9.7.6.1 Creating or Modifying Reception Equipment In Atoll, reception equipment models the reception characteristics of user terminals and is used when you create a terminal. The graphs defined for each reception equipment entry are used for quality predictions and for selecting HSDPA and HSUPA bearers. To create or modify reception equipment: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the Reception Equipment folder.
"Standard" is the default reception equipment type for all terminals. 4. Double-click the reception equipment type you want to modify. The reception equipment type’s Properties dialogue appears. You can create a new reception equipment type by right-clicking the Reception Equipment folder and selecting New from the context menu.
801
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
5. Click the General tab. On the General tab, you can define the Name of the reception equipment. 6. Click the R99 Bearer Selection tab. On the R99 Bearer Selection tab, you can define downlink and uplink Eb⁄Nt requirements. These are the thresholds (in dB) that must be reached to provide users with the service. These parameters depend on the mobility type. Using transmit (Tx) and receive (Rx) diversity results in a quality gain on received downlink and uplink Eb⁄Nt. You can specify gains on received downlink and uplink Eb⁄Nt for each diversity 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 (Eb⁄Nt) threshold. Uplink 2RX Diversity Gain (dB): Enter or modify the two-receiver uplink diversity gain in dB. Uplink 4RX Diversity Gain (dB): Enter or modify the four-receiver uplink diversity gain in dB. DL Target (dB): Enter or modify the downlink (Eb⁄Nt) threshold. Downlink Open Loop Diversity Gain (dB): Enter or modify the downlink open loop diversity gain in dB. 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 predictions. 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 HS-PDSCH CQI as a function of the HS-PDSCH Ec/Nt); the values displayed depend on the calculation parameter you have selected in the Global Parameters tab of the UMTS Network Settings Properties dialogue (for more information, see "The Options of the Network Settings Properties Dialogue" on page 796). The HS-PDSCH CQI table describes the index of the best HSDPA bearer as a function of the HS-PDSCH CQI. The CQI graphs and best bearer graphs are used in the simulation and in the HSDPA prediction to model fast link adaptation (selection of the HSDPA bearer). The supplier RRM (radio resource management) strategy can be taken into account using the HS-PDSCH CQI table, for example: • • •
You can define several pieces of reception equipment with a separate table for each. You can reserve low bearer indexes for poor-performance reception equipment and higher bearer indexes for high-performance equipment. You can specify a graph for each mobility. Here, you can reserve low bearer indexes for high speeds and higher bearer indexes for low speeds. You can also give priority to either one user by assigning him a high bearer index or to all users by assigning them low bearer indexes.
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 HSDPA BLER table describes the variation of the BLER as a function of the HS-PDSCH Ec⁄Nt. It is used to calculate the application throughput for the HSDPA coverage prediction. 13. Click the HSUPA Bearer Selection tab. 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 Ec⁄Nt 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 Ec⁄Nt 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.
802
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
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 HSUPA BLER table describes the variation of the BLER as a function of the E-DPDCH Ec⁄Nt. 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 804. RX No MIMO gain (diversity, spatial multiplexing) is applied if N TX Ant = N Ant = 1 .
19. Click OK to close the reception equipment type’s Properties dialogue.
9.7.6.2 HSDPA UE Categories HSDPA user equipment capabilities are standardised into 22 different categories according to 3GPP specifications. To edit a UE category: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the UE Categories folder.
4. Right-click HSDPA UE Categories. The context menu appears. 5. Select Open Table from the context menu. The HSDPA User Equipment Categories table appears. 6. The HSDPA User Equipment Categories table has the following columns: • • • • • •
• •
Index: Each HSDPA UE category is a separate record in the table and has a unique index. Category Name: Name of the HSDPA UE category. Max. Number of HS-PDSCH Channels: The maximum number of HS-PDSCH channels allowed for the category. Min. Number of TTI Between Two Used TTI: The minimum number of TTI (Transmission Time Interval) between two TTI used. Max. Transport Block Size (bits): The maximum transport block size allowed for the category. Highest Modulation: Select the highest modulation supported by the category. You can choose between QPSK, 16QAM (if you select 16QAM, 16QAM and QPSK modulations can be used) or 64QAM (if you select 64QAM, 64QAM, 16QAM and QPSK modulations can be used). MIMO Support: Select whether the category supports MIMO systems or not. Multi-cell Mode: Select whether the category supports dual-cell HSDPA or not.
9.7.6.3 HSUPA UE Categories HSUPA user equipment capabilities are standardised into 7 different categories according to 3GPP specifications. To edit a UE category: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the UMTS Network Settings folder.
3. Click the Expand button (
) to expand the UE Categories folder.
4. Right-click HSUPA UE Categories. The context menu appears. 5. Select Open Table from the context menu. The HSUPA User Equipment Categories table appears. 6. The HSUPA User Equipment Categories table has the following columns: • • •
Index: Each HSUPA UE category is a separate record in the table and has a unique index. Category Name: Name of the HSUPA UE category. Max Number of E-DPDCH Codes: The maximum number of E-DPDCH codes allowed for the category.
803
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
• • • • •
© Forsk 2012
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.
9.7.7 Multiple Input Multiple Output Systems Multiple Input Multiple Output (MIMO) systems which are supported by some HSDPA bearers (following improvements introduced by release 7 of the 3GPP UTRA specifications, referred to as HSPA+) use different transmission and reception diversity techniques. MIMO diversity systems can be roughly divided into the types described in the following sections, all of which are modelled in Atoll. Transmit and Receive Diversity Transmit or receive diversity uses more than one transmission or reception antenna to send or receive more than one copy of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining) at the receiver to extract the useful signal. As the receiver gets more than one copy of the useful signal, the signal level at the receiver after combination of all the copies is more resistant to interference than a single signal would be. Therefore, diversity improves the quality at the receiver. It is often used for the regions of a cell that have bad quality conditions. In Atoll, you can define whether a cell supports transmit diversity by selecting HSPA+ (Transmit Diversity) in cell properties (see "Cell Definition" on page 633). Diversity gains on downlink can be defined in the reception equipment for different numbers of transmission and reception antenna ports, mobility types and HSDPA bearers. For more information on downlink diversity gains, see "Creating or Modifying Reception Equipment" on page 801. Additional gain values can be defined per clutter class. For information on setting the additional downlink diversity gain for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. During calculations in Atoll, a user (mobile, pixel, or point receiver) using a MIMO-capable terminal, and connected to a cell that supports HSPA+ with transmit diversity, will benefit from the downlink diversity HS-PDSCH Ec/Nt gain. Spatial Multiplexing Spatial multiplexing uses more than one transmission antenna to send different signals (data streams) on each antenna. The receiver can also have more than one antenna for receiving different signals. When spatial multiplexing is used with M transmission and N reception antenna ports, the throughput over the transmitter-receiver link can be theoretically increased M or N times, depending on which is smaller, M or N. Spatial multiplexing improves the throughput (i.e., the channel capacity) for a given HS-PDSCH Ec/Nt, and is used for the regions of a cell that have sufficient HS-PDSCH Ec⁄Nt 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 633). 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 801. During calculations in Atoll, a user (mobile, pixel, or point receiver) using a MIMO-capable terminal, and connected to a cell that supports HSPA+ with spatial multiplexing, will benefit from the spatial multiplexing gain in its throughput depending on its HS-PDSCH Ec⁄Nt. Because spatial multiplexing improves the channel capacity or throughputs, the HS-PDSCH Ec⁄Nt of a user is determined first. Once the HS-PDSCH Ec⁄Nt is known, Atoll determines the corresponding CQI and calculates the user throughput based on the bearer available at the user location. The obtained user throughput is then increased according to the spatial multiplexing capacity gain and the Spatial Multiplexing Gain Factor of the user’s 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 145. The spatial multiplexing capacity gain vs. HS-PDSCH Ec/Nt graphs available in Atoll by default have been generated based on the maximum theoretical spatial multiplexing capacity gains obtained using the following equations: CC MIMO G MIMO = --------------------CC SISO
Where CC MIMO =
TX Min ( N Ant,
RX N Ant )
Ec ------- Nt HS – PDSCH × Log 2 1 + ------------------------------------------ is the channel capacity at a given HS-PDSCH Ec/Nt for a TX RX Min ( N Ant, N Ant )
RX - is the chanMIMO system using N TX Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 1 + -----Nt HS – PDSCH
Ec
804
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
nel capacity for a single antenna system at a given HS-PDSCH Ec⁄Nt. HS-PDSCH Ec⁄Nt 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.
9.7.8 Conditions for Entering the Active Set The mobile active set is the list of the transmitters to which the mobile is connected. The active set may consist of one or more transmitters; depending on whether the service supports soft handover and on the terminal active set size. Transmitters in the mobile active set must use a frequency band with which the terminal is compatible. It is, however, the quality of the pilot (Ec⁄I0) that finally determines whether or not a transmitter can belong to the active set. In order for a given transmitter to enter the mobile active set as best server, the pilot quality from this transmitter must exceed an upper threshold defined in the properties of the mobility type. In addition, the pilot quality must be the highest one. In order for a transmitter to enter the active set: •
• •
It must use the same carrier as the best server transmitter. In Atoll, carriers are modelled using cells. For information on accessing cell properties, see "Creating or Modifying a Cell" on page 638. For a description of the properties of a cell, see "Cell Definition" on page 633. The pilot quality difference between the cell and the best server must not exceed the AS-threshold set per cell. For information on accessing the AS threshold defined for a given cell, see "Creating or Modifying a Cell" on page 638. 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 800.
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.
9.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 Ec⁄I0 and Eb⁄Nt values and the macro-diversity gain. For information on setting the model standard deviation and the Ec⁄I0 and Eb⁄Nt standard deviations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. Shadowing can be taken into consideration when Atoll calculates the signal level, Ec⁄I0, and Eb⁄Nt for: • •
A point analysis (see "Making a Point Analysis to Study the Profile" on page 656) A coverage prediction (see "Studying Signal Level Coverage" on page 658).
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 805.
9.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. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears.
805
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
3. Select Shadowing Margins from the context menu. The Shadowing Margins and Gains dialogue appears (see Figure 9.57). 4. You can set the following parameters: • •
Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin or macrodiversity gains: • •
•
•
Model: The model standard deviation. Atoll will display the shadowing margin of the signal level. Ec⁄I0: The Ec⁄I0 standard deviation. Atoll will display the Ec⁄I0 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 Eb⁄Nt: The Eb⁄Nt UL standard deviation. Atoll will display the Eb⁄Nt 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 Eb⁄Nt: The Eb⁄Nt DL standard deviation. Atoll will display the Eb⁄Nt DL shadowing margin.
5. If you select "Ec⁄I0" or "Eb⁄Nt 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 "Ec⁄I0" as the standard deviation under Standard Deviation, enter the allowed Ec⁄I0 difference between the best server and the second one. This value is used to calculate DL macrodiversity gains. If you selected "Eb⁄Nt UL" as the standard 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 "Ec⁄I0" as the standard deviation under Standard Deviation, enter the allowed Ec⁄I0 difference between the second-best server and the third one. This value is used to calculate DL macro-diversity gains. If you selected "Eb⁄Nt UL" as the standard 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 "Ec⁄I0" or "Eb⁄Nt UL" as the standard deviation under Standard Deviation, Atoll also displays the macro-diversity gains for two links and for three links. 7. Click Close to close the dialogue.
Figure 9.57: The Shadowing Margins and Gains dialogue
9.7.10 Modelling Inter-technology Interference Analyses of UMTS networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in a UMTS network. Atoll can take into account interference from co-existing networks in Monte Carlo simulations and coverage predictions. The following inter-technology interference scenarios are modeled in Atoll: •
Interference received by mobiles on the downlink: Interference can be received by mobiles in a UMTS network on the downlink from external base stations and mobiles in the vicinity. Interference from external base stations (also called downlink-to-downlink interference) can be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions),
806
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
AT312_UM_E1
and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (CDMA, TDMA, OFDM). These graphs are then used for calculating the interference from the external base stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-technology IRFs" on page 807. Interference from external mobiles (also called uplink-to-downlink interference) can be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your UMTS network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled in Atoll using the Inter-technology DL Noise Rise definable for each cell in the UMTS network. This noise rise is taken into account in all downlink interference-based calculations. However, this noise rise does not impact the calculation of the mobile reuse factor. For more information on the Inter-technology DL Noise Rise, see "Cell Definition" on page 633. You can study the downlink inter-technology interference by carrying out an Inter-technology Downlink Interference coverage prediction as explained in "Studying Inter-technology Downlink Interference" on page 694.
Figure 9.58: 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) can be created by insufficient separation between the downlink frequency used by the external network and the uplink frequency used by your UMTS network. Such interference may also come from co-existing TDD networks. Interference from external mobiles (also called uplink-to-uplink interference) can be created by the use of same or nearby frequencies for uplink in both networks. Unless the exact locations of external mobiles is known, it is not possible to separate interference received from external base stations and mobiles on the uplink. The effect of this interference is modelled in Atoll using the Inter-technology UL Noise Rise definable for each cell in the UMTS network. This noise rise is taken into account in uplink interference-based calculations in the simulation. However, this noise rise is not taken into consideration in predictions (AS Analysis and coverage predictions) and does not have an impact on the calculation of the cell reuse factor. For more information on the Inter-technology UL Noise Rise, see "Cell Definition" on page 633.
Figure 9.59: Interference received by cells on the uplink
9.7.10.1 Defining Inter-technology IRFs Interference received from external base stations on mobiles of your UMTS network can be calculated by Atoll. Atoll uses inter-technology interference reduction factor (IRF) graphs for calculating the interference levels. An IRF graph represents the variation of the Adjacent Channel Interference Ratio (ACIR) as a function of frequency separation. ACIR is determined from the Adjacent Channel Suppression (ACS) and the Adjacent Channel Leakage Ratio (ACLR) parameters as follows:
807
Atoll 3.1.2 User Manual Chapter 9: UMTS HSPA Networks
© Forsk 2012
1 ACIR = ------------------------------------1 1 ------------- + ----------------ACS ACLR
An IRF depends on: • • • •
The interfering technology (TDMA, CDMA, or OFDM) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).
IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your UMTS document, i.e., when Atoll is in co-planning mode. For more information on how to switch to co-planning mode, see "Switching to Co-planning Mode" on page 776. To define the inter-technology IRFs in the victim network: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the Radio Network Equipment folder.
3. Right-click Inter-technology Interference Reduction Factors. The context menu appears. 4. Select Open Table from the context menu. The Inter-technology Interference Reduction Factors table appears. 5. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter: • • • •
Technology: Select the technology used by the interfering network. Interferer Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfering network. This channel width must be consistent with that used in the linked document. Victim Bandwidth (kHz): Enter the width in kHz of the channels (carriers) used by the interfered network. This channel width must be consistent with that used in the main document. Reduction Factors (dB): Click the cell corresponding to the Reduction Factors (dB) column and the current row in the table. The Reduction Factors (dB) dialogue appears. •
Enter the interference reduction factors in the Reduction (dB) column for different frequency separation, Freq. Delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document. • •
•
Reduction values must be positive. If you leave reduction factors undefined, Atoll assumes there is no interference.
Click OK. The interference reduction factors are stored.
You can, if you want, link more than one Atoll document with your main document following the procedure described in "Switching to Co-planning Mode" on page 776. 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.
808
Chapter 10 CDMA2000 Networks This chapter provides the information to use Atoll to design, analyse, and optimise a CDMA2000 network.
In this chapter, the following are explained: •
"Planning and Optimising CDMA Base Stations" on page 811
•
"Studying Network Capacity" on page 904
•
"Optimising Network Parameters Using the ACP" on page 933
•
"Verifying Network Quality" on page 935
•
"Co-planning CDMA Networks with Other Networks" on page 947
•
"Advanced Configuration" on page 965
Atoll 3.1.2 User Manual Chapter 10: Starting a Project
810
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
10 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 811. Allocating neighbours is explained in "Planning Neighbours" on page 882 and allocating PN Offset codes is explained in "Planning PN Offsets" on page 896. 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 904, 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 935. Filtering imported drive test data paths, and using the data in coverage predictions is also explained. A Note on the Terminology Used in This Chapter The terminology used in CDMA is slightly different from the standard terminology used in Atoll. Therefore, the terminology used in explanations reflects the standard CDMA terminology with the equivalent Atoll terminology given when references are made to the user interface. CDMA
Atoll
handoff
handover
radio configuration
terminal
reverse link
uplink (UL)
forward link
downlink (DL)
10.1 Planning and Optimising CDMA Base Stations As described in Chapter 2: Starting an Atoll Project, you can start an Atoll document from a template, with no sites, or from a database with a set of sites. As you work on your Atoll document, you will still need to create sites and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any other additional equipment, such as the TMA, feeder cables, etc. In a CDMA project, you must also add cells to each transmitter. A cell refers to the characteristics of a carrier on a transmitter.
A n te n n a - A z im u t h - M e c h a n i c a l t i lt
TMA A n te n n a - H e ig h t
F e e d e r C a b le
T r a n s m it t e r - N o is e fig u r e - P ow er
S it e - X , Y c o o r d in a t e s
Figure 10.1: A transmitter
811
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Atoll lets you create one site, transmitter, or cell at a time, or create several at once by creating a station template. Using a station template, you can create one or more base stations at the same time. In Atoll, a base station refers to a site with its transmitters, antennas, equipment, and cells. Atoll allows you to make a variety of coverage predictions, such as signal level or transmitter coverage predictions. The results of calculated coverage predictions can be displayed on the map, compared, or analysed. Atoll enables you to model network traffic by allowing you to create services, users, user profiles, environments, and terminals. This data can be then used to make quality coverage predictions, such as effective service area, noise, or handoff status predictions, on the network. In this section, the following are explained: • • • • • • • • • • • •
"Creating a CDMA Base Station" on page 812 "Creating a Group of Base Stations" on page 828 "Modifying Sites and Transmitters Directly on the Map" on page 828 "Display Tips for Base Stations" on page 829 "Creating a Dual-Band CDMA Network" on page 829 "Creating a Repeater" on page 829 "Creating a Remote Antenna" on page 833 "Setting the Working Area of an Atoll Document" on page 836 "Studying a Single Base Station" on page 837 "Studying Base Stations" on page 841 "Planning Neighbours" on page 882 "Planning PN Offsets" on page 896.
10.1.1 Creating a CDMA Base Station When you create a CDMA site, you create only the geographical point; you must add the transmitters and cells afterwards. The site, with the transmitters, antennas, equipment, and cells is called a base station. In this section, each element of a base station is described. If you want to add a new base station, see "Placing a New Station Using a Station Template" on page 820. If you want to create or modify one of the elements of a base station, see "Creating or Modifying a Base Station Element" on page 818. If you need to create a large number of base stations, Atoll allows you to import them from another Atoll document or from an external source. For information, see "Creating a Group of Base Stations" on page 828. This section explains the various parts of the base station process: • • • • •
"Definition of a Base Station" on page 812 "Creating or Modifying a Base Station Element" on page 818 "Placing a New Station Using a Station Template" on page 820 "Managing Station Templates" on page 821 "Duplicating of an Existing Base Station" on page 826.
10.1.1.1 Definition of a Base Station A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. You will usually create a new base station using a station template, as described in "Placing a New Station Using a Station Template" on page 820. This section describes the following elements of a base station and their parameters: • • •
812
"Site Description" on page 813 "Transmitter Description" on page 814 "Cell Definition" on page 816.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
10.1.1.1.1
Site Description The parameters of a site can be found in the site’s Properties dialogue. The Properties dialogue has two tabs: •
The General tab (see Figure 10.2):
Figure 10.2: New Site dialogue • •
Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If you want to change the default name that Atoll gives to new sites, see the Administrator Manual. Position: By default, Atoll places the new site at the centre of the map window. You can modify the location of the site here. While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 41.
•
• •
Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can specify the actual altitude under Real, if you want. If an altitude is specified here, Atoll will use this value for calculations. Comments: You can enter comments in this field if you want.
The Equipment tab: • • •
Max Number of Uplink Channel Elements 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 970. If no equipment is assigned to the site, Atoll uses 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.
813
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
10.1.1.1.2
© Forsk 2012
Transmitter Description The parameters of a transmitter can be found in the transmitter’s 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 816), the Propagation tab (see "Assigning a Propagation Model to One Transmitter" on page 845), and the Display tab (see "Display Properties of Objects" on page 43). •
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.
•
•
•
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 966. Shared antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the same site or on sites with the same position and that share the same antenna. The entry in the field must be the same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna Position, you can modify the position of the antennas (main and secondary): • •
•
Relative to Site: Select this option if you want to enter the antenna positions as offsets with respect to the site location, and enter the x-axis and y-axis offsets, Dx and Dy, respectively. Coordinates: Select this option if you want to enter the coordinates of the antenna, and then enter the x-axis and y-axis coordinates of the antenna, X and Y, respectively.
The Transmitter tab (see Figure 10.3):
Figure 10.3: Transmitter dialogue - Transmitter tab
814
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed in red in the Transmitters folder of the Network explorer. Only active transmitters are taken into consideration during calculations.
•
Transmission/Reception: Under Transmission/Reception, you can define the total losses and the noise figure in the Real text boxes. Atoll can calculate losses and noise according to the characteristics of the equipment assigned to the transmitter; the calculated values are indicated in the Computed text boxes. Atoll always considers the values in the Real boxes in coverage predictions even if they are different from the values in the Computed boxes. You can update the values in the Real boxes with the values in the Computed text boxes. For information, see "Updating the Values for Total Losses and the Transmitter Equipment Noise Figure" on page 177. 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 10.4), 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 176.
•
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 176. Transmitter: You can select transmitter equipment from the Transmitter list. You can click the Browse button
•
• • •
( ) to access the properties of the transmitter equipment. For information on creating transmitter equipment, see "Defining Transmitter Equipment" on page 176. Feeder Length: You can enter the feeder length at transmission and reception. Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value you enter must be positive. Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter must be positive.
Figure 10.4: The Equipment Specifications dialogue Any loss related to the noise due to a transmitter’s 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.
815
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
•
Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens a dialogue displaying all the possible antennas based on the same physical antenna as the currently selected one. Selecting the Electrical tilt of the antenna model displays the appropriate antennas under Available Antennas. Selecting the antenna under Available Antennas and clicking OK assigns the antenna to the transmitter. The other fields, Azimuth, Mechanical Downtilt, and Additional Electrical Downtilt, display additional antenna parameters. • • •
•
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.1.1.1.3
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. The mechanical and additional electrical downtilts defined for the main antenna are also used for the calculations of smart antennas.
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
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 automatically creates 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 want, 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 following 1xEV-DO Rev B options apply to all the 1xEV-DO cells of the transmitter: •
Under EV-DO Rev B, the following 1xEV-DO Rev B options are available: •
Multi-carrier support: You can define whether the transmitter supports the multi-carrier EV-DO operation. When multi-carrier EV-DO is active, multi-carrier EV-DO users can simultaneously connect with two or more EV-DO carriers of transmitters that support the mode (i.e., multi-carrier EV-DO users receive the data on several separate carriers. In Atoll, a multi-carrier EV-DO user is refered to as a user with multi-carrier EV-DO-based services and a multi-carrier terminal.
•
MUG=f(no. of 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. It is used to calculate the downlink average cell data rate. For transmitters that support multi-carrier EV-DO, this MUG graph is used in calculations instead of the MUG graph set per cell.
•
Min Ec/Nt (UL): You can enter or modify the minimum Ec/Nt to operate multi-carrier EV-DO in the reverse link.
The following parameters can be set for each individual cell of the transmitter: •
• • •
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: • • •
816
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.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
• • • •
•
• • • •
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 Ec⁄I0 required from the cell to be the best server in the active set. T_Drop: Enter the minimum Ec⁄I0 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 interferencebased calculations involving this cell in simulations. It is not used in predictions (AS Analysis and coverage predictions). In predictions, Atoll calculates the uplink total interference from the UL load factor which includes intertechnology uplink interference. For more information on inter-technology interference, see "Modelling Intertechnology Interference" on page 975. 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 975. 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 inter-carrier) and inter-technology neighbours by clicking the Browse button ( "Planning Neighbours" on page 882.
). For information on defining neighbours, see
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. By default, the synchronisation power and paging power are set as absolute values. You can set these values as relative to the pilot power by right-clicking the Network Settings folder in the Parameters explorer and selecting Properties from the context menu. Then, on the Global Parameters tab of the Properties 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. By default, the total power is set as absolute value. You can set this value as a percentage of the maximum power of the cell by right-clicking the Network Settings folder in the Parameters explorer and selecting Properties from the context menu. Then, on the Global Parameters tab of the Properties 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.
817
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
•
•
© Forsk 2012
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.
The following parameters are available for 1xEV-DO carriers: •
• •
Max Power (dBm): The power transmitted by a 1xEV-DO cell when there is at least one user. For 1xEV-DO carriers, the transmitter equipment always transmits at maximum power (the DL maximum power) unless it has no user to support. When there is no user, the transmitter equipment transmits a very low level of power during idle traffic slots (DL maximum power + Idle gain). Idle Power Gain (dB): The gain applied to the DL power when there is no active user connected to the cell. It must be a negative value. MUG Table = 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. In transmitters that support multi-carrier EV-DO, this MUG graph is used in calculations instead of the MUG graph set per cell.
•
• •
•
•
•
• • •
•
Noise Rise Threshold (dB): The noise rise threshold. The noise rise threshold and the acceptable noise rise margin are considered in the simulation during reverse link congestion. Atoll ensures that the cell reverse link noise rise is within a range defined by the noise rise threshold plus the margin and the noise rise threshold minus the margin. Acceptable Noise Rise Margin (dB): The acceptable noise rise margin. DRC Error Rate (%): The error rate as a percentage received by the cell on the Data Rate Control (DRC) channel. The cell may receive the DRC channel from a mobile incorrectly. If this happens, the mobile will not be scheduled for data transmission. This value is taken into account during rate control when Atoll calculates the average cell throughput on the forward link. EV-DO Timeslots Dedicated to BCMCS (%): The percentage of timeslots dedicated to Broadcast/Multicast Services (BCMCS). This parameter is taken into account during rate control when Atoll calculates the cell average forward link throughput. EV-DO Timeslots Dedicated to Control Channels (%): The percentage of timeslots dedicated to control channels (control, pilot, and ACK channels). This parameter is taken into account during rate control when Atoll calculates the cell average forward link throughput. BCMCS Throughput (kbps): The BCMCS throughput. Two throughput values are available: 204.8 kbps and 409.6 kbps. This parameter is taken into account during rate control when Atoll calculates the cell average forward link throughput. Max UL Load Factor (%): The maximum reverse link load factor not to be exceeded. This limit can be taken into account during the simulation. Total Power (dBm): The total transmitted power on forward link. This value can be a simulation result or can be entered by the user. UL Load Factor (%): The reverse link cell load factor. This factor corresponds to the ratio between the reverse link total interference and the reverse link total noise. This is the global value for the reverse link load factor including the reverse link inter-technology interference. This value can be a simulation result or can be entered by the user. Max No. of EV-DO Users: The maximum number of EV-DO carrier users that this cell can support at any given time. Multi-carrier EV-DO users are counted once in each cell they are connected to.
10.1.1.2 Creating or Modifying a Base Station Element A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: • • •
10.1.1.2.1
"Creating or Modifying a Site" on page 818 "Creating or Modifying a Transmitter" on page 819 "Creating or Modifying a Cell" on page 819.
Creating or Modifying a Site You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 813, through the site’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create a new site: 1. Select the Network explorer. 2. Right-click the Sites folder. The context menu appears. 3. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 10.2 on page 813). 4. Modify the parameters described in "Site Description" on page 813. 5. Click OK.
818
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
To modify the properties of an existing site: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Sites folder. 3. Right-click the site you want to modify. The context menu appears. 4. Select Properties from the context menu. The site’s Properties dialogue appears. 5. Modify the parameters described in "Site Description" on page 813. 6. Click OK. If you are creating several sites at the same time, or modifying several existing sites, you can do it quickly by editing or pasting the data directly in the Sites table. You can open the Sites table by right-clicking the Sites folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
10.1.1.2.2
Creating or Modifying a Transmitter You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio Planning toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 814, through the transmitter’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create a new transmitter: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 10.3). 4. Modify the parameters described in "Transmitter Description" on page 814. 5. Click OK. When you create a new transmitter, Atoll automatically creates a cell based on the default station template. For information on creating a cell, see "Creating or Modifying a Cell" on page 819. To modify the properties of an existing transmitter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Modify the parameters described in "Transmitter Description" on page 814. 6. Click OK. •
•
10.1.1.2.3
If you are creating several transmitters at the same time, or modifying several existing transmitters, you can do it more quickly by editing or pasting the data directly in the Transmitters table. You can open the Transmitters table by rightclicking the Transmitters folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77. If you want to add a transmitter to an existing site on the map, you can add the transmitter by right-clicking the site and selecting New Transmitter from the context menu.
Creating or Modifying a Cell You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Definition" on page 816, through the Properties dialogue of the transmitter where the cell is located. How you access the Properties dialogue depends on whether you are creating a new cell or modifying an existing cell. To create or modify a cell: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears.
819
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Definition" on page 816. 7. Click OK. •
•
If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder in the Network explorer and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 77), or import data into the table (see "Importing Tables from Text Files" on page 82). If you want to add a cell to an existing transmitter on the map, you can add the cell by right-clicking the transmitter and selecting New Cell from the context menu.
10.1.1.3 Placing a New Station Using a Station Template In Atoll, a station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template: 1. In the Radio Planning toolbar, select a template from the list.
2. Click the New Transmitter or Station button (
) in the Radio Planning 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 pointer’s current location are visible in the Status bar.
4. Click to place the station. •
•
To place the station more accurately, you can zoom in on the map before you click the New Station button. For information on using the zooming tools, see "Changing the Map Scale" on page 49. 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 a Station Template" on page 821. To place a series of stations within a defined area: 1. In the Radio Planning 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.
820
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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 (
):
In the Network explorer, clear the display check box beside the Hexagonal Design folder.
You can work with the sites and transmitters in these stations as you work with any station object, adding, for example, another antenna to a transmitter. Placing a Station on an Existing Site When you place a new station using a station template as explained in "Placing a New Station Using a Station Template" on page 820, the site is created at the same time as the station. However, you can also place a new station on an existing site. To place a station on an existing site: 1. In the Network explorer, clear the display check box beside the Hexagonal Design folder. 2. In the Radio Planning toolbar, select a template from the list. 3. Click the New Station button (
) in the Radio Planning toolbar.
4. Move the pointer to the site on the map. When the frame appears around the site, indicating it is selected, click to place the station.
10.1.1.4 Managing Station Templates Atoll comes with CDMA station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio Planning toolbar (see Figure 10.5).
Figure 10.5: The Radio Planning toolbar In this section, the following are explained: • • • • •
10.1.1.4.1
"Creating a Station Template" on page 821 "Modifying a Station Template" on page 822 "Copying Properties from One Station Template to Another" on page 825 "Modifying a Field in a Station Template" on page 826 "Deleting a Station Template" on page 826.
Creating a Station Template When you create a station template, Atoll bases it on the station template selected in the Station Template Properties dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing station template that most closely resembles the station template you want to create, you can create a new template by only modifying the parameters that differ. To create a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the Station Templates table, right-click the station template that most closely resembles the station template you want to create. The context menu appears. 6. Select Copy from the context menu. 7. Right-click the row marked with the New Row icon (
). The context menu appears.
821
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
8. Select Paste from the context menu. The station template you copied in step 5. is pasted in the new row, with the Name of the new station template given as the same as the template copied but preceded by "Copy of". 9. Edit the parameters of the new station template in the table or as explained in "Modifying a Station Template" on page 822.
10.1.1.4.2
Modifying a Station Template You can modify a station template directly in the Station Templates table, or you can open the Properties dialogue for that station template and modify the parameters in the dialogue. To modify a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. Right-click the station template you want to modify. The context menu appears. 6. Select Record Properties from the context menu. The station template’s Properties dialogue appears. 7. Click the General tab of the Properties dialogue. On this tab (see Figure 10.6), 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 10.6: Station Template Properties dialogue – General tab •
Under Main Antenna, you can modify the following: the Height/Ground of the antennas from the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of building), the main antenna Model, 1st Sector Azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Mechanical Downtilt, and the Additional Electrical Downtilt for the antenna. • •
822
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
•
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 845. Under Comments, you can add additional information. The information you enter will be the default information in the Comments field of any transmitter created using this station template.
8. Click the Transmitter tab. On this tab (see Figure 10.7). You can modify the following: •
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 Network explorer.
•
Transmission/Reception: Under Transmission/Reception, you can define the total losses and the noise figure in the Real text boxes. Atoll can calculate losses and noise according to the characteristics of the equipment assigned to the transmitter; the calculated values are indicated in the Computed text boxes. Atoll always considers the values in the Real boxes in coverage predictions even if they are different from the values in the Computed boxes. You can update the values in the Real boxes with the values in the Computed text boxes. For information, see "Updating the Values for Total Losses and the Transmitter Equipment Noise Figure" on page 177. 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 814.
Figure 10.7: Station Template Properties dialogue – Transmitter tab 9. Click the CDMA tab. On this tab (see Figure 10.8), 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 816. •
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 975. You can also modify the Number of Uplink and Downlink Channel Elements and select the Equipment.
823
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Figure 10.8: Station Template Properties dialogue – CDMA tab 10. Click the CDMA2000 tab. On this tab (see Figure 10.9), 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 816. • • • • • •
824
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 Rev.0, you can set the Noise Rise Threshold, the Acceptable Noise Rise Margin, and the DRC Error Rate. Under Rev.A, you can set the Timeslot BCMCS, the Timeslot Control Channels, and the BCMCS Throughput. Under Rev.B, you can select whether Multi-carrier EV-DO is supported and you can enter a MUG=f(No. Users) graph and define the min Ec/Nt (UL).
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Figure 10.9: Station Template Properties dialogue – CDMA2000 tab 11. Click the Neighbours tab. On this tab (see Figure 10.10), 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 882.
Figure 10.10: Station Template Properties dialogue – Neighbours tab 12. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the Sites table, or if you have defined an additional field in the Station Template Properties dialogue. 13. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.
10.1.1.4.3
Copying Properties from One Station Template to Another You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the 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.
825
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
10.1.1.4.4
© Forsk 2012
Modifying a Field in a Station Template To modify a field in a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Properties from the context menu. The Station Template Properties dialogue appears. 5. Select the Table tab. 6. On the Table tab, you have the following options: •
Add: If you want to add a user-defined field to the station templates, you must have already added it to the Sites table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Type’s Data Table" on page 71) for it to appear as an option in the station template properties. To add a new field: i.
Click the Add button. The Field Definition dialogue appears.
ii. Enter a Name for the new field. This is the name that will be used in database. iii. If desired, you can define a Group that this custom field will belong to. When you open an Atoll document from a database, you can then select a specific group of custom fields to be loaded from the database, instead of loading all custom fields. iv. In Legend, enter the name for the field that will appear in the Atoll document. v. For Type, you can select from Text, Short integer, Long integer, Single, Double, True/False, Date/Time, and Currency. If you choose text, you can also set the field Size (in characters), and create a Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER after each one. vi. Enter, if desired, a Default value for the new field. vii. Click OK to close the Field Definition dialogue and save your changes. •
Delete: To delete a user-defined field: i.
Select the user-defined field you want to delete.
ii. Click the Delete button. The user-defined field appears in strikeout. It will be definitively deleted when you close the dialogue. •
Properties: To modify the properties of a user-defined field: i.
Select the user-defined field you want to modify.
ii. Click the Properties button. The Field Definition dialogue appears. iii. Modify any of the properties as desired. iv. Click OK to close the Field Definition dialogue and save your changes. 7. Click OK.
10.1.1.4.5
Deleting a Station Template To delete a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Station Templates folder. 4. In the Station Templates folder, right-click the station template you want to delete. The context menu appears. 5. Select Delete from the context menu. The template is deleted.
10.1.1.5 Duplicating of an Existing Base Station You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same transmitter, and cell parameter values as the original base station. If no site exists where you place the duplicated base station, Atoll will create a new site with the same parameters as the site of the original base station. Duplicating a base station allows you to: • •
826
Quickly create a new base station with the same settings as an original base station in order to study the effect of a new station on the coverage and capacity of the network, and Quickly create a new homogeneous network with stations that have the same characteristics.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
To duplicate an existing base station: 1. Select the Network explorer. 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 > Without Neighbours from the context menu, if you want to duplicate the base station without the intra- and inter-technology neighbours of its transmitters. Select Duplicate > With Neighbours from the context menu, if you want to duplicate the base station along with the lists of intra- and inter-technology neighbours of its transmitters.
5. Place the new base station on the map using the mouse: •
Creating a duplicate base station and site: In the map window, move the pointer over the map to where you would like to place the duplicate. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 10.11).
Figure 10.11: Creating a duplicate base station and site •
Placing the duplicate base station on an existing site: In the map window, move the pointer over the existing site where you would like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 10.12).
Figure 10.12: Placing the duplicate base station on an existing site •
•
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 49. 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. A new base station is placed on the map. If the duplicate base station was placed on a new site, the site, transmitters, and cells of the new base station have the same names as the site, transmitters, and cells of the original base station with each name marked as "Copy of." The site, transmitters, and cells of the duplicate base station have the same settings as those of the original base station. If the duplicate base station was placed on an existing site, the transmitters, and cells of the new base station have the same names as the transmitters, and cells of the original base station with each name preceded by the name of the site on which the duplicate was placed. All the remote antennas and repeaters of any transmitter on the original site are also duplicated. Any duplicated remote antennas and repeaters will retain the same donor transmitter as the original. If you want the duplicated remote antenna or repeater to use a transmitter on the duplicated base station, you must change the donor transmitter manually.
827
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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 812.
10.1.2 Creating a Group of Base Stations You can create base stations individually as explained in "Creating a CDMA Base Station" on page 812, or you can create one or several base stations by using station templates as explained in "Placing a New Station Using a Station Template" on page 820. However, if you have a large data-planning project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations. 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 121. You can import base station data in the following ways: •
Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. The table you copy 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 77. •
Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80. For information on importing table data, see "Importing Tables from Text Files" on page 82. You can quickly create a series of base stations for study purposes using the Hexagonal Design tool on the Radio Planning toolbar. For information, see "Placing a New Station Using a Station Template" on page 820.
10.1.3 Modifying Sites and Transmitters Directly on the Map In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu in the Network explorer. However, in a complex radio-planning project, it can be difficult to find the data object in the Network explorer, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. You can also select a site to display all of the transmitters located on it in the Site Configuration window. When selecting a transmitter, if there there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: • • • • • •
828
"Working with the Site Configuration Window" on page 37 "Selecting One of Several Transmitters" on page 41 "Moving a Site Using the Mouse" on page 41 "Moving a Site to a Higher Location" on page 42 "Changing the Azimuth of the Antenna Using the Mouse" on page 42 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
10.1.4 Display Tips for Base Stations Atoll allows to you to display information about base stations in a number of different ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations: •
•
•
•
Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object type’s data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information will lead to a cluttered display. For information on defining the label, see "Defining the Object Type Label" on page 46. Tip text: You can display information about each object, such as each site or transmitter, in the form of tip text that is only visible when you move the pointer over the object. You can choose to display more information than in the label, because the information is only displayed when you move the pointer over the object. You can display information from any field in that object type’s data table, including from fields that you add. For information on defining the tip text, see "Defining the Object Type Tip Text" on page 46. Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example, you can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active sites. You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns a colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding it. For information on defining the transmitter colour, see "Defining the Display Type" on page 44. Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can select a symbol that graphically represents the antenna half-power beamwidth (
). If you have two transmitters on the
same site with the same azimuth, you can differentiate them by selecting different symbols for each ( For information on defining the transmitter symbol, see "Defining the Display Type" on page 44.
and
).
10.1.5 Creating a Dual-Band CDMA Network In Atoll, you can model a dual-band CDMA network, i.e., a network consisting of 1900 MHz and 700 MHz transmitters, in one document. Creating a dual-band CDMA network consists of the following steps: 1. Defining the two frequency bands in the document (see "Defining Frequency Bands" on page 966). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Working with Calculations in Atoll). 3. Assigning a frequency band, with its propagation model, to each transmitter (see "Transmitter Description" on page 814). 4. Defining the frequency bands with which terminals are compatible (see "Modelling Terminals" on page 867).
10.1.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 a radio link or a microwave link. The server side re-transmits the received signal. Atoll models RF repeaters and microwave repeaters. The modelling focuses on: • •
The additional coverage these systems provide to transmitters in the downlink. The UL total gain value in service areas predictions (effective service area and reverse link Eb⁄Nt service area) and the noise rise generated at the donor transmitter by the repeater.
In this section, the following are explained: • • • • • •
"Opening the Repeaters Table" on page 830 "Creating and Modifying Repeater Equipment" on page 830 "Placing a Repeater on the Map Using the Mouse" on page 830 "Creating Several Repeaters" on page 831 "Defining the Properties of a Repeater" on page 831 "Tips for Updating Repeater Parameters" on page 833 Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor transmitter are amplified.
829
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
10.1.6.1 Opening the Repeaters Table Repeaters and their defining parameters are stored in the Repeaters table. To open the Repeaters table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Repeaters > Open Table from the context menu. The Repeaters table appears.
10.1.6.2 Creating and Modifying Repeater Equipment You can define repeater equipment to be assigned to each repeater in the network. To create repeater equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Repeater Equipment. The context menu appears. 4. Select Open Table from the context menu. The Repeater Equipment table appears. 5. Enter the following in the row marked with the New Row icon (
):
a. Enter a Name and Manufacturer for the new equipment. b. Enter a Noise Figure (dB). The repeater causes a rise in noise at the donor transmitter, so the noise figure is used to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive value. c. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if there are any. d. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier gain using the buttons to the right of the Amplification box ( logue.
) on the General tab of the repeater Properties dia-
e. Enter the maximum power that the equipment can transmit on the downlink in the Maximum Downlink Power column. This parameter enables Atoll to ensure that the downlink power after amplification does not exceed the limit of the equipment. f. If desired, enter a Maximum Uplink Power, an Internal Delay and Comments. These fields are for information only and are not used in calculations. To modify repeater equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Repeater Equipment. The context menu appears. 4. Select Open Table from the context menu. The Repeater Equipment table appears. 5. Change the parameters in the row containing the repeater equipment you want to modify.
10.1.6.3 Placing a Repeater on the Map Using the Mouse In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site, or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater or of a remote antenna. To create a repeater and place it using the mouse: 1. Select the donor transmitter, repeater, or remote antenna. You can select it from the Transmitters folder of the Network explorer, or directly on the map. 2. Click the arrow next to New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
3. Select Repeater from the menu. 4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty icon. By default, the repeater has the same azimuth as the donor. Its tip text and label display the same information as displayed for the donor. As well, its tip text identifies the repeater and the donor. In the Explorer window, the
830
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
repeater is found in the Transmitters folder of the Network explorer under its donor transmitter, repeater, or remote antenna. For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on page 831. •
•
When the donor is a transmitter, you can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. You can hide the link by clicking it again. When the donor is a repeater or a remote antenna, Atoll displays a spider-type link showing the entire chain down to the donor transmitter. The same spider-type link is displayed when you click any of the items belonging to the chain is clicked (i.e., donor transmitter, any repeater, or any remote antenna).
10.1.6.4 Creating Several Repeaters In Atoll, the characteristics of each repeater are stored in the Repeaters table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document. To paste the information into the Repeaters table: 1. Open the Repeaters table as explained in "Opening the Repeaters Table" on page 830. 2. Copy the data from the source document and paste it into the Repeaters table. 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 77.
10.1.6.5 Defining the Properties of a Repeater To define the properties of a repeater: 1. Right-click the repeater either directly on the map, or in the Repeaters table (for information on opening the Repeaters table, see "Opening the Repeaters Table" on page 830). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
You can change the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created. If the donor is a remote antenna or another repeater, then "RepZ" is preceded by "RemA_" or "RepB_" where "A" and "B" identify the donor remote antenna and the donor repeater.
•
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, a remote antenna, or another repeater. Clicking the Browse button (
• •
•
You can change the Site on which the repeater is located. Clicking the Browse button ( ) opens the Properties dialogue of the selected site. You can enter a value in the Shared antenna (coverage side) field for the repeater. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna Position, you can define the position of the repeater, if it is not located on the site itself: • •
•
) opens the Properties dialogue of the selected donor.
Relative to Site: Select Relative to Site, if you want to define the position of the repeater relative to the site itself and then enter the XY offsets. Coordinates: Select Coordinates, if you want to define the position of the repeater by its XY coordinates.
You can select equipment from the Equipment list. Clicking the Browse button ( logue of the equipment.
) opens the Properties dia-
831
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
•
© Forsk 2012
You can change the Amplification Gain. The amplification gain is used in the link budget to evaluate the repeater total gain.
4. Click the Donor Side tab. You can modify the following parameters: •
Under Donor-Repeater Link, select a Link Type. • •
If you select Microwave Link, enter the Propagation Losses and continue with step 5. If you select Air, select a Propagation Model and enter the Propagation Losses or click Calculate to determine the actual propagation losses between the donor and the repeater. If you do not select a propagation model, the propagation losses between the donor transmitter and the repeater are calculated using the ITU 526-5 propagation model. When you create an off-air repeater, it is assumed that the link between the donor transmitter and the repeater has the same frequency as the network. If you want to create a remote antenna, you must select Optical Fibre Link.
•
If you selected Air under Donor-Repeater Link, enter the following information under Antenna: •
Model: The type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the repeater. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas. and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the repeater.
•
•
Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of building. Mechanical Azimuth and Mechanical Downtilt display additional antenna parameters. You can click the Calculate button to update the mechanical azimuth and mechanical downtilt values after changing the repeater donor side antenna height or the repeater location. If you choose another site or change site coordinates in the General tab, click Apply before clicking the Calculate button.
•
If you selected Air under Donor-Repeater Link, enter the following information under Feeders: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. 5. Click the Coverage Side tab. You can modify the following parameters: • •
Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Network explorer) 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 Eb⁄Nt service area coverage predictions. The forward link total gain is applied to each power (pilot power, SCH power, etc.). The reverse link total gain is applied to each terminal power. The total gains take into account losses between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses), amplification gain, and coverage characteristics (coverage antenna gain and transmission feeder losses).
•
Under Antennas, you can modify the following parameters: •
•
Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of building. Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna.
832
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the repeater. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas. and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the repeater. • •
Mechanical 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. • • •
•
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. •
Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.
6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propagation parameters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
10.1.6.6 Tips for Updating Repeater Parameters Atoll provides you with a few shortcuts that you can use to change certain repeater parameters: • •
You can update the calculated azimuth and downtilt of the donor-side antennas of all repeaters by selecting Repeaters > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu. You can update the reverse link and forward link total gains of all repeaters by selecting Repeaters > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected repeaters by creating a custom Boolean field named "FreezeTotalGain" in the Repeaters table and setting the value of the field to "True." Afterwards, when you select Repeaters > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for repeaters with the custom field "FreezeTotalGain" set to "False".
• •
You can update the propagation losses of all off-air repeaters by selecting Repeaters > Calculate Donor Side Propagation Losses from the Transmitters context menu. You can select a repeater on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
10.1.7 Creating a Remote Antenna Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder cable. A remote antenna is connected to the base station with an optical fibre. Remote antennas allow you to ensure radio coverage in an area without a new base station. In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a remote antenna, as opposed to a repeater, does not have any equipment and generates no amplification gain nor noise. In certain cases, you may want to model a remote antenna with equipment or a remote antenna connected to a base station that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a Repeater" on page 829. In this section, the following are explained: •
"Opening the Remote Antennas Table" on page 834
833
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
• • • •
© Forsk 2012
"Placing a Remote Antenna on the Map Using the Mouse" on page 834 "Creating Several Remote Antennas" on page 834 "Defining the Properties of a Remote Antenna" on page 835 "Tips for Updating Remote Antenna Parameters" on page 836.
10.1.7.1 Opening the Remote Antennas Table The remote antennas and their defining parameters are stored in the Remote Antennas table. To open the Remote Antennas table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Remote Antennas > Open Table from the context menu. The Remote Antennas table appears.
10.1.7.2 Placing a Remote Antenna on the Map Using the Mouse In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it to an existing base station without antennas, or have Atoll automatically create a new site. To create a remote antenna and place it using the mouse: 1. Select the donor transmitter. You can select it from the Transmitters folder of the Network explorer, or directly on the map. Ensure that the remote antenna’s donor transmitter does not have any antennas.
2. Click the arrow next to New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
3. Select Remote Antenna from the menu. 4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its tip text and label display the same information as displayed for the donor transmitter. As well, its tip text identifies the remote antenna and the donor transmitter. For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote Antenna" on page 835. •
•
When the donor is a transmitter, you can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. You can hide the link by clicking it again. When the donor is a repeater or a remote antenna, Atoll displays a spider-type link showing the entire chain down to the donor transmitter. The same spider-type link is displayed when you click any of the items belonging to the chain is clicked (i.e., donor transmitter, any repeater, or any remote antenna).
10.1.7.3 Creating Several Remote Antennas In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in your current Atoll document. To paste the information into the Remote Antennas table: 1. Open the Remote Antennas table as explained in "Opening the Remote Antennas Table" on page 834. 2. Copy the data from the source document and paste it into the Remote Antennas table. The table you copy data from must have the same column layout as the table you are pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
834
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
10.1.7.4 Defining the Properties of a Remote Antenna To define the properties of a remote antenna: 1. Right-click the remote antenna either directly on the map, or in the Remote Antennas table (for information on opening the Remote Antennas table, see "Opening the Remote Antennas Table" on page 834). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RemZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the remote antenna when it was created. If the donor is a repeater or another remote antenna, then "RemZ" is preceded by "RepA_" or "RemB_" where "A" and "B" identify the donor repeater and the donor remote antenna.
•
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another remote antenna or a repeater. Clicking the Browse button (
• •
•
) opens the Properties dialogue of the selected donor.
You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens the Properties dialogue of the selected site. You can enter a value in the Shared Antenna (coverage side) field for the remote antenna. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna Position, you can define the position of the remote antenna, if it is not located on the site itself: • •
Relative to Site: Select Relative to Site, if you want to define the position of the remote antenna relative to the site itself and then enter the XY offsets. Coordinates: Select Coordinates, if you want to define the position of the remote antenna by its XY coordinates. A remote antenna does not have equipment.
4. Click the Donor Side tab. You can modify the following parameters: •
Under Donor-Repeater Link, select Optical Fibre Link and enter the Fibre Losses.
5. Click the Coverage Side tab. You can modify the following parameters: • •
Select the Active check box. Only active remote antennas (displayed in red in the Transmitters folder in the Network explorer) 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 Eb⁄Nt service area coverage predictions. The forward link total gain is applied to each power (pilot power, SCH power, etc.). The reverse link total gain is applied to each terminal power. The total gains take into account losses between the donor transmitter and the remote antenna.
•
Under Antennas, you can modify the following parameters: •
•
Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the remote antenna is situated on a building, the height entered must include the height of the building. Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the remote antenna. Based on the selected physical antenna and the electrical
835
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas. and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the remote antenna. • •
Mechanical 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. • • •
•
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. 6. Click the Propagation tab. Since remote antennas are taken into account during calculations, you must set propagation parameters, as with transmitters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
10.1.7.5 Tips for Updating Remote Antenna Parameters Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters: •
You can update the reverse link and forward link total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected remote antennas by creating a custom Boolean field named "FreezeTotalGain" in the Remote Antennas table and setting the value of the field to "True." Afterwards, when you select Remote Antennas > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for remote antennas with the custom field "FreezeTotalGain" set to "False."
•
You can select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
10.1.8 Setting the Working Area of an Atoll Document When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the sites that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of sites covered by a coverage prediction, each with its own advantages: •
Filtering the desired sites You can simplify the selection of sites to be studied by using a filter. You can filter sites according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 107. This enables you to keep only the base stations with the characteristics you want to study. The filtering zone is taken into account whether or not it is visible. For information on filtering, see "Filtering Data" on page 95.
836
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
Setting a computation zone Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated predictions in order to see the effects of small changes in site configuration, the savings in time is considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc., while the focus zone or hot spot is the area taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 846.
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.1.9 Studying a Single Base Station As you create a site, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of sites can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the site you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of sites once you have optimised the settings for each individual site. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and computes losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Atoll enables you to assign both a main propagation model, with a shorter radius and a higher resolution, and an extended propagation model, with a longer radius and a lower resolution. By using a calculation radius, Atoll limits the scope of calculations to a defined area. By using two matrices, Atoll allows you to calculate high resolution path loss matrices closer to the transmitter, while reducing calculation time by using an extended matrix with a lower resolution. Atoll can calculate the optimised main and/or extended calculation radii (of existing matrices) based on user-defined minimum received signal levels. As an consequence, the storage of path loss matrices can drastically be reduced. See "Optimising Path Loss Matrix Storage" on page 204 for more information. You can assign a propagation model to all transmitters at once, to a group of transmitters, or to a single transmitter. Assigning a propagation model is explained in "Assigning a Propagation Model" on page 843. In this section, the following are explained: • •
"Making a Point Analysis to Study the Profile" on page 837 "Studying Signal Level Coverage" on page 838
10.1.9.1 Making a Point Analysis to Study the Profile In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a CDMA user. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and computes losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on each selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 843. 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 Planning toolbar. The Point Analysis Tool window appears and the
) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: • • •
Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: • •
Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.
4. Select Profile from the list at the top of the Point Analysis window. In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you do a point analysis on the "Best" carrier, 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.
837
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
The profile analysis appears in the Profile view 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 view: • • • •
The received signal strength of the selected transmitter The propagation model used The shadowing margin and the indoor loss (if selected) The distance between the transmitter and the receiver.
You can change the following options at the top of the Profile view: • •
Transmitter: Select the transmitter from the list. Carriers: Select the carrier to be analysed.
5. At the top of the Profile view, you can click one of the following buttons: •
: Click the Properties button (
•
: Click the Options button ( • • • •
•
•
) to display the Properties dialogue of the selected transmitter. ) to display the Calculations Options dialogue. You can change the following:
Change the X and Y coordinates to change the present position of the receiver. Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability. Select Signal Level, Path loss, or Total losses from the Result Type list. You can select the Indoor Coverage check box to add indoor losses.
: Click the Geographic button ( ) if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate or display signal levels and losses. : Click the Link Budget button (
) to display a dialogue with the link budget.
•
: Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis. Detailed reports are only available for the standard propagation model.
•
) to copy the Profile view. You can then paste the contents of the Profile view as : Click the Copy button ( a graphic into a graphic editing or word-processing programme.
•
: Click the Print button (
) to print the Profile view.
Figure 10.13: Point Analysis Tool - Profile view
10.1.9.2 Studying Signal Level Coverage As you are building your radio-planning project, you may want to check the coverage of a new site without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single site. A signal level coverage prediction displays the strength of the best signal received at each pixel of the area studied.
838
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
You can use the same procedure to study the signal level coverage of several sites by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 89. To study the signal level coverage of a single base station: 1. Select the Network explorer. 2. Right-click the Transmitters folder and select Group By > Site from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated. If you want to study only 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 Prediction from the context menu. The Prediction Types dialogue appears. The Prediction Types dialogue lists the coverage predictions available. They are divided into Standard Predictions, supplied with Atoll, and Customised Predictions. Unless you have already created some customised predictions, the Customised Predictions list will be empty. 5. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 6. You can configure the following parameters in the Properties dialogue: •
General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can add a Comment. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient: Size of the Coverage Prediction
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
According to the size of the country
839
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
•
© Forsk 2012
Conditions tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel (see Figure 10.14). • • • • •
At the top of the Conditions tab, you can set the signal level range to be considered. In Figure 10.14, 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 "Best". In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "Best", the values displayed will always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier. 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 10.14: Condition settings for a signal level coverage prediction •
Display tab: You can modify how the results of the coverage prediction will be displayed. • •
• • •
Under Display Type, select "Value Intervals." Under Field, select "Best signal level." Selecting "All" or "Best signal level" on the Conditions tab will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best signal level" necessitates, however, the longest time for calculation. You can change the value intervals and their displayed colour. For information on changing display properties, see "Display Properties of Objects" on page 43. You can create tip text with information about the coverage prediction by clicking the Browse button ( next to the Tip Text box and selecting the fields you want to display in the tip text. You can select the Add to Legend check box to add the displayed value intervals to the legend.
)
If you change the display properties of a coverage prediction after you have calculated it, you may make the coverage prediction invalid. You will then have to recalculate the coverage prediction to obtain valid results. 7. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the 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 in the Network explorer. Atoll automatically locks the results of a
840
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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.1.10 Studying Base Stations When you make a coverage prediction on a group of base stations, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. The computation zone is the area covered by the rectangle defined by the calculation radius. When you set the propagation model, you can define the calculation radius. For information on setting the propagation model and defining the calculation radius, see "Assigning a Propagation Model" on page 843. Figure 10.15 gives an example of a computation zone. In Figure 10.15, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction.
Figure 10.15: An example of a computation zone Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main propagation model with a shorter radius (displayed with a blue square in Figure 10.15) and a higher resolution and an extended propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower resolution path loss matrices outside the area covered by the main propagation model. In this section, the following are explained: • • • • • • •
"Path Loss Matrices" on page 842 "Assigning a Propagation Model" on page 843 "The Calculation Process" on page 846 "Creating a Computation Zone" on page 846 "Setting Transmitters or Cells as Active" on page 847 "Signal Level Coverage Predictions" on page 848 "Analysing a Coverage Prediction" on page 852
841
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
• •
© Forsk 2012
"CDMA-Specific Coverage Predictions" on page 862 "Printing and Exporting Coverage Prediction Results" on page 882.
10.1.10.1 Path Loss Matrices Path loss is caused by objects in the transmitter-receiver path and is calculated by the propagation model. In Atoll, the path loss matrices are needed for all base stations that are active, filtered and whose propagation zone intersects a rectangle containing the computation zone (for an explanation of the computation zone, see "Studying Signal Level Coverage" on page 838) and must be calculated before predictions and simulations can be made. Storing Path Loss Matrices Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radioplanning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: • • •
One file per transmitter with the extension LOS for its main path loss matrix A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices: 1. Select the Network explorer. 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 Private Directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally. Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private Directory.
When you save the path loss files externally, the external files are updated as soon as calculations are performed and not only when you save the Atoll document. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it, if you have updated the path loss matrices. •
Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the common path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see the Administrator Manual. If you are working in a multi-user Atoll environment, ensure that the path to the Shared Directory is correct.
5. Click OK.
842
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Checking the Validity of Path Loss Matrices Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check if the path loss matrices are invalid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the following display options: • •
Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix: • • • • • •
Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a boolean field indicating whether or not the path loss matrix is valid. 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.
5. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 10.16) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.
Figure 10.16: Path loss matrices statistics
10.1.10.2 Assigning a Propagation Model In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 845, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 844, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 844, this is the propagation model that will be used for all transmitters, except for those to which you will later assign a propagation model either individually or as part of a group. When you assign a propagation model globally, you override any selection you might have made to an individual transmitter or to a group of transmitters.
843
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
If, after assigning a propagation model to an individual transmitter or to a group of transmitters, you assign a propagation model globally, you will override the propagation models that you had assigned to individual transmitters or to a group of transmitters. 3. If you have assigned a default propagation model for coverage predictions, as described in "Assigning a Default Propagation Model for Coverage Predictions" on page 845, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following methods of assigning a propagation model are explained: • • • •
"Assigning a Propagation Model to All Transmitters" on page 844 "Assigning a Propagation Model to a Group of Transmitters" on page 844 "Assigning a Propagation Model to One Transmitter" on page 845 "Assigning a Default Propagation Model for Coverage Predictions" on page 845.
Assigning a Propagation Model to All Transmitters In Atoll, you can choose a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. 5. Under Main Matrix: • •
Select a Propagation Model Enter a Radius and Resolution.
6. If desired, under Extended Matrix: • •
Select a Propagation Model Enter a Radius and Resolution.
7. Click OK. The selected propagation models will be used for all transmitters. Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 845 will override this entry.
Assigning a Propagation Model to a Group of Transmitters Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters and then assigning the propagation model. To define a main and extended propagation model for a defined group of transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. From the Group by submenu of the context menu, select the property by which you want to group the transmitters. The objects in the folder are grouped by that property. You can group transmitters by several properties by using the Group By button on the Properties dialogue. For more information, see "Advanced Grouping" on page 90.
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: • •
844
Main Propagation Model Main Calculation Radius (m)
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
• • • •
Main Resolution (m) Extended Propagation Model Extended Calculation Radius (m) Extended Resolution (m)
To enter the same values in one column for all transmitters in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69. Assigning a Propagation Model to One Transmitter If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main Matrix: • •
Select a Propagation Model Enter a Radius and Resolution.
7. If desired, under Extended Matrix: • •
Select a Propagation Model Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter. Assigning a Default Propagation Model for Coverage Predictions You can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters whose main propagation model is "(Default model)." To assign a default propagation model for coverage predictions: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Predictions tab. 5. Select a Default Propagation Model from the list. 6. Enter a Default Resolution. When you create a new coverage prediction, the resolution by default is the value you have entered here.
845
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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)."
10.1.10.3 The Calculation Process When you create a coverage prediction and click the Calculate button (
), Atoll follows the following process:
1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button (
).
3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( Predictions folder.
) beside the coverage prediction in the
•
You can stop any calculations in progress by clicking the Stop Calculations button
•
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.
(
) in the toolbar.
10.1.10.4 Creating a Computation Zone To create a computation zone: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Computation Zone. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the zone.
ii. Click once on the map to define each point on the map where the border of the zone changes direction. iii. Click twice to finish drawing and close the zone. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the zone.
ii. Drag to the opposite corner of the rectangle that will define the zone. When you release the mouse, the zone will be created from the rectangle defined by the two corners. The computation zone is delimited by a red line. If you clear the computation zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a computation zone as follows: • •
846
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor 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. You can also combine an existing computation zone with any existing polygon by right-clicking it on the map or in the Explorer window and selecting Add To > Computation Zone from the context menu.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
•
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 in the Geo explorer and selecting Import from the context menu. Fit Zone to Map Window: You can create a computation zone the size of the map window by selecting Fit Zone to Map Window from the context menu. You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the computation zone in the user configuration: For information on saving the computation zone in the user configuration, see "Saving a User Configuration" on page 101. Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone in the Geo explorer and selecting Export from the context menu.
10.1.10.5 Setting Transmitters or Cells as Active When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Before you define a coverage prediction, you must ensure that all the transmitters on the sites you want to study have been activated. In the Explorer window, active transmitters are indicated with a red icon (
) in the Transmitters folder and with the defined
colour on the map and inactive transmitters are indicated with an empty icon (
) in the Transmitters folder and on the map.
In Atoll, you can also set individual cells on a transmitter as active or inactive. You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by activating them from the Transmitters context menu, by activating the transmitters’ cells from the Cells table, or by selecting the transmitters with a zone and activating them from the zone’s context menu. To set an individual transmitter as active: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter you want to activate. The context menu appears. 4. Select Activate Transmitter from the context menu. The transmitter is now active. To set more than one transmitter as active using the Transmitters context menu: 1. Select the Network explorer. 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 rightclick the group of transmitters you want to set as active. The context menu appears.
3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one cell as active using the Cells table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cell’s 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. Select the Geo explorer. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder. 3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 54.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
847
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Working with Calculations in Atoll. Calculating path loss matrices can be extremely time and resource intensive when you are working on larger projects. Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the Atoll computing server application on other workstations or on servers. Once the computing server application is installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on the network. For information on distributed calculations, see the Administrator Manual.
10.1.10.6 Signal Level Coverage Predictions Atoll offers a series of standard coverage predictions that are common to all radio technologies. Coverage predictions specific to CDMA are covered in "CDMA-Specific Coverage Predictions" on page 862. Once you have created and calculated a coverage prediction, you can use the coverage prediction’s context menu to make the coverage prediction into a customised prediction which will appear in the Prediction Types dialogue. You can also select Duplicate from the coverage prediction’s context menu to create a copy. By duplicating an existing prediction that has the parameters you want to study, you can create a new coverage prediction more quickly than by creating a new coverage prediction. If you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the coverage prediction with the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the calculated coverage prediction. You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to load it into a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predictions are saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations, see "Saving a User Configuration" on page 101. The following standard coverage predictions are explained in this section: • • •
10.1.10.6.1
"Making a Coverage Prediction by Signal Level" on page 848 "Making a Coverage Prediction by Transmitter" on page 850 "Making a Coverage Prediction on Overlapping Zones" on page 851.
Making a Coverage Prediction by Signal Level A coverage prediction by signal level allows you to predict the best signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by signal level: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Signal Level and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.17). On the Conditions tab, you can define the signals that will be considered for each pixel. • • • • •
848
At the top of the Conditions tab, you can set the range of signal level to be considered. In Figure 10.17, 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 "Best". In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "Best", the values displayed will always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier. 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.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Figure 10.17: Condition settings for a coverage prediction by signal level 7. Click the Display tab. 8. Choose to display the results by best signal level. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 43. 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. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 10.18).
Figure 10.18: Coverage prediction by signal level You can run a specific prediction study displaying a coverage by pilot signal level for a given terminal, service, mobility and carrier as explained in "Making a Pilot Signal Quality Prediction" on page 870.
849
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
10.1.10.6.2
© Forsk 2012
Making a Coverage Prediction by Transmitter A coverage prediction by transmitter allows the user to predict which server is the best at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by transmitter: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types 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 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 10.17). On the Conditions tab, you can define the signals that will be considered for each pixel. •
At the top of the Conditions tab, you can set the range of signal level to be considered. In Figure 10.17, a signal level greater than or equal to -120 dBm or greater then -85 dBm will be considered.
•
Under Server, select "Best signal level." You can also define a Margin. Atoll will then consider the best signal level on each pixel and any other signal level within the defined margin of the best one.
•
If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability.
• •
You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "Best". In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "Best", the values displayed will always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier. 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 10.19: 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 43.
850
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
When creating a coverage prediction by discrete values, you can not export the values per pixel.
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. You can also predict which server is the second best server on each pixel by selecting "Second best signal level" on the Conditions tab setting "Discrete Values" as the Display Type and "Transmitter" as the Field on the Display tab.
10.1.10.6.3
Making a Coverage Prediction on Overlapping Zones Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction of overlapping zones on the signal level, path loss, or total losses within a defined range. To make a coverage prediction on overlapping zones: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Overlapping Zones and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.20). On the Conditions tab, you can define the signals that will be considered for each pixel. •
At the top of the Conditions tab, you can set the range of signal level to be considered. In Figure 10.20, a signal level greater than or equal to -120 dBm will be considered.
•
Under Server, select "Best signal level" and define a Margin. Atoll will then consider the best signal level on each pixel and any other signal level within the defined margin of the best one.
•
If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability.
• •
You can select the Indoor Coverage check box to add indoor losses. You can select the Carrier to be studied, or select "Best". In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "Best", the values displayed will always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier. 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.
851
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Figure 10.20: 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 43. 8. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. By changing the parameters selected on the Conditions tab and by selecting different results to be displayed on the Display tab, you can calculate and display information other than that which has been explained in the preceding sections.
10.1.10.7 Analysing a Coverage Prediction Once you have completed a prediction, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 838). If several coverage predictions are visible on the map, it can be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following tools are explained: • • • • • •
10.1.10.7.1
"Displaying the Legend Window" on page 852 "Displaying Coverage Prediction Results Using the Tip Text" on page 853 "Using the Point Analysis Reception View" on page 853 "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 854 "Viewing Coverage Prediction Statistics" on page 857 "Comparing Coverage Predictions: Examples" on page 858.
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to Legend check box on the Display tab.
852
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
To display the Legend window: •
10.1.10.7.2
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction identified by the name of the coverage prediction.
Displaying Coverage Prediction Results Using the Tip Text You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 838). To get coverage prediction results in the form of tip text: •
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined in the Display tab of the coverage prediction properties (see Figure 10.21).
Figure 10.21: Displaying coverage prediction results using tip text
10.1.10.7.3
Using the Point Analysis Reception View Once you have calculated the coverage prediction, you can use the Point Analysis tool to analyse the coverage prediction. Therefore, you will recreate the conditions of the coverage prediction. You can also use the Reception view of the Point Analysis tool without a coverage prediction, to study reception at any point on the map as long as you have valid path loss matrices. 1. Click the Point Analysis ( changes (
) in the Radio Planning toolbar. The Point Analysis window appears and the pointer
) to represent the receiver.
2. Select Reception (
) from the list at the top of the Point Analysis window (see Figure 10.22).
The predicted signal level from different transmitters is reported in the Reception view in the form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed in the map window. The best server of the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer location is displayed in the tool-tip. At the top of the Reception view, select the Carrier to be analysed.
Figure 10.22: Point Analysis Tool - Reception view 3. At the top of the Reception view, you can click one of the following buttons: •
: Click the Options button (
) to display the Calculations Options dialogue. You can change the following:
853
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
• • • •
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.
: Click the Copy button ( ) to copy the Reception view. You can then paste the contents of the Reception view as a graphic into a graphic editing or word-processing programme.
•
: Click the Print button (
) to print the Reception view.
You can also select the Results view ( ) to get more information. The Results view 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, and PN Offset.
10.1.10.7.4
Creating a Focus Zone or Hot Spot for a Coverage Prediction Report The focus and hot spots define an area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spots in addition to the focus zone. It is important not to confuse the computation zone and the focus and hot spots. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc., while the focus and hot spots are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spots. To define a focus zone or hot spot: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Focus Zone or Hot Spots folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the focus zone or hot spot.
ii. Click once on the map to define each point on the map where the border of the focus zone or hot spot changes direction. iii. Click twice to finish drawing and close the focus zone or hot spot. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the focus zone or hot spot.
ii. Drag to the opposite corner of the rectangle that will define the focus zone or hot spot. When you release the mouse, the focus zone or hot spot will be created from the rectangle defined by the two corners. A focus zone is delimited by a green line; a hot spot is delimited by a heavy black line. If you clear the zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot as follows: • •
•
•
854
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot by right-clicking it and selecting Use As > Focus Zone or Use As > Hot Spot from the context menu. You can also combine an existing focus zone or hot spot with any existing polygon by right-clicking it on the map or in the Explorer window and selecting Add To > Hot Spot or Add To > Hot Spot from the context menu. 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. You can import it by right-clicking the Focus Zone or Hot Spots folder in the Geo explorer and selecting Import from the context menu. When you import hot spots, you can import the name given to each zone as well. Fit Zone to Map Window: You can create a focus or hot spot the size of the map window by selecting Fit Zone to Map Window from the context menu.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
You can save the focus zone or hot spots, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the focus zone in the user configuration: For information on saving the focus zone in the user configuration, see "Saving a User Configuration" on page 101. Exporting the focus zone or hot spots: You can export the focus zone or hot spots by right-clicking the Focus Zone or the Hot Spots folder in the Geo explorer and selecting Export from the context menu.
You can include population statistics in the focus or hot spot by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137.
10.1.10.7.5
Displaying a Coverage Prediction Report Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage prediction’s Properties dialogue. The coverage prediction report is displayed in a table. For information on working with tables, see "Working with Data Tables" on page 69. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 74. Atoll bases the report on the area covered by the focus zone and hot spots; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot must be defined before you display a report; it is not necessary to define it before calculating coverage. The focus zone or hot spot does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 854. Once you have generated a report, you can export it to a text file or to an Excel spreadsheet. For more information on exporting a coverage prediction report, see "Exporting a Coverage Prediction Report" on page 856. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Predictions folder. 3. Right-click the coverage prediction for which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Define the format and content of the report: You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down.
to move it up or
You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spots and on the focus zone if available or on the hot spots and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears.
855
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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.
to move it up or
You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spots by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137. Normally, Atoll takes all geo data into consideration, whether it is displayed or not. However, for the population statistics to be used in a report, the population map has to be displayed. To include population statistics in the focus zone or hot spots: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. 2. Select the Network explorer. 3. Right-click the Predictions folder. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Select the following columns, where "Population" is the name of the folder in the Geo explorer 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.
6. Click OK. Atoll saves the names of the columns you select and will automatically select them the next time you create a coverage prediction report. 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 154.
10.1.10.7.6
Exporting a Coverage Prediction Report Once you have generated a coverage prediction report as explained in "Displaying a Coverage Prediction Report" on page 855, you can export it to a text file or to a spreadsheet. To export a coverage prediction report: 1. Right-click the report and select Export from the context menu or click the Export button ( The Save As dialogue appears. 2. In the Save As dialogue, enter the File name and select the format from the Save as type list: • • • •
856
TXT: To save the report as a text file. CSV: To save the report as a comma-separated values file. XLS: To save the report as an Excel spreadsheet. XML Spreadsheet 2003: To save the report as an XML spreadsheet.
) in the Table toolbar.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
3. Click Save to export the coverage prediction report.
10.1.10.7.7
Viewing Coverage Prediction Statistics Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage prediction colours, interval steps, and shading as defined on the Display tab of the coverage prediction’s Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spots are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before calculating coverage. For information on defining a focus zone, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 854. To display the statistics on a coverage prediction: 1. Select the Network explorer. 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.26). • •
• • •
Under Histogram based on covered areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Zoom on selected values section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics based on prediction conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.
Figure 10.23: Histogram of a coverage prediction by signal level
857
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
10.1.10.7.8
© Forsk 2012
Comparing Coverage Predictions: Examples Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison in one of the following ways: • •
•
Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both predictions are displayed in red). Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and pixels covered by only one prediction are blue). Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for example, pixels covered by both predictions are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).
To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction. 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 858 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 860.
Example 1: Studying the Effect of a New Base Station If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can verify if a newly added base station improves coverage. A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 848. The results are displayed in Figure 10.24. An area with poor coverage is visible on the right side of the figure.
Figure 10.24: 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 812, or by placing a station template, as explained in "Placing a New 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 impos-
858
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
sible 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.25).
Figure 10.25: Signal level coverage prediction of network with new base station Now you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the Display tab, you can choose how you want the results of the comparison to be displayed. You can choose among: • • •
Intersection Union Difference
In order to see what changes adding a new base station made, you should choose Difference. 5. Click OK to create the comparison. The comparison in Figure 10.26, shows clearly the area covered only by the new site.
859
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Figure 10.26: Comparison of both signal level coverage predictions Example 2: Studying the Effect of a Change in Transmitter Tilt If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can see how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 850. The results are displayed in Figure 10.27. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated by a red oval in Figure 10.27.
Figure 10.27: Coverage prediction by transmitter of existing network You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue. Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be impossible to compare the results. Instead, the original coverage prediction by can be copied by selecting Duplicate from its context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see Figure 10.28).
860
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Figure 10.28: Coverage prediction by transmitter of network after modifications As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change in coverage, you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties dialogue appears. 3. Click the General tab. You can change the Name of the comparison and add Comments. The General tab contains information about the coverage predictions being compared, including their name and resolution. 4. Click the Display tab. On the Display tab, you can choose how you want the results of the comparison to be displayed. You can choose among: • • •
Intersection Union Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The increase in coverage, seen in only the second coverage prediction, will be immediately clear. 5. Click OK to create the comparison. The comparison in Figure 10.29, shows clearly the increase in coverage due at the change in antenna tilt.
Figure 10.29: Comparison of both transmitter coverage predictions
861
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
10.1.10.8 CDMA-Specific Coverage Predictions In CDMA, the quality of the signal and the size of the area that can be covered are influenced by the network load. As the network load increases, the area a cell can effectively cover decreases. For this reason, the network load must be defined in order to calculate CDMA-specific coverage predictions. If you have traffic maps, you can do a Monte-Carlo simulation to model power control and evaluate the network load for a generated user distribution. If you do not have traffic maps, Atoll can calculate the network load using the reverse link load factor and forward link total power defined for each cell. 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 coverage predictions, each pixel is considered a noninterfering 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 862. "Service and User Modelling" on page 863.
Several different types of CDMA-specific coverage predictions are explained in this section. The following quality coverage predictions are explained: • • • •
"Making a Pilot Signal Quality Prediction" on page 870 "Studying Service Area (Eb⁄Nt) Uplink and Downlink for 1xRTT" on page 871 "Studying Service Area (Eb⁄Nt) Reverse Link for EV-DO" on page 873 "Studying Effective Service Area" on page 874.
The following noise predictions, another type of coverage prediction, are explained: • •
"Studying Forward Link Total Noise" on page 876 "Calculating Pilot Pollution" on page 877.
Another type of coverage prediction, the handoff coverage prediction, is also explained: •
"Making a Handoff Status Coverage Prediction" on page 879.
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 880.
Interference coming from an external project can also be modelled and is explained in "Modelling Inter-technology Interference" on page 975.
10.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 transmitter’s 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. Select the Network explorer. 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 816.
To enter the same values in one column for all cells in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
862
) in the
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69.
10.1.10.8.2
Service and User Modelling The different services offered by a CDMA network require different data rates. Voice, for example, does not require a very high data rate whereas a data service being used for video conferencing requires a much higher data rate. CDMA responds to the differing data rate requirements with a range of carriers. For example, CDMA2000 can provide voice using 1xRTT. Data services, which require higher data rates than voice, can be provided using 1xRTT or 1xEV-DO Rev. 0, Rev. A or Rev. B. For more information on the data rates available for voice, 1xRTT, and 1xEV-DO Rev. 0, Rev. A and Rev. B, see "Data Rates Available for Services in CDMA" on page 968. The CDMA reverse link traffic channels can provide five data rates for 1xEV-DO Rev. 0 and many more different data rates for 1xEV-DO Rev. A and 1xEV-DO Rev. B based services. In Atoll, the data rates available for 1xEV-DO Rev. A and 1xEV-DO Rev. B based services are modelled using radio bearers. You must define 1xEV-DO radio bearers before you can model services using them. For information on defining 1xEV-DO radio bearers, see "The 1xEV-DO Radio Bearers" on page 969. In this section, the following are explained: • • •
"Modelling Services" on page 863 "Creating a Mobility Type" on page 866 "Modelling Terminals" on page 867.
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. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears. You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.
863
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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: 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 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 user’s head, is estimated to be 3dB.
•
1xRTT Data: 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 1xRTT Data. • SCH Rate Probabilities: Under SCH Rate Probabilities, 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 user’s head, is estimated to be 3dB.
•
1xEV-DO Rev. 0 Data: 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. • UL Rate Probabilities: Under UL Rate Probabilities, 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 over- or 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.
864
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Possible Rate Changes During Upgrading
•
• •
Possible Rate Changes During Downgrading
From
To
From
To
9.6 kbps
19.2 kbps
153.6 kbps
76.8 kbps
19.2 kbps
38.4 kbps
76.8 kbps
38.4 kbps
38.4 kbps
76.8 kbps
38.4 kbps
19.2 kbps
76.8 kbps
153.6 kbps
19.2 kbps
9.6 kbps
UL Throughput Due to TCP Acknowledgement: If the Transmission Control Protocol (TCP) is used on the downlink (forward link), check the TCP Used check box. When TCP is used, reverse link traffic due to acknowledgements is generated. The traffic generated is calculated using the graph which describes the reverse link traffic due to TCP acknowledgements as a function of the forward link application throughput. The generated traffic is taken into account in simulation during the reverse link power control. 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 user’s head, is estimated to be 3dB.
1xEV-DO Rev. A Data and 1xEV-DO Rev. B Data: The following options are available for services with the type 1xEV-DO Rev. A Data and 1xEV-DO Rev. B Data. • QoS Class: The class of the service. Select "Guaranteed Bit Rate" for the services requiring a minimum bit rate, or "Best Effort" for best-effort applications. • 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. • Guaranteed Bit Rate: If you have selected "Guaranteed Bit Rate" as QoS class, enter the minimum required bit rate in order for the service to be available in the uplink and downlink. This parameter is not available for best-effort applications. • UL Rate Probabilities: Under UL Rate Probabilities, you can enter the probability of the service having the specified uplink rate. This parameter is available for best-effort applications only. In the column marked with the New Column icon ( ), select a Radio Bearer Index and enter a Usage Probability. Atoll automatically creates a new blank column. The sum of the probabilities must be lower than or equal to 1. The rate probabilities are used during simulations to determine the throughput requested by each user. If the bearer is not defined under UL Rate Probabilities, it is assumed that there are no users using the bearer. For services requiring a minimum bit rate, the usage probability is automatically calculated according to the number of selected radio bearers. •
•
UL Throughput Due to TCP Acknowledgement: 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 user’s head, is estimated to be 3dB. Best-effort services with the 1xEV-DO Rev. B Data type can be provided in multi-carrier mode if the server and the user terminal support it.
8. If you selected "1xEV-DO Rev. 0 Data" or "1xEV-DO Rev. A Data" or "1xEV-DO Rev. B 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 Eb⁄Nt tab, is available.
865
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Click the Eb⁄Nt tab. On the Eb⁄Nt 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
Data Rate
0
FCH nominal rate
2
(FCH nominal rate) + 2*(FCH nominal rate)
4
(FCH nominal rate) + 4*(FCH nominal rate)
8
(FCH nominal rate) + 8*(FCH nominal rate)
16
(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 Network Settings 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 Eb⁄Nt 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 Network Settings Properties dialogue. DL Target (dB): Enter the Eb⁄Nt 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 Ec⁄Nt 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 Network Settings Properties dialogue. 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 Network Settings 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 Network Settings 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. In order to define the VoIP service, select 1xEV-DO Rev.A Data as type of service, Guaranteed Bit Rate as QoS class and Low Latency as Uplink mode.
Creating a Mobility Type In CDMA, information about receiver mobility is important to efficiently manage the active set: a mobile used by someone travelling a certain speed and a mobile used by a pedestrian will not necessarily be connected to the same transmitters. Ec⁄I0 requirements and the Ec/Nt threshold (used only by 1xEV-DO Rev 0) are largely dependent on mobile speed. The following parameters are used in coverage predictions: • • •
Delta Min. Ec/I0 Delta T_Drop Min. Ec⁄Nt (UL)
To create or modify a mobility type: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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.
866
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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. Ec⁄I0: Enter a positive value in order to increase the minimum Ec⁄I0 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 Ec⁄I0 required from a transmitter not to be rejected from the active set, or a negative value to decrease it.
Under 1xEV-DO (Rev 0), enter or modify the following parameters: •
•
Min. Ec⁄Nt (UL): Enter or modify the minimum Ec⁄Nt 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(C⁄I) (Rev 0): The graph of the data rate on the forward link as a function of (C⁄I). 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 car’s 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 CDMA Rho factor
•
Voice and 1xRTT-specific parameters: • • • • •
•
1xEV-DO Rev. 0-specific parameters: • • •
•
Acknowledgement (ACK) channel gain Data Rate Control (DRC) channel gains Data channel gains
1xEV-DO Rev. A-specific parameters: • • • •
•
Active set size on FCH and SCH Number of fingers DL rake factor Pilot power percentage Nominal rate
Acknowledgement (ACK) channel gain Radio Reverse Indicator (RRI) channel gain Data Rate Control (DRC) channel gains Data channel and Auxiliary pilot gains
1xEV-DO Rev. B-specific parameters: • • •
Handoff type Highest supported modulation Data Rate Control (DRC) channel gains
To create or modify a terminal: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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.
867
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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: Select a type of reception equipment from the list. You can create a new type of reception equipment by using the Reception Equipment table. You can open open the Reception Equipment table by clicking the Expand button ( ) to expand the Network Settings folder, and then right-clicking the Reception Equipment folder and selecting Open Table 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 band. Leave the Secondary Band field empty if the terminal works only on one frequency band. There are two ways of defining dual-band terminals. Depending on the configuration, Atoll processes dual-band terminal users differently in the Monte-Carlo simulation. •
•
The first method 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. 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. For EV-DO-capable terminals, the FCH active set size also determines the active set size on the reverse link.
• •
868
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.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
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. 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. 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. 1xEV-DO Rev A-capable terminals support the 16QAM modulation.
9. Click the 1xEV-DO Rev B tab. •
Handoff Type: Select whether the terminal supports locked or unlocked mode. This parameter is taken into consideration when determining the terminal active set when multi-carrier mode is used. The active set of a multicarrier user consists of sub-active sets, each one being associated with one carrier. When locked mode is used, the serving transmitters must be the same in all sub-active sets. In this case, the active set is rectangular (i.e., the same number of serving cells in each sub-active set). With unlocked mode, the serving transmitters can be different from one sub-active set to another. Here, the active set might be rectangular is not necessarily so (i.e., the number of serving cells in each sub-active set can vary). Atoll does not manage the non-rectangular active set configuration when locked mode is selected.
• •
Highest Supported Modulation: Select the highest modulation supported by the terminal. You can choose either 16QAM or 64QAM (if you select 64QAM, 64QAM, and 16QAM modulations can be used). Max Number of Carriers in Multi-carrier Mode: Select the maximum number of EV-DO carriers that can be used when multi-carrier mode is active.
10. Click OK.
10.1.10.8.3
Making Quality Coverage Predictions In Atoll, you can make several predictions to study the quality. In this section, the following quality predictions are explained: • • • • • •
"Making a Pilot Signal Quality Prediction" on page 870 "Studying Service Area (Eb⁄Nt) Uplink and Downlink for 1xRTT" on page 871 "Studying Service Area (Eb⁄Nt) Reverse Link for EV-DO" on page 873 "Studying the Forward Link EV-DO Throughput" on page 872 "Studying Effective Service Area" on page 874 "Creating a Quality Coverage Prediction Using Quality Indicators" on page 875. A table listing quality indicators (BER, BLER, etc.) to be analysed is available. Quality coverage predictions proposed by Atoll depend on the quality indicators specified in this table.
869
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Making a Pilot Signal Quality Prediction A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is received sufficiently well to be added to the probe mobile active set. Atoll calculates the best pilot quality received on each pixel. Then, Atoll compares this value to the Ec⁄I0 threshold required to be the best server (Min Ec/I0 defined for the given cell plus the Delta Min Ec/I0 value defined for the selected mobility type). The pixel is coloured if the condition is fulfilled (in other words, if the best Ec⁄I0 is higher than the Ec⁄I0 threshold. To make a pilot signal quality prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Pilot Quality Analysis and click OK. The Pilot Quality Analysis 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.30). Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 863. 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 10.30: 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 "Ec⁄I0 (dB)" is selected by default. Each pixel is displayed in a colour corresponding to the pilot signal quality. For information on defining display properties, see "Display Properties of Objects" on page 43.
870
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
You can also set parameters to display the following results: • • • •
Where at least one transmitter is in the active set: Select "Unique" as the Display Type. Where at least one transmitter is in the active set, with information on the best server: Select "Discrete Value" as the Display Type and "Transmitter" as the Field. The pilot signal level: Select "Value Intervals" as the Display Type and "Ec (dBm)" as the Field. The pilot quality relative to the Ec⁄I0 threshold: Select "Value Intervals" as the Display Type and "Ec⁄I0 Margin (dB)" as the Field.
8. Click the Result Export tab. If, on the Display tab, you have selected to display the results by value intervals, you can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Studying Service Area (Eb⁄Nt) Uplink and Downlink for 1xRTT Atoll calculates the traffic channel quality on FCH (as defined by Eb⁄Nt) when using the maximum power allowed. In the coverage prediction, the forward link service area is limited by the maximum traffic channel power allowable on FCH per cell and by the pilot quality. The reverse link service area is limited by the maximum terminal power allowable on FCH and by the pilot quality. On both the forward and reverse links, if the received pilot is below the set threshold on a given pixel, Atoll will not display the traffic channel quality. Mobile macro-diversity is taken in consideration to evaluate the traffic channel quality (Eb⁄Nt). Atoll combines the signal from each transmitter in the probe mobile active set. To make a coverage prediction on service area (Eb/Nt) forward link or reverse link: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select one of the following coverage predictions and click OK: • •
Service Area Analysis (Eb/Nt) (UL) Service Area Analysis (Eb/Nt) (DL)
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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.30). Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a 1xRTT-capable Terminal, a 1xRTT Service, and a Mobility, as defined in "Service and User Modelling" on page 863. You must also select a 1xRTT Carrier. 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 also select the Indoor Coverage check box to add indoor losses. 7. Click the Display tab.
871
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
For a service area (Eb/Nt) coverage prediction, the Display Type "Value Intervals" based on the Field "Max Eb⁄Nt (dB)" is selected by default. The Field you choose determines which information the service area (Eb⁄Nt) 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 43. You can also set parameters to display the following results: • • • •
The traffic channel quality relative to the Eb⁄Nt threshold: Select "Value Intervals" as the Display Type and "Eb⁄Nt Margin (dB)" as the Field. The power required to reach the Eb⁄Nt threshold: Select "Value Intervals" as the Display Type and "Required Power (dB)" as the Field. Where traffic channel quality exceeds the Eb⁄Nt threshold for each mobility type: On the Conditions tab, select "All" as the Mobility Type. The parameters on the Display tab are automatically set. The throughput on the forward or reverse link: Select "Discrete values" as the Display Type and "Rate (Kbps)" as the Field.
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Studying the Forward Link EV-DO Throughput Atoll calculates the pilot channel quality (as defined by Ec⁄Nt) and, using the calculated Ec⁄Nt, Atoll calculates the maximum data rate that can be supplied. To make a forward link EV-DO throughput coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Service Area Analysis (Eb/Nt) (DL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.30). Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select an EV-DO-capable Terminal, an EV-DO Service, and a Mobility, as defined in "Service and User Modelling" on page 863. You must also select an EV-DO Carrier. In order to model a multi-carrier EV-DO user, select an EV-DO Rev. B-capable Terminal, an EV-DO Rev. B Service with the "Best Effort" QoS and "Best (1xEV-DO)" as carrier. If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box. You can also select the Indoor Coverage check box to add indoor losses. 7. Click the Display tab. By default, the Display Type "Value Intervals" based on the Field "Max Eb⁄Nt (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:
872
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
• •
•
The Ec⁄Nt ratio: Select "Value Intervals" as the Display Type and "C⁄I (dB)" as the Field. The throughput on the forward link: Select "Discrete values" as the Display Type and "Rate (Kbps)" as the Field. For multi-carrier EV-DO users, Atoll will calculate the throughput on each carrier and will display the total throughput (i.e., the sum of the throughputs obtained on each carrier) as prediction results. The average throughput on the forward link: This information is available when you model EV-DO Rev. A users, single-carrier and multi-carrier EV-DO Rev. B users. Select "Discrete values" as the Display Type and "Average Rate (Kbps)" as the Field. Atoll calculates the average EV-DO throughput on the forward link using the early termination probabilities, defined in the terminal’s reception equipment, to model HARQ (Hybrid Automatic Repeat Request).
For information on defining display properties, see "Display Properties of Objects" on page 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Studying Service Area (Eb⁄Nt) Reverse Link for EV-DO Atoll calculates the reverse link EV-DO traffic channel quality (Eb⁄Nt) with an uplink data channel rate of 9.6 kbps for EVDO Rev.0 users and 4.8 kbps for EVDO Rev.A and Rev.B users. The service area is limited by the maximum terminal power allowed and by the pilot quality. Mobile macro-diversity is taken in consideration to evaluate the traffic channel quality (Eb⁄Nt). Atoll combines the signal from each transmitter in the probe mobile active set. For multi-carrier EV-DO users, Atoll considers the best sub-active set. To make a coverage prediction on service area (Eb/Nt) reverse link: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Service Area Analysis (Eb/Nt) (UL) and click OK. The Service Area Analysis (Eb/Nt) (UL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.30). Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select an EV-DO-capable Terminal, an EV-DO Service, and a Mobility, as defined in "Service and User Modelling" on page 863. You must also select an EV-DO Carrier. In order to model a multi-carrier EV-DO user, select an EV-DO Rev. B-capable Terminal, an EV-DO Rev. B Service with the "Best Effort" QoS and "Best (1xEV-DO)" as carrier. If you want the service area (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 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 Eb⁄Nt (dB)" is selected by default. The Field you choose determines which information the service area (Eb⁄Nt) reverse link prediction makes available. Each pixel is displayed in a colour corresponding to the traffic channel quality with an uplink data
873
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
channel rate of 9.6 kbps for EVDO Rev.0 users and 4.8 kbps for EVDO Rev.A and Rev.B users. For information on defining display properties, see "Display Properties of Objects" on page 43. You can also set parameters to display the following results: • • • •
•
The traffic channel quality relative to the Eb⁄Nt threshold: Select "Value Intervals" as the Display Type and "Eb⁄Nt Margin (dB)" as the Field. The power required to reach the Eb⁄Nt threshold: Select "Value Intervals" as the Display Type and "Required Power (dB)" as the Field. Where traffic channel quality exceeds the Eb⁄Nt threshold for each mobility type: On the Conditions tab, select "All" as the Mobility Type. The parameters on the Display tab are automatically set. The throughput: Select "Discrete values" as the Display Type and "Rate (Kbps)" as the Field. For multi-carrier EVDO users, Atoll shares the available terminal power equally between each carrier in order to calculate the throughput obtained on each carrier. It displays the results for the best configuration among all combinations of carriers, i.e., the combination which provides the highest total throughput. The average EV-DO throughput: This information is available when you model EV-DO Rev. A users, single-carrier and multi-carrier EV-DO Rev. B users. Select "Discrete values" as the Display Type and "Average Rate (Kbps)" as the Field. Atoll calculates the average EV-DO throughput on the reverse link using the early termination probabilities, defined in the terminal’s reception equipment, to model HARQ (Hybrid Automatic Repeat Request).
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Studying Effective Service Area The effective service area is the intersection zone between the pilot reception area, and the reverse link and forward link service areas. In other words, the effective service area prediction calculates where a service actually is available for the probe mobile. To make an effective service area prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Effective Service Area Analysis (Eb/Nt) (DL+UL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.30). Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 863. 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.
874
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
For an effective service area prediction, the Display Type "Unique" is selected by default. The coverage prediction will display where a service actually is available for the probe mobile. In the calculations, Atoll considers 1xRTT users with the nominal FCH rate, EVDO Rev.A users with a data channel rate of 9.6 kbps in the reverse link and 38.4 kbps in the forward link, and EVDO Rev.B users with a data channel rate of 4.8 kbps in the reverse and the forward links. For information on defining display properties, see "Display Properties of Objects" on page 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Creating a Quality Coverage Prediction Using Quality Indicators You can create a quality coverage prediction based on a given quality indicators (BER, BLER, or FER). The coverage prediction will show for each pixel the measurement of the selected quality indicator. This type of coverage prediction is not available in the list of standard coverage predictions; you can, however, use quality indicators in a coverage prediction by first ensuring that the parameters of the quality indicators have been correctly set and then creating a coverage prediction, selecting display parameters that use these quality indicators. Before you define the quality coverage prediction, you must ensure that the parameters of the quality indicators have been correctly set. To check the parameters of the quality indicators: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click Quality Indicators. The context menu appears. 4. Select Open Table from the context menu. The Quality Indicators table appears. • • • •
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 UMTS Network Settings folder, right-click the Reception Equipment folder. The context menu appears. 7. Select Open Table from the context menu. The Reception Equipment table appears. "Standard" is the default reception equipment type for all terminals. 8. Double-click the reception equipment type for which you want to verify the correspondence between the measured quality and the quality indicator. The reception equipment type’s 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 type’s 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 coverage prediction. How you define a coverage prediction according to the measured quality indicator, depends several parameters: • • • •
The settings made in the Quality Indicators table The service you want to study The quality indicator you want to use (BER, BLER, or FER) The coverage prediction you want to use (Pilot Quality Analysis, the Service Area Analysis Downlink, or Service Area Analysis Uplink).
In the following example, you will create a quality coverage prediction showing BLER, for a user on foot, and with a 1xRTT data service.
875
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
To create a quality coverage prediction showing BLER for a user on foot, and with a 1xRTT data service: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Service Area Analysis (Eb⁄Nt) (DL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.30). Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
• • • •
Terminal: Select the appropriate radio configuration for mobile Internet access from the Terminal list. Service: Select "1xRTT Data" from the Service list. Mobility: Select "Pedestrian" from the Mobility list. Carrier: Select "1xRTT" from the Carrier list.
If you want the service area (Eb⁄Nt) 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
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 (Eb⁄Nt) (provided when using the maximum traffic channel power allowed). Then, it calculates the corresponding BLER value from the quality graph (BLER=f(DL Eb⁄Nt)). The pixel is coloured if the condition is fulfilled (i.e., if BLER is evaluated as being higher than the specified threshold).
10.1.10.8.4
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 876 "Calculating Pilot Pollution" on page 877 "Studying Inter-technology Downlink Noise" on page 878.
Studying Forward Link Total Noise In the forward link total noise prediction, Atoll calculates and displays the areas where the forward link total noise or the forward link noise rise exceeds a set threshold.
876
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
To make a forward link total noise or forward link noise rise prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Total Noise Level (DL) and click OK. The Coverage by Total Noise Level (DL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.30). Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 863. 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. •
Coverage by Total Noise Level (DL) 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Calculating Pilot Pollution A transmitter which fulfils all the criteria to enter a mobile’s active set but which is not admitted because the active set limit has already been reached is considered a polluter. In the Pilot Pollution Analysis prediction, Atoll calculates and displays the areas where the probe mobile is interfered by the pilot signal from polluter transmitters. For 1xRTT, pilot pollution is the same on the forward and on the reverse links because 1xRTT can be connected to more than one transmitter on both the forward and on the reverse links. EV-DO, on the other hand,
877
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
can only be connected to one transmitter on the forward link, but several on the reverse link. Therefore, pilot pollution for EV-DO will be different on the forward link and on the reverse link. The Pilot Pollution Analysis only calculates pilot pollution on the forward link. For multi-carrier EV-DO users, Atoll considers the active set associated with the best carrier. To make a pilot pollution prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Pilot Pollution Analysis 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.30). Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility as defined in "Service and User Modelling" on page 863. You must also select which Carrier is to be considered. If you want the Pilot Pollution Analysis to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box. You can also select the Indoor Coverage check box to add indoor losses. 7. Click the Display tab. For a Pilot Pollution Analysis, the Display Type "Value Intervals" and the Field "Number of Polluters" are selected by default. For information on defining display properties, see "Display Properties of Objects" on page 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Studying Inter-technology Downlink Noise In the inter-technology downlink noise prediction, Atoll calculates and displays the areas where the downlink noise or noise rise from external base stations and mobiles exceeds a set threshold. For more information on modelling inter-technology interference, see "Modelling Inter-technology Interference" on page 975. To make an inter-technology downlink noise or noise rise prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Inter-technology Interference Level Analysis (DL) 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 216. Under Display configuration, you can create a Filter to select
878
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab. Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. If you were going to base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list. You must select a Terminal and a Service, as defined in "Service and User Modelling" on page 863. You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or for the "Best" carrier selected according to the carrier selection method defined for the site equipment. If you want the prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box. 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
10.1.10.8.5
Making a Handoff Status Coverage Prediction In the handoff status prediction, Atoll calculates and displays the zones where a handoff can be made. For a handoff to be possible, there must be a potential active transmitter, i.e., a transmitter that fulfils all the criteria to enter the mobile active set, and the service chosen by the user must be available. You can also use the handoff status coverage prediction to display the number of potential active transmitters. For 1xRTT, the handoff status is the same on the forward and on the reverse links because 1xRTT can be connected to more than one transmitter on both the forward and on the reverse links. EV-DO, on the other hand, can only be connected to one transmitter on the forward link, but several on the reverse link. Therefore, the handoff status coverage prediction for EV-DO is calculated on the reverse link. For multi-carrier EV-DO users, Atoll considers the active set associated with the best carrier. To make a handoff status coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Handoff Zones 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction).The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 10.30).
879
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 863. 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
10.1.10.8.6
Making an AS Analysis The Point Analysis window gives you information on reception for any point on the map. The AS Analysis view gives you information on the pilot quality (Ec⁄I0) (which is the main parameter used to define the mobile active set), the connection status, and the active set of the probe mobile. 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 972. To make an AS analysis: 1. Click the Point Analysis button (
) on the toolbar. The Point Analysis Tool window appears (see Figure 10.32).
2. Select the AS Analysis view at the top of the Point Analysis window. 3. At the top of the AS Analysis view, select "Cells Table" from Load conditions. 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 Rev.0, you must select "9.6 kbps" for the UL Rate. If the coverage prediction was for EV-DO Rev.A or Rev.B, you must select "4.8 kbps" for the UL Rate. b. Click the Options button ( • • •
880
) to display the Calculation Options dialogue.
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.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
c. Click OK to close the Calculation Options dialogue. 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 10.31). Information on the current position is given in the AS Analysis view of the Point Analysis window. See Figure 10.32 on page 881 for an explanation of the displayed information.
Figure 10.31: Point analysis on the map 6. Click the map to leave the point analysis pointer at its current position. To move the pointer again, click the point analysis pointer on the map and drag it to a new position. 7. Click the Point Analysis button (
) on the toolbar again to end the point analysis.
Figure 10.32: Point Analysis - AS Analysis view The bar graph displays the following information: • • •
The pilot quality (Ec⁄I0) of all transmitters using the selected carrier (the colour of the bar corresponds to the colour of the transmitter on the map). The thresholds required to enter the active set as best server and not to be rejected from the active set. The portion of the graph with the grey background indicates the transmitters in the active set. The pilot and the availability of service on the reverse link and forward link.
If there is at least one successful connection (for pilot, forward link, or reverse link), double-clicking the icons in the right-hand frame will open a dialogue with additional information.
881
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
10.1.10.9 Printing and Exporting Coverage Prediction Results Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. •
•
•
Printing coverage prediction results: Atoll offers several options allowing you to customise and optimise the printed coverage prediction results. Atoll supports printing to a variety of paper sizes, including A4 and A0. For more information on printing coverage prediction results, see "Printing a Map" on page 84. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 59. Exporting coverage prediction results: In Atoll, you can export the coverage areas of a coverage prediction in raster or vector formats. In raster formats, you can export in BMP, TIF, ArcView© grid, or Vertical Mapper (GRD and GRC) formats. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 GB. In vector formats, you can export in ArcView©, MapInfo©, or AGD formats. For more information on exporting coverage prediction results, see "Exporting Coverage Prediction Results" on page 67.
10.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 define. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as possible neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as possible neighbours all the active and filtered cells whose propagation zone intersects a rectangle containing the computation zone. If there is no focus zone, Atoll allocates neighbours to the cells within the computation zone. The focus and computation zones are taken into account whether or not they are visible. In other words, the focus and computation zones will be taken into account whether or not their visibility check box in the Zones folder of the Geo explorer is selected. 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 Zone or Hot Spot for a Coverage Prediction Report" on page 854. For information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 89. 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. Intratechnology 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 882 "Defining Exceptional Pairs" on page 883 "Configuring Importance Factors for Neighbours" on page 883 "Allocating Neighbours Automatically" on page 884 "Checking Automatic Allocation Results" on page 887 "Allocating and Deleting Neighbours per Cell" on page 891 "Calculating the Importance of Existing Neighbours" on page 893 "Checking the Consistency of the Neighbour Plan" on page 895 "Exporting Neighbours" on page 896.
10.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 Network explorer. b. Right-click the Transmitters folder. The context menu appears. c. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears.
882
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 82.
10.1.11.2 Defining Exceptional Pairs In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs can be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Exceptional Pairs from the context menu. The Exceptional Pairs of IntraTechnology Neighbours table appears. 4. Click the Edit button on the bottom-right of the dialogue. The exceptional pair list becomes editable. 5. In the row marked with the New Row icon ( from the Cell column.
), select the cell for which you want to define neighbour constraints
6. From the Neighbour column, select the second cell of the exceptional pair. 7. 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. 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.
10.1.11.3 Configuring Importance Factors for Neighbours You can define the relative importance of the factors that Atoll uses to evaluate possible intra- and inter-carrier neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. Select the Intra-carrier Neighbours tab. On the Intra-carrier Neighbours tab, you can set the following importance factors: •
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter.
•
Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency Factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency Factor will be used if you select the Force adjacent transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 884. 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 884.
•
•
5. Select the Inter-carrier Neighbours tab. On the Inter-carrier Neighbours tab, you can set the following importance factors: •
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter.
•
Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. 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 884.
•
883
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
6. Click OK. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual.
10.1.11.4 Allocating Neighbours Automatically Atoll can automatically allocate both intra- and inter-carrier neighbours in a CDMA network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. To automatically allocate intra-carrier CDMA neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Click the Intra-carrier Neighbours tab. You can set the following parameters: • • •
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 Ec⁄I0 required from a transmitter to enter the active set as best server. • T_Drop: Enter or modify the minimum Ec⁄I0 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 cell’s coverage area must overlap the reference cell’s 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 cell’s 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 cell’s 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 883. 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.
884
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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 893 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 cell’s 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 Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. 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 cell’s Properties dialogue. To automatically allocate inter-carrier CDMA neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > 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.
885
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
•
© Forsk 2012
% Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cell’s coverage area must overlap the reference cell’s 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 883. 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. 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 893 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 cell’s 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 Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. 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 on the Intra-technology Neighbours tab of each cell’s Properties dialogue.
886
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
•
•
•
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint on the forbidden neighbour will be ignored by the algorithm because the neighbour already exists. When the options Force exceptional pairs and Force symmetry are selected, Atoll considers the constraints between exceptional pairs in both directions in order to respect symmetry. On the other hand, if the neighbour relation is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event Viewer. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Saving a User Configuration" on page 101.
Atoll also enables you to automatically allocate neighbours to a single base station or transmitter: • •
10.1.11.4.1
"Allocating Neighbours to a New Base Station" on page 887 "Allocating Neighbours to a New Transmitter" on page 887.
Allocating Neighbours to a New Base Station When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects with the coverage area of the cells of the new base station. To allocate neighbours to a new base station: 1. In the Network explorer, group the transmitters by site, as explained in "Grouping Data Objects" on page 89. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Neighbours > Intra-technology > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 884.
10.1.11.4.2
Allocating Neighbours to a New Transmitter When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new transmitters and other cells whose coverage area intersects with the coverage area of the cells of the new transmitter. To allocate neighbours to a new transmitter: 1. Select the Network explorer. 2. In the Transmitters folder, right-click the new transmitter. The context menu appears. 3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 884.
10.1.11.5 Checking Automatic Allocation Results You can verify the results of automatic neighbour allocation in the following ways: • •
10.1.11.5.1
"Displaying Neighbour Relations on the Map" on page 887 "Displaying the Coverage of Each Neighbour of a Cell" on page 890.
Displaying Neighbour Relations on the Map You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
2. Select Display Options from the context menu. The Edit Relations on the Map dialogue appears. 3. Under Intra-technology Neighbours, select the Display Links check box.
887
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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 cell’s 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 cell’s neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors. 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 Type’s Data Table" on page 71.
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 43. 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 tip text. 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 Links: Select the Symmetric Links 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 Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 14. Click the Edit Relations on the Map button (
) in the Radio Planning toolbar.
15. Select a transmitter to show its neighbour links: •
•
•
888
In the Transmitters folder of the Network explorer: Select the transmitter in the Transmitters folder. The selected transmitter is centred in the map and all its neighbours are indicated. Atoll displays the selected transmitter in the Neighbours table if it is open. On the map: Select the transmitter on the map. The neighbours of the selected transmitter are displayed on the map. 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 41). Atoll displays the selected transmitter in the Neighbours table if it is open. In the Neighbours table: Select the transmitter-neighbour relation you want to display by clicking in the left margin of the table row to select the entire row. The selected transmitter is centred in the map with the selected transmitter-neighbour relation (see Figure 10.33). The selected transmitter is also displayed in the Transmitters folder of the Network explorer.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Figure 10.33: Selecting a transmitters in the Neighbours table Atoll displays the following information (see Figure 10.34) 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 10.34.). 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 10.34.).
In Figure 10.34, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward neighbour links have the same colour as the corresponding neighbour transmitters and the inward neighbour link has the same colour as the reference transmitter as it is neighbour of Site9_3(0) here.
Figure 10.34: Neighbours of Site 22_3(0) - Display According to the Neighbour In Figure 10.35, neighbour links are displayed according to the neighbour carrier. You can view intra-carrier and intercarrier neighbour links. In this example, all neighbour relations are symmetric.
889
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Figure 10.35: Intra-carrier and Inter-carrier Neighbours of Site 14_3(0) You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
10.1.11.5.2
Displaying the Coverage of Each Neighbour of a Cell By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cell’s neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a "Coverage by transmitter" prediction, with the Display Type set to "Discrete Values" and the Field set to Transmitter (for information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by Transmitter" on page 850). 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
3. Select Display Options from the context menu. The Edit Relations on the Map dialogue appears. 4. Under Intra-technology neighbours, select the Display coverage areas check box. 5. Click the Browse button ( dialogue appears.
) beside the Display Coverage Areas check box. The Intra-technology Neighbour Display
6. 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 cell’s 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 cell’s neighbours according to a value from the Intra-technology Neighbours table. Value Intervals: Select "Value Intervals" to colour the coverage area of a cell’s neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors.
7. Click the Browse button ( ) next to Tip text and select the neighbour characteristics to be displayed in the tip text. This information will be displayed on each coverage area. 8. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
9. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 10. Click the Edit Relations on the Map button (
890
) in the Radio Planning toolbar.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
11. 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 41). Only intra-carrier neighbour coverage areas are displayed.
12. In order to restore colours and cancel the neighbour display, click the Edit Relations on the Map button ( Radio Planning toolbar.
) in the
10.1.11.6 Allocating and Deleting Neighbours per Cell Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of the Transmitter Properties dialogue. This section explains the following: • • •
"Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 891 "Allocating or Deleting Neighbours Using the Neighbours Table" on page 892 "Allocating or Deleting Neighbours on the Map" on page 893.
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 transmitter’s 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 transmitter’s 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 cell’s Properties dialogue appears. 5. Click the Intra-technology Neighbours tab. 6. Allocate or delete a neighbour. To allocate a new neighbour: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon (
).
c. Click elsewhere in the table to complete creating the new neighbour. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Source to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row.
891
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
c. Press DEL to delete the neighbour. 7. Click OK. Allocating or Deleting Neighbours Using the Neighbours Table To allocate or delete CDMA neighbours using the Neighbours table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Neighbours from the context menu. The Neighbours table appears. For information on working with data tables, see "Working with Data Tables" on page 69.
To allocate a neighbour: a. In the row marked with the New Row icon (
), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Source to "manual," and sets the Importance to "1." To create a 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 exceptional pairs: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. 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. 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.
892
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. Allocating or Deleting Neighbours on the Map You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 887. 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. •
•
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 41). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
10.1.11.7 Calculating the Importance of Existing Neighbours After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours in the AFP process. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears.
893
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
3. Select Neighbours > Intra-technology > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 4. Select the Intra-technology Neighbours tab. 5. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as possible neighbours. 6. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 883): • •
Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that neighbours are adjacent to their reference transmitters when calculating importance. Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.
7. 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 Ec⁄Io which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage. T_Drop: Enter the minimum Ec⁄Io 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.
8. Click OK to save your modifications and close the Coverage Conditions dialogue. 9. Select the Inter-carrier Neighbours tab. 10. 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 883): 11. Under Coverage Conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: • • •
• •
• •
Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell and the neighbour. Min. Ec/Io: Enter the minimum Ec⁄Io which must be provided by reference cell in an area with overlapping coverage. The reference cell must also be the best server in terms of pilot quality in the area with overlapping coverage. T_Drop: Enter the minimum Ec⁄Io 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.
12. Click OK to save your modifications and close the Coverage Conditions dialogue. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.
894
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
13. 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 transmitter’s 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.
14. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
10.1.11.8 Checking the Consistency of the Neighbour Plan You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the neighbour allocation plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Intra-technology Neighbours tab. 5. Define the parameters of the audit: • • • •
•
• • • •
Neighbourhood Type: Select whether you want to perform an audit on Intra-Carrier or Inter-Carrier neighbour relations. Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Lists > Max Number: Select the Lists > Max Number check box if you want to verify which cells have more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that should not be exceeded.
6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: •
Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax:
•
|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.
895
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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| If the field Maximum number of intra-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.
•
Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax:
•
Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
|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.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 to use it in another application or in another Atoll document. To export neighbour data: 1. Select the Network explorer. 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 > Open Table: This table contains the data for the intra-technology neighbours in the current Atoll document. Inter-technology > Open Table: This table contains the data for the inter-technology neighbours in the current Atoll document. Intra-technology > Exceptional Pairs: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document. Inter-technology > Exceptional Pairs: This table contains the data for the inter-technology exceptional pairs (forced and forbidden) in the current Atoll document.
4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files and Spreadsheets" on page 80.
10.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: •
896
Preparing for PN Offset allocation • "Creating PN Offset Domains and Groups for PN Offset Allocation" on page 974. This step is needed only if you must restrict the range of PN Offsets.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
• •
"Defining Exceptional Pairs for PN Offset Allocation" on page 897.
Allocating PN Offsets • •
"Automatically Allocating PN Offsets to CDMA Cells" on page 898 "Allocating PN Offsets to CDMA Cells Manually" on page 900.
•
"Checking the Consistency of the PN Offset Plan" on page 900.
•
Displaying the allocation of PN Offsets • • • • • •
"Using Find on Map to Display PN Offset Allocation" on page 901 "Displaying PN Offset Allocation Using Transmitter Display Settings" on page 901 "Grouping Transmitters by PN Offset" on page 902 "Displaying the PN Offset Allocation Histogram" on page 902 "Making a PN Offset Collision Zone Prediction" on page 902. "Making a PN Offset Collision Analysis" on page 903 Within the context of PN Offset allocation, "neighbours" refer to intra-carrier neighbours.
10.1.12.1 Defining Exceptional Pairs for PN Offset Allocation You can also define pairs of cells which cannot have the same primary PN Offset. These pairs are referred to as exceptional pairs. Exceptional pairs are used along with other constraints, such as neighbours, reuse distance, and domains, in allocating PN Offsets. To create a pair of cells that cannot have the same PN Offset: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select PN Offsets > Exceptional Pairs. The Exceptional Separation Constraints table appears. For information on working with data tables, see "Working with Data Tables" on page 69. 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.
10.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 897 "Automatically Allocating PN Offsets to CDMA Cells" on page 898 "Allocating PN Offsets to CDMA Cells Manually" on page 900.
Defining Automatic Allocation Constraint Costs You can define the costs of the different types of constraints used in the automatic PN Offset allocation algorithm. To define the different constraint costs: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select PN Offsets > Constraint Costs. The Allocation Constraint Costs dialogue appears. In this dialogue you can define the following costs of constraint violations for the automatic allocation process (the cost is a value from 0 to 1): • • • •
Max 1st, 2nd, and 3rd Order Neighbours: Enter the maximum costs for 1st, 2nd, and 3rd order neighbour constraint violations. Co-planning Share: Enter the cost for inter-technology neighbour constraint violations. Max Reuse Distance: Enter the maximum cost for reuse distance constraint violations. Exceptional Pair: Enter the cost for exceptional pair constraint violations.
4. Click OK. The allocation constraint costs are stored and will be used in the automatic allocation.
897
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Automatically Allocating PN Offsets to CDMA Cells The allocation algorithm enables you to automatically allocate PN Offsets to cells in the current network. You can choose among several automatic allocation strategies. The actual automatic allocation strategies available will depend on your network and options selected in the atoll.ini file. For more information on the atoll.ini file, see the Administrator Manual. For more information on automatic allocation strategies, see the Technical Reference Guide. • •
•
PN Offset per Cell: The purpose of this strategy is to reduce the spectrum of allocated PN Offsets the maximum possible. Atoll will allocate the first possible PN Offsets in the domain. Adjacent PN-Clusters per Site: This strategy consists of allocating one cluster of adjacent PN Offsets to each base station, then, one PN Offset of the cluster to each cell of each transmitter according to its azimuth. When all the clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses the clusters at another base station. Distributed PN-Clusters per Site: This strategy consists of allocating one cluster of PN Offsets to each base station in the network, then, one PN Offset of the cluster to each cell of each transmitter according to its azimuth. With this strategy, the cluster is made of PN Offsets separated as much as possible. When all the clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses the clusters at another base station. Within the context of PN Offset allocation, the term "PN-cluster" refers to a sub-group of PN Offsets that Atoll assigns to base stations during the allocation process. Atoll allows you to change the number of PN Offsets in a PN-cluster. The following example explains the difference between "Adjacent PN-clusters" and "Distributed PN-clusters". The PILOT_INC has been set to 4 and the PN-cluster size to 3. There are: • •
128 PN Offsets that can be allocated: they are from 4 to 508 with a separation interval of 4. Each PN-cluster consists of three PN Offsets. Therefore, there are 42 PN-clusters available.
If you select "Adjacent PN-cluster per site" as allocation strategy, Atoll will consider PNclusters consisted of adjacent PN Offsets (e.g., {4,8,12}, {16,20,24}, ..., {496,500,504}). If you select "Distributed PN-cluster per site" as allocation strategy, Atoll will consider PNclusters consisted of PN Offsets separated as much as possible (e.g., {4,172,340}, {8,176,344}, ..., {168,336,504}). To automatically allocate PN Offsets: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select PN Offsets > Automatic Allocation. The PN Offsets 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 PNchips, of cells. The PILOT_INC value must be from 1 to 15. Atoll uses this parameter to determine the pool of possible PN Offsets (512 divided by PILOT_INC value). The first PN Offset is PILOT_INC and other ones are multiples of this value. For example: When PILOT_INC is set to 4, the pool of possible PN Offsets consists of PN Offsets from 4 to 508 with a separation interval of 4 (i.e., [4,8,12,16,...508]).
•
Existing Neighbours: Select the Existing Neighbours check box if you want to consider intra-carrier neighbour relations and then choose the neighbourhood level to take into account: Neighbours of a cell are referred to as the first order neighbours, neighbours’ neighbours are referred to as the second order neighbours and neighbours’ neighbours’ neighbours as the third order neighbours. First Order: No cell will be allocated the same PN Offset as its neighbours. Second Order: No cell will be allocated the same PN Offset as its neighbours or its second order neighbours. Third Order: No cell will be allocated the same PN Offset as its neighbours or its second order neighbours or third order neighbours. Atoll can only consider neighbour relations if neighbours have already been allocated. For information on allocating neighbours, see "Planning Neighbours" on page 882.
898
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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 963 •
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 cell’s 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. Ec⁄I0: Enter the minimum Ec⁄I0 which must be provided by reference cell A in an area with overlapping coverage. Reference cell A must also be the best server in terms of pilot quality in the area with overlapping coverage. T_Drop: Enter or modify the minimum Ec⁄I0 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.
• •
From the Strategy list, you can select an automatic allocation strategy: • • •
• •
•
•
•
Exceptional Pairs: Select the Exceptional Pairs check box if you want the automatic allocation process to consider the exceptional pair constraints. PN Offset per Cell Adjacent PN-Clusters per Site Distributed PN-Clusters per Site
Carrier: Select the Carrier on which you want to run the allocation. You may choose one carrier (Atoll will assign PN Offsets to transmitters using the selected carrier) or all of them. PN-Cluster Size: The number of PN Offsets per cluster. This parameter is used only by the Adjacent PN-Clusters per Site and Distributed PN-Clusters per Site allocation strategies. It should correspond to the average number of transmitters located on a site. Use a Max of Codes: Select the Use a Max of Codes check box to make Atoll use the maximum number of PN Offsets. For example, if there are two cells using the same domain with two PN Offsets, Atoll will assign the remaining PN Offset to the second cell even if there are no constraints between these two cells (for example, neighbour relations, reuse distance, etc.). If you do not select this option, Atoll only checks the constraints, and allocates the first ranked PN Offset in the list. Delete Existing PN Offsets: Select the Delete Existing PN Offsets check box if you want Atoll to delete currently allocated PN Offsets and recalculate all PN Offsets. If you do not select this option, Atoll will keep currently allocated PN Offsets and will only allocate PN Offsets to cells that do not yet have PN Offsets allocated. Allocate Carriers Identically: Select the Allocate Carriers Identically check box if you want Atoll to allocate the same PN Offset to each carrier of a transmitter. If you do not select this option, Atoll allocates PN Offsets independently for each carrier.
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.
899
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
•
© Forsk 2012
Code: The PN Offset allocated to the cell.
6. Click Commit. The PN Offsets are committed to the cells. 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 "Saving a User Configuration" on page 101.
•
•
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 transmitter’s 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 group’s context menu.
Allocating PN Offsets to CDMA Cells Manually When you allocate PN Offsets to a large number of cells, it is easiest to let Atoll allocate PN Offsets automatically, as described in "Automatically Allocating PN Offsets to CDMA Cells" on page 898. However, if you want to add a PN Offset to one cell or to modify the PN Offset of a cell, you can do it by accessing the properties of the cell. To allocate a PN Offset to a CDMA cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate a PN Offset. The context menu appears. 2. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 3. Select the Cells tab. 4. Enter a PN Offset in the cell’s column. 5. Click OK.
10.1.12.3 Checking the Consistency of the PN Offset Plan Once you have completed allocating PN Offsets, you can verify whether the allocated PN Offsets respect the specified constraints by performing an audit of the plan. The PN Offset audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select PN Offsets > Audit. The Code Audit dialogue appears. 4. In the Code Audit dialogue, select the allocation criteria that you want to check: •
Neighbours: Select Neighbours in order to check PN Offset constraints between cells and their neighbours and then choose the neighbourhood level to take into account. First Order: Atoll will check that no cell has the same PN Offset as any of its neighbours. Second Order: Atoll will check that no cell has the same PN Offset as any of its neighbours or any of the neighbours of its neighbours. Third Order: Atoll will check that no cell has the same PN Offset as any of its neighbours or any of the neighbours of its neighbours or any of the neighbours of its second order neighbours. The report will list the cells and the neighbours that do not meet one of these constraints. In addition, it will indicate the allocated PN Offset and the neighbourhood level.
•
•
•
900
Domain Compliance: If you select the Domain Compliance check box, Atoll will check if allocated PN Offsets belong to domains assigned to cells. The report will list any cells with PN Offsets that do not belong to domains assigned to the cell. Distance: If you select the Distance check box and set a reuse distance, Atoll will check for and list the cell pairs that do not respect the reuse distance condition. For any cell pair, Atoll uses the lowest of the reuse distance values among the values defined for the two cells in their properties and the value that you set in the Code Audit 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.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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.
10.1.12.4 Displaying the Allocation of PN Offsets Once you have completed allocating PN Offsets, you can verify several aspects of PN Offset allocation. You have several options for displaying PN Offsets: • • • • • •
"Using Find on Map to Display PN Offset Allocation" on page 901 "Displaying PN Offset Allocation Using Transmitter Display Settings" on page 901 "Grouping Transmitters by PN Offset" on page 902 "Displaying the PN Offset Allocation Histogram" on page 902 "Making a PN Offset Collision Zone Prediction" on page 902. "Making a PN Offset Collision Analysis" on page 903
Using Find on Map to Display PN Offset Allocation In Atoll, you can search for PN Offsets and PN Offset groups using the Find on Map tool. Results are displayed in the map window in red. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. PN Offsets and PN Offset groups and any potential problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 850. To find PN Offsets or PN Offset groups using the Find on Map tool: 1. Click Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "PN Offset." 3. Select what you what you want to search for: • •
PN Offset: If you want to find a PN Offset, select PN Offset and select it from the list. PN Offset Group: If you want to find a PN Offset group, select PN Offset Group and select it from the list.
4. Select the carrier you want to search on from the For carrier list, or select "(All)" to search in all carriers. 5. Click Search. Transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match the search criteria are displayed as grey lines. To restore the initial transmitter colours, click the Reset Display button in the Find on Map tool. Displaying PN Offset Allocation Using Transmitter Display Settings You can use the display characteristics of transmitters to display PN Offset-related information. To display PN Offset-related information on the map: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. You can display the following information per transmitter: • • •
PN Offset: To display the PN Offset of a transmitter’s cell, select "Discrete values" as the Display Type and "Cells: PN Offset" as the Field. Ranges of PN Offsets: To display ranges of PN Offsets, select "Value intervals" as the Display Type and "Cells: PN Offset" as the Field. PN Offset domain: To display the PN Offset domain of a transmitter’s cell, select "Discrete values" as the Display Type and "Cells: PN Offset Domain" as the Field.
You can display the following information in the transmitter label or tip text: • •
PN Offset: To display the PN Offset of a transmitter’s cell in the transmitter label or tip text, "Cells: PN Offset" from the Label or Tip Text Field Definition dialogue. PN Offset domain: To display the PN Offset domain of a transmitter’s cell in the transmitter label or tip text, "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 43.
901
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Grouping Transmitters by PN Offset You can group transmitters in the Network explorer by their PN Offset or by their PN Offset domain. To group transmitters by PN Offset: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available Fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: • •
PN Offset PN Offset Domain
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to the list of parameters on which the transmitters will be grouped. For more information on grouping objects, see "Advanced Grouping" on page 90. 8. Click OK to save your changes and close the Group dialogue. If a transmitter has more than one cell, Atoll cannot arrange the transmitter by cell. Transmitters that cannot be grouped by cell are arranged in a separate folder under the Transmitters folder. Displaying the PN Offset Allocation Histogram You can use a histogram to analyse the use of allocated PN Offsets in a network. The histogram represents the PN Offsets as a function of the frequency of their use. To display the PN Offset histogram: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select PN Offset > PN Offset Distribution. The Distribution Histograms dialogue appears. Each bar represents a PN Offset, its height depending on the frequency of its use. 4. Move the pointer over the histogram to display the frequency of use of each PN Offset. The results are highlighted simultaneously in the Zoom on selected values list. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. Making a PN Offset Collision Zone Prediction You can make a PN Offset collision zone prediction to view areas covered by cells using the same PN Offset. Atoll checks on each pixel if the best server and other servers satisfying the conditions to enter the user active set have the same PN Offset. If so, Atoll considers that there is PN Offset collision. To make a PN Offset collision zone prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select PN Offset Collision 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 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab.
902
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load factor and the forward link total power defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 863. You must also select which Carrier is to be considered. If you want the PN Offset collision zone prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box. You can also select the Indoor Coverage check box to add indoor losses. 7. Click the Display tab. For a PN Offset collision zone prediction, the Display Type "Discrete Values" based on the Field "Transmitter" is selected by default. Each pixel with PN Offset collision is displayed with the same colour as that defined for the interfered transmitter. In the Explorer window, the coverage prediction results are ordered first by interfered transmitter and then by interferer. For information on defining display properties, see "Display Properties of Objects" on page 43. 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: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Making a PN Offset Collision Analysis The PN Offset Collision tab of the Point Analysis window gives you information on the reception for any point on the map where there is PN Offset collision. PN Offset collision occurs when the best server and other servers satisfying the conditions to enter the user active set have the same PN Offset. When there is PN Offset collision, Atoll displays the pilot quality (Ec⁄I0) received from interfered and interferer transmitters. Analysis is based on the UL load percentage and the DL total power of cells. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service. You can make a PN Offset collision analysis to review the PN Offset collision zone coverage prediction. In this case, before you make the PN Offset collision analysis, you should ensure that the coverage prediction you want to use in the PN Offset collision analysis is displayed on the map. To make a PN Offset collision analysis: 1. Click the Point Analysis button (
) on the toolbar. The Point Analysis Tool window appears.
2. Click the PN Offset Collision tab. 3. At the top of the PN Offset Collision tab, select "Cells Table" from Load Conditions. 4. If you are making a PN Offset collision 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.
903
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
If you are making a PN Offset collision 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 collision analysis for the current location of the pointer. 6. Click the map to leave the point analysis pointer at its current position. To move the pointer again, click the point analysis pointer on the map and drag it to a new position. 7. Click the Point Analysis button (
) on the toolbar again to end the point analysis.
10.2 Studying Network Capacity A CDMA network automatically regulates power with the objective of minimising interference and maximising network capacity. In the case of CDMA2000 1xRTT, fast power control is made on both the forward and reverse links (uplink and downlink, respectively). In CDMA2000 1xRTT, power control can be performed on either the FCH and SCH or on the pilot channel. In CDMA2000 EV-DO, rate control is used instead of power control on the forward link. On the reverse link, power control is made on the pilot channel. Atoll can simulate these network regulation mechanisms, thereby enabling you to study the capacity of the CDMA network. In Atoll, a simulation is based on a realistic distribution of users at a given point in time. The distribution of users at a given moment is referred to as a snapshot. Based on this snapshot, Atoll calculates various network parameters such as the active set for each mobile, the required power of the mobile, SHO gain, the total forward link power and forward link throughput per cell, and the reverse link load per cell. Simulations are calculated in an iterative fashion. When several simulations are performed at the same time using the same traffic information, the distribution of users will be different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snapshot to another. To create snapshots, services and users must be modelled. As well, certain traffic information in the form of traffic maps must be provided. Once services and users have been modelled and traffic maps have been created, you can make simulations of the network traffic. In this section, the following are explained: • • • •
"Defining Multi-service Traffic Data" on page 904 "Creating a Traffic Map" on page 904 "Calculating and Displaying Traffic Simulations" on page 914 "Analysing the Results of a Simulation" on page 931.
10.2.1 Defining Multi-service Traffic Data The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters used in the network, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: • •
•
Services: Services are the various services, such as voice, mobile internet access, etc., available to subscribers. For information on modelling end-user services, see "Modelling Services" on page 863. Mobility type: In CDMA, information about receiver mobility is important to efficiently manage the active set: a mobile used by a driver moving quickly or a pedestrian will not necessarily be connected to the same transmitters. Ec⁄I0 requirements and Eb⁄Nt targets per radio bearer and per link (forward or reverse) are largely dependent on mobile speed. For information on creating a mobility type, see "Creating a Mobility Type" on page 866. Radio configuration: In CDMA, a radio configuration is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a car’s on-board navigation device. In Atoll, radio configurations are modelled using terminals. For information on creating a terminal, see "Modelling Terminals" on page 867.
10.2.2 Creating a Traffic Map The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atollprovides three types of traffic maps for CDMA projects. • • •
Sector traffic map User profile traffic map User density traffic map (number of users per km2)
The maps you can create depend on the types of traffic data sources available to you: •
904
Sector traffic maps can be used if you have live traffic data from the OMC (Operation and Maintenance Centre).
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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 905. •
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 908, "Creating a User Profile Environment Based Traffic Map" on page 910, and "Importing 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. 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 911, "Creating a User Density Traffic Map" on page 912, "Converting 2G Network Traffic" on page 913 and "Exporting Cumulated Traffic" on page 913.
10.2.2.1 Creating a Sector Traffic Map The section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands in the reverse and forward links or the number of users per activity status or the total number of users including all activity statuses. A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by Transmitter" on page 850. Because each of the CDMA technologies has capabilities and services that are specific to it, it is recommended to create a separate traffic map for: • • •
voice 1xRTT data EV-DO data
To create a sector traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector Traffic Map. 5. Select the type of traffic information you want to input. You can choose between 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. 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. 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.
905
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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 82. 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 Maps folder. You can modify the sector traffic map after it has been created. To modify the sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 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 850. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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 913.
10.2.2.2 Creating a User Profile Traffic Map The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There may also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create traffic maps based on user profiles and environments.
906
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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. 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 908, "Importing a User Profile Environment Based Traffic Map" on page 910 and "Creating a User Profile Environment Based Traffic Map" on page 910 describe how to use traffic data from the marketing department in Atoll to model traffic. In this section, the following are explained: • •
"Modelling User Profiles" on page 907 "Modelling Environments" on page 907.
Modelling User Profiles You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user can be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: To create a user profile: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles New Element Properties dialogue appears. 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 863. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 867. 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. 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. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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.
907
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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.
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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
For example: An area of 10 km² with a subscriber density of 100/km². Therefore, in this area, there are 1000 subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in the Building clutter class. 10. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss.
10.2.2.2.1
Importing a User Profile Traffic Map User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscribers⁄km, or polygons with a number of subscribers⁄km²) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Densities from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue.
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 map’s properties dialogue appears. 11. Select the Traffic tab (see Figure 10.36). Under Traffic Fields, you can specify the user profiles to be considered, their mobility type (km⁄h), and their density. If the file you are 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.
908
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Figure 10.36: Traffic map properties dialogue - Traffic tab Define each of the following: •
•
•
User Profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points. When you import user profile or mobility information from the file, the values in the file must be exactly the same as the corresponding names in the Traffic Parameters folder in the Parameters explorer. If the imported user profile or mobility does not match, Atoll will display a warning.
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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
13. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simulation, an additional loss will be added to the indoor users path loss. 14. Click OK to finish importing the traffic map.
909
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
10.2.2.2.2
© Forsk 2012
Importing a User Profile Environment Based Traffic Map Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 910. 7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, 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 map’s 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 Traffic Parameters in the Parameters explorer. For more information, see "Modelling Environments" on page 907. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 43.
10.2.2.2.3
Creating a User Profile Environment Based Traffic Map Atoll enables you to create a user profile environment based traffic map based on by drawing it in the map window. To draw a traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Profile Traffic Map. 5. Select User Profile Environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 10.37).
Draw Map Delete Map Figure 10.37: 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.
910
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
10.2.2.2.4
Displaying Statistics on a User Profile Environment Based Traffic Map You can display the statistics of a user profile environment based traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment based traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the user profile environment based traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears. The Statistics window lists the surface (Si in km²) and the percentage of surface (% of i) for each environment class "i" S
i - × 100 within the focus zone. The percentage of surface is given by: % of i = -------------
Sk k
You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.
10.2.2.3 Creating User Density Traffic Maps (No. Users/km2) User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit surface, i.e., the density of users, as input. This can be either the density of users per activity status or the density of users including all activity statuses. In this section, the following ways of creating a user density traffic map are explained: • •
"Importing a User Density Traffic Map" on page 911 "Creating a User Density Traffic Map" on page 912.
User density traffic maps can be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. For more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 913.
10.2.2.3.1
Importing a User Density Traffic Map The user density traffic map defines the density of users per pixel. For a traffic density of X users per km², Atoll will distribute x users per pixel during the simulations, where "x" depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined on the Traffic tab of the traffic map’s properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. Because each of the CDMA technologies has capabilities and services that are specific to it, it is recommended to create a separate traffic map per user density for: • • •
voice 1xRTT data EV-DO data
To create a user density traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (No. Users/km2). 5. Select the type of traffic information you are importing: • •
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.
911
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
• • •
© Forsk 2012
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. 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 map’s 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 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 Maps folder.
10.2.2.3.2
Creating a User Density Traffic Map Atollenables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User Density Traffic Map (Number of users per km2). 5. Select the type of traffic information: • • • • •
All Activity Statuses: Select All Activity Statuses if the map you are importing provides a density of users with any activity status. Active in Uplink: Select Active in Uplink if the map you are importing provides a density of users active in the uplink only. Active in Downlink: Select Active in Downlink if the map you are importing provides a density of users active in the downlink only. Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.
6. Click the Create button. The traffic map’s 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.
912
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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 Maps 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 Editor toolbar to draw contours. For more information on editing contours, see "Editing Polygons, Lines, and Points" on page 61. Atoll creates an item called Density values in the User Density Map folder. 16. Right-click Density values 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. When you have finished creating the user density traffic map, right-click the map. The context menu appears. 20. Select Edit from the context menu again to end editing.
10.2.2.3.3
Creating User Density Traffic Maps from Sector Traffic Maps You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. To create user density traffic maps from a sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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 there are 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.
10.2.2.4 Converting 2G Network Traffic Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km² for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as user density traffic maps into your CDMA document. These maps can then be used in traffic simulations like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 913, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 911. To import a 2G traffic map into a CDMA document: 1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 438. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 913. 3. Import the traffic exported in step 2 to your CDMA document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 911.
10.2.2.5 Exporting Cumulated Traffic Atollallows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user densities. The cumulated traffic is exported in 32-bit BIL, ArcView© Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. 4. Enter a file name and select the file format.
913
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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. 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 voice traffic, or select "Packet 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, independently of their 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.
10.2.3 Exporting a Traffic Map To export a traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save. If you are exporting a raster traffic map, you have to define: •
The Export Region: • • •
•
Entire Project Area: Saves the entire traffic map. Only Pending Changes: Saves only the modifications made to the map. Computation Zone: Saves only the part of the traffic map inside the computation zone.
An export Resolution.
10.2.4 Calculating and Displaying Traffic Simulations Once you have modelled the network services and users and have created traffic maps, you can create simulations. The simulation process consists of two steps: 1. Obtaining a realistic user distribution: Atoll generates a user distribution using a Monte-Carlo algorithm; this user distribution is based on the traffic database and traffic maps and is weighted by a Poisson distribution between simulations of a same group. Each user is assigned a service, a mobility type, and an activity status by random trial, according to a probability law that uses the traffic database. The user activity status is an important output of the random trial and has direct consequences on the next step of the simulation and on network interference. A user can be either active or inactive. Both active and inactive users consume radio resources and create interference.
914
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Additionally, each 1xEV-DO Rev. 0 user is assigned a transition flag ("True" or "False") for each possible rate transition (from 9.6 to 19.2 kbps, 19.2 to 38.4 kbps, 38.4 to 76.8 kbps, and 76.8 to 153.6 kbps for rate upgrading and from 153.6 to 76.8 kbps, 76.8 to 38.4 kbps, 38.4 to 19.2 kbps, and 19.2 to 9.6 kbps for rate downgrading). These transition flags are based on the rate downgrading and upgrading probabilities. If a transition flag is "True," the user rate can be downgraded or upgraded if necessary. Then, Atoll randomly assigns a shadowing error to each user using the probability distribution that describes the shadowing effect. Finally, another random trial determines user positions in their respective traffic zone (possibly according to the clutter weighting and the indoor ratio per clutter class). 2. Modelling network power control: Atoll uses a power control algorithm for CDMA2000 1xRTT users, and performs the forward link power control on the FCH and SCH and the reverse link power control on either the pilot channel or on the FCH and SCH for 1xRTT users. For users of 1xEV-DO, Atoll performs the reverse link power control on the pilot channel. On the forward link, Atoll performs rate control based on the C⁄I ratio calculated for the mobile. The power control simulation algorithm is described in "The Power Control Simulation Algorithm" on page 915.
10.2.4.1 The Power Control Simulation Algorithm The power control algorithm simulates the way a CDMA network regulates itself by using forward link and reverse link power controls or, for CDMA2000 1xEV-DO, rate control in the forward link and power control in the reverse link in order to minimise interference and maximise capacity. Atoll simulates the network regulation mechanisms for each user distribution. During each iteration of the algorithm, all the mobiles (voice, 1xRTT data, and EV-DO data service users) selected during the user distribution generation attempt to connect one by one to network transmitters. The process is repeated until the network is balanced, i.e., until the convergence criteria (on the forward and the reverse link) are satisfied. The CDMA2000 1xRTT Power Control Simulation Algorithm The CDMA2000 1xRTT power control simulation algorithm (see Figure 10.38) simulates the power control, congestion, and radio resource control performed for CDMA2000 1xRTT users. Atoll considers each user in the order established during the generation of the user distribution, determines his best server and his active set. Atoll performs the forward link power control on the FCH and SCH and the reverse link power control on either the pilot channel or on the FCH and SCH, depending on the option selected under UL 1xRTT Power Control Based On on the Global Parameters tab of the Network Settings Properties dialogue (see "The Options of the Network Settings Properties Dialogue" on page 967). 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 10.38: Power control simulation for CDMA2000 1xRTT
915
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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 "Ec⁄I0 < (Ec⁄I0)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 network is saturated: • • • •
The maximum reverse link load factor is exceeded (at admission or during congestion control): the status is either "Admission Rejection" or "UL Load Saturation." There are not enough available channel elements on the site: the status is "Ch. Elts Saturation." There is not enough power for cells: the status is "DL Load Saturation." There are no more Walsh codes available: the status is "Walsh Code Saturation."
The CDMA2000 1xEV-DO Rate and Power Control Simulation Algorithm The CDMA2000 1xEV-DO simulation algorithm (see Figure 10.39) simulates the power and rate controls, congestion, and radio resource control performed for CDMA2000 1xEV-DO users (i.e. 1xEV-DO Rev.0, 1xEV-DO Rev.A and 1xEV-DO Rev.B service users). Atoll considers the guaranteed bit rate service users first, in the order established during the generation of the user distribution, and then, it processes the variable bit rate service users, in the order established during the generation of the user distribution. It determines the best server and the active set of each user, and performs the reverse link power control on the pilot channel. On the forward link, there is no power control; the transmitter transmits at full power. Instead, Atoll performs rate control based on the C⁄I ratio calculated for the mobile. 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. Guaranteed bit rate service users have the highest priority and are processed first, in the order established during the generation of the user distribution. Atoll determines the 1xEV-DO bearer for each user in the forward link and in the reverse link. The selected 1xEV-DO bearer must provide a RLC peak rate higher than the guaranteed bit rate defined for the service. To achieve the highest cell capacity, 1xEV-DO Rev. A has a multi-user packet that combines packets from several users into a single physical-layer packet. Atoll models the multi-user packet by allowing several guaranteed bit rate service users to share the same 1xEV-DO radio bearer. Then, Atoll calculates the 1xEV-DO 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 MAC indexes, and the number of channel elements). Atoll checks if enough MAC indexes and channel elements are available for the user (taking into account the maximum number of MAC indexes defined for the cell and the maximum number of channel elements allowed on the site in the downlink). If not enough indexes or channel elements are available, the user is rejected. A multi-carrier EV-DO user is managed as several single-carrier users. The user has several allocated 1xEV-DO radio bearers and consumes resources in each cell he is connected to. In the reverse link, load balancing between carriers is modelled. The user can simultaneously transmit on all carriers. Atoll shares the available terminal power equally between each carrier and determines the uplink 1xEV-DO radio bearer obtained on each carrier, without exceeding the available resources (channel elements, MAC index, and UL load factor). Atoll selects the best configuration among all combinations of carriers, i.e., the combination which provides the highest total throughput. If, with the selected configuration, the total throughput exceeds the original throughput demand, Atoll adjusts the 1xEV-DO radio bearers on each carrier until the user obtains the requested throughput. In the forward link, Atoll performs rate control on each carrier. Atoll calculates the C/I ratio received by the mobile on each carrier and determines the downlink 1xEV-DO radio bearer obtained on each carrier. The user downlink throughput corresponds to the sum of the throughputs obtained on each carrier.
916
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Figure 10.39: Power control simulation for CDMA2000 1xEV-DO During reverse link power control, if the service supports downgrading, Atoll might downgrade the rate of 1xEV-DO Rev. 0 service users 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 met, the mobile is rejected. During congestion control, if the service supports downgrading, Atoll might adjust the rate of 1xEV-DO Rev. 0 service users on the reverse link traffic data channel 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. If the noise rise is too high, Atoll downgrades all 1xEV-DO Rev. 0 users that can be downgraded. When the noise rise is too low, it upgrades all 1xEV-DO Rev. 0 users that can be upgraded. 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. 1xEV-DO Rev. A and Rev. B service users are not downgraded. They are rejected when the cell noise rise threshold is exceeded. 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 "Ec⁄I0 pilot < Ec⁄I0 min. pilot". On the reverse link, there is not enough power to transmit: the status is "Pmob > Pmob max".
•
The obtained downlink bit rate is lower than the downlink guaranteed bit rate: the status is "Obtained DL bit rate < Guaranteed DL bit rate". This rejection cause applies to guaranteed bit rate service users only.
•
The network is saturated: • • •
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".
10.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. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name and Comments for this simulation or group of simulations.
917
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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 in the Network explorer. 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 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. 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 (
) beside the box and 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 904.
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.
918
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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. 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 Planning toolbar.
All simulations created at the same time are grouped together in a folder in the Network explorer. You can now use the completed simulations for specific CDMA coverage predictions (see "Making Coverage Predictions Using Simulation Results" on page 932) or for an AS analysis using the Point Analysis window (see "Making an AS Analysis of Simulation Results" on page 932).
10.2.4.3 Displaying the Traffic Distribution on the Map Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to service, activity status, or soft handoff gain. You can set the display of the traffic distribution according to discrete values and then select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 43. In this section are the following examples of traffic distribution display: • • •
"Displaying the Traffic Distribution by Handoff Status" on page 919 "Displaying the Traffic Distribution by Connection Status" on page 920 "Displaying the Traffic Distribution by Service" on page 920. 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 Windows" on page 38.
10.2.4.3.1
Displaying the Traffic Distribution by Handoff Status In this example, the traffic distribution is displayed by the handoff status. To display the traffic distribution by the handoff status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "HO Status (Sites/No. Transmitters Act. Set)" as the Field. The handoff status is displayed as "X⁄Y" where "Y" is the number of transmitters to which the mobile is connected and "X" is the number of sites. For example, "1⁄2" means that the mobile is connected to two different transmitters on one site. "2⁄3" would mean that the mobile is connected to three different transmitters on two sites. If a mobile is not connected, the handoff status is given as "0⁄0". 5. Click OK. The traffic distribution is now displayed by handoff status (see Figure 10.40).
919
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Figure 10.40: Displaying the traffic distribution by handoff status
10.2.4.3.2
Displaying the Traffic Distribution by Connection Status In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Connection Status" as the Field. 5. Click OK. The traffic distribution is now displayed by connection status (see Figure 10.41).
Figure 10.41: Displaying the traffic distribution by connection status
10.2.4.3.3
Displaying the Traffic Distribution by Service In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 10.42).
920
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Figure 10.42: Displaying the traffic distribution by service
10.2.4.4 Displaying the User Active Set on the Map Atoll enables you to display on the map the active set for each user generated by a simulation. To display the active set for a user: •
On the map, click and hold the icon of the user whose best and second-best servers you want to display. The servers in the user’s active set are connected to the user with lines the same colour as the serving transmitter. The best server is indicated with the number "1", the second-best with number "2" and so on. Figure 10.43 shows a user with three servers in his active set.
Figure 10.43: The active set of a user
10.2.4.5 Displaying the Results of a Single Simulation After you have created a simulation, as explained in "Creating Simulations" on page 917, you can display the results. To access the results of a single simulation: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. 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 917.
921
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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.
Results: Under Results, you will find data on the connection results: • • •
•
The number of iterations that were run in order to converge. The number and the percentage of rejected users is given along with the reason for rejection. These figures 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 dualband 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.
The Sites tab: The Sites tab contains the following information per site: • • • • • • • • • • • • • •
Max No. of DL and UL CEs per Carrier: The maximum number of channel elements available per 1xRTT carrier on the forward and reverse links. Max No. of EV-DO CEs per Carrier: The maximum number of channel elements available per 1xEV-DO carrier. No. of DL and UL FCH CEs: The number of channel elements used by the FCH on the forward and reverse links by the site. No. of DL and UL SCH CEs: The number of channel elements used by the SCH on the forward and reverse links by the site. No. EV-DO CEs: The number of channel elements used by EV-DO users. No. of DL and UL FCH CEs Due to SHO Overhead: The number of extra channel elements due to soft handoff, on reverse link and forward link for CDMA2000 1xRTT users. No. of DL and UL SCH CEs Due to SHO Overhead: The number of extra channel elements due to soft handoff, on reverse link and forward link for CDMA2000 1xRTT users. No. of EV-DO CEs Due to SHO Overhead: The number of extra channel elements due to soft handoff, on reverse link and forward link for CDMA2000 1xEV-DO users. Carrier Selection: The carrier selection method defined on the site equipment. AS Restricted to Neighbours: Whether the active set is restricted to neighbours of the reference cell. This option is selected on the site equipment. Rake Factor: The rake factor, defined on the site equipment, enables Atoll to model a rake receiver on the reverse link. MUD Factor: The multi-user detection factor, defined on the site equipment, is used to decrease intra-cell interference on the reverse link. FCH throughput per service (Uplink and Downlink) (kbps): The throughput in kbits⁄s for speech service and each 1xRTT data service on the FCH. The result is detailed on the forward and reverse link only when relevant. SCH throughput per service (Uplink and Downlink) (kbps): The throughput in kbits⁄s for each 1xRTT data service on the SCH. The result is detailed on the forward and reverse link only when relevant.
The Cells (1xRTT) tab: The Cells (1xRTT) tab contains the following information, per site, transmitter, and 1xRTT carrier: • • • • • • • • • • • • •
922
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. Noise Figure (dB): The noise figure as defined in the transmitter properties Total Transmitted DL Power (dBm): The total transmitted power on the forward link. Total Transmitted DL FCH Power (dBm): The total power used on the forward link for the FCH. Total Transmitted DL SCH Power (dBm): The total power used on the forward link for the SCH. UL Total Noise (dBm): The total noise on the reverse link. UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total interference on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been selected, the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor on the reverse link (defined either in the cell properties, or in the simulation creation dialogue).
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
• •
•
• • • • • • • •
• • • • • • • •
•
DL Load Factor (%): The load factor of the cell i on the forward link corresponds to the ratio (average interference on the forward link [due to transmitter signals on the same carrier] for terminals in the transmitter i area) ⁄ (average total noise on the forward link [due to transmitter signals and to thermal noise of terminals] for terminals in the transmitter i area). DL Noise Rise (dB): The noise rise on the forward link is calculated from the load factor on the forward link. These data indicate signal degradation due to cell load (interference margin in the link budget). DL Load (% Pmax): The percentage of power used is determined by the total transmitted power-maximum power ratio (power stated in W). When the constraint "DL load" is set, the DL Load can not exceed the user-defined Max DL Load (defined either in the cell properties, or in the simulation). Number of UL and DL Radio Links: The number of radio links corresponds to the number of user-transmitter links on the same carrier. This data is calculated on the forward and reverse links and indicates the number of users connected to the cell on the forward and reverse links. Because of handover, a single user can use several radio links. Connection Success Rate (%): The connection success rate gives the ratio of connected users over the total number of users in the cell. UL Noise Rise (dB): The noise rise on the reverse link is calculated from the load factor on the reverse link. These data indicate signal degradation due to cell load (interference margin in the link budget). UL Reuse Factor: The reverse link reuse factor is the ratio between the reverse link total interference and the intracell interference. UL Reuse Efficiency Factor: The reuse efficiency factor on the reverse link is the reciprocal of the reuse factor on the reverse link. No. of Codes (128 bits): The total number of 128-bit Walsh codes used by cell. No. of FCH Codes (128 bits): The total number of 128-bit Walsh codes used by the FCH of the cell. No. of SCH Codes (128 bits): The total number of 128-bit Walsh codes used by the SCH of the cell. The Types of Handoff as a Percentage: Atoll estimates the percentages of handoff types for each transmitter. Atoll only lists the results for the following handoff status, no handoff (1⁄1), softer (1⁄2), soft (2⁄2), softer-soft (2⁄3) and soft-soft (3⁄3) handoffs; the other handoff status (other HO) are grouped. No. of DL and UL FCH CEs: The number of channel elements used by the FCH on the forward and reverse links. No. of DL and UL SCH CEs: The number of channel elements used by the SCH on the forward and reverse links. FCH Throughput (Uplink and Downlink) (kbps): The throughput of the FCH on the forward and reverse links. SCH Throughput (Uplink and Downlink) (kbps): The throughput of the SCH on the forward and reverse links. Min TCH Pwr (dBm): The minimum power allocated to a traffic channel for supplying services. Max TCH Pwr (dBm): The maximum power allocated to a traffic channel for supplying services. Avg TCH Pwr (dBm): The average power allocated to a traffic channel for supplying services. Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob > PmobMax, Ptch > PtchMax, Ec⁄Io < (Ec⁄Io)min, UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Walsh Code Saturation, and Admission Rejection. Connection Success Rate (%) for Each Service: For each service, the connection success rate gives the ratio of connected users over the total number of users of that service in the cell.
The Cells (1xEV-DO) tab: The Cells (1xEV-DO) tab contains the following information, per site, transmitter, and 1xEV-DO carrier: • • • • • • • •
• • • • • • •
Max Power (dBm): The maximum power as defined in the cell properties. Idle Power Gain (dB): The idle power gain as defined in the cell properties. Gain (dBi): The gain as defined in the antenna properties for that transmitter. Reception Loss (dB): The reception loss as defined in the transmitter properties. Transmission Loss (dB): The transmission loss as defined in the transmitter properties. Noise Figure (dB): The noise figure as defined in the transmitter properties. UL Total Noise (dBm): The total noise received by the cell on the reverse link. UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total interference on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been selected, 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 intracell interference. UL Reuse Efficiency Factor: The reuse efficiency factor on the reverse link is the reciprocal of the reuse factor on the reverse link. Number of UL Radio Links: The number of radio links on the reverse link. Multi-carrier users are counted once in each cell they are connected to. No. of Active Users: The number of active users connected to the cell. Multi-carrier users are counted once in each cell they are connected to. No. of Inactive Users: The number of inactive users among the users connected to the cell. Multi-carrier users are counted once in each cell they are connected to. Connection Success Rate (%): The percentage of connections that are successfully made.
923
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
•
• • •
•
© Forsk 2012
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 (1⁄1), softer (1⁄2), soft (2⁄2), softer-soft (2⁄3) and soft-soft (3⁄3) 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, Ec⁄Io < (Ec⁄Io)min, UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Walsh Code Saturation, Admission Rejection, and 1xEV-DO Resources Saturation. Connection Success Rate (%) For Each Service: For each service, the connection success rate gives the percentage of connected users from the total number of users of that service in the cell.
The Mobiles (1xRTT) tab: The Mobiles (1xRTT) tab contains the following information for CDMA2000 1xRTT users: The Mobiles (1xRTT) tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 917, you select either "Standard information about mobiles" or "Detailed information about mobiles" under Information to Retain. • • • • • • • •
• • • • • • •
• • • • •
X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second random trial). Service: The service assigned during the first random trial during the generation of the user distribution. Terminal: The assigned radio configuration. User Profile: The assigned user profile. Mobility: The mobility type assigned during the first random trial during the generation of the user distribution. Activity Status: The activity status assigned during the first random trial during the generation of the user distribution. DL and UL 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. 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): Ec⁄I0 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 917, you select "Detailed Information About Mobiles" under Information to retain: •
• • • •
• •
924
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.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
Iintra AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The intra-cell interference on the forward link for each cell (I) of the active set. DL
DL
I Intra ( ic ) = ( 1 – F Ortho ) × P tot ( ic ) txi
•
Iextra AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The extra-cell interference on the forward link for each cell (I) of the active set. DL
I extra ( ic ) =
DL
P tot ( ic )
txj, j ≠ i
• • • • • •
•
Total Loss AS1, AS2, AS3, AS4, AS5, AS6 (dB): The total attenuation for each link between the mobile and a transmitter in the active set. Name: The name of the mobile, as assigned during the random user generation. Clutter: The clutter class on which the mobile is located. Orthogonality Factor: The orthogonality factor used in the simulation. The orthogonality factor is the remaining orthogonality of the Walsh codes at reception. The value used is the orthogonality factor set in the clutter classes. % Pilot Finger: The percentage pilot finger used in the simulation, defined per clutter class or globally for all clutter classes. DL and UL FCH SHO Gain (dB): The soft handoff gain for the FCH on the forward and the reverse link. The soft handoff gain on the forward link is calculated if mobile receivers are connected either on the forward link or on the forward link and the reverse link. DL and UL SCH SHO Gain (dB): The soft handoff gain for the SCH on the forward and the reverse link. The soft handoff gain on the forward link is calculated if mobile receivers are connected either on the forward link or on the forward link and the reverse link.
The Mobiles (1xEV-DO) tab: The Mobiles (1xEV-DO) tab contains the following information for CDMA2000 1xEV-DO users: The Mobiles (1xEV-DO) tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 917, 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 Status: 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): For a 1xEV-DO Rev. 0 service user, 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 uplink throughput is calculated using the downgrading factor. If the user was rejected, the total obtained rate is "0". The uplink total rate obtained by the 1xEV-DO Rev. A and Rev. B service users depends on the service QoS class (i.e., whether this is a guaranteed bit rate or a variable bit rate service). For a guaranteed bit rate service user, when the user is connected, the uplink total obtained rate equals the guaranteed bit rate defined for the service. For variable bit rate service users, the uplink total obtained rate is the same as the total requested rate. If the user is rejected, the uplink total obtained rate is rate is "0".
• •
• • •
• •
DL Max Data Rate: The maximum data rate on the forward link depends on the value of C⁄I at the terminal. Atoll calculates this value from the Max rate=f(C⁄I) graph specified in the mobility type properties. Carrier: The carrier used for the mobile-transmitter connection. Multi-carrier users are connected to several carriers. Details can be displayed per carrier by clicking the Actions button and then selecting Detailed Display from the menu. Frequency Band: The frequency band used for the mobile-transmitter connection. Mobile Total Power (dBm): The mobile total power corresponds to the total power transmitted by the terminal. For constant bit rate service users, the percentage of bearer consumption is taken into account. Connection Status: The connection status indicates whether the user is connected or rejected at the end of the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection cause is given. Best Server: The best server among the transmitters in the mobile active set. HO Status (Sites/No. Transmitters Act. Set): The HO status is the number of sites compared to the number of transmitters in the active set.
925
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
• • • •
© Forsk 2012
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): Ec⁄I0 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. DL C/I: The C⁄I for the pilot on the forward link. Indoor: This field indicates whether indoor losses have been added or not.
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on page 917, you select "Detailed information about mobiles" under Information to Retain: • • •
UL Throughput due to TCP (kbps): The uplink data rate due to TCP aknowledgements. 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): For a 1xEV-DO Rev. 0 service user, 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, it is calculated using the downgrading factor. If the user was rejected, the obtained data peak rate is zero. The uplink data peak rate obtained by the 1xEV-DO Rev. A and Rev. B service users depends on the service QoS class (i.e., whether this is a guaranteed bit rate or a variable bit rate service). For a guaranteed bit rate service user, when the user is connected, the uplink obtained data peak rate equals the guaranteed bit rate defined for the service. For variable bit rate service users, the uplink obtained data peak rate is the same as the uplink requested data peak rate. If the user is rejected, the uplink obtained data peak rate is "0".
• • • • • • • • • • •
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 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. 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 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: • • • •
926
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
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
• • •
The input parameters specified when creating the simulation: • • • • • •
•
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.
10.2.4.6 Displaying the Average Results of a Group of Simulations After you have created a group of simulations, as explained in "Creating Simulations" on page 917, you can display the average results of the group. If you want to display the results of a single simulation of a group, see "Displaying the Results of a Single Simulation" on page 921. To access the averaged results of a group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the SimulationsSimulations folder. 3. Right-click the group of simulations whose results you want to access. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation. The Statistics tab: The Statistics tab contains the following two sections: •
Request: Under Request, you will find data on the connection requests: • •
• •
Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; power control has not yet started. The result depends on the traffic description and traffic input. During the first random trial, each user is assigned a service and an activity status. The number of users per activity status and the reverse link and forward link rates that all users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and reverse link and forward link rates) is given.
Results: Under Results, you will find data on the connection results: • • •
•
The number of iterations that were run in order to converge. The number and the percentage of rejected users is given along with the reason for rejection. These figures 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 dualband 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.
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 intracell interference. UL Reuse Efficiency Factor: The reverse link reuse efficiency factor is the reciprocal of the reverse link reuse factor. DL Load Factor (%): The forward link load factor of the cell i corresponds to the ratio (forward link average interference [due to transmitter signals on the same carrier] for terminals in the transmitter i area) ⁄ (forward link
927
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
• • •
•
• • •
• • • • • •
•
© Forsk 2012
average total noise [due to transmitter signals and to thermal noise of terminals] for terminals in the transmitter i area). DL Noise Rise (dB): The forward link noise rise is calculated from the forward link load factor. These data indicate signal degradation due to cell load (interference margin in the link budget). Total Transmitted DL Power (dBm): The total power transmitted on the forward link. DL Load (% Pmax): The percentage of power used is determined by the total transmitted power-maximum power ratio (power stated in W). When the constraint "DL load" is set, the DL Load can not exceed the user-defined Max DL Load (defined either in the cell properties, or in the simulation). Number of UL and DL Radio Links: The number of radio links corresponds to the number of user-transmitter links on the same carrier. This data is calculated on the forward and reverse links and indicates the number of users connected to the cell on the forward and reverse links. Because of handover, a single user can use several radio links. Connection Success Rate (%): The connection success rate gives the ratio of connected users over the total number of users in the cell. No. of Codes (128 bits): The average number of 128-bit Walsh codes used per cell. The types of handoff as a percentage: Atoll estimates the percentages of handoff types for each transmitter. Atoll only lists the results for the following handoff status, no handoff (1⁄1), softer (1⁄2), soft (2⁄2), softer-soft (2⁄3) and soft-soft (3⁄3) handoffs; the other handoff status (other HO) are grouped. FCH Throughput (Uplink and Downlink) (kbps): The throughput of the FCH on the forward and reverse links. SCH Throughput (Uplink and Downlink) (kbps): The throughput of the SCH on the forward and reverse links. Min TCH Pwr (dBm): The minimum power allocated to a traffic channel for supplying services. Max TCH Pwr (dBm): The maximum power allocated to a traffic channel for supplying services. Avg TCH Pwr (dBm): The average power allocated to a traffic channel for supplying services. Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob > PmobMax, Ptch > PtchMax, Ec⁄Io < (Ec⁄Io)min, UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Walsh Code Saturation, and Admission Rejection. Connection Success Rate (%) for Each Service: For each service, the connection success rate gives the ratio of connected users over the total number of users of that service in the cell.
The Cells (Average - 1xEV-DO) and Cells (Standard Deviation - 1xEV-DO) tabs: The Cells (Average - 1xEV-DO) and Cells (Standard Deviation - 1xEV-DO) tabs contain the following average and standard deviation information, respectively, per site, transmitter, and 1xEV-DO carrier: •
•
• • • • • •
• • •
•
UL Total Noise (dBm): The total noise on the reverse link takes into account the total signal received at the transmitter on a carrier from intra and extra-cell terminals using the same carrier and adjacent carriers (total interference on the reverse link) and the thermal noise. UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total interference on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been selected, the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor on the reverse link (defined either in the cell properties, or in the simulation creation 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 intracell interference. UL Reuse Efficiency Factor: The reverse link reuse efficiency factor is the reciprocal of the reverse link reuse factor. Number of UL Radio Links: The number of radio links on the reverse link. Connection Success Rate (%): The percentage of connections that are successfully made. The types of handoff as a percentage: Atoll estimates the percentages of handoff types for each transmitter. Atoll only lists the results for the following handoff status, no handoff (1⁄1), softer (1⁄2), soft (2⁄2), softer-soft (2⁄3) and soft-soft (3⁄3) 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, Ec⁄Io < (Ec⁄Io)min, UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Walsh Code Saturation, Admission Rejection, and 1xEV-DO Resources Saturation. Connection Success Rate (%) for Each Service: For each service, the connection success rate gives the ratio of connected users over the total number of users of that service in the cell.
The Initial Conditions tab: The Initial Conditions tab contains the following information: •
The global transmitter parameters: • • • • • •
928
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.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
The input parameters specified when creating the group of simulations: • • • • • •
•
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.
10.2.4.7 Updating Cell Values With Simulation Results After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 917, you can update values for each cell with the results calculated during the simulation. The following values are updated: • •
UL Load Factor Total DL Power
To update cell values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Select the Network explorer. b. Click the Expand button ( ) to expand the 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. Select the Network explorer. b. Click the Expand button ( ) to expand the Simulations folder. c. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. 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.
10.2.4.8 Adding New Simulations to an Atoll Document When you have created a simulation or group of simulations, you can re-examine the same conditions by adding new simulations to the Atoll document. In Atoll, there are the following ways of adding new simulations: •
Adding to a group: When you add one or more simulations to an existing group of simulations, Atoll reuses the same input (radio, traffic, and simulation parameters) as those used to generate the group of simulations. It then generates a new user distribution and performs the power control simulation. To add a simulation to a group of simulations, see "Adding a Simulation to a Group of Simulations" on page 930.
•
Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution (users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shadowing error distribution between simulations is different. Traffic parameter changes (such as maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) can be taken into account. Radio data modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during the power control (or rate/power control) simulation. To replay a group of simulations, see "Replaying a Group of Simulations" on page 930.
•
Using the Generator Initialisation Number: When you create groups of simulations using the same generator initialisation number (which must be an integer other than 0) Atoll generates the same user and shadowing error distributions (user with a service, a mobility, an activity status and a shadowing error) in all groups using the same number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers allowed, Eb⁄Nt thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during the power control simulation.
929
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
By creating and calculating one group of simulations, making a change to the network and then creating and calculating a new group of simulations using the same generator initialisation number, you can see the difference your parameter changes make. To create a new simulation to a group of simulations using the generator initialisation number, see "Adding a Simulation to a Group of Simulations" on page 930. •
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 931.
Adding a Simulation to a Group of Simulations To add a simulation to an existing group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Right-click the group of simulations to which you want to add a simulation. The context menu appears. 4. Select New from the context menu. The properties dialogue of the group of simulations appears. When adding a simulation to an existing group of simulations, the parameters originally used to calculate the group of simulations are used for the new simulations. Consequently, few parameters can be changed for the added simulation. 5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations. 6. Under Execution on the General tab, you can set the following parameters: •
Number of Simulations: Enter the number of simulations to added to this group of simulations.
7. 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 Planning toolbar.
Replaying a Group of Simulations To replay an existing group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Right-click the group of simulations you want to replay. The context menu appears. 4. Select Replay from the context menu. The properties dialogue of the group of simulations appears. When replaying an existing group of simulations, most parameters used to calculate the group of simulations are reused for the replayed group. Consequently, few parameters can be changed for the replayed group. 5. On the General tab of the dialogue, you can set the following parameters: • •
Select the level of detail that will be available in the output from the Information to retain list as explained in "Creating Simulations" on page 917. 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. On the Source Traffic tab of the dialogue, select the Refresh Traffic Parameters check box if you want to take into account traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) in the replayed simulation. 7. On the Advanced tab, you can set the following parameters: • • •
930
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.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
8. Click Run. Atoll immediately begins the simulation. Creating a New Group of Simulations Using the Generator Initialisation Number To create a new group of simulations using the generator initialisation number: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new group of simulations appears. 4. Click the Advanced tab. 5. Under Generator Initialisation, enter an integer as the generator initialisation value. The integer must be the same generator initialisation number as used in the group of simulations with the user and shadowing error distributions you want to use in this group of simulations. If you enter "0", the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value. 6. For information on setting other parameters, see "Creating Simulations" on page 917. 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 931. Duplicating a Group of Simulations To duplicate an existing group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Right-click the group of simulations you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The properties dialogue for the duplicated group of simulations appears. You can change the parameters for the duplicated simulation or group of simulations as explained in "Creating Simulations" on page 917.
10.2.4.9 Estimating a Traffic Increase When you create a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increased traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a group of simulations by: • •
Creating a new group of simulations as described in "Creating Simulations" on page 917. Duplicating an existing group of simulations as described in "Adding New Simulations to an Atoll Document" on page 929.
2. Click the Source Traffic tab of the properties dialogue. 3. Enter a Global Scaling Factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps).
10.2.5 Analysing the Results of a Simulation In Atoll, you have several methods available to help you analyse simulation results. You can make an active set analysis of a real-time probe user or you can make a coverage prediction where each pixel is considered as a probe user with a defined terminal, mobility, and service. The analyses are based on a single simulation or on an averaged group of simulations. You can find information on the analysis methods in the following sections: • •
"Making an AS Analysis of Simulation Results" on page 932 "Making Coverage Predictions Using Simulation Results" on page 932.
931
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
10.2.5.1 Making an AS Analysis of Simulation Results The Point Analysis window gives you information on reception for any point on the map. The AS Analysis view gives you information on the pilot quality (Ec⁄I0) (which is the main parameter used to define the mobile active set), the connection status, and the active set of the probe mobile. Analysis is based on the reverse link load factor and the forward link total power of cells. In this case, these parameters can be either outputs of a given simulation, or average values calculated from a group of simulations. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility and a service. For information on the criteria for belonging to the active set, see "Conditions for Entering the Active Set" on page 972. Before you make an AS analysis: • •
Ensure the simulation or group of simulations you want to use in the AS analysis is displayed on the map. Replay the simulation or group of simulations you want to use if you have modified radio parameters since you made the simulation. The AS analysis does not take possible network saturation into account. Therefore, there is no guarantee that a simulated mobile with the same receiver characteristics can verify the point analysis, simply because the simulated network can be saturated.
To make an AS analysis of simulation results: 1. Click the Point Analysis button (
) on the toolbar. The Point Analysis window appears (see Figure 10.13).
2. Select the AS Analysis view at the top of the Point Analysis window. 3. At the top of the AS Analysis view, select the simulation or group of simulations you want to base the AS analysis on from the Load Conditions list. 4. Select the Terminal, Service, Mobility, Carrier, and DL and UL Rates. 5. Click the Options button (
) to display the Calculation Options dialogue.
6. Select or clear the following options: • •
Whether shadowing is to be taken into account (and, if so, the cell edge coverage probability). Whether indoor coverage is to be taken into account.
7. Click OK to close the Calculation Options dialogue. 8. Move the pointer over the map to make an active set analysis for the current location of the pointer. As you move the pointer, Atoll indicates on the map which is the best server for the current position (see Figure 10.31 on page 881). Information on the current position is given in the AS Analysis view of the Point Analysis window. See Figure 10.32 on page 881 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.
10.2.5.2 Making Coverage Predictions Using Simulation Results When no simulations are available, Atoll uses the reverse link load factor, the total forward link power defined for each cell to make coverage predictions. For information on cell properties, see "Creating or Modifying a Cell" on page 819; for information on modifying cell properties, see "Cell Definition" on page 816. Once you have made simulations, Atoll can use this information instead of the defined parameters in the cell properties to make coverage predictions where each pixel is considered as a probe user with a terminal, mobility, profile, and service. For each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a group of simulations, choosing either an average analysis of all simulations in the group or a statistical analysis based on a defined probability. The coverage predictions that can use simulation results are: •
Coverage predictions on the pilot or on a service: • •
932
Pilot Quality Analysis: For information on making a Pilot Quality Analysis, see "Making a Pilot Signal Quality Prediction" on page 870. Service Area Analysis (Eb/Nt) (DL): For information on making a coverage prediction on the forward link service area, see "Studying Service Area (Eb⁄Nt) Uplink and Downlink for 1xRTT" on page 871 or "Studying the Forward Link EV-DO Throughput" on page 872.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
• •
Coverage predictions on noise and interference: • •
•
Service Area Analysis (Eb/Nt) (UL): For information on making a coverage prediction on the reverse link service area, see "Studying Service Area (Eb⁄Nt) Uplink and Downlink for 1xRTT" on page 871 or "Studying Service Area (Eb⁄Nt) Reverse Link for EV-DO" on page 873. Effective Service Area Analysis (Eb/Nt) (DL+UL): For information on making a pilot pollution coverage analysis, see "Studying Effective Service Area" on page 874. Coverage by Total Noise Level (DL): For information on making a forward link total noise coverage prediction, see "Studying Forward Link Total Noise" on page 876. Pilot Pollution Analysis: For information on making a pilot pollution coverage analysis, see "Calculating Pilot Pollution" on page 877.
A handoff status coverage prediction to analyse macro-diversity performance: •
Handoff Zones: For information on making a handoff status coverage prediction, see "Making a Handoff Status Coverage Prediction" on page 879.
The procedures for the coverage predictions assume that simulation results are not available. When no simulations are available, you select "(Cells Table)" from the Load Conditions list, on the Conditions tab. However, when simulations are available you can base the coverage prediction on one simulation or a group of simulations. To base a coverage prediction on a simulation or group of simulations, when setting the parameters: 1. Click the Conditions tab. 2. From the Load Conditions list, select the simulation or group of simulations on which you want to base the coverage prediction. 3. If you select a group of simulations from the Load Conditions list, select one of the following: •
•
All: Select All to make a statistical analysis of all simulations based on the defined Probability (the probability must be from 0 to 1). This will make a global analysis of all simulations in a group and with an evaluation of the network stability in terms of fluctuations in traffic. Average: Select Average make the coverage prediction on the average of the simulations in the group.
10.3 Optimising Network Parameters Using the ACP Atoll Automatic Cell Planning (ACP) enables radio engineers designing UMTS networks to automatically calculate the optimal network settings in terms of network coverage and quality. The ACP can also be used to add sites from a list of candidate sites or to remove unnecessary sites or sectors. Atoll ACP can also be used in co-planning projects where networks using different radio access technologies must be taken into consideration when calculating the optimal network settings. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and cell pilot power. ACP can also be used during the initial planning stage of a UMTS network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP not only takes transmitters into account in optimisations but also any repeaters and remote antennas. Atoll ACP can also be used to measure and optimise the EMF exposure created by the network. This permits the optimisation of power and antenna settings to reduce excessive EMF exposure in existing networks and optimal site selection for new transmitters. ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have defined the objectives and the network parameters to be optimised, Atoll ACP uses an efficient global search algorithm to test many network configurations and propose the reconfigurations that best meet the objectives. The ACP presents the changes ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the suggested changes. The ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 6: Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how you can view the results of an optimisation. In this section, only the concepts specific to CDMA networks are explained: • • •
"CDMA Optimisation Objectives" on page 933 "CDMA Quality Parameters" on page 934 "The CDMA Quality Analysis Maps" on page 935.
10.3.1 CDMA Optimisation Objectives ACP optimises the network using user-defined objectives to evaluate the quality of the network reconfiguration. The objectives are dependent on the technology used by the project and are consistent with the corresponding coverage predictions in Atoll. In projects using CDMA, either alone, or in a co-planning or multi-RAT project, the following objectives are used: • •
RSCP Ec/Io
933
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
For information on setting objective parameters, see "Setting Objective Parameters" on page 242 of Chapter 6: Automatic Cell Planning.
10.3.2 CDMA Quality Parameters When you create an optimisation setup, you define how the ACP evaluates the objectives. The quality parameters are technology dependent. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own maps. However, if you have saved the display options of an ACP map as default, or if you are using a configuration file for ACP, these defined ranges and colours will be used as the default, overriding the settings in the selected coverage prediction. In projects using CDMA, either alone, or in a co-planning project, the following quality parameters are used: • • •
Overlap Signal level Ec/Io
To define the quality parameters for CDMA: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233 in Chapter 6: Automatic Cell Planning. 2. Click the Objectives tab. 3. Under Criteria, in the left-hand pane, under Parameters, expand CDMA. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own maps. However, if you have saved the display options of an ACP map as default, or if you are using a configuration file for ACP, these defined ranges and colours will be used as the default, overriding the settings in the selected coverage prediction. For information on setting ACP map display options as the default, see "Changing the Display Properties of ACP Predictions" on page 284. For information on saving a configuration file, see "Configuring Default Settings" on page 231. If you want to use a coverage prediction, the coverage prediction must have already been calculated.
4. Click Overlap. In the right-hand pane, you can define how the ACP will evaluate overlapping coverage. 5. Select what the objective evaluation will be based on from the Base prediction settings on list: • •
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, define an Overlap threshold margin and a Minimum signal level. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate overlapping coverage using the same parameters that were used to calculate the coverage prediction.
6. Under CDMA in the left-hand pane under Parameters, select Signal Level. 7. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate the signal level using the same parameters that were used to calculate the coverage prediction.
8. Under CDMA in the left-hand pane under Parameters, select Ec⁄Io. 9. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
934
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box and define a Cell edge coverage probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is available, default values are used. Additionally you must define the Service and Terminal used to evaluate Ec⁄Io coverage. Select a Service and a Terminal. The service and terminal specified are used during the calculation of Ec⁄Io through gain and losses (i.e., the service body loss, the gain and loss of the terminal antenna, and terminal noise factor). Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate Ec⁄Io using the same parameters that were used to calculate the coverage prediction.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
10.3.3 The CDMA Quality Analysis Maps The quality analysis maps enable you to display the signal level and Ec⁄Io quality maps in the Atoll map window. These maps are the same as those displayed on the Quality tab of the optimisation’s Properties dialogue. The quality analysis maps are the equivalent of maps created by different Atoll coverage predictions: • •
The signal level maps correspond to the Atoll coverage by signal level in CDMA. For information on the coverage by signal level, see "Studying Signal Level Coverage" on page 838. The overlapping zones maps correspond to the Atoll overlapping zones coverage prediction. For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 851.
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 analysis. 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 signal level and Ec⁄Io values on any pixel by letting the pointer rest over the pixel. The signal level or Ec⁄Io value is then displayed in tip text. For the overlapping zones map, you can set the best server threshold on the User Preferences tab of the ACP Properties dialogue (see "Configuring Default Settings" on page 231) or by setting the CellOverlap parameter in the acp.ini file. For each network quality coverage prediction, ACP offers a map showing the initial network state, the final network state, and a map showing the changes between the initial and final state.
10.4 Verifying Network Quality An important step in the process of creating a CDMA network is verifying the quality of the network. This is done using measurements of the strength of the pilot signal and other parameters in different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: • • • • • • •
"Importing a Drive Test Data Path" on page 935 "Displaying Drive Test Data" on page 938 "Defining the Display of a Drive Test Data Path" on page 938 "Network Verification" on page 939 "Exporting a Drive Test Data Path" on page 946 "Extracting CW Measurements from Drive Test Data" on page 946 "Printing and Exporting the Drive Test Data Window" on page 947.
10.4.1 Importing a Drive Test Data Path In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, commas, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: • •
The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells). In CDMA networks, a cell is identified by its PN Offset. Therefore, you must indicate during the import process which columns contain the PN Offset of cells. Because a PN Offset can belong to several groups, you can also indicate from which group the PN Offset has been selected.
The data in the file must be structured so that the columns identifying the PN Offset group and the PN Offset are placed before the data columns for each cell. Otherwise Atoll will not be able to properly import the file.
935
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
You can import a single drive test data file or several drive test data files at the same time. If you regularly import drive test data files of the same format, you can create an import configuration. The import configuration contains information that defines the structure of the data in the drive test data file. By using the import configuration, you will not need to define the data structure each time you import a new drive test data file. To import one or several drive test data files: 1. Select the Network explorer. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. You can import one or several files. Select the file or files you want to open. If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing SHIFT and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import. 5. Click Open. The Import of Measurement Files dialogue appears. Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue. 6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Import configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Import configuration, select an import configuration from the Import configuration list. b. Continue with step 10. •
•
When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. if several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters: • • •
Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement Conditions, • •
Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document.
8. Click the Setup tab (see Figure 10.44).
936
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Figure 10.44: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Decimal Symbol used in the file. b. Click the Setup button to link file columns and internal Atoll fields. The Drive Test Data Setup dialogue appears. c. Under Measurement point position, select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in the drive test data file. You can also identify the columns containing the XY coordinates of each point in the drive test data file by selecting them from the Field row of the table on the Setup tab.
d. If you are importing data using PN Offsets as cell identifiers: i.
Select By PN Offset under Transmitter Identification.
ii. In the PN Offset Identifier box, enter a string that is found in the column names identifying the PN Offset of scanned cells. For example, if the string "PN" is found in the column names identifying the PN Offset of scanned cells, enter it here. Atoll will then search for columns with this string in the column name. iii. Ensure that the PN Offset format selected in the PN Offset Format list is "Decimal." iv. In the PN Group Identifier box, enter a string that is 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. If you are importing data using Cell ID as cell identifiers:
f.
i.
Select By Cell ID under Transmitter Identification.
i.
In the Cell ID Identifier box, enter a string found in the column name identifying the cell Ids of scanned cells. For example, if the string "Cell_ID" is found in the column names identifying the Cell_ID of scanned cells, enter it here. Atoll will then search for the column with this string in the column name.
Click OK to close the Drive Test Data Setup dialogue.
937
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Setup dialogue, Atoll should recognise all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "". If a column is marked with "", it will not be imported. 9. If you want to save the definition of the data structure so that you can use it again, you can save it as an import configuration: a. On the Setup tab, under Import configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll’s installation folder. If you cannot write into that folder, you can click the Browse button to choose a different location. c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for example, "*.csv"). d. Click OK. Atoll will now select this import configuration automatically every time you import a drive test data path file with the selected extension. If you import a file with the same structure but a different extension, you will be able to select this import configuration from the Configuration list. • •
•
You do not have to complete the import procedure to save the import configuration and have it available for future use. When importing a measurement file, you can expand the NumMeasINIfile.ini file by clicking the Expand button ( ) in front of the file under Import configuration to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Import configuration and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The mobile data are imported into the current Atoll document.
10.4.2 Displaying Drive Test Data When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see information about the active set at that location. To display information about a single drive test data point: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Select the display check box beside the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want active set information. Atoll displays an arrow pointing towards the serving cells (see Figure 10.49 on page 945), 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 44.
10.4.3 Defining the Display of a Drive Test Data Path You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to manage permanent labels on the map, tip texts and the legend. In other words, the display of measurement path are managed in the same way as sites, transmitters, etc. To display the Display tab of a drive test data path’s Properties dialogue: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder.
938
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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. • • •
•
Fast Display forces Atoll to use the lightest symbol to display the points. This is particularly useful when you have a very large number of points. You can not use Advanced Display if the Fast Display check box has been selected. You can sort drive test data paths in alphabetical order in the Network explorer by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can save the display settings (such as colours and symbols) of a drive test data path in a user configuration file to make them available for use on another drive test data path. To save or load the user configuration file, click the Actions button on the Display tab of the path properties dialogue and select Save or Load from the Display Configuration submenu.
10.4.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 939 "Creating Coverage Predictions on Drive Test Data Paths" on page 942 "Displaying Statistics Over a Drive Test Data Path" on page 943 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 944 "Analysing Data Variations Along the Path" on page 944.
10.4.4.1 Filtering Incompatible Points Along Drive Test Data Paths When using a drive test data path, some measured points may present values that are too far outside of the median values to be useful. As well, test paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from the more lightly populated region between the two. In Atoll, you can filter out points that are incompatible with the points you are studying, either by filtering out the clutter classes where the incompatible points are located, or by filtering out points according to their properties. To filter out incompatible points by clutter class: 1. Select the Network explorer. 2. In the Network explorer, right-click the drive test data on which you want to filter out incompatible points: • •
All drive test data measurements: Right-click the Drive Test Data folder. Only one drive test data path: Click the Expand button ( ) to expand the Drive Test Data folder and right-click the drive test path.
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.
939
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
5. If you want to keep the measurement points inside the focus zone, select the Use focus zone to filter check box. 6. If you want to permanently remove the measurement points outside the filter, select the Delete Points Outside Filter check box. If you permenantly delete measurement points and later want to use them, you will have to re-import the original measurement data. To filter out incompatible points using a filter: 1. Select the Network explorer. 2. In the Network explorer, right-click the Drive Test Data on which you want to filter out incompatible points: • •
All Drive Test Data measurements: Right-click the Drive Test Data folder. Only one Drive Test Data path: Click the Expand button ( ) to expand the Drive Test Data folder.
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.45).
Figure 10.45: 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:
940
Formula
Data are kept in the table only if
=X
value equal to X (X can be a number or characters)
X
value not equal to X (X can be a number or characters)
X
numerical value is greater than X
=X
numerical value is greater than or equal to X
*X*
text objects which contain X
*X
text objects which end with X
X*
text objects which start with X
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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 96. You can permanently delete the points that do not fulfil the filter conditions by selecting the Delete points outside the filter check box.
8. Click OK to apply the filter and close the dialogue.
10.4.4.2 Predicting Signal Level on Drive Test Data Points To predict the signal level on drive test data points: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to create the point prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Point predictions, select Point Signal Level and click OK. The Point Signal Level Properties dialogue appears (see Figure 10.46).
Figure 10.46: Point Signal Level Properties dialogue The errors between measured and predicted signal levels can be calculated and added to the drive test data table. 6. If you want to calculate errors between measured and predicted signal levels, under Select signal levels for error calculations, select the names of the columns representing measured signal level values in the drive test data table for which you want to calculate the errors (see Figure 10.47). If you do not want to add this information to the drive test data table, continue with step 7.
Figure 10.47: Selecting measured signal levels for which errors will be calculated 7. Click OK. A new point prediction is created for the selected drive test data path. 8. Right-click the drive test data path. The context menu appears. 9. Select Calculations > Calculate All the Predictions from the context menu. If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the drive test data table for the predicted point signal level from the serving cell and the errors between the measured and predicted values.
941
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Figure 10.48: Drive Test Data table after Point Signal Level Prediction (with error calculations) New columns are also added for the predicted point signal level from each neighbour cell and the errors between the predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Data Variations Along the Path" on page 944. The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main matrix. For more information on propagation models, see Chapter 5: Working with Calculations in Atoll.
10.4.4.3 Creating Coverage Predictions on Drive Test Data Paths You can create the following coverage predictions for all transmitters on each point of a drive test data path: • • • •
Coverage by Signal Level Pilot Quality Analysis Service Area Analysis (Eb⁄Nt) (DL) Service Area Analysis (Eb⁄Nt) (UL)
To create a coverage prediction along a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Standard Predictions, select one of the following coverage predictions and click OK: •
Coverage by Signal Level: Click the Conditions tab. •
•
Pilot Quality Analysis (Ec⁄I0): Click the Conditions tab. •
•
• • • •
On the Conditions tab, you can select which simulation to study in the Load Conditions list. Or you can select a group of simulations and either select All to perform an average analysis of all simulations in the group based on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simulations. If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from Load Conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the DL total power defined in the cell properties. You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 863. 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.
Service Area Analysis (Eb⁄Nt) Downlink: Click the Conditions tab. •
•
•
942
At the top of the Conditions tab, you can set the range of signal level to be calculated. Under Server, you can select whether to calculate the signal level from all transmitters, or only the best or second-best signal. If you choose to calculate the best or second-best signal, you can enter a Margin. If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Probability. You can select the Indoor Coverage check box to add indoor losses. Finally, you can select the Carrier to be studied.
On the Conditions tab, you can select which simulation to study in the Load Conditions list. Or you can select a group of simulations and either select All to perform an average analysis of all simulations in the group based on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simulations. If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from Load Conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the DL total power defined in the cell properties. You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 863. You must also select which Carrier is to be considered.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
• • •
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.
Service Area Analysis (Eb⁄Nt) Uplink: Click the Conditions tab. •
•
• • •
On the Conditions tab, you can select which simulation to study in the Load Conditions list. Or you can select a group of simulations and either select All to perform an average analysis of all simulations in the group based on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simulations. If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from Load Conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the DL total power defined in the cell properties. You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 863. 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 Predictions from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Working with Calculations in Atoll). You can display the information in these new columns in the Drive Test Data window. For more information on the Drive Test Data window, see "Analysing Data Variations Along the Path" on page 944.
10.4.4.4 Displaying Statistics Over a Drive Test Data Path Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path. To display the statistics for a specific Drive Test Data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to display comparative statistics. The context menu appears. 4. Select Display Statistics from the context menu. The Measurement and Prediction Fields Selection 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.4.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path. To display the statistics for a specific Drive Test Data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder.
943
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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.
10.4.4.6 Extracting a Field From a Drive Test Data Path for a Transmitter You can extract the information from a specific field for a given transmitter on each point of an existing drive test data path. The extracted information will be added to a new column in the drive test data table. To extract a field from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to extract a field. The context menu appears. 4. Select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter 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.4.4.7 Analysing Data Variations Along the Path In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data window. You can also use the Drive Test Data window to see which cell is the serving cell for a given test point. To analyse data variations using the Drive Test Data window. 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 10.49).
944
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Figure 10.49: The Drive Test Data window 5. Click Display at the top of the Drive Test Data window. The Display Parameters dialogue appears (see Figure 10.50).
Figure 10.50: The Drive Test Data window 6. In the Display Parameters dialogue: • • •
Select the check box next to any field you want to display in the Drive Test Data window. If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new colour from the palette that appears. Click OK to close the Display Parameters dialogue. You can change the display status or the colour of more than one field at a time. You can select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field you want to import. You can select non-contiguous fields by pressing CTRL and clicking each field. You can then change the display status or the colour by right-clicking on the selected fields and selecting the choice from the context menu. The selected fields are displayed in the Drive Test Data window.
7. You can display the data in the drive test data path in two ways: • •
Click the values in the Drive Test Data window. Click the points on the drive test path in the map window.
945
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
The drive test data path appears in the map window as an arrow pointing towards the serving cell, with a number identifying the best server (see Figure 10.49 on page 945). 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 44. 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. 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.49 on page 945).
10.4.5 Exporting a Drive Test Data Path You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.
10.4.6 Extracting CW Measurements from Drive Test Data You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears. 5. Under Extract CW Measurements: a. Select one or more transmitters from the For the Transmitters list. b. Select the field that contains the information that you want to export to CW measurements from the For the Fields list.
946
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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.4.7 Printing and Exporting the Drive Test Data Window You can print or export the contents of the Drive Test Data window, using the context menu in the Drive Test Data window. To print or export the contents of the Drive Test Data window: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data you want to analyse. The context menu appears. 4. Select Open the Analysis Tool from the context menu. The Drive Test Data window appears (see Figure 10.49 on page 945). 5. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 944. 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.
10.5 Co-planning CDMA Networks with Other Networks Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a CDMA and a GSM network for the same area in Atoll, and then work with Atoll’s co-planning features to study the mutual impacts of the two networks. Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other network’s Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In this section, the following are explained: • • • • •
"Switching to Co-planning Mode" on page 948. "Working with Coverage Predictions in a Co-Planning Project" on page 949. "Performing Inter-technology Neighbour Allocation" on page 952. "Creating a CDMA Sector From a Sector in the Other Network" on page 963. "Ending Co-planning Mode" on page 965.
947
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
10.5.1 Switching to Co-planning Mode Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a CDMA Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, the CDMA document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems.
To switch to co-planning mode: 1. Open the main document. •
Select File > Open or File > New > From an Existing Database.
2. Link the other document with the open main document. a. Click the main document’s map window. The main document’s 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]. 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 Atoll’s co-planning features are now available. When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll syncronises the display for the following: • • • •
Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.
Displaying Both Networks in the Same Atoll Document After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 948, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the Explorer window of the linked document to the Explorer window of the main document (e.g., you can display GSM sites and measurement paths in a CDMA document). To display sites from the linked document in the main document: 1. Click the linked document’s map window. The linked document’s map window becomes active and the Explorer window shows the contents of the linked document. 2. Select the Network explorer. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In from the context menu, and select the name of the main document from the submenu that opens.
948
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
The Sites folder of the linked document is now available in the main document. The Explorer window of the main document now contains a folder named Sites in [linked document], where [linked document] is the name of the linked document. If you want the Sites folder of the linked document to appear in the main document automatically, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual. The same process can be used to link other folders in one document, folders such as CW Measurements, Drive Test Data, Clutter classes, Traffic, and DTM, etc., in the other document. Once the folders are linked, you can access their properties and the properties of the items in the folders from either of the two documents. Any changes you make in the linked document are taken into account in the both the linked and main documents. However, because working document is the main document, any changes made in the main document are not automatically taken into account in the linked document. If you close the linked document, Atoll displays a warning icon ( ) in the main document’s Explorer window, and the linked items are no longer accessible from the main document. You can load the linked document in Atoll again by right-clicking the linked item in the Explorer window of the main document, and selecting Open Linked Document. The administrator can create and set a configuration file for the display parameters of linked and main document transmitters in order to enable you to distinguish them on the map and to be able to select them on the map using the mouse. If such a configuration file has not been set up, you can choose different symbols, sizes and colours for the linked and the main document transmitters. For more information on folder configurations, see "Folder Configurations" on page 105. You can also set the tip text to enable you to distinguish the objects and data displayed on the map. For more information on tip text, see "Defining the Object Type Tip Text" on page 46. 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 Windows" on page 39. Figure 10.51 shows an example of CDMA transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in tip text.
Figure 10.51: GSM and CDMA Transmitters displayed on the map
10.5.2 Working with Coverage Predictions in a Co-Planning Project Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: • •
"Updating Coverage Predictions" on page 949 "Analysing Coverage Predictions" on page 950.
10.5.2.1 Updating Coverage Predictions You can access the properties of the coverage predictions in the linked Predictions folder in the main document’s Explorer window. After modifying the linked coverage prediction properties, you can update them from the main document.
949
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
To update a linked coverage prediction: 1. Click the main document’s map window. The main document’s map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button (
) in the toolbar.
When you click the Calculate button, Atoll first calculates uncalculated and invalid path loss matrices and then unlocked coverage predictions in the main and linked Predictions folders. When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions" on page 218. 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. To prevent Atoll from calculating coverage predictions in the linked Predictions folder, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual.
10.5.2.2 Analysing Coverage Predictions In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tip text to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which coverage predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following are explained: • • • • •
10.5.2.2.1
"Co-Planning Coverage Analysis Process" on page 950 "Displaying the Legend Window" on page 951 "Comparing Coverage Prediction Results Using Tip Text" on page 951 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 951 "Studying Differences Between Coverage Areas" on page 952.
Co-Planning Coverage Analysis Process The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes. The recommended process for analysing coverage areas, and the effect of parameter modifications in one 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
950
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
by Transmitter" on page 850 and "Studying Signal Level Coverage" on page 838. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tip text contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage prediction’s 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 948. 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 951 and "Studying Differences Between Coverage Areas" on page 952. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.
10.5.2.2.2
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: •
10.5.2.2.3
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction in the main and linked Predictions folders, identified by the name of the coverage prediction.
Comparing Coverage Prediction Results Using Tip Text You can compare coverage predictions by by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. Atoll displays information for all displayed coverage predictions in both the working and the linked documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Co-Planning Coverage Analysis Process" on page 950). To get coverage prediction results in the form of tip text: •
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 10.21). The tip text for the working document is on top and the tip text for the linked document, with the linked document identified by name is on the bottom.
Figure 10.52: Comparing coverage prediction results using tip text
10.5.2.2.4
Comparing Coverage Areas by Overlaying Coverage Predictions You can compare the coverage areas of the main and linked documents by overlaying coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main document’s map window. The main document’s map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer.
951
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
3. Click the Expand button ( ) to expand the Predictions folder. 4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is dislayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 43. 9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The coverage prediction is dislayed on the map. 11. Right-click the coverage prediction. The context menu appears. 12. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 13. Modify the display parameters of the coverage prediction. 14. Calculate the two coverage predictions again, if needed. To more easily view differences between the coverage areas, you can also change the order of the Predictions folders in the Explorer window. For more information on changing the order of items in the Explorer window, see "Working with Layers Using the Explorer Windows" on page 39.
10.5.2.2.5
Studying Differences Between Coverage Areas You can compare coverage predictions to find differences in coverage areas. To compare coverage predictions: 1. Click the main document’s map window. The main document’s map window becomes active and the Explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 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 document’s Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 858.
10.5.3 Performing Inter-technology Neighbour Allocation The following sections describe the features available in Atoll that help the RF planner to carry out inter-technology neighbour planning. For example, handovers between a CDMA and a GSM network can be studied in Atoll by allocating neighbour GSM sectors to CDMA cells. In this section, the following are explained: • • • • • • •
"Setting Inter-technology Exceptional Pairs" on page 953 "Configuring Importance Factors for Inter-technology Neighbours" on page 955 "Allocating Inter-technology Neighbours Automatically" on page 955 "Displaying Inter-technology Neighbours on the Map" on page 957 "Allocating and Deleting Inter-technology Neighbours per Cell" on page 958 "Calculating the Importance of Existing Inter-technology Neighbours" on page 961 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 962.
In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Coplanning Mode" on page 948.
952
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
10.5.3.1 Setting Inter-technology Exceptional Pairs You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Exceptional Pairs from the context menu. The Exceptional Pairs of Inter-technology Neighbours table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list. c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. d. Atoll fills the Number and Distance (m) fields automatically. In GSM, neighbours and exceptional pairs are allocated by transmitter (i.e., by sector). You can access a cell’s inter-technology neighbours and exceptional pairs by using its Properties dialogue. To open a cell’s Properties dialogue: 1. Select the Network explorer. 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 cell’s Properties dialogue appears. 5. Click the Inter-technology Neighbours tab. In GSM, the Inter-technology Neighbours tab is found on the transmitter’s Properties dialogue. Displaying Inter-technology Exceptional Pairs on the Map You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table. To display exceptional pairs defined between the main and the linked documents: 1. Click the main document’s map window. 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
3. Select Display Options from the menu. The Edit Relations on the Map 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 Links: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines.
6. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
953
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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 Edit Relations on the Map button ( ) in the Radio Planning toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Edit Relations on the Map 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 41). The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the map. Adding and Removing Inter-technology Exceptional Pairs on the Map You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-technology Exceptional Pairs on the Map" on page 953. 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. 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 41).
954
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
10.5.3.2 Configuring Importance Factors for Inter-technology Neighbours You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Inter-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: • • •
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. 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 955.
5. Click OK.
10.5.3.3 Allocating Inter-technology Neighbours Automatically Atoll can automatically determine handover relations between networks of different technologies, for example, CDMA and GSM. In this case, inter-technology handovers from CDMA to GSM may occur when the CDMA coverage is not continuous. The network’s overall coverage is extended by a CDMA-to-GSM handover. Atoll can automatically determine neighbours in the linked document for cells in the main document and vice versa. Inter-technology neighbours are stored in the database. To automatically allocate neighbours in the linked document for cells in the main document: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > 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 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.
955
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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 cell’s coverage area that the neighbour’s 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: Reason
Description
When
Exceptional Pair
Neighbour relation is defined as an exceptional pair.
Force exceptional pairs is selected
Co-site
The neighbour is located at the same site as the reference cell.
Force co-site as neighbours is selected
Distance
The neighbour is within the maximum distance from the reference cell.
Use coverage overlapping is not selected
% of covered area and overlapping area
Neighbour relation that fulfils coverage conditions.
Use coverage overlapping is selected
Existing
The neighbour relation existed before running the automatic allocation.
Reset is not selected
12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document.
956
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
To compare the proposed and existing neighbour lists: •
Click Compare. The list of automatically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: • • • •
The document name and the neighbour allocation type, 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.5.3.4 Displaying Inter-technology Neighbours on the Map You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios. To display neighbours in the linked document for cells in the main document: 1. Click the main document’s map window. 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
3. Select Display Options from the menu. The Edit Relations on the Map dialogue appears. 4. Under Inter-technology Neighbours, select the Display Links check box. 5. Under Advanced, select the neighbour links to display: •
•
•
Outwards Non-Symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards Non-Symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric Links: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines.
6. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
7. Select Neighbours as the type of neighbour links to display. 8. Click the Edit Relations on the Map button ( ) in the Radio Planning toolbar. Neighbours are now displayed on the map. Neighbours are displayed until you click the Edit Relations on the Map button again. 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, 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 41). If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intratechnology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.
957
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
10.5.3.5 Allocating and Deleting Inter-technology Neighbours per Cell Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Inter-technology Neighbours table. This section explains the following: • • •
"Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 958. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 959. "Allocating and Removing Inter-technology Neighbours on the Map" on page 960.
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 transmitter’s Properties dialogue: 1. On the main document’s map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitter’s 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 cell’s Properties dialogue appears. 5. Click the Inter-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. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon (
).
c. 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." To create a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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.
958
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
To delete a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Press DEL to delete the neighbour. 8. Click OK. In GSM, the Inter-technology Neighbours tab is available in each transmitter’s Properties dialogue. Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Neighbours from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour. 6. Allocate or delete a neighbour. To allocate an inter-technology neighbour: a. In the row marked with the New Row icon (
), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Source to "manual." 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 all exceptionnal pairs into consideration: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. You can add or delete either forced neighbours or forbidden neighbours using the Exceptional Pairs of Inter-technology Neighbours table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu.
959
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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 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. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector). Allocating and Removing Inter-technology Neighbours on the Map You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-technology Neighbours on the Map" on page 957. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter. T remove an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the list of inter-technology neighbours of the other transmitter. To add an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. There can be two cases: • •
If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric intertechnology 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.
960
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
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 41).
10.5.3.6 Calculating the Importance of Existing Inter-technology Neighbours After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing inter-technology neighbours: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 5. Select the Inter-technology Neighbours tab. 6. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as possible neighbours. 7. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance. 8. Clear the Use Overlapping Coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 10. Otherwise, select the Use Overlapping Coverage check box if you want to base the neighbour importance calculation on coverage conditions. 9. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for 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.
961
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
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. 10. If you cleared the Use Overlapping Coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max Inter-site Distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated. 11. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. • • • •
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.
12. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
10.5.3.7 Checking the Consistency of the Inter-technology Neighbour Plan You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Inter-technology > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Neighbours tab. 5. Define the parameters of the audit: • • •
•
962
Average No. of Neighbours: Select the Average No. of Neighbours check box if you want to verify the average number of neighbours per cell. Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full Lists: Select the Full Lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table. Lists > Max Number: Select the Lists > Max Number check box if you want to verify which cells have more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the Cells table
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
• • • •
Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site neighbours. Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance Between Neighbours: Select the Distance Between Neighbours check box and enter the distance between neighbours that should not be exceeded.
6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: •
Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax:
•
Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax:
•
|CELL|
|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| If the field Maximum number of inter-technology neighbours in the Cells table is empty, the Full Lists check and the Lists > Max Number check use the Default Max Number value defined in the audit dialogue.
•
Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan. Syntax:
•
Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
|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.5.4 Creating a CDMA Sector From a Sector in the Other Network You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main document’s map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new CDMA transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document.
963
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
To update the display settings of the new sector: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder of the main document. The context menu appears. 4. Select Apply Current Configuration from the context menu.
Figure 10.53: New sector – Before and after applying the configuration The azimuths and mechanical tilts of secondary antennas or remote antennas are not included when you select Apply Configuration and have to be set up manually.
10.5.5 Using ACP in a Co-planning Project Atoll ACP enables you to automatically calculate the optimal network settings in terms of network coverage and capacity in co-planning projects where networks using different technologies, for example, CDMA and GSM, must both be taken into consideration. When you run an optimisation setup in a co-planning environment, you can display the sites and transmitters of both networks in the document in which you will run the optimisation process, as explained in "Switching to Co-planning Mode" on page 948. 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 964 "Importing the Other Network into the Setup" on page 964.
10.5.5.1 Creating a New Co-planning Optimisation Setup Once you have displayed both networks in the main document as explained in "Switching to Co-planning Mode" on page 948, you can create the new co-planning optimisation setup. To create a new co-planning optimisation setup: 1. Click the main document’s map window. 2. Select the Network explorer. 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 234. 5. After defining the optimisation setup, click the Create Setup button to save the defined optimisation. The optimisation setup has now been created. The next step is to add the GSM network to the ACP optimisation setup you have just created.
10.5.5.2 Importing the Other Network into the Setup Once you have created the co-planning optimisation setup, you must import the linked network. To import the linked network: 1. Click the main document’s map window. 2. Select the Network explorer.
964
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
3. Click the Expand button (
) to expand the ACP - Automatic Cell Planning folder.
4. Right-click the setup you created in "Creating a New Co-planning Optimisation Setup" on page 964. The context menu appears. 5. Select Import Project from the context menu and select the name of the linked document you want to import into the newly created setup.
The setup has been modified to include the linked network. You can modify the parameters for the optimisation setup by right-clicking it in the Network explorer and selecting Properties from the context menu. For information on the parameters available, see "Defining Optimisation Parameters" on page 234. After defining the co-planning optimisation setup: •
Right-click the setup in the ACP - Automatic Cell Planning folder and select Run from the context menu to run the optimisation. For information on running the optimisation, see "Running an Optimisation Setup" on page 267. For information on the optimisation results, see "Viewing Optimisation Results" on page 270.
10.5.6 Ending Co-planning Mode once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents. To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select File > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.
10.6 Advanced Configuration In this section, the following advanced configuration options are explained: • • • • • • • • • •
"Defining Inter-carrier Interference" on page 966 "The Global Network Settings" on page 967 "Data Rates Available for Services in CDMA" on page 968 "The 1xEV-DO Radio Bearers" on page 969 "Site Equipment" on page 970 "Receiver Equipment" on page 971 "Conditions for Entering the Active Set" on page 972 "Modelling Shadowing" on page 973 "Creating PN Offset Domains and Groups for PN Offset Allocation" on page 974 "Modelling Inter-technology Interference" on page 975.
965
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
10.6.1 Defining Inter-carrier Interference If you want Atoll to take into account the interference between two carriers, you must create a carrier pair with an interference reduction factor. Atoll will take the interference reduction factor into account on both the reverse link and the forward link. To create a pair of carriers with an interference reduction factor: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Frequencies folder. 4. In the Frequencies folder, right-click Inter-carrier Interference Reduction Factors. The context menu appears. 5. Select Open Table. The Inter-carrier Interference Reduction Factors table appears. 6. For each carrier pair for which you want define inter-carrier interference: a. Enter the first carrier of the pair in the 1st Carrier column. b. Enter the second carrier of the pair in the 2nd Carrier column. c. Enter an interference reduction factor in the Reduction Factor (dB) column. When Atoll is calculating interference, it subtracts the interference reduction factor from the calculated interference. If the interference reduction factor is set to "0," Atoll assumes that the carriers in the defined pair generate as much interference as cells with the same carrier interference. The interference reduction factor must be a positive value.
For every pair of carriers that is not defined, Atoll assumes that there is no inter-carrier interference. d. Press ENTER to create the carrier pair and to create a new row in the table.
10.6.2 Defining Frequency Bands To define a frequency band: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Frequencies folder. 4. In the Frequencies folder, right-click Bands. The context menu appears. 5. Select Open Table. The Frequency Bands table appears. 6. In the Frequency Bands table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each frequency band, enter: • • • •
Name: Enter a name for the frequency, for example, "Band 1900." This name will appear in other dialogues when you select a frequency band. Average Frequency (MHz): Enter the average frequency. First Carrier: Enter the number of the first carrier in this frequency band. Last Carrier: Enter the number of the last carrier in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First Carrier field. When you have more than one frequency band, the carriers must be numbered sequentially, contiguously (i.e., you cannot skip numbers in a range of carriers, and the range of carriers in one band cannot overlap the range of carriers in another), and uniquely (i.e., you can only use each number once). For example: Band 1900: First carrier: 0; Last carrier 1 and Band 700: First carrier: 2 and Last carrier: 2
7. In the Frequencies folder, right-click Carrier Types. The context menu appears. 8. Select Open Table. The Carrier Types table appears. 9. In the Carrier Types table, define the carriers and whether the carrier is 1xRTT or 1xEV-DO. 10. When you have finished defining carriers, click the Close button (
966
).
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
11. When you have finished adding frequency bands, click the Close button (
).
You can also access the properties dialogue of each individual frequency band by double-clicking the left margin of the row with the frequency band.
10.6.3 The Global Network Settings In the Network Settings Properties dialogue, you can define many calculation parameters that are used in predictions and in Monte Carlo simulations. This section explains the options available in the Network Settings Properties dialogue, and explains how to access the dialogue: • •
"The Options of the Network Settings Properties Dialogue" on page 967 "Modifying Global Network Settings" on page 968.
10.6.3.1 The Options of the Network Settings Properties Dialogue The Network Settings Properties dialogue has two tabs: the Global Parameters Tab and the Calculation Parameters tab. • •
10.6.3.1.1
"The Global Parameters Tab" on page 967 "The Calculation Parameters Tab" on page 967
The Global Parameters Tab The Global Parameters tab has the following options: •
DL Powers: Under DL Powers, you can define whether the power values on the forward link are Absolute or Relative to Pilot. The power values affected are the synchronisation power and the paging power defined in the cell properties and the TCH power in 1xRTT and Speech service properties. Atollautomatically converts the power values defined in the cell properties (i.e., synchronisation channel and paging powers) when changing the option. On the other hand, the values for the TCH powers have to be modified manually.
•
DL Load: Under DL Load, you can define whether the total power values on the forward link are Absolute or a percentage of the maximum power (% Pmax). Atollautomatically converts the total power values when changing the option.
•
UL 1xRTT Power Control Based On: Under UL 1xRTT Power Control Based On, you can define whether the reverse link power control for the 1xRTT network is based on Traffic Quality or Pilot Quality.
•
Interferences: Under Interferences, you can define the method used to calculate interference on the forward link (Nt): • Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus thermal noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the signal of the studied cell.
•
Handoff: Under Handoff, you can define the parameters used to model soft handoff on the reverse link. •
•
10.6.3.1.2
Default UL Macro-Diversity Gain: You can set a default value for the reverse link gain due to macro-diversity on soft and soft-soft handoffs. If you clear the Shadowing taken into account check box on the Conditions tab when defining a coverage prediction or during a point analysis, Atoll uses this value. If you select the Shadowing taken into account check box on the Conditions tab, Atoll calculates the reverse link macro-diversity gain, based on the standard deviation value of Eb⁄Nt on the reverse link defined per clutter class. +MRC in Softer/Soft: If you select the +MRC (maximal ratio combining) in Softer/Soft check box, Atoll selects the serving cell during a softer/soft handoff by recombining the signal of co-site transmitters and multiplying the resulting signal by the rake efficiency factor and then comparing this value to the signal received at transmitters located on the other sites of the active set. Atoll chooses the greatest value and multiplies it by the macro-diversity gain.
The Calculation Parameters Tab The Calculation Parameters tab has the following options: •
Calculation limitation: Under Calculation limitation, you can define the following data: •
•
Min. interferer reception threshold: This value is used by Atoll to limit the input of interferers in calculations. The performance of CDMA-specific coverage predictions and Monte Carlo simulations can be improved by setting a high value for the minimum interferer reception threshold. This value is used as a filter criterion on the signal level received from interferers. Atoll will discard all interferers with a signal level lower than this value. • Min. pilot RSCP threshold: The minimum pilot RSCP threshold. The value is used as a filter criterion on the received pilot signal level when calculating CDMA-specific predictions. Atoll does not display any result on the pixel if the pilot signal level received from the best server is lower than the defined Min. pilot RSCP threshold. Receiver: Under Receiver, you can enter the Height of the receiver.
967
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
10.6.3.2 Modifying Global Network Settings You can change global network settings in the Network Settings Properties dialogue.
To change global network settings: 1. Select the Parameters explorer. 2. Right-click the Network Settings folder. The context menu appears. 3. Select Properties from the context menu. The Network Settings Properties dialogue appears. 4. Modify the parameters described in "The Options of the Network Settings Properties Dialogue" on page 967. 5. Click OK.
10.6.4 Data Rates Available for Services in CDMA The different services offered by a CDMA network require different data rates. CDMA responds to the differing data rate requirements with a range of carriers. For example, CDMA2000 can provide voice using 1xRTT. Data services, which require higher data rates than voice, can be provided using 1xRTT or 1xEV-DO Rev. 0 or Rev. A. The following table gives the data rates available for voice, 1xRTT, and 1xEV-DO Rev. 0 and Rev. A. Service
Reverse Link
Forward Link
Speech
N FCH *
N FCH
1xRTT Data
N FCH
N FCH
3 X N FCH
3 X N FCH
5 X N FCH
5 X N FCH
9 X N FCH
9 X N FCH
17 X N FCH
17 X N FCH
9.6
38.4
19.2
76.8
38.4
153.6
76.8
307.6
153.6
614.4
For 1xRTT, N FCH can be 9.6 or 14.4 kbps on either the forward or reverse link. 1xEV-DO Rev. 0 Data
921.6 1228.8 1843.2 2457.6 1xEV-DO Rev. A Data
968
4.8
4.8
9.6
9.6
19.2
19.2
38.4
38.4
76.8
76.8
115.2
115.2
153.6
153.6
230.4
230.4
307.2
307.2
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
Service
Reverse Link
Forward Link
460.8
460.8
614.4
614.4
921.6
921.6
1228.8
1228.8
1848.2
1848.2 2457.6 3072.0
* N FCH is the nominal throughput of FCH.
10.6.5 The 1xEV-DO Radio Bearers In Atoll, the data rates available for 1xEV-DO Rev. A and 1xEV-DO Rev. B based services are modelled using radio bearers. The 1xEV-DO Radio Bearers tables list the 1xEV-DO radio bearers with their RLC peak rate, index numbers, and transport block size.You must define 1xEV-DO radio bearers before you can model services using them. In this section, the following are explained: • •
"Defining the Forward Link 1xEV-DO Radio Bearers" on page 969 "Defining the Reverse Link 1xEV-DO Radio Bearers" on page 969.
10.6.5.1 Defining the Forward Link 1xEV-DO Radio Bearers The Downlink 1xEV-DO Radio Bearers table lists the different transport block sizes that can be transmitted in one timeslot and the corresponding RLC peak rates. To create or modify a 1xEV-DO forward link radio bearer: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Radio Bearers folder. 4. In the Radio Bearers folder, right-click Downlink 1xEV-DO Radio Bearers. The context menu appears. 5. Select Open Table. The Downlink 1xEV-DO Radio Bearers table appears. 6. In the Downlink 1xEV-DO Radio Bearers 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 forward link radio bearer. If you are creating a new 1xEV-DO forward link radio bearer, enter an index number in the row marked with the New Row icon ( ). Transport Block Size (bits): Enter or modify the packet size in bits transmitted in one timeslot. RLC Peak Rate (kbps): Enter or modify the RLC peak rate in kbits per second.
10.6.5.2 Defining the Reverse Link 1xEV-DO Radio Bearers The Uplink 1xEV-DO Radio Bearer table lists the different transport block sizes that can be transmitted in one subframe (i.e., 4 timeslots) and the corresponding RLC peak rates. To create or modify a 1xEV-DO reverse link radio bearer: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Radio Bearers folder. 4. In the Radio Bearers folder, right-click Uplink 1xEV-DO Radio Bearers. The context menu appears. 5. Select Open Table. The Uplink 1xEV-DO Radio Bearers table appears. 6. In the Uplink 1xEV-DO 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 reverse link radio bearer. If you are creating a new 1xEV-DO reverse link radio bearer, enter an index number in the row marked with the New Row icon ( ). Transport Block Size (bits): Enter or modify the packet size in bits transmitted in one subframe (4 timeslots).
969
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
•
© Forsk 2012
RLC Peak Rate (kbps): Enter or modify the RLC peak rate in kbits per second.
10.6.6 Site Equipment In this section, the following are explained: • •
"Creating Site Equipment" on page 970 "Defining Channel Element Consumption per CDMA Site Equipment and Radio Configuration" on page 970.
10.6.6.1 Creating Site Equipment To create a new piece of CDMA site equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Radio Resource Management folder. 4. Right-click Site Equipment. The context menu appears. 5. Select Open Table from the context menu. The Site Equipment table appears. 6. In the Equipment table, each row describes a piece of equipment. For information on working with data tables, see "Working with Data Tables" on page 69. For the new piece of CDMA equipment you are creating, enter the following: • • •
•
Name: The name you enter will be the one used to identify this piece of equipment. Manufacturer: The name of the manufacturer of this piece of equipment. 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 predictions. 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. You can define the rake efficiency factor used to model the recombination on the forward link 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 predictions). Choose one of the following: • • • •
•
• • •
Min. UL Load Factor: The carrier with the minimum reverse link noise (carrier with the lowest reverse link load factor) is selected. Min. DL Total Power: The carrier with the minimum forward link total power is selected. Random: The carrier is randomly chosen. Sequential: Carriers are sequentially loaded. The first carrier is selected as long as it is not overloaded. Then, when the maximum reverse link load factor is reached, the second carrier is chosen and so on.
Downlink and Uplink Overhead Resources for Common Channels/Cell: The reverse link and forward link overhead resources for common channels/cell correspond to the number of channel elements that a cell uses for common channels in the forward and the reverse link. This setting is also used for Walsh code allocation; it indicates the number of Walsh codes to be allocated to control channels per cell. AS Restricted to Neighbours: Select this option if you want the other transmitters in the active set to belong to the neighbour list of the best server. Pool of Shared CEs: Select this option if you want all cells on the site to share channel elements. Power Pooling Between Transmitters: Select this option if you want all cells on the site to share power on the traffic channels.
7. Click the Close button (
) to close the table.
10.6.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.
970
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
To define channel element consumption during CDMA simulations: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Radio Resource Management folder. 4. Right-click CE Consumption. The context menu appears. 5. Select Open Table from the context menu. The CE Consumption table appears. 6. For each equipment-radio configuration pair, enter in the CE Consumption table the number of reverse link and forward link channel elements that Atoll will consume during the power control simulation. 7. Click the Close button (
) to close the table.
10.6.7 Receiver Equipment In this section, the following are explained: • •
"Setting Receiver Height" on page 971 "Creating or Modifying Reception Equipment" on page 971.
10.6.7.1 Setting Receiver Height When you make CDMA coverage predictions, you can define the height of the receiver. To define the height of the receiver: 1. Select the Parameters explorer. 2. Right-click the Network Settings folder. The context menu appears. 3. Select Properties from the context menu. The Network Settings Properties dialogue appears. 4. Click the Calculation Parameters tab. 5. Under Receiver, enter a Height. This value will be used when calculating a CDMA coverage predictions and during a point analysis. 6. Click OK.
10.6.7.2 Creating or Modifying Reception Equipment In Atoll, reception equipment is used when you create a terminal. The graphs defined for each reception equipment entry are used for quality coverage predictions and for selecting 1xEV-DO radio bearers. To create or modify reception equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Reception Equipment folder. "Standard" is the default reception equipment type for all terminals. 4. Double-click the reception equipment type you want to modify. The reception equipment type’s Properties dialogue appears. You can create a new reception equipment type by entering a name in the row marked with the New Row icon ( ) and pressing ENTER.
5. Click the General tab. On the General tab, you can define the Name of the reception equipment. 6. Click the Quality Graphs tab. 7. Ensure that a Quality Indicator has been chosen for each Service. You can edit the values in the DL and UL Quality Indicator Tables by clicking directly on the table entry, or by selecting the Quality Indicator and clicking the Downlink Quality Graphs or the Uplink Quality Graphs buttons. The DL and UL Quality Indicator tables describe the variation of the quality indicator as a function of the measured parameter (as defined in the Quality Indicators table). The Uplink and Downlink Quality Graphs are used for quality coverage predictions. 8. Click the 1xEV-DO Radio Bearer Selection (Downlink) tab.
971
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
9. Enter the Required C⁄I (dB), the Modulation used (you can choose between QPSK, 8PSK, 16QAM, or 64QAM) and the Early Termination Probabilities for each Radio Bearer Index, with Mobility and No. of Slots. The radio bearer index with the number of timeslots and the modulation indicates the downlink transmission format. The Required C/I values are used in simulations and in the Service Area Analysis (Eb/Nt) (DL) coverage prediction to select the downlink 1xEV-DO radio bearer and then to calculate the data rate provided on downlink. A downlink 1xEV-DO radio bearer is selected only if the user terminal supports the modulation required by the radio bearer. 1xEVDO Rev. A-capable terminals support 16QAM modulation while 1xEV-DO Rev. B-capable terminals can support 16QAM and 64QAM modulations. The Early Termination Probabilities are used in the Service Area Analysis (Eb/Nt) (DL) coverage prediction to calculate the average 1xEV-DO throughput when HARQ (Hybrid Automatic Repeat Request) is used. 10. Click the 1xEV-DO Radio Bearer Selection (Uplink) tab. 11. Enter the following for each Radio Bearer Index with Mobility and No. of Subframes: • • • •
Required Ec⁄Nt (High Capacity) (dB): The Ec/Nt required for services with high capacity uplink mode. Required Ec⁄Nt (Low Latency) (dB): Ec/Nt required for services with low latency uplink mode. Early Termination Probabilities Modulation: The modulation used. You can choose between QPSK, 8PSK, 16QAM or 64QAM.
The Required Ec/Nt values are used in simulations and in the Service Area Analysis (Eb/Nt) (UL) coverage prediction to select the uplink 1xEV-DO radio bearer and then to calculate the data rate provided on uplink. An uplink 1xEV-DO radio bearer is selected only if the user terminal supports the modulation required by the radio bearer. 1xEV-DO Rev. A-capable terminals support 16QAM modulation while 1xEV-DO Rev. B-capable terminals support the 16QAM and 64QAM modulations. The Early Termination Probabilities are used in the Service Area Analysis (Eb/Nt) (UL) coverage prediction to calculate the average 1xEV-DO throughput when HARQ (Hybrid Automatic Repeat Request) is used. 12. Click OK to close the reception equipment type’s Properties dialogue.
10.6.8 Conditions for Entering the Active Set The mobile active set is the list of the transmitters to which the mobile is connected. The active set may consist of one or more transmitters; depending on whether the service supports soft handoff and on the terminal active set size. Transmitters in the mobile active set must use a frequency band with which the terminal is compatible and the same carrier. It is, however, the quality of the pilot (Ec⁄I0) that finally determines whether or not a transmitter can belong to the active set. In order for a given transmitter to enter the mobile active set as best server, the quality of this transmitter’s pilot must be the highest one and it must exceed an upper threshold equal to the sum of the minimum Ec/I0 defined in the properties of the best serving cell and the Delta minimum Ec/I0 defined in the properties of the mobility type. The upper threshold is set for the carrier as defined in the cell properties and can also take into account the user mobility type if the Delta minimum Ec/I0 defined in the mobility type is different from 0. The carrier used by the transmitters in the active set corresponds to the best carrier of the best server. For information on best carrier selection, see the Technical Reference Guide. In order for a transmitter to enter the active set: •
•
•
It must use the same carrier as the best server transmitter. In Atoll, carriers are modelled using cells. For information on accessing cell properties, see "Creating or Modifying a Cell" on page 819. For a description of the properties of a cell, see "Cell Definition" on page 816. The pilot quality of the transmitter must exceed a threshold. The threshold depends both on the type of carrier and the mobility type. It is equal to the sum of T_Drop defined in the properties of the best server and the Delta T_Drop defined in the properties of the mobility type. If you have selected to restrict the active set to neighbours, the transmitter must be a neighbour of the best server. You can restrict the active set to neighbours by selecting the AS Restricted to Neighbours option in the Site Equipment table. For an explanation of how to set the AS Restricted to Neighbours option, see "Creating Site Equipment" on page 970.
For multi-carrier EVDO Rev.B users, the active set can consist of several sub-active sets, each one being associated with one carrier. The number of sub-active sets depends on the maximum number of carriers supported by the terminal. As described earlier, the quality of the pilot (Ec⁄I0) determines whether or not a transmitter can belong to a sub-active set. The sub-active set associated with the best carrier is the same as the active set of a single-carrier user. For other carriers, the uplink Ec⁄Nt received by the best server on the best carrier and on the studied carrier determines whether or not a carrier can have a subactive set, and the transmitters in the sub-active sets depend on the mode supported by the terminal (locked mode or unlocked mode):
972
•
The Ec/Nt received by the best serving transmitter on the best carrier must exceed the minimum uplink Ec/Nt.
• •
The Ec/Nt received by the best serving transmitter on the studied carrier must exceed the minimum uplink Ec/Nt. When locked mode is used, the serving transmitters must be the same in all sub-active sets. With unlocked mode, the serving transmitters can be different from one sub-active set to another.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
10.6.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 Ec⁄I0 and Eb⁄Nt values and the macro-diversity gain. For information on setting the model standard deviation and the Ec⁄I0 and Eb⁄Nt standard deviations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. Shadowing can be taken into consideration when Atoll calculates the signal level, Ec⁄I0, and Eb⁄Nt for: • •
A point analysis (see "Making a Point Analysis to Study the Profile" on page 837) A coverage prediction (see "Studying Signal Level Coverage" on page 838).
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 973.
10.6.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. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins and Gains dialogue appears (see Figure 10.54). 4. You can set the following parameters: • •
Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin or macrodiversity gains: • •
•
•
From Model: The model standard deviation. Atoll will display the shadowing margin of the signal level. Ec⁄I0: The Ec⁄I0 standard deviation. Atoll will display the Ec⁄I0 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 Eb⁄Nt: The Eb⁄Nt reverse link standard deviation. Atoll will display the Eb⁄Nt 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 Eb⁄Nt: The Eb⁄Nt forward link standard deviation. Atoll will display the Eb⁄Nt forward link shadowing margin.
5. If you select "Ec⁄I0" or "Eb⁄Nt 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 "Ec⁄I0" as the standard deviation under Standard Deviation, enter the allowed Ec⁄I0 difference between the best server and the second one. This value is used to calculate forward link macro-diversity gains. If you selected "Eb⁄Nt 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 "Ec⁄I0" as the standard deviation under Standard Deviation, enter the allowed Ec⁄I0 difference between the second-best server and the third one. This value is used to calculate forward link macro-diversity gains. If you selected "Eb⁄Nt UL" as the standard deviation under Standard Deviation,
973
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
enter the allowed Eb⁄Nt difference between the second-best server and the third one. This value is used to calculate reverse link macro-diversity gains. 6. Click Calculate. The calculated shadowing margin is displayed. If you selected "Ec⁄I0" or "Eb⁄Nt UL" as the standard deviation under Standard Deviation, Atoll also displays the macro-diversity gains for two links and for three links. 7. Click Close to close the dialogue.
Figure 10.54: The Shadowing Margins and Gains dialogue
10.6.10 Creating PN Offset Domains and Groups for PN Offset Allocation Atoll facilitates the management of available PN Offsets during automatic allocation with the pilot PN sequence offset index increment (PILOT_INC) parameter. For example, if you set PILOT_INC to "4," all PN Offsets from 4 to 508 with a separation interval of 4 can be allocated. If you need to restrict the range of PN Offsets available further, you can create groups of PN Offsets and domains, where each domain is a defined set of groups. Using PN Offsets groups and domains is recommended for this purpose only. The procedure for managing PN Offsets in a CDMA document consists of the following steps: 1. Creating a PN Offset domain, as explained in this section. 2. Creating groups, each containing a range of PN Offsets, and assigning them to a domain, as explained in this section. 3. Assigning a PN Offset domain to a cell or cells. If there is no PN Offset domain, Atoll will consider the PILOT_INC parameter only to determine the possible PN Offsets when assigning PN Offsets (e.g., If PILOT_INC is set to 4, all PN Offsets from 4 to 508 with a separation interval of 4 can be allocated). To create a PN Offset domain: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the PN Offsets folder. 4. Right-click Domains in the PN Offsets folder. The context menu appears. 5. Select Open Table from the context menu. The Domains table appears. 6. In the row marked with the New Row icon (
), enter a Name for the new domain.
7. Click another cell of the table to create the new domain and add a new blank row to the table. 8. Double-click the domain to which you want to add a group. The domain’s Properties dialogue appears. 9. Under Groups, enter the following information for each group you want to create. The definition of the group must be consistent with the default domain defined using the PILOT_INC parameter. • • • • •
974
Group: Enter a name for the new PN Offset group. Min.: Enter the lowest available PN Offset in this group’s range. Max: Enter the highest available PN Offset in this group’s 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.
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
AT312_UM_E1
•
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."
10. Click in another cell of the table to create the new group and add a new blank row to the table.
10.6.11 Modelling Inter-technology Interference Analyses of CDMA networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in a CDMA network. Atoll can take into account interference from co-existing networks in Monte Carlo simulations and coverage predictions. The following inter-technology interference scenarios are modeled in Atoll: •
Interference received by mobiles on the downlink: Interference can be received by mobiles in a CDMA network on the downlink from external base stations and mobiles in the vicinity. Interference from external base stations (also called downlink-to-downlink interference) can be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (CDMA, TDMA, OFDM). These graphs are then used for calculating the interference from the external base stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-technology IRFs" on page 976. Interference from external mobiles (also called uplink-to-downlink interference) can be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your CDMA network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled in Atoll using the Inter-technology DL Noise Rise definable for each cell in the CDMA network. This noise rise is taken into account in all downlink interference-based calculations. However, this noise rise does not impact the calculation of the mobile reuse factor. For more information on the Inter-technology DL Noise Rise, see "Cell Definition" on page 816. You can study the downlink inter-technology interference by carrying out an Inter-technology Downlink Interference coverage prediction as explained in "Studying Inter-technology Downlink Noise" on page 878.
Figure 10.55: 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) can be created by insufficient separation between the downlink frequency used by the external network and the uplink frequency used by your CDMA network. Such interference may also come from co-existing TDD networks. Interference from external mobiles (also called uplink-to-uplink interference) can be created by the use of same or nearby frequencies for uplink in both networks. Unless the exact locations of external mobiles is known, it is not possible to separate interference received from external base stations and mobiles on the uplink. The effect of this interference is modelled in Atoll using the 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 taken into consideration in predictions (AS Analysis and coverage predictions) and does not have an impact on the calculation of the cell reuse factor. For more information on the Inter-technology UL Noise Rise, see "Cell Definition" on page 816.
975
Atoll 3.1.2 User Manual Chapter 10: CDMA2000 Networks
© Forsk 2012
Figure 10.56: Interference received by cells on the uplink
10.6.11.1 Defining Inter-technology IRFs Interference received from external base stations on mobiles of your CDMA network can be calculated by Atoll. Atoll uses the inter-technology interference reduction factor (IRF) graphs for calculating the interference levels. An IRF graph represents the variation of the Adjacent Channel Interference Ratio (ACIR) as a function of frequency separation. ACIR is determined from the Adjacent Channel Suppression (ACS) and the Adjacent Channel Leakage Ratio (ACLR) parameters as follows: 1 ACIR = ------------------------------------1 1 ------------- + ---------------ACS ACLR
An IRF depends on: • • • •
The interfering technology (TDMA, CDMA, and OFDM) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).
IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your CDMA document, i.e., when Atoll is in co-planning mode. For more information on how to switch to co-planning mode, see "Switching to Co-planning Mode" on page 948. To define the inter-technology IRFs in the victim network: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Inter-technology Interference Reduction Factors. The context menu appears. 4. Select Open Table. The Inter-technology Interference Reduction Factors table appears. 5. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter: • • • •
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 separations, Freq. Delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document. • •
Reduction values must be positive. If you leave reduction factors undefined, Atoll assumes there is no interference.
6. When you have finished defining interference reduction factors, click OK. You can, if you want, link more than one Atoll document with your main document following the procedure described in "Switching to Co-planning Mode" on page 948. 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.
976
Chapter 11 TD-SCDMA Networks This chapter provides the information to use Atoll to design, analyse, and optimise a TD-SCDMA network.
In this chapter, the following are explained: •
"Designing a TD-SCDMA Network" on page 979
•
"Planning and Optimising TD-SCDMA Base Stations" on page 980
•
"Studying Network Capacity" on page 1078
•
"Verifying Network Capacity" on page 1108
•
"Co-planning TD-SCDMA Networks with Other Networks" on page 1117
•
"Advanced Configuration" on page 1134
Atoll 3.1.2 User Manual Chapter 11: Starting a Project
978
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
11 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 979. Creating the network of base stations is explained in "Planning and Optimising TD-SCDMA Base Stations" on page 980. 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 1078, 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 1108. Filtering imported drive test data paths, and using the data in coverage predictions is also explained.
11.1 Designing a TD-SCDMA Network Figure 11.1 depicts the process of planning and creating a TD-SCDMA network.
Figure 11.1: Planning a TD-SCDMA network - workflow The steps involved in planning a TD-SCDMA network are described below. The numbers refer to Figure 11.1. 1. Open an existing radio-planning document or create a new one ( • •
1
).
You can open an existing Atoll document by selecting File > Open. Creating a new Atoll document is explained in Chapter 2: Starting an Atoll Project.
2. Configure the network by adding network elements and changing parameters (
2
).
You can add and modify the following elements of base stations: • • •
"Creating or Modifying a Site" on page 988 "Creating or Modifying a Transmitter" on page 988 "Creating or Modifying a Cell" on page 989.
You can also add base stations using a base station template (see "Placing a New Base Station Using a Station Template" on page 989). 3. Carry out basic coverage predictions ( •
3
)
"Making a Point Analysis to Study the Profile" on page 1006
979
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
•
© Forsk 2012
"Studying Signal Level Coverage" on page 1007 and "Signal Level Coverage Predictions" on page 1016
4. Allocate neighbours ( •
4
).
"Planning Neighbours" on page 1057.
5. Before making more advanced coverage predictions, you need to define cell load conditions (
5
).
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 1078). You can define them manually either on the Cells tab of each transmitter’s Properties dialogue or in the Cells table (see "Creating or Modifying a Cell" on page 989) (
5c
).
6. Make TD-SCDMA-specific coverage predictions using the defined cell load conditions ( • •
).
"Signal Quality Coverage Predictions" on page 1032 "HSDPA Quality and Throughput Analysis" on page 1052.
7. Allocate scrambling codes ( •
6
7
).
"Planning Scrambling Codes" on page 1069.
11.2 Planning and Optimising TD-SCDMA Base Stations As described in Chapter 2: Starting an Atoll Project, you can start an Atoll document from a template, with no base stations, or from a database with an existing set of base stations. As you work on your Atoll document, you will still need to create base stations and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any additional equipment, such as the TMA, feeder cables, etc. In a TD-SCDMA project, you must also add cells to each transmitter. A cell refers to the characteristics of an RF carrier on a transmitter. Atoll lets you create one site, transmitter, or cell at a time, or create several at once using station templates. In Atoll, a base station refers to a site with its transmitters, antennas, equipment, and cells. In Atoll, you can study a single base station or a group of base stations using coverage predictions. Atoll allows you to make a variety of coverage predictions, such as signal level or signal quality coverage predictions. The results of calculated coverage predictions can be displayed on the map, compared, and studied. Atoll enables you to model network traffic by creating services, users, user profiles, traffic environments, and terminals. These can be then used to make signal quality coverage predictions, such as effective service area, noise, or interference predictions, on the network. In this section, the following are explained: • • • • • • • • • • • • •
"Creating a TD-SCDMA Base Station" on page 980. "Creating a Group of Base Stations" on page 997. "Modifying Sites and Transmitters Directly on the Map" on page 997. "Display Tips for Base Stations" on page 997. "Creating a Dual-Band TD-SCDMA Network" on page 998. "Creating a Repeater" on page 998. "Creating a Remote Antenna" on page 1002. "Setting the Working Area of an Atoll Document" on page 1005. "Studying a Single Base Station" on page 1006. "Studying Base Stations" on page 1010. "Planning Frequencies" on page 1054. "Planning Neighbours" on page 1057. "Planning Scrambling Codes" on page 1069.
11.2.1 Creating a TD-SCDMA Base Station When you create a site, you create only the geographical point; you must add the transmitters and cells afterwards. The site, with the transmitters, antennas, equipment, and cells is called a base station. In this section, each element of a base station is described. If you want to add a new base station, see "Placing a New Base Station Using a Station Template" on page 989. If you want to create or modify one of the elements of a base station, see "Creating or Modifying a Base Station Element" on page 988. If you need to create a large number of base stations, Atoll allows you to import them from another Atoll document or from an external source. For information, see "Creating a Group
980
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
of Base Stations" on page 997. This section explains the various parts of the base station process: • • • • •
"Definition of a Base Station" on page 981. "Creating or Modifying a Base Station Element" on page 988. "Placing a New Base Station Using a Station Template" on page 989. "Managing Station Templates" on page 990. "Duplicating an Existing Base Station" on page 995.
11.2.1.1 Definition of a Base Station A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. You will usually create a new base station using a station template, as described in "Placing a New Base Station Using a Station Template" on page 989. This section describes the following elements of a base station and their parameters: • • •
11.2.1.1.1
"Site Description" on page 981. "Transmitter Description" on page 981. "Cell Description" on page 985.
Site Description The parameters of a site can be found in the site’s Properties dialogue. The Properties dialogue has the following tabs: •
The General tab (see Figure 11.2):
Figure 11.2: New Site dialogue • •
Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If you want to change the default name that Atoll gives to new sites, see the Administrator Manual. Position: By default, Atoll places the new site at the centre of the map window. You can modify the location of the site here. While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 41.
•
• •
The Equipment tab: •
11.2.1.1.2
Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can specify the actual altitude under Real, if you want. If an altitude is specified here, Atoll will use this value for calculations. Comments: You can enter comments in this field if you want. Equipment: You can select equipment from the list. To create new site equipment, see "Creating Site Equipment" on page 1143. If no equipment is assigned to the site, Atoll considers that the JD factor and MCJD factor have a value of "0".
Transmitter Description The parameters of a transmitter can be found in the transmitter’s 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 Proper-
981
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
ties dialogue has three additional tabs: the Cells tab (see "Cell Description" on page 985), the Propagation tab (see Chapter 5: Working with Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 43). •
The General tab: •
•
-
Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You can enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names transmitters, see the Administrator Manual. Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can click the Browse button ( ) to access the properties of the site. For information on the site Properties dialogue, see "Site Description" on page 981. You can click the New button to create a new site for the transmitter. Shared antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the same site or on sites with the same position and that share the same antenna. The entry in the field must be the same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. This field is also used for dual-band transmitters to synchronise antenna parameters for different frequency bands.
•
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 1134. Under Antenna position, you can modify the position of the antennas (main and secondary): • •
•
Relative to site: Select this option if you want to enter the antenna positions as offsets with respect to the site location, and then enter the x-axis and y-axis offsets, Dx and Dy, respectively. Coordinates: Select this option if you want to enter the coordinates of the antenna, and then enter the x-axis and y-axis coordinates of the antenna, X and Y, respectively.
The Transmitter tab (see Figure 11.3):
Figure 11.3: Transmitter dialogue - Transmitter tab •
982
Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed in red in the Transmitters folder of the Network explorer.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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 11.4), 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 176.
•
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 176. Transmitter equipment: You can select transmitter equipment from the Transmitter list. You can click the
•
• • •
Browse button ( ) to access the properties of the transmitter equipment. For information on creating transmitter equipment, see "Defining Transmitter Equipment" on page 176. Feeder length: You can enter the feeder length at transmission and reception. Miscellaneous losses: You can enter miscellaneous losses at transmission and reception. The value you enter must be positive. Receiver antenna diversity gain: You can enter a receiver antenna diversity gain. The value you enter must be positive.
Figure 11.4: The Equipment Specifications dialogue Any loss related to the noise due to a transmitter’s repeater is included in the calculated losses. Atoll always considers the values in the Real boxes in coverage predictions even if they are different from the values in the Computed boxes. The information in the real Noise figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Total losses at transmission and reception and the real Noise figure at reception if you want. Any value you enter must be positive. •
Antennas: •
•
Height⁄ground: The Height⁄ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered must include the height of building. Main antenna: Under Main antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens a dialogue displaying all the possible antennas based on the same physical antenna as the currently selected one. Selecting the Electrical tilt of the antenna model displays the appropriate antennas under Available antennas. Selecting the
983
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
antenna under Available antennas and clicking OK assigns the antenna to the transmitter. The other fields, Azimuth, Mechanical downtilt, and Additional electrical downtilt, display additional antenna parameters. • • •
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. The mechanical and additional electrical downtilts defined for the main antenna are also used for the calculations of smart antennas.
•
Diversity: Under Diversity, you can select the No. of ports on the Transmission and Reception sides, as well as the Type of diversity, if there is more than one port on the Transmission side.
•
Smart antenna: Under Smart antenna, the available smart antenna equipment are visible in the Equipment list. You can click the Browse button (
) to access the properties of the smart antenna equipment. When
you click the Browse button ( ), the Smart Antenna Equipment Properties 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 11.5). For more information on smart antenna equipment, see "Smart Antenna Equipment" on page 1141. 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.
Figure 11.5: 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, 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. • • •
984
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
•
The transmission power is distributed among the main and secondary antennas. This is not compatible with smart antennas. You must not assign smart antennas to transmitters with secondary antennas, and vice versa. In calculations, repeaters and remote antennas are transparent to the donor transmitters and the served users. For example, beamforming smart antennas on donor transmitters create beams directly towards the served users, and not towards the repeater or remote antenna that covers the users. This results in a combined signal level received from the transmitter using the smart antenna and from the repeater or remote antenna. If this approach does not match how your equipment works, you must not assign smart antennas to transmitters with repeaters and remote antennas, and vice versa.
The main antenna is used to transmit the pilot signals. Coverage predictions based on the P-CCPCH signal are performed using the main antenna. It is also used for traffic signals if there is no smart antenna equipment selected for the transmitter. If there is smart antenna equipment assigned to the transmitter, traffic data is transmitted and received using the smart antenna, while the pilot and other common channels are transmitted using the main antenna.
11.2.1.1.3
Cell Description In Atoll, a cell is defined as an RF carrier, with all its characteristics, on a transmitter; the cell is the mechanism by which you can configure a TD-SCDMA multi-carrier network. In other words, a transmitter has one cell for every carrier. When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently selected station template. The following describes the parameters of a TD-SCDMA cell. 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 belongs. 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 1054. Name: By default, Atoll names the cell after its transmitter, adding the carrier number in parentheses. If you change transmitter name or carrier, Atoll does not update the cell name. You can enter a name for the cell, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names cells, see the Administrator Manual. Active: If this cell is to be active, you must select the Active check box. Carrier: The number of the carrier. Carrier type: The type of carrier, i.e., Standalone, Master, or Slave. ID: You can enter an ID for the cell. This is a user-definable network-level parameter for cell identification. Scrambling code: The scrambling code allocated to the 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. SC locked: If you select the SC locked check box, the scrambling code will not be modified during automatic scrambling code allocation. 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 every 10 μs , you should enter P⁄10 dBm in order to correctly represent the average interference from these channels. DwPCH power [DwPTS] (dBm): The power transmitted on the DwPTS timeslot. By default, the DwPCH power and the other CCH power are set as absolute values. You can set these values as relative to the pilot power in the Global Parameters. For more information, see "Network Settings" on page 1135.
985
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
•
•
© Forsk 2012
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. 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 1049. There are two switching points in the frame, one after the first mandatory downlink timeslot (D), and the other can be after 1 to 5 uplink timeslots. The symmetric configuration is selected by default.
• •
• •
Required UL resource units: The number of resource units required in the uplink. Required DL resource units: The number of resource units required in the downlink. Atoll can calculate the number of required resource units in the uplink and downlink. For information on calculating network capacity, see "Calculating TD-SCDMA Network Capacity" on page 1078. Comments: If desired, you can enter any comments in this field. HSPA Support: The HSPA functionality supported by the cell. You can choose between None (i.e., R99 only), HSDPA, or HSPA (i.e., HSDPA and HSUPA). When HSDPA is supported, the following fields are available: •
HS-PDSCH power dynamic allocation: If you are modelling dynamic power allocation, you should select this check box. During simulations, Atoll first allocates power to R99 users and then dynamically allocates the remaining power of the cell to the HS-PDSCH channels of HSDPA users. At the end of the simulation, you can commit the calculated HS-PDSCH power and total power values to each cell and timeslot. In the context of dynamic power allocation, the total power is the maximum power minus the power headroom.
•
•
•
•
•
•
•
•
•
•
986
Available HS-PDSCH power per DL TS (dBm): When you are modelling static power allocation, the HS-PDSCH power dynamic allocation check box is cleared and the HS-PDSCH power available for each downlink timeslot is entered in this box. This is the default value of power available per timeslot for the HS-PDSCH channels of HSDPA users. In case of dynamic HS-PDSCH power allocation, the value entered here represents the maximum power for the HS-PDSCH of HSDPA users per timeslot. Power headroom (dB): The power headroom is a reserve of power that Atoll keeps for Dedicated Physical Channels (DPCH) in case of fast fading. During simulation, HSDPA users will not be connected if the cell power remaining after serving R99 users is less than the power headroom value. HS-SCCH dynamic power allocation: If you are modelling dynamic power allocation, you should select this check box and enter a value in HS-SCCH power per DL TS (dBm). The HS-SCCH power calculated for HS-SCCH channel during a simulation cannot exceed the value defined in HS-SCCH power per DL TS (dBm). During power control, Atoll controls HS-SCCH power in order to meet the minimum quality threshold (as defined for each mobility type). HS-SCCH power per DL TS (dBm): When you are modelling static power allocation, the HS-SCCH dynamic power allocation check box is cleared and the actual power per HS-SCCH channel is entered in this box. In case of dynamic HS-SCCH power allocation, the value entered here represents the maximum power for the HS-SCCH channel per HSDPA user. Number of HS-SCCH channels: The maximum number of HS-SCCH channels for this cell. Each Packet (HSDPA) and Packet (HSPA) user consumes one HS-SCCH channel. Therefore, at any given time (over a transmission time interval), the number of HSDPA users cannot exceed the number of HS-SCCH channels per cell. HS-SICH dynamic power allocation: If you are modelling dynamic power allocation, you should select this check box. During power control, Atoll controls HS-SICH power of the HSDPA-capable terminal in order to meet the minimum quality threshold (as defined for each mobility type) in the uplink. Number of HS-SICH channels: The maximum number of HS-SICH channels for this cell. Each Packet (HSDPA) and Packet (HSPA) user consumes one HS-SICH channel. Therefore, at any given time (over a transmission time interval), the number of HSPA users cannot exceed the number of HS-SICH channels per cell. Min number of HS-PDSCH codes per DL TS: The minimum number of OVSF codes available for HS-PDSCH channels for each downlink timeslot. This value will be taken into account during simulations in order to find a suitable bearer. Max number of HS-PDSCH codes per DL TS: The maximum number of OVSF codes available for HS-PDSCH channels for each downlink timeslot. This value will be taken into account during simulations and coverage predictions in order to find a suitable bearer. HSDPA scheduler algorithm: The scheduling technique that will be used to rank the HSDPA users to be served: • Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by the channel quality indicator (CQI). • Round robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order).
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
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.
• •
Max number of HSDPA users: The maximum number of HSDPA bearer users (i.e., Packet (HSDPA) users and Packet (HSPA) users users) that this cell can support at any given time. Number of HSDPA users: The number of HSDPA bearer users is an average and can be used for certain coverage predictions. You can enter this value yourself, or have the value calculated by Atoll using a simulation.
When HSUPA is supported, the following fields are also available: •
•
DL HSUPA Power: The power (in dBm) allocated to HSUPA DL channels (E-AGCH, E-RGCH, and E-HICH). This value must be entered by the user. • Max number of HSUPA users: The maximum number of HSUPA bearer users (i.e., Packet (HSPA) users) that this cell can support at any given time. • Number of HSUPA users: The number of HSUPA bearer users is an average and can be used for certain coverage predictions. This value can be a simulation result or can be entered by the user. • E-DCH dynamic power allocation: If you are modelling dynamic power allocation, you should select this check box and enter a value in E-DCH power per DL TS (dBm). The E-DCH power calculated for E-DCH channel during a simulation cannot exceed the value defined in E-DCH power per DL TS (dBm). During power control, Atoll controls E-DCH power in order to meet the minimum quality threshold (as defined for each mobility type). • E-DCH power per DL TS (dBm): When you are modelling static power allocation, the E-DCH dynamic power allocation check box is cleared and the actual power per E-DCH channel is entered in this box. In case of dynamic EDCH power allocation, the value entered here represents the maximum power for the E-DCH channel per HSUPA user. • UL load factor due to HSUPA (%): The uplink cell load contribution due to HSUPA. This value can be a simulation result or can be entered by the user. Max Number of Intra-technology Neighbours: The maximum number of intra-technology neighbours for this cell. This value is used by the intra-technology neighbour allocation algorithm. Max Number of Inter-technology Neighbours: The maximum number of inter-technology neighbours for this cell. This value is used by the inter-technology neighbour allocation algorithm. Neighbours: You can access a 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 1057. Timeslots: You can access information about the cell’s traffic timeslots, i.e, for each of the six traffic timeslots, by
• •
clicking the Browse button (
).
The Browse buttons ( ) might not be visible in the Neighbours and Timeslot boxes if this is a new cell. You can make the Browse buttons appear by clicking Apply.
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., R99, HSDPA, HSUPA, etc. Other CCH power (dBm): The power of other common channels (S-CCPCH, FPACH, and PICH) on the traffic timeslot. Other common control channels can be transmitted on a downlink traffic timeslot using the main antenna. DL traffic power (dBm): The traffic power transmitted on downlink is the power necessary to serve users on the downlink timeslots. This value can be a simulation result or can be entered by the user. UL load factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between the uplink total interference and the uplink total noise. This value can be a simulation result or can be entered by the user. Angular distribution of UL and DL loads: The angular distribution of downlink transmitted power and uplink loads calculated for cells whose transmitters have smart antenna equipment. This value is a simulation result. Resource units overhead: The number of resource units corresponding to overhead. This overhead is used in network dimensioning. For information on calculating network capacity, see "Calculating TD-SCDMA Network Capacity" on page 1078. Max DL load (% Pmax): The percentage of the maximum downlink power (set in Max power [Traffic TS]) not to be exceeded. This limit can be taken into account during simulations.
987
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
• •
•
•
© Forsk 2012
Max UL load factor (%): The maximum uplink load factor not to be exceeded. This limit can be taken into account during simulations. Available HS-PDSCH power (dBm): When you are modelling static power allocation, the HS-PDSCH dynamic power allocation check box in the Cells tab is cleared and the HS-PDSCH power available for the downlink timeslot is entered in this box. This power is available for the HS-PDSCH channels of HSDPA users. In case of dynamic HSPDSCH power allocation, the value entered here represents the maximum power for the HS-PDSCH of HSDPA users. Min number of HS-PDSCH codes: The minimum number of OVSF codes available for HS-PDSCH channels. This value will be taken into account during simulations in order to find a suitable bearer. If no value is defined here, the value defined for the cell is considered for the timeslot. Max number of HS-PDSCH codes: The maximum number of OVSF codes available for HS-PDSCH channels. This value will be taken into account during simulations and coverage predictions in order to find a suitable bearer. If no value is defined here, the value defined for the cell is considered for the timeslot.
11.2.1.2 Creating or Modifying a Base Station Element A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: • • •
11.2.1.2.1
"Creating or Modifying a Site" on page 988. "Creating or Modifying a Transmitter" on page 988. "Creating or Modifying a Cell" on page 989.
Creating or Modifying a Site You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 981, through the site’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create a new site: 1. Select the Network explorer. 2. Right-click the Sites folder. The context menu appears. 3. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 11.2 on page 981). 4. Modify the parameters described in "Site Description" on page 981. 5. Click OK. To modify the properties of an existing site: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Sites folder. 3. Right-click the site you want to modify. The context menu appears. 4. Select Properties from the context menu. The site’s Properties dialogue appears. 5. Modify the parameters described in "Site Description" on page 981. 6. Click OK. If you are creating several sites at the same time, or modifying several existing sites, you can do it quickly by editing or pasting the data directly in the Sites table. You can open the Sites table by right-clicking the Sites folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
11.2.1.2.2
Creating or Modifying a Transmitter You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio Planning toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 981, through the transmitter’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create or modify a transmitter: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see Figure 11.3).
988
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
4. Modify the parameters described in "Transmitter Description" on page 981. 5. Click OK. To modify the properties of an existing transmitter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Modify the parameters described in "Transmitter Description" on page 981. 6. Click OK. If you are creating a new transmitter, Atoll automatically creates a cell based on the default station template. For information on creating a cell, see "Creating or Modifying a Cell" on page 989. •
•
11.2.1.2.3
If you are creating several transmitters at the same time, or modifying several existing transmitters, you can do it more quickly by editing or pasting the data directly in the Transmitters table. You can open the Transmitters table by rightclicking the Transmitters folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77. If you want to add a transmitter to an existing site on the map, you can add the transmitter by right-clicking the site and selecting New Transmitter from the context menu.
Creating or Modifying a Cell You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Description" on page 985, through the Properties dialogue of the transmitter where the cell is located. How you access the Properties dialogue depends on whether you are creating a new cell or modifying an existing cell. To create or modify a cell: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Description" on page 985. 7. Click OK. •
•
If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder in the Network explorer and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 77), or import data into the table (see "Importing Tables from Text Files" on page 82). If you want to add a cell to an existing transmitter on the map, you can add the cell by right-clicking the transmitter and selecting New Cell from the context menu.
11.2.1.3 Placing a New Base Station Using a Station Template In Atoll, a base station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing base stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template:
989
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
1. In the Radio Planning toolbar, select a template from the list.
2. Click the New Transmitter or Station button (
) in the Radio Planning 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 pointer’s current location are visible in the Status bar.
4. Click to place the station. •
•
To place the base station more accurately, you can zoom in on the map before you click the New Station button. For information on using the zooming tools, see "Changing the Map Scale" on page 49. 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 a Station Template" on page 991. To place a series of base stations within a defined area: 1. In the Radio Planning 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. 3. Draw a zone delimiting the area where you want to place the series of base stations: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. Atoll fills the delimited zone with new base stations and their hexagonal shapes. Base station objects such as sites and transmitters are also created and placed into their respective folders. You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for example, another antenna to a transmitter. Placing a Base Station on an Existing Site When you place a new base station using a station template as explained in "Placing a New Base Station Using a Station Template" on page 989, the site is created at the same time as the base station. However, you can also place a new base station on an existing site. To place a base station on an existing site: 1. In the Network explorer, clear the display check box beside the Hexagonal Design folder. 2. In the Radio Planning toolbar, select a template from the list. 3. Click the New Station button (
) in the Radio Planning 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 base station.
11.2.1.4 Managing Station Templates Atoll comes with TD-SCDMA station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio Planning toolbar (see Figure 11.6).
990
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Figure 11.6: The Radio Planning toolbar In this section, the following are explained: • • • • •
11.2.1.4.1
"Creating a Station Template" on page 991 "Modifying a Station Template" on page 991 "Copying Properties from One Station Template to Another" on page 995 "Modifying a Field in a Station Template" on page 995 "Deleting a Station Template" on page 995.
Creating a Station Template When you create a station template, you can do so by selecting an existing station template that most closely resembles the station template you want to create and making a copy. Then you can modify the parameters that differ. To create a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the Station Templates table, right-click the station template that most closely resembles the station template you want to create. The context menu appears. 6. Select Copy from the context menu. 7. Right-click the row marked with the New row icon (
). The context menu appears.
8. Select Paste from the context menu. The station template you copied in step 5. is pasted in the new row, with the Name of the new station template given as the same as the template copied but preceded by "Copy of". 9. Edit the parameters of the new station template in the table or as explained in "Modifying a Station Template" on page 991.
11.2.1.4.2
Modifying a Station Template You can modify a station template directly in the Station Templates table, or you can open the Properties dialogue for that station template and modify the parameters in the dialogue. To modify a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. Right-click the station template you want to modify. The context menu appears. 6. Select Record Properties from the context menu. The station template’s Properties dialogue appears. 7. Click the General tab of the Properties dialogue. On this tab (see Figure 11.7), 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, you can modify the following: 1st sector azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Height/ground of the antennas from the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of the building), the Mechanical downtilt, and the Additional electrical downtilt for the antennas. • •
The Additional Electrical Downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide.
Under Main antenna, you can select the main antenna Model, and under Smart antenna, you can select the smart antenna Equipment used by the transmitter.
991
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
•
•
© Forsk 2012
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information on propagation models, see Chapter 5: Working with Calculations in Atoll. Under Comments, you can add additional information. The information you enter will be the default information in the Comments field of any transmitter created using this station template.
Figure 11.7: Station Template Properties dialogue – General tab 8. Click the Transmitter tab. On this tab (see Figure 11.8), if the Active check box is selected, you can modify the following: •
Under Transmission⁄Reception, you can click the Equipment button to open the Equipment Specifications dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or transmitter equipment. For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 981. 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 11.4 on page 983). Any loss related to the noise due to a transmitter’s 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 Noise figure reception box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Noise figure at reception if you want. Any value you enter must be positive.
•
992
Diversity: Under Diversity, you can select the No. of ports on the Transmission and Reception sides, as well as the Type of diversity, if there is more than one port on the Transmission side.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Figure 11.8: Station Template Properties dialogue – Transmitter tab 9. Click the TD-SCDMA tab. On this tab (see Figure 11.9), 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 985. •
•
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 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 Primary 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 11.9: Station Template Properties dialogue – TD-SCDMA tab
993
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
10. Click the HSPA tab. On this tab (see Figure 11.10), you can define the parameters related to HSPA (for more information on the fields, see "Cell Description" on page 985). 11. Select the type of HSPA support. You can choose between None (i.e., R99 only), HSDPA, or HSPA (i.e., HSDPA and HSUPA). If you select HSDPA as HSPA support, you can set the following HSDPA parameters: • •
Under HSDPA, you can define a Power headroom. Under HS-SICH, you can select either Static or Dynamic allocation strategy for HS-SICH power and define the Number of channels for HS-SICH.
•
Under HS-PDSCH, you can select either Static or Dynamic allocation strategy for HS-PDSCH power, enter the Fixed power, if you selected Static power allocation, and enter the Min. and Max number of codes for HS-PDSCH.
•
Under HS-SCCH, you can select either Static or Dynamic allocation strategy for HS-SCCH power, enter the HSSCCH power for HS-SCCH, if you selected Static power allocation, and define the Number of channels for HS-SCCH.
•
Under Scheduler, you can select the scheduler Algorithm and enter the Max number of users.
When you create an HSDPA-capable base station using a station template, the timeslots of all the cells created automatically are by default set to support R99 and HSDPA. If you select HSDPA as HSPA support, you can set the following HSUPA parameters as well: •
Under HSDPA, you can select Dynamic allocation strategy for E-DCH power and enter the Max number of users.
When you create an HSPA-capable base station using a station template, the timeslots of all the cells created automatically are by default set to support R99 and HSPA.
Figure 11.10: Station Template Properties dialogue – HSDPA tab 12. Click the Neighbours tab. On this tab (see Figure 11.11), you can enter the maximum numbers of Intra-technology neighbours and Inter-technology neighbours.
994
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Figure 11.11: Station Template Properties dialogue – Neighbours tab 13. 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. 14. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.
11.2.1.4.3
Copying Properties from One Station Template to Another You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the Stations Templates table, copy the settings in the row corresponding to the station template you want to copy from and paste them into the row corresponding to the station template you want to modify.
11.2.1.4.4
Modifying a Field in a Station Template To modify a field in a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Properties from the context menu. The Station Template Properties dialogue appears. 5. Right-click the station template you want to modify. The context menu appears. 6. Select the Table tab. 7. For information on adding, deleting, and editing user-defined fields, see "Adding, Deleting, and Editing Data Table Fields" on page 70). 8. When you have finished, click OK.
11.2.1.4.5
Deleting a Station Template To delete a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Station Templates folder. 4. In the Station Templates folder, right-click the station template you want to delete. The context menu appears. 5. Select Delete from the context menu. The template is deleted.
11.2.1.5 Duplicating an Existing Base Station You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same transmitter, cell, and timeslot parameter values as the original base station. If no site exists where you place the duplicated base station, Atoll will create a new site with the same parameters as the site of the original base station. Duplicating a base station allows you to: • •
Quickly create a new base station with the same settings as an original one in order to study the effect of a new station on the coverage and capacity of the network, and Quickly create a new homogeneous network with stations that have the same characteristics.
995
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To duplicate an existing base station: 1. Select the Network explorer. 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 > Without Neighbours from the context menu, if you want to duplicate the base station without the intra- and inter-technology neighbours of its transmitters. Select Duplicate > With Neighbours from the context menu, if you want to duplicate the base station along with the lists of intra- and inter-technology neighbours of its transmitters.
5. Place the new base station on the map using the mouse: •
Creating a duplicate base station and site: In the map window, move the pointer over the map to where you would like to place the duplicate. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 11.12).
Figure 11.12: Creating a duplicate base station and site •
Placing the duplicate base station on an existing site: In the map window, move the pointer over the existing site where you would like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 11.13).
Figure 11.13: Placing the duplicate base station on an existing site •
•
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 49. 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. If the duplicate base station was placed on a new site, the site, transmitters, and cells of the new base station have the same names as the site, transmitters, and cells of the original base station with each name marked as "Copy of." The site, transmitters, cells, and timeslots of the duplicate base station have the same settings as those of the original base station. If the duplicate base station was placed on an existing site, the transmitters, and cells of the new base station have the same names as the transmitters, and cells of the original base station with each name preceded by the name of the site on which the duplicate was placed. All the remote antennas and repeaters of any transmitter on the original site are also duplicated. Any duplicated remote antennas and repeaters will retain the same donor transmitter as the original. If you want the duplicated remote antenna or repeater to use a transmitter on the duplicated base station, you must change the donor transmitter manually. You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each duplicate base station. For more information on the site, transmitter, cell, and timeslot properties, see "Definition of a Base Station" on page 981.
996
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
11.2.2 Creating a Group of Base Stations You can create base stations individually as explained in "Creating a TD-SCDMA Base Station" on page 980, or you can create one or several base stations by using station templates as explained in "Placing a New Base Station Using a Station Template" on page 989. However, if you have a large project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations. 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 121. You can import base station data in the following ways: •
Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. The table you copy data from must have the same column layout as the table you are pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77. •
Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80. For information on importing table data, see "Importing Tables from Text Files" on page 82. You can quickly create a series of base stations for study purposes using the Hexagonal Design tool on the Radio Planning toolbar. For information, see "Placing a New Base Station Using a Station Template" on page 989.
11.2.3 Modifying Sites and Transmitters Directly on the Map In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu in the Network explorer. However, in a complex radio-planning project, it can be difficult to find the data object in the Network explorer, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. You can also select a site to display all of the transmitters located on it in the Site Configuration window. When selecting a transmitter, if there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: • • • • • •
"Working with the Site Configuration Window" on page 37 "Selecting One of Several Transmitters" on page 41 "Moving a Site Using the Mouse" on page 41 "Moving a Site to a Higher Location" on page 42 "Changing the Azimuth of the Antenna Using the Mouse" on page 42 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42.
11.2.4 Display Tips for Base Stations Atoll allows to you to display information about base stations in a number of different ways. This enables you not only to display selected information, but also to distinguish base stations at a glance.
997
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
The following tools can be used to display information about base stations: •
•
•
•
Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object type’s data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information will lead to a cluttered display. For information on defining the label, see "Defining the Object Type Label" on page 46. Tip text: You can display information about each object, such as each site or transmitter, in the form of tip text that is only visible when you move the pointer over the object. You can choose to display more information than in the label, because the information is only displayed when you move the pointer over the object. You can display information from any field in that object type’s data table, including from fields that you add. For information on defining the tip text, see "Defining the Object Type Tip Text" on page 46. Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example, you can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active sites. You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns a colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding it. For information on defining the transmitter colour, see "Defining the Display Type" on page 44. Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can select a symbol that graphically represents the antenna half-power beamwidth (
). If you have two transmitters on the
same site with the same azimuth, you can differentiate them by selecting different symbols for each ( For information on defining the transmitter symbol, see "Defining the Display Type" on page 44.
and
).
11.2.5 Creating a Dual-Band TD-SCDMA Network In Atoll, you can model a dual-band TD-SCDMA network, i.e., a network consisting of 2100 MHz and 900 MHz transmitters, in one document. Creating a dual-band TD-SCDMA network consists of the following steps: 1. Defining the two frequency bands in the document (see "Defining Frequency Bands" on page 1134). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Working with Calculations in Atoll). 3. Assigning a frequency band, with its propagation model, to each transmitter (see "Transmitter Description" on page 981).
11.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 a radio link or a microwave link. The server side re-transmits the received signal. Atoll models RF repeaters and microwave repeaters. The modelling focuses on: • •
The additional coverage these systems provide to transmitters in the downlink. The UL total gain value and the noise rise generated at the donor transmitter by the repeater. •
Broadband repeaters are not modelled. Atoll assumes that all carriers of 3G donor transmitters are amplified.
In calculations, repeaters are transparent to the donor transmitters and the served users. For example, beamforming smart antennas at donor transmitters create beams directly towards the served users, and not towards the repeater that covers the users. This results in a combined signal level received from the transmitter using the smart antenna and from the repeater. If this approach does not match how your equipment works, you must not assign smart antennas to transmitters with repeaters and vice versa. In this section, the following are explained: • • • • •
998
"Opening the Repeaters Table" on page 999. "Creating and Modifying Repeater Equipment" on page 999 "Placing a Repeater on the Map Using the Mouse" on page 999. "Creating Several Repeaters" on page 1000. "Defining the Properties of a Repeater" on page 1000.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
"Tips for Updating Repeater Parameters" on page 1002.
11.2.6.1 Opening the Repeaters Table Repeaters and their defining parameters are stored in the Repeaters table. To open the Repeaters table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Repeaters > Open Table from the context menu. The Repeaters table appears.
11.2.6.2 Creating and Modifying Repeater Equipment You can define repeater equipment to be assigned to each repeater in the network. To create or modify repeater equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Repeater Equipment. The context menu appears. 4. Select Open Table from the context menu. The Repeater Equipment table appears. 5. Define the following in an existing record or in the row marked with the New row icon (
):
a. Enter a Name and Manufacturer for the new equipment. b. Enter a Noise figure (dB). The repeater causes a rise in noise at the donor transmitter, so the noise figure is used to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive value. c. Enter minimum and maximum repeater amplification gains in the Min gain and Max gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if there are any. d. Enter a Gain increment. Atoll uses the increment value when you increase or decrease the repeater amplifier gain using the buttons to the right of the Amplifier gain box ( logue.
) on the General tab of the repeater Properties dia-
e. Enter the maximum power that the equipment can transmit on the downlink in the Max downlink power column. This parameter enables Atoll to ensure that the downlink power after amplification does not exceed the limit of the equipment. f.
If desired, enter a Max uplink power, an Internal delay and Comments. These fields are for information only and are not used in calculations.
11.2.6.3 Placing a Repeater on the Map Using the Mouse In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site, or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater or of a remote antenna. To create a repeater and place it using the mouse: 1. Select the donor transmitter, repeater, or remote antenna. You can select it from the Transmitters folder in the Network explorer, or directly on the map. 2. Click the arrow next to New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
3. Select Repeater from the menu. 4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty icon. By default, the repeater has the same azimuth as the donor. Its tip text and label display the same information as displayed for the donor. As well, its tip text identifies the repeater and the donor. In the explorer window, the repeater is found in the Transmitters folder of the Network explorer under its donor transmitter, repeater, or remote antenna. For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on page 1000.
999
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
•
•
When the donor is a transmitter, you can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. You can hide the link by clicking it again. When the donor is a repeater or a remote antenna, Atoll displays a spider-type link showing the entire chain down to the donor transmitter. The same spider-type link is displayed when you click any of the items belonging to the chain is clicked (i.e., donor transmitter, any repeater, or any remote antenna).
11.2.6.4 Creating Several Repeaters In Atoll, the characteristics of each repeater are stored in the Repeaters table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document. To paste the information into the Repeaters table: 1. Open the Repeaters table as explained in "Opening the Repeaters Table" on page 999. 2. Copy the data from the source document and paste it into the Repeaters table. 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 77.
11.2.6.5 Defining the Properties of a Repeater To define the properties of a repeater: 1. Right-click the repeater either directly on the map, or in the Repeaters table (for information on opening the Repeaters table, see "Opening the Repeaters Table" on page 999). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
You can change the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created. If the donor is a remote antenna or another repeater, then "RepZ" is preceded by "RemA_" or "RepB_" where "A" and "B" identify the donor remote antenna and the donor repeater.
•
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, a remote antenna, or another repeater. Clicking the Browse button (
• •
•
You can change the Site on which the repeater is located. Clicking the Browse button ( ) opens the Properties dialogue of the selected site. You can enter a value in the Shared antenna (coverage side) field for the repeater. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna position, you can define the position of the repeater, if it is not located on the site itself: • •
• •
) opens the Properties dialogue of the selected donor.
Relative to site: Select Relative to site, if you want to define the position of the repeater relative to the site itself and then enter the XY offsets. Coordinates: Select Coordinates, if you want to define the position of the repeater by its XY coordinates.
You can select equipment from the Equipment list. Clicking the Browse button ( ) opens the Properties dialogue of the equipment. You can change the Amplifier gain. The amplifier gain is used in the link budget to evaluate the repeater total gain.
4. Click the Donor Side tab. You can modify the following parameters: •
Under Donor-repeater link, select a Link type. •
1000
If you select Microwave link, enter the Propagation losses and continue with step 5.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
If you select Air, select a Propagation model and enter the Propagation losses or click Calculate to determine the actual propagation losses between the donor and the repeater. If you do not select a propagation model, the propagation losses between the donor transmitter and the repeater are calculated using the ITU 526-5 propagation model. When you create an off-air repeater, it is assumed that the link between the donor transmitter and the repeater has the same frequency as the network. If you want to create a remote antenna, you must select Optical fibre link.
•
If you selected Air under Donor-repeater link, enter the following information under Antenna: •
Model: The type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, you select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the remote antenna. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. You select the antenna model to use from the Available Antennas. and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the remote antenna.
•
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of building. Mechanical Azimuth and Mechanical Downtilt display additional antenna parameters. You can click the Calculate button to update the mechanical azimuth and mechanical downtilt values after changing the repeater donor side antenna height or the repeater location. If you choose another site or change site coordinates in the General tab, click Apply before clicking the Calculate button.
•
If you selected Air under Donor-repeater link, enter the following information under Feeders: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. 5. Click the Coverage side tab. You can modify the following parameters: • •
Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Network explorer) 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 or C⁄I service area coverage predictions. The DL total gain is applied to each power (P-CCPCH power, DwPCH power, etc.). The UL total gain is applied to each terminal power. The total gains take into account losses between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses), amplification gain, and coverage characteristics (coverage antenna gain and transmission feeder losses).
•
Under Antennas, you can modify the following parameters: •
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of building. Main antenna: Under Main antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, you select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the remote antenna. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. You select the antenna model to use from the Available
1001
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Antennas. and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the remote antenna. • •
Mechanical 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. • • •
•
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. •
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: Working with Calculations in Atoll.
11.2.6.6 Tips for Updating Repeater Parameters Atoll provides you with a few shortcuts that you can use to change certain repeater parameters: • •
You can update the calculated azimuths and downtilts of the donor-side antennas of all repeaters by selecting Repeaters > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu. You can update the UL and DL total gains of all repeaters by selecting Repeaters > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected repeaters by creating a custom Boolean field named "FreezeTotalGain" in the Repeaters table and setting the value of the field to "True." Afterwards, when you select Repeaters > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for repeaters with the custom field "FreezeTotalGain" set to "False."
• •
You can update the propagation losses of all off-air repeaters by selecting Repeaters > Calculate Donor Side Propagation Losses from the Transmitters context menu. You can select a repeater on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
11.2.7 Creating a Remote Antenna Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder cable. A remote antenna is connected to the base station with an optical fibre. Remote antennas allow you to ensure radio coverage in an area without a new base station. In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a remote antenna, as opposed to a repeater, does not have any equipment and generates no amplification gain nor noise. In certain cases, you may want to model a remote antenna with equipment or a remote antenna connected to a base station that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a Repeater" on page 998.
1002
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
In calculations, remote antennas are transparent to the donor transmitters and the served users. For example, beamforming smart antennas at donor transmitters create beams directly towards the served users, and not towards the remote antenna that covers the users. This results in a combined signal level received from the transmitter using the smart antenna and from the remote antenna. If this approach does not match how your equipment works, you must not assign smart antennas to transmitters with remote antennas and vice versa. In this section, the following are explained: • • • • •
"Opening the Remote Antennas Table" on page 1003. "Placing a Remote Antenna on the Map Using the Mouse" on page 1003. "Creating Several Remote Antennas" on page 1003. "Defining the Properties of a Remote Antenna" on page 1004. "Tips for Updating Remote Antenna Parameters" on page 1005.
11.2.7.1 Opening the Remote Antennas Table Repeaters and their defining parameters are stored in the Remote Antennas table. To open the Remote Antennas table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Remote Antennas > Open Table from the context menu. The Remote Antennas table appears.
11.2.7.2 Placing a Remote Antenna on the Map Using the Mouse In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it to an existing base station without antennas, or have Atoll automatically create a new site. To create a remote antenna and place it using the mouse: 1. Select the donor transmitter. You can select it from the Transmitters folder in the Network explorer, or directly on the map. Ensure that the remote antenna’s donor transmitter does not have any antennas.
2. Click the arrow next to the New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
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 the same symbol and colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its tip text and label display the same information as displayed for the donor transmitter. As well, its tip text identifies the remote antenna and the donor transmitter. For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote Antenna" on page 1004. •
•
When the donor is a transmitter, you can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. You can hide the link by clicking it again. When the donor is a repeater or a remote antenna, Atoll displays a spider-type link showing the entire chain down to the donor transmitter. The same spider-type link is displayed when you click any of the items belonging to the chain is clicked (i.e., donor transmitter, any repeater, or any remote antenna).
11.2.7.3 Creating Several Remote Antennas In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in your current Atoll document.
1003
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To paste the information into the Remote Antennas table: 1. Open the Remote Antennas table as explained in "Opening the Remote Antennas Table" on page 1003. 2. Copy the data from the source document and paste it into the Remote Antennas table. The table you copy data from must have the same column layout as the table you are pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
11.2.7.4 Defining the Properties of a Remote Antenna To define the properties of a remote antenna: 1. Right-click the remote antenna either directly on the map, or in the Remote Antennas table (for information on opening the Remote Antennas table, see "Opening the Remote Antennas Table" on page 1003). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RemZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned as the remote antenna is created. If the donor is a repeater or another remote antenna, then "RemZ" is preceded by "RepA_" or "RemB_" where "A" and "B" identify the donor repeater and the donor remote antenna.
•
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another remote antenna or a repeater. Clicking the Browse button (
• •
•
) opens the Properties dialogue of the selected donor.
You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens the Properties dialogue of the selected site. You can enter a value in the Shared Antenna (coverage side) field for the remote antenna. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna position, you can define the position of the remote antenna, if it is not located on the site itself: • •
Relative to site: Select Relative to site, if you want to define the position of the remote antenna relative to the site itself and then enter the XY offsets. Coordinates: Select Coordinates, if you want to define the position of the remote antenna by its XY coordinates. A remote antenna does not have equipment.
4. Click the Donor Side tab. You can modify the following parameters: •
Under Donor-repeater link, select Optical fibre link and enter the Fibre losses.
5. Click the Coverage Side tab. You can modify the following parameters: • •
Select the Active check box. Only active remote antennas (displayed with in red in the Transmitters folder in the Network explorer) are calculated. 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 Eb⁄Nt or C⁄I service area coverage predictions. The DL total gain is applied to each power (P-CCPCH power, DwPCH power, etc.). The UL total gain is applied to each terminal power. The total gains take into account losses between the donor transmitter and the remote antenna.
1004
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
Under Antennas, you can modify the following parameters: •
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the remote antenna is situated on a building, the height entered must include the height of the building. Main antenna: Under Main antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, you select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the remote antenna. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. You select the antenna model to use from the Available Antennas. and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the remote antenna.
• •
Mechanical 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. • • •
•
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. 6. Click the Propagation tab. As remote antennas are taken into account during calculations, you must set propagation parameters as with transmitters. On the Propagation tab, you can modify the Propagation model, Radius, and Resolution for both the Main matrix and the Extended matrix. By default, the propagation characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
11.2.7.5 Tips for Updating Remote Antenna Parameters Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters: •
You can update the UL and DL total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected remote antennas by creating a custom Boolean field named "FreezeTotalGain" in the Remote Antennas table and setting the value of the field to "True." Afterwards, when you select Remote Antennas > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for remote antennas with the custom field "FreezeTotalGain" set to "False."
•
You can select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
11.2.8 Setting the Working Area of an Atoll Document When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the sites that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of sites covered by a coverage prediction, each with its own advantages:
1005
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
•
© Forsk 2012
Filtering the desired sites You can simplify the selection of sites to be studied by using a filter. You can filter sites according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 107. 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 95.
•
Setting a computation zone Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated predictions in order to see the effects of small changes in site configuration, the savings in time is considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc., while the focus zone or hot spot is the area taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 1014.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.
11.2.9 Studying a Single Base Station As you create a base station, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of sites can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the base station you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of base stations once you have optimised the settings for each individual base station. Before studying a base station, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Atoll enables you to assign both a main propagation model, with a shorter radius and a higher resolution, and an extended propagation model, with a longer radius and a lower resolution. By using a calculation radius, Atoll limits the scope of calculations to a defined area. By using two matrices, Atoll allows you to calculate high resolution path loss matrices closer to the transmitter, while reducing calculation time by using an extended matrix with a lower resolution. You can assign a propagation model to all transmitters at once, to a group of transmitters, or to a single transmitter. Assigning a propagation model is explained in "Assigning a Propagation Model" on page 1012. In this section, the following are explained: • •
"Making a Point Analysis to Study the Profile" on page 1006. "Studying Signal Level Coverage" on page 1007.
11.2.9.1 Making a Point Analysis to Study the Profile In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a TD-SCDMA user. Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on each selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 1012. 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 Planning toolbar. The Point Analysis Tool window appears and the
) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: • • •
Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: • •
Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. Target Site: Select a site from the list to place the receiver directly on a site.
4. Select the Profile view.
1006
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
The profile analysis appears in the Profile view of the Point Analysis window. The altitude (in metres) is reported on the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some propagation models using a 3 knife-edge Deygout diffraction method, the results may display two additional attenuations peaks. The total attenuation is displayed above the main peak. Details of the analysis are displayed at the top of the Profile view: • • • •
The received signal strength of the selected transmitter The propagation model used The shadowing margin and the indoor loss (if selected) The distance between the transmitter and the receiver.
You can change the following options using the Profile view toolbar: • • •
Transmitter: Select the transmitter from the list. You can click the Properties button ( ) to open the transmitter properties dialogue. 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. Options: Click the Options button ( • • • •
) to display the Calculation Options dialogue. In this dialogue, you can:
Change the X and Y coordinates to change the current position of the receiver. Select the Shadowing taken into account check box and enter a Cell edge coverage probability. Select Signal level, Path loss, or Total losses from the Result type list. You can select the Indoor coverage check box to add indoor losses.
•
Geographic Profile: Click the Geographic Profile button ( ) if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate or display signal levels and losses.
•
Link Budget: Click the Link Budget button (
•
Detailed Report: Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis. The detailed report is only available for the Standard Propagation Model.
) to display a dialogue with the link budget.
Figure 11.14: Point Analysis - Profile view 5. To end the point analysis, click the Point Analysis button (
) in the Radio Planning toolbar again.
11.2.9.2 Studying Signal Level Coverage As you are building your radio-planning project, you may want to check the coverage of a new base station without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction.
1007
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
This section explains how to calculate the signal level coverage of a single base station. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. You can use the same procedure to study the signal level coverage of several sites by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 89. To study the signal level coverage of a single base station: 1. Select the Network explorer. 2. Right-click the Transmitters folder and select Group By > Site from the context menu. The transmitters are now displayed in the Transmitters folder by the site on which they are situated. If you want to study only sites by their status, you can 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: • •
Select a Propagation model. Enter a Radius and Resolution.
f. 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 Prediction from the context menu. The Prediction Types dialogue appears. The Prediction Types dialogue lists the coverage predictions available. They are divided into Standard Predictions, supplied with Atoll, and Customised Predictions. Unless you have already created some customised coverage predictions, the Customised Predictions list will be empty. 5. Select Coverage by 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 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:
1008
Size of the Coverage Prediction
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
Size of the Coverage Prediction
Display Resolution
Country
According to the size of the country
Conditions tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel (see Figure 11.15). You can set: • • •
•
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add (P-CCPCH RSCP threshold) defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
Timeslot: The coverage prediction by P-CCPCH 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 11.15: 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. • • •
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 43.
•
You can create tip text with information about the coverage prediction by clicking the Browse button ( next to the Tip text box and selecting the fields you want to display in the tip text. You can select the Add to legend check box to add the displayed value intervals to the legend.
•
)
If you change the display properties of a coverage prediction after you have calculated it, you may make the coverage prediction invalid. You will then have to recalculate the coverage prediction to obtain valid results. 7. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
1009
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The P-CCPCH RSCP coverage prediction can be found in the Predictions folder in the Network explorer. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button (
) beside the coverage prediction in the Predictions
), Atoll only calculates unlocked coverage predictions (
).
11.2.10 Studying Base Stations When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Figure 11.16 gives an example of a computation zone. In Figure 11.16, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction. Site 130 is within the coverage zone but has no active transmitters. Therefore, it will not be taken into consideration either.
Figure 11.16: 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.16) 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: • • • • • • • • • •
1010
"Path Loss Matrices" on page 1011 "Assigning a Propagation Model" on page 1012 "The Calculation Process" on page 1014 "Creating a Computation Zone" on page 1014 "Setting Transmitters or Cells as Active" on page 1015 "Signal Level Coverage Predictions" on page 1016 "Analysing a Coverage Prediction" on page 1024 "Signal Quality Coverage Predictions" on page 1032 "HSDPA Quality and Throughput Analysis" on page 1052 "Printing and Exporting Coverage Prediction Results" on page 1054.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
11.2.10.1 Path Loss Matrices In addition to the distance between the transmitter and the receiver, path loss is caused by objects in the transmitter-receiver path. In Atoll, the path loss matrices must be calculated before predictions and simulations can be made. Storing Path Loss Matrices Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radioplanning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: • • •
One file per transmitter with the extension LOS for its main path loss matrix. A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions 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 Private directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally. Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private Directory.
When you save the path loss files externally, the external files are updated as soon as calculations are performed. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it, if you have updated the path loss matrices. •
Shared directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see the Administrator Manual.
5. Click OK. Checking the Validity of Path Loss Matrices Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears.
1011
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available results table. You have the following display options: • •
Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available results table lists the following information for each displayed path loss matrix: • • • • • •
Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: Whether or not the path loss matrix is valid. 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.
5. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 11.17) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.
Figure 11.17: Path loss matrices statistics
11.2.10.2 Assigning a Propagation Model In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 1014, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 1013, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 1013, this is the propagation model that will be used for all transmitters, except for those to which you will later assign a propagation model either individually or as part of a group. When you assign a propagation model globally, you override any selection you might have already made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 201, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following are explained: • •
1012
"Assigning a Propagation Model to All Transmitters" on page 1013. "Assigning a Propagation Model to a Group of Transmitters" on page 1013.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
"Assigning a Propagation Model to One Transmitter" on page 1014.
For more information about the available propagation models, see Chapter 5: Working with Calculations in Atoll. Assigning a Propagation Model to All Transmitters In Atoll, you can choose a propagation model for a single transmitter or globally for all transmitters. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. 5. Under Main matrix: • •
Select a Propagation model Enter a Radius and Resolution.
6. If desired, under Extended matrix: • •
Select a Propagation model Enter a Radius and Resolution.
7. Click OK. The selected propagation models will be used for all transmitters. Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 1014 will override this entry.
Assigning a Propagation Model to a Group of Transmitters Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters and then assigning the propagation model. To define a main and extended propagation model for a defined group of transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. From the Group By submenu of the context menu, select the property by which you want to group the transmitters. The objects in the folder are grouped by that property. You can group transmitters by several properties by using the Group By button in the Properties dialogue. For more information, see "Advanced Grouping" on page 90.
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 Main resolution Extended propagation model Extended calculation radius Extended resolution
To enter the same values in one column for all transmitters in the table: 1. Enter the value in the first row in the column. 2. Select the entire column.
1013
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69. Assigning a Propagation Model to One Transmitter If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main matrix: • •
Select a Propagation model. Enter a Radius and Resolution.
7. If desired, under Extended matrix: • •
Select a Propagation model. Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter.
11.2.10.3 The Calculation Process When you create a coverage prediction and click the Calculate button (
), Atoll follows the following process:
1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button (
).
3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( Predictions folder. •
You can stop any calculations in progress by clicking the Stop Calculations button (
•
) in the toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.
11.2.10.4 Creating a Computation Zone To create a computation zone: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Computation Zone. The context menu appears. 4. From the context menu, select one of the following:
1014
) beside the coverage predictions in the
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
Draw Polygon i.
Click once on the map to start drawing the zone.
ii. Click once on the map to define each point on the map where the border of the zone changes direction. iii. Click twice to finish drawing and close the zone. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the zone.
ii. Drag to the opposite corner of the rectangle that will define the zone. When you release the mouse, the zone will be created from the rectangle defined by the two corners. The computation zone is delimited by a red line. If you clear the computation zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a computation zone as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the 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. You can also combine an existing computation zone with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Computation Zone from the context menu. 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 in the Geo explorer and selecting Import from the context menu. Fit Zone to Map Window: You can create a computation zone the size of the map window by right-clicking the Computation Zone in the Geo explorer and selecting Fit Zone to Map Window from the context menu. You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the computation zone in the user configuration: For information on saving the computation zone in the user configuration, see "Saving a User Configuration" on page 101. Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone in the Geo explorer and selecting Export from the context menu.
11.2.10.5 Setting Transmitters or Cells as Active When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Therefore, before you define a coverage prediction, you must ensure that all the transmitters on the base stations you want to study have been activated. In the explorer window, active transmitters are indicated with a red icon (
) in the Transmitters folder
and with the defined colour on the map and inactive transmitters are indicated with an empty icon ( folder and on the map.
) in the Transmitters
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 zone’s context menu. To set an individual transmitter as active: 1. Select the Network explorer. 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. Select the Network explorer. 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 rightclick the group of transmitters you want to set as active. The context menu appears.
1015
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table. The Transmitters table appears with each transmitter’s 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. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cell’s 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. Select the Geo explorer. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder. 3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 54.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Working with Calculations in Atoll. Calculating path loss matrices can be 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.10.6 Signal Level Coverage Predictions Atoll offers a series of coverage predictions that are based on the received signal code power (RSCP) level per pixel. The RSCP can be the P-CCPCH RSCP on TS0, the DwPCH RSCP on the DwPTS timeslot, or the UpPCH RSCP on the UpPTS timeslot. Coverage predictions based on interference and network load conditions are covered in "Signal Quality Coverage Predictions" on page 1032, and "HSDPA Quality and Throughput Analysis" on page 1052. Once you have created and calculated a coverage prediction, you can use the coverage prediction’s context menu to make the coverage prediction into a customised prediction which will appear in the Prediction Types dialogue. You can also select Duplicate from the coverage prediction’s context menu to create a copy. By duplicating an existing prediction that has the parameters you want to study, you can create a new coverage prediction more quickly than by creating a new coverage prediction. If you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the coverage prediction with the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the calculated coverage prediction. You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to load it into a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predictions are saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations, see "Saving a User Configuration" on page 101. The following standard coverage predictions are explained in this section: • • • • •
1016
"Making a Coverage Prediction by P-CCPCH RSCP" on page 1017. "Making a Coverage Prediction by P-CCPCH Best Server" on page 1018. "Making a P-CCPCH Pollution Coverage Prediction" on page 1019. "Making a Coverage Prediction by DwPCH RSCP" on page 1021. "Making a Coverage Prediction by UpPCH RSCP" on page 1022.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
11.2.10.6.1
Making a Coverage Prediction by P-CCPCH RSCP A coverage prediction by P-CCPCH RSCP allows you to predict the signal strength (received signal code power) of the pilot channel (TS0) using the main antenna of the transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by P-CCPCH RSCP: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by P-CCPCH RSCP and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.18). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set the following: • • • •
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add (P-CCPCH RSCP threshold) defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist on a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
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 11.18: 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 43. You can also set parameters to display the following results:
1017
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
• •
© Forsk 2012
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. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.19).
Figure 11.19: Coverage prediction by P-CCPCH RSCP
11.2.10.6.2
Making a Coverage Prediction by P-CCPCH Best Server A P-CCPCH best server coverage prediction allows you to predict which transmitter has the highest P-CCPCH RSCP at each pixel. The coverage prediction is performed for TS0 using the main antenna of the transmitter. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by P-CCPCH best server: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by P-CCPCH Best Server and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 11.18). On the Conditions tab, you can define the signals that will be considered for each pixel. On the Conditions 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 service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add (P-CCPCH RSCP threshold) defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a trans-
1018
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
mitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters. • • •
Timeslot: The coverage prediction by P-CCPCH best server is performed for TS0. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 11.20: 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.21).
Figure 11.21: Coverage prediction by P-CCPCH best server
11.2.10.6.3
Making a P-CCPCH Pollution Coverage Prediction A P-CCPCH pollution coverage prediction calculates the pixels that are, for a defined condition, covered by the P-CCPCH signal of at least two transmitters. The coverage prediction considers the P-CCPCH RSCP (TS0) transmitted using the main antenna of the transmitters.
1019
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To make a P-CCPCH pollution coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select P-CCPCH Pollution Analysis 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.22). On the Conditions tab, you can define the signals that will be considered for each pixel. On the Conditions 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 service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add (P-CCPCH RSCP threshold) defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • • •
Timeslot: The 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 11.22: 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: •
1020
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.23). By changing the parameters selected on the Conditions tab and by selecting different results to be displayed on the Display tab, you can calculate and display information other than that which has been explained in the preceding sections.
Figure 11.23: P-CCPCH pollution coverage prediction
11.2.10.6.4
Making a Coverage Prediction by DwPCH RSCP A coverage prediction by DwPCH RSCP allows you to predict the signal strength of the DwPCH channel (DwPTS timeslot) using the main antenna of the transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. To make a coverage prediction by DwPCH RSCP: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by DwPCH RSCP and click OK. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.24). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set: • • • •
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. The DwPCH RSCP threshold defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest DwPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
1021
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
• • •
© Forsk 2012
Timeslot: The coverage prediction by DwPCH RSCP is performed for DwPTS timeslot. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 11.24: 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 43. 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. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.25).
Figure 11.25: Coverage prediction by DwPCH RSCP
11.2.10.6.5
Making a Coverage Prediction by UpPCH RSCP A coverage prediction by UpPCH RSCP allows you to predict the signal strength of the UpPCH channel (UpPTS timeslot) using the main antenna of the transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range.
1022
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
To make a coverage prediction by UpPCH RSCP: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by UpPCH RSCP and click OK. The Coverage by UpPCH RSCP 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.26). 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 service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. UpPCH RSCP threshold defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
Timeslot: The coverage prediction by UpPCH RSCP is performed for UpPTS timeslot. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 11.26: 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 43. 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.
1023
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.27).
Figure 11.27: Coverage prediction by UpPCH RSCP
11.2.10.7 Analysing a Coverage Prediction Once you have completed a prediction, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 1007). If several coverage predictions are displayed on the map, it can be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following tools are explained: • • • • • •
11.2.10.7.1
"Displaying the Legend Window" on page 1024. "Displaying Coverage Prediction Results Using Tip Text" on page 1024. "Using the Point Analysis Reception View" on page 1025. "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1025. "Viewing Coverage Prediction Statistics" on page 1028. "Comparing Coverage Predictions: Examples" on page 1029.
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: •
11.2.10.7.2
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction identified by the name of the coverage prediction.
Displaying Coverage Prediction Results Using Tip Text You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 6. of "Studying Signal Level Coverage" on page 1007). To get coverage prediction results in the form of tip text: •
1024
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined in the Display tab of the coverage prediction properties (see Figure 11.28).
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Figure 11.28: Displaying coverage prediction results using tip text
11.2.10.7.3
Using the Point Analysis Reception View Once you have calculated the coverage prediction, you can use the Point Analysis tool. 1. Click the Point Analysis button ( pointer changes (
) in the Radio Planning toolbar. The Point Analysis window appears and the
) to represent the receiver.
2. At the bottom of the Point Analysis window, select the Reception view (see Figure 11.29). The predicted signal level from different transmitters is reported in the Reception view in the form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they represent. A thick black line from the receiver to its best server is also displayed in the map window. The best server of the receiver is the transmitter from which the receiver receives the highest signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer location is displayed in the tip text. 3. At the top of the Reception view, select the carrier to be analysed.
Figure 11.29: Point Analysis - Reception view 4. Click the Options button (
) in the Reception view toolbar. The Calculation Options dialogue appears.
a. Edit the X and Y coordinates to change the present position of the receiver. b. Select the Shadowing taken into account check box and enter a Cell edge coverage probability. c. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per clutter class. d. Click OK to close the Calculation Options dialogue. 5. Click the Point Analysis button (
11.2.10.7.4
) on the Radio Planning toolbar again to end the point analysis.
Creating a Focus Zone or Hot Spot for a Coverage Prediction Report The focus zone and hot spots define an area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spots in addition to the focus zone. It is important not to confuse the computation zone and the focus zone and hot spots. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc., while the focus zone and hot spots are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spots.
1025
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To define a focus zone or hot spot: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Focus Zone or Hot Spots, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the focus zone or hot spot.
ii. Click once on the map to define each point on the map where the border of the focus zone or hot spot changes direction. iii. Click twice to finish drawing and close the focus zone or hot spot. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the focus zone or hot spot.
ii. Drag to the opposite corner of the rectangle that will define the zone. When you release the mouse, the focus zone or hot spot will be created from the rectangle defined by the two corners. A focus zone is delimited by a green line; a hot spot is delimited by a heavy black line. If you clear the zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a focus zone or hot spot as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a focus zone or hot spot by right-clicking it and selecting Use As > Focus Zone or Use As > Hot Spot from the context menu. You can also combine an existing focus zone or hot spot with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Hot Spot or Add To > Hot Spot from the context menu. 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. You can import it by right-clicking the Focus Zone or Hot Spots in the Geo explorer and selecting Import from the context menu. When you import hot spots, you can import the name given to each zone as well. Fit Zone to Map Window: You can create a focus zone or hot spot the size of the map window by selecting Fit Zone to Map Window from the context menu. You can save the focus zone or hot spots, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the focus zone in the user configuration: For information on saving the focus zone in the user configuration, see "Saving a User Configuration" on page 101. Exporting the focus zone or hot spots: You can export the focus zone or hot spots by right-clicking the Focus Zone or the Hot Spots in the Geo explorer and selecting Export from the context menu.
You can include population statistics in the focus zone or hot spot by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137.
11.2.10.7.5
Displaying a Coverage Prediction Report Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage prediction’s Properties dialogue. The coverage prediction report is displayed in a table. For information on working with tables, see "Working with Data Tables" on page 69. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 74. Atoll bases the report on the area covered by the focus zone and hot spots; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot must be defined before you display a report; it is not necessary to define it before calculating coverage. The focus zone or hot spot does not, however, need to be visible; even if it is not displayed, Atoll will take it into account
1026
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
when generating the report. For information on defining a focus zone or hot spot, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1025. Once you have generated a report, you can export it to a text file or to an Excel spreadsheet. For more information on exporting a coverage prediction report, see "Exporting a Coverage Prediction Report" on page 1028. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Predictions folder. 3. Right-click the coverage prediction for which you want to generate a report. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Define the format and content of the report: You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down.
to move it up or
You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spots and on the focus zone if available or on the hot spots and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Select the Network explorer. 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.
to move it up or
You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spots by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137. 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.
1027
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To include population statistics in the focus zone or hot spots: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. 2. Select the Network explorer. 3. Right-click the Predictions folder. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Select the following columns, where "Population" is the name of the folder in the Geo explorer 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.
6. 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 154.
11.2.10.7.6
Exporting a Coverage Prediction Report Once you have generated a coverage prediction report as explained in "Displaying a Coverage Prediction Report" on page 1026, you can export it to a text file or to a spreadsheet. To export a coverage prediction report: 1. Right-click the report and select Export from the context menu or click the Export button ( The Save As dialogue appears.
) in the Table toolbar.
2. In the Save As dialogue, enter the File name and select the format from the Save as type list: • • • •
TXT: To save the report as a text file. CSV: To save the report as a comma-separated values file. XLS: To save the report as an Excel spreadsheet. XML Spreadsheet 2003: To save the report as an XML spreadsheet.
3. Click Save to export the coverage prediction report.
11.2.10.7.7
Viewing Coverage Prediction Statistics Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage prediction colours, interval steps, and shading as defined on the Display tab of the coverage prediction’s Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spots are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before calculating coverage. For information on defining a focus zone, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1025. To display the statistics on a coverage prediction: 1. Select the Network explorer. 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.30). • •
•
1028
Under Histogram based on covered areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Zoom on selected values section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. You can copy the graph by clicking the Copy button.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
• •
You can print the graph by clicking the Print button. Under Statistics based on prediction conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.
Figure 11.30: Histogram of a coverage prediction by signal level
11.2.10.7.8
Comparing Coverage Predictions: Examples Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison in one of the following ways: • •
•
Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both predictions are displayed in red). Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and pixels covered by only one prediction are blue). Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for example, pixels covered by both predictions are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).
To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction. 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 1029. "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 1031.
Example 1: Studying the Effect of a New Base Station If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can verify if a newly added base station improves coverage. A coverage prediction by P-CCPCH RSCP for the current network is made as described in "Making a Coverage Prediction by PCCPCH RSCP" on page 1017. The results are displayed in Figure 11.31. An area with poor coverage is visible on the right side of the figure.
1029
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Figure 11.31: 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 TD-SCDMA Base Station" on page 980, or by using a station template, as explained in "Placing a New Base Station Using a Station Template" on page 989. 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 11.32).
Figure 11.32: Coverage prediction by P-CCPCH RSCP of the network with a new base station Now you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties 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: • • •
1030
Intersection Union Difference
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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.33, shows clearly the area covered only by the new base station.
Figure 11.33: Comparison of both coverage predictions by P-CCPCH RSCP Example 2: Studying the Effect of a Change in Transmitter Tilt If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can see how modifying transmitter tilt can improve coverage. A coverage prediction by P-CCPCH best server for the current network is made as described in "Making a Coverage Prediction by P-CCPCH Best Server" on page 1018. The results are displayed in Figure 11.34. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated by a red oval in Figure 11.34.
Figure 11.34: Coverage prediction by P-CCPCH best server for the existing network You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and electrical tilt of the antenna are defined on the Transmitter tab of the Properties 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 11.35).
1031
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Figure 11.35: Coverage prediction by P-CCPCH best server of the network after modifications As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change in coverage, you can compare the two predictions. To compare two predictions: 1. Right-click one of the two predictions. The context menu appears. 2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you want to compare with the first. The Comparison Properties 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 11.36, shows clearly the increase in coverage due at the change in antenna tilt.
Figure 11.36: Comparison of both coverage predictions by P-CCPCH best server
11.2.10.8 Signal Quality Coverage Predictions In TD-SCDMA, the quality of the signal and the size of the area that can be covered are influenced by the network load. As the network load increases, the area a cell can effectively cover decreases. For this reason, the network load must be defined in order to calculate signal quality coverage predictions. If you have traffic maps, you can do a Monte Carlo simulation to model power control and evaluate the network load for a generated user distribution. You can base a coverage prediction on simulation results by committing the results of a simulation to cell properties. If you do not have traffic maps, you can enter these values manually in the Cells and Cell Parameters per Timeslot tables. Atoll calculates the network load using the UL load factor and DL traffic power defined for each timeslot of each cell.
1032
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
In this section, the signal quality coverage predictions will be calculated using UL load factor and DL traffic power parameters defined at the timeslot level for each cell. For the purposes of these coverage predictions, each pixel is considered a non-interfering user with a defined timeslot, service, mobility type, and terminal. Before making a coverage prediction, you will have to set the UL load factor and DL traffic power and the parameters that define the services and users. These are explained in the following sections: • •
"Setting the UL Load Factor and the DL Traffic Power" on page 1033. "Service and User Modelling" on page 1033.
Several different types of signal quality coverage predictions, based either on Eb⁄Nt, C⁄I, or traffic channel quality, are explained in this section: • • • • •
"Making a Pilot Signal Quality Prediction" on page 1038. "Making a DwPCH Signal Quality Prediction" on page 1039. "Studying Downlink and Uplink Traffic Channel Coverage" on page 1041. "Studying Downlink and Uplink Service Areas" on page 1043. "Studying the Effective Service Area" on page 1045.
Making the following noise coverage prediction is explained: •
"Studying Downlink Total Noise" on page 1046.
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 1048. To study the interference on UpPCH when the UpPCH is shifted to a traffic timeslot, see "Studying UpPCH Interference" on page 1049.
Making another type of coverage prediction, the baton handover coverage prediction, is also explained: •
11.2.10.8.1
"Making a Baton Handover Coverage Prediction" on page 1051.
Setting the UL Load Factor and the DL Traffic Power If you are setting the UL load factor and the DL traffic power for a single transmitter, you can set these parameters on the timeslot properties dialogue available from the Cells tab of the transmitter’s Properties dialogue. However, you can set the UL load factor and the DL traffic power for all the timeslots of all cells using the Cell Parameters per Timeslot table. To set the UL load factor and the DL traffic power using the Cell Parameters per Timeslot table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Timeslots Table from the context menu. The Cell Parameters per Timeslot table appears. 4. Enter the following values: • •
DL traffic power (dBm): The value of downlink traffic power for downlink timeslots. UL load factor (%): The value of uplink load factor for uplink timeslots.
You can see the configuration of the uplink and downlink timeslots by referring to the cell’s timeslot configuration. For a definition of the values, see "Cell Description" on page 985.
11.2.10.8.2
Service and User Modelling Before you model services, you must have R99 radio bearers defined in your Atoll document. The following R99 radio bearer parameters are used in predictions: • • • •
Max TCH power (dBm) Uplink and downlink TCH RSCP thresholds per mobility Uplink and downlink TCH Eb/Nt thresholds or uplink and downlink TCH C/I thresholds per mobility The type of bearer.
For more information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 1142. In this section, the following are explained: • • •
"Modelling Services" on page 1033. "Creating a Mobility Type" on page 1035. "Modelling Terminals" on page 1036.
Modelling Services Services are the various services available to subscribers. These services can be either circuit-switched or packet-switched services. This section explains how to create a service. However, only the following parameters are used in predictions: •
R99 radio bearer parameters
1033
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
• • •
© Forsk 2012
HSPA capabilities 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 1142. To create or modify a service: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services New Element Properties dialogue appears. You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.
5. You can edit the fields on the General tab to define the new service. • •
•
Name: Atoll proposes a name for the new service, but you can change the name to something more descriptive. Activity factor: The uplink and downlink activity factors are used to determine the probability of activity for each user during Monte-Carlo simulations. For packet-switched services, this parameter is used when working with sector traffic maps and user density traffic maps. For circuit-switched services, the parameter is taken into consideration with all 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. How the average requested rate is used in Atoll depends on the type of service: •
•
•
Circuit (R99): This rate is the average rate obtained by a user of the service. It is used in simulations during user distribution generation to calculate the number of users attempting a connection and to determine their activity status. Packet (R99): This rate is the average rate obtained by a user of the service. It is used in simulations during user distribution generation to calculate the number of users attempting a connection and to determine their activity status. Packet (HSPA): This rate is the requested average rate which guarantees a minimum average rate during an HSUPA call. It is used twice in a simulation: once during user distribution generation in order to calculate the number of HSUPA users attempting a connection and then during power control as a quality target to be compared to the real obtained average throughput.
6. Click the UMTS tab to define the new service. 7. Select an R99 radio bearer from the list. If you want to edit the settings of the selected R99 radio bearer, click the Browse button (
) to open the bearer’s Properties dialogue.
8. Select a service Type: • • • •
Circuit (R99): For circuit services, select Circuit (R99). Packet (R99): For packet services that can only use R99 channels, select Packet (R99). Packet (HSDPA): For packet services that can use HSDPA channels, select Packet (HSDPA). Packet (HSPA): For packet services that can use HSDPA and HSUPA channels, select Packet (HSPA).
9. Enter Preferred or Allowed carriers: 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 the "Best" carrier 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. 10. Enter a Priority for this service. "0" is the lowest priority. 11. 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 user’s head, is estimated to be 3 dB. 12. For a Packet (HSDPA) service, enter: • •
1034
A-DPCH activity factor: The downlink 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 guarantees a minimum average rate during a call. It is used twice in a simulation: once during user distribution gener-
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
ation in order to calculate the number of HSPA 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.
13. For a Packet (HSPA) service, enter: • •
•
E-UCCH/A-DPCH activity factor: The uplink E-UCCH and downlink A-DPCH activity factors are used to estimate the average power on these channels. Average requested rate: You can enter the average requested rate for uplink and downlink. This rate guarantees a minimum average rate during a call. It is used twice in a simulation: once during user distribution generation in order to calculate the number of HSPA 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.
14. For a Packet (R99), Packet (HSDPA), and Packet (HSPA) services, click the Packet button. The Packet dialogue appears. The parameters in the Packet dialogue are used to determine the probability of activity for each user during MonteCarlo simulations. These parameters are used when working with user profile traffic maps only. In the Packet dialogue, you can set the following parameters for packet-switched services: •
Under BLER, you can define the following: •
•
Under Session, you can set: • •
•
Average number of packet calls: Enter the average number of packet calls in the uplink and downlink during one session. Average time between two packet calls: Enter the average time between two packet calls (in milliseconds) in the uplink and downlink.
Under Packet calls, you can set: • • •
•
Efficiency factor: The uplink and downlink efficiency factors are used to determine duration of usage by the user during Monte-Carlo simulations.
Min size (Kbytes): Enter the minimum size of a packet call in kilobytes in the uplink and downlink. Max size (Kbytes): Enter the maximum size of a packet call in kilobytes in the uplink and downlink. Average time between two packets (ms): Enter the average time between two packets in milliseconds in the uplink and downlink.
Under Packet, you can set: •
Size (Bytes): Enter the packet size in bytes in the uplink and downlink.
15. Click OK to save your changes and close the dialogue. Creating a Mobility Type Radio propagation conditions as well as connection properties and criteria vary with the speed the user is travelling. A mobile user travelling at a high speed and a pedestrian will not necessarily be connected to the same transmitters and both users will not experience the same service characteristics. Ec⁄I0 requirements and Eb⁄Nt or C/I targets per radio bearer and per link (up and down) are largely dependent on mobile speed. The following parameters are used in predictions: • • • • • • • •
P-CCPCH RSCP T_Add (RSCP P-CCPCH Threshold) P-CCPCH RSCP T_Drop DwPCH RSCP Threshold UpPCH RSCP Threshold P-CCPCH Eb⁄Nt Threshold or P-CCPCH C⁄I Threshold DwPCH C⁄I Threshold HS-SCCH Ec⁄Nt Threshold (DL) HS-SICH Ec⁄Nt Threshold (UL) 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 Network Settings folder’s properties dialogue. For more information, see "Network Settings" on page 1135.
1035
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To create or modify a mobility type: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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. Click the General tab. On the General tab, you can enter or modify the following parameters: • •
Name: Enter or modify the descriptive name for the mobility type. Speed: Enter or modify an average speed for the mobility type. This field is for information only; the average speed is not used in any calculation.
6. Click the TD-SCDMA tab. On the TD-SCDMA tab, you can enter or modify the following parameters: •
•
• • • •
•
Under Baton handover parameters, you can set the minimum pilot signal levels required from transmitters to enter and exit the list of potential servers. • P-CCPCH 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. P-CCPCH Eb⁄Nt threshold or P-CCPCH C⁄I threshold: Enter or modify the minimum P-CCPCH Eb⁄Nt or C⁄I quality. This value is used as the minimum requirement limit for the P-CCPCH Quality Analysis (Eb⁄Nt) or P-CCPCH Quality Analysis (C⁄I) coverage predictions. DwPCH RSCP threshold: Enter or modify the minimum signal level required for the DwPTS coverage. This value is used as the minimum requirement limit for the Coverage by DwPCH RSCP coverage prediction. DwPCH C⁄I threshold: Enter or modify the minimum DwPCH C⁄I quality. This value is used as the minimum requirement limit for the DwPCH Quality Analysis (C⁄I) coverage prediction. UpPCH RSCP threshold: Enter or modify the minimum signal level required for the UpPTS coverage. This value is used as the minimum requirement limit for the Coverage by UpPCH RSCP coverage prediction. Under HSDPA, you can set the minimum Ec/Nt levels required for HSDPA channels. • HS-SCCH Ec⁄Nt threshold (DL): Enter or modify the minimum quality required for the HSDPA link to be available. Atoll calculates the HS-SCCH Ec⁄Nt from the HS-SCCH power set in the cell properties and compares it to this threshold. This field is used only with HSDPA. • HS-SICH Ec⁄Nt threshold (UL): Enter or modify the minimum quality required for the HSDPA link to be available. Atoll calculates the HS-SICH Ec⁄Nt from the HS-SICH power set in the terminal properties and compares it to this threshold. This field is used only with HSDPA. Under HSUPA, you can set the minimum Ec/Nt levels required for E-DCH channel. • E-DCH Ec⁄Nt threshold (DL): Enter or modify the minimum quality required for the HSUPA link to be available. This field is used only with HSUPA.
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 car’s onboard navigation device. The following parameters are used in predictions: • • • • • • • • • • •
1036
Reception equipment Number of carriers supported Maximum terminal power UpPCH power Gain and losses Noise figure JD factor CDMA Rho factor HSPA capabilities UE categories HS-SICH power
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
To create or modify a terminal: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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. On the General tab, you can modify the following parameters: •
Name: You can change the name of the terminal.
6. Click the TD-SCDMA tab. On the TD-SCDMA tab, you can modify the following parameters: • • •
Reception equipment: Select a type of reception equipment from the list. For more information on reception equipment, see "Receiver Equipment" on page 1144. 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. • • •
•
Under Interference, you can set the parameters that influence interference: • •
•
• • •
Min: Set the minimum transmission power. The minimum and maximum transmission powers make up the dynamic range for uplink power control. Max: Set the maximum transmission power. UpPCH: The transmission power for the UpPTS timeslot (or the TS1 uplink timeslot in case of UpPCH shifting). 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. HSPA support: Select the type of HSPA support for this terminal if the terminal is able to use HSPA channels. You can choose between None (i.e., R99 only), HSDPA, or HSPA (i.e., HSDPA and HSUPA). For an HSDPA-capable terminal, you can set the following parameters under HSDPA: • •
UE category: The HSDPA user equipment category of the terminal. For more information on HSDPA UE categories, see "HSDPA UE Categories" on page 1145. 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.
For an HSPA-capable terminal, you can also set the following parameters under HSUPA: •
UE category: The HSUPA user equipment category of the terminal. For more information on HSUPA UE categories, see "HSDPA UE Categories" on page 1145.
7. Click OK.
11.2.10.8.3
Making Quality Coverage Predictions In Atoll, you can make several predictions to study the quality. In this section, the following quality predictions are explained: • • • • •
"Making a Pilot Signal Quality Prediction" on page 1038. "Making a DwPCH Signal Quality Prediction" on page 1039. "Studying Downlink and Uplink Traffic Channel Coverage" on page 1041. "Studying Downlink and Uplink Service Areas" on page 1043. "Studying the Effective Service Area" on page 1045.
1037
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Making a Pilot Signal Quality Prediction A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is received sufficiently well. Atoll calculates the best pilot quality received on each pixel. Then, depending on the prediction definition, it compares this value either to the P-CCPCH Eb⁄Nt or C⁄I threshold defined for the selected mobility type. The pixel is coloured if the condition is fulfilled (in other words, if the received pilot quality is better than the P-CCPCH Eb⁄Nt or C⁄I threshold). The total noise, Nt, includes the pilot power (P-CCPCH power). The processing gain used for the Eb⁄Nt coverage prediction is the one defined on the Global Parameters tab of the Network Settings Properties dialogue. For more information on the global parameters, see "Network Settings" on page 1135. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type. To make a pilot signal quality prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select P-CCPCH Quality Analysis (Eb⁄Nt) or P-CCPCH Quality Analysis (C⁄I) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.37). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set: • • • •
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH Eb⁄Nt threshold or P-CCPCH C⁄I threshold defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
Timeslot: The P-CCPCH reception analysis predictions are performed for TS0. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 11.37: Condition settings for a P-CCPCH reception analysis (Eb⁄Nt) coverage prediction
1038
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
7. Click the Display tab. For a pilot signal quality prediction, the Display type "Value intervals" based on the Field "Eb⁄Nt (dB)" or "C⁄I (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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 11.38).
Figure 11.38: P-CCPCH reception analysis (Eb⁄Nt) coverage prediction Making a DwPCH Signal Quality Prediction Atoll calculates the best DwPCH signal quality received on each pixel. Then, depending on the prediction definition, it compares this value with the DwPCH C⁄I threshold defined for the selected mobility type. The pixel is coloured if the condition is fulfilled (in other words, if the received DwPCH signal quality is better than the DwPCH C⁄I threshold). The coverage prediction is limited by the DwPCH RSCP threshold of the selected mobility type. To make a DwPCH signal quality prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select DwPCH Quality Analysis (C⁄I) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.37). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set: • • • •
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. The DwPCH C⁄I threshold defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best".
1039
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best", Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters. • • •
Timeslot: The DwPCH reception analysis (C⁄I) predictions are performed for DwPTS. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 11.39: Condition settings for a DwPCH reception analysis (C⁄I) coverage prediction 7. Click the Display tab. For a DwPCH signal quality prediction, the Display type "Value intervals" based on the Field "C⁄I (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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 11.38).
Figure 11.40: DwPCH reception analysis (C⁄I) coverage prediction
1040
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Studying Downlink and Uplink Traffic Channel Coverage Atoll calculates the received traffic channel power on the uplink or on the downlink taking into consideration the effect of any smart antenna equipment assigned to transmitters, and the smart antenna simulation results stored for the selected timeslot. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type. To make an effective service area prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select one of the following coverage predictions and click OK: • •
Coverage by TCH RSCP (DL) Coverage by TCH RSCP (UL)
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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.41). 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 service’s R99 bearer and corresponding to the selected mobility type is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
Timeslot: The coverage predictions by TCH RSCP can be performed for any downlink or uplink timeslot. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 11.41: Condition settings for a downlink TCH RSCP coverage prediction
1041
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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 43. 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 service’s 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 calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 11.42 and Figure 11.43).
Figure 11.42: Coverage prediction by downlink TCH RSCP
Figure 11.43: Coverage prediction by uplink TCH RSCP
1042
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Studying Downlink and Uplink Service Areas Atoll calculates the traffic channel quality, as defined by Eb⁄Nt or C⁄I, on the uplink or on the downlink considering the effect of any smart antenna equipment assigned to transmitters, and the smart antenna simulation results stored for the selected timeslot. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type. To make a prediction on downlink or uplink service area (Eb⁄Nt or C⁄I): 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select one of the following coverage predictions and click OK: • • • •
Service Area Analysis (Eb⁄Nt) (DL) Service Area Analysis (C⁄I) (DL) Service Area Analysis (Eb⁄Nt) (UL) Service Area Analysis (C⁄I) (UL)
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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.44). 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 Eb⁄Nt or C⁄I using the maximum power defined for the selected terminal. Service: The R99 service to be considered in the coverage prediction. The uplink TCH Eb⁄Nt threshold and downlink TCH Eb⁄Nt threshold (or uplink TCH C⁄I threshold and downlink TCH C⁄I threshold) defined for the service’s 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 Eb⁄Nt or C⁄I 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 Eb⁄Nt coverage predictions. Mobility: The mobility type to be considered in the coverage prediction. The uplink and downlink TCH Eb⁄Nt thresholds (or uplink or downlink TCH C⁄I thresholds), defined in the service selected above, corresponding to the selected mobility type are used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
Timeslot: The service area coverage predictions can be performed for any downlink or uplink timeslot. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
1043
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Figure 11.44: Condition settings for a downlink service area (Eb⁄Nt) coverage prediction 7. Click the Display tab. For a service area prediction, the Display type "Value intervals" based on the Field "Max Eb⁄Nt (dB)" or "Max C⁄I (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 43. You can also set parameters to display the following results: • • •
The traffic channel quality relative to the Eb⁄Nt or C⁄I threshold: Select "Value intervals" as the Display type and "Eb⁄Nt margin (dB)" or "C⁄I margin (dB)" as the Field. The power required to reach the Eb⁄Nt or C⁄I threshold: Select "Value intervals" as the Display type and "Required power (dB)" as the Field. Where traffic channel quality exceeds the Eb⁄Nt or C⁄I threshold for each mobility type: On the Conditions 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 calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 11.45 and Figure 11.46).
Figure 11.45: Downlink service area (Eb⁄Nt) coverage prediction
1044
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Figure 11.46: Uplink service area (Eb⁄Nt) coverage prediction Studying the Effective Service Area The goal of this coverage prediction is to identify the areas where there might be coverage problems for a service either on the downlink or on the uplink. Atoll calculates the traffic channel quality, as defined by Eb⁄Nt or C⁄I, on the uplink and on the downlink taken into consideration the effect of any smart antenna equipment assigned to transmitters, and the smart antenna simulation results stored for the selected timeslot. The effective service area is the intersection zone between the uplink and downlink service areas. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type. To make an effective service area prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Effective Service Area Analysis (Eb⁄Nt) (DL+UL) or Effective Service Area Analysis (C⁄I) (DL+UL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.47). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can define the following parameters: •
•
•
•
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. For the uplink, Atoll calculates the Eb⁄Nt or C⁄I using the maximum power defined for the selected terminal. Service: The R99 service to be considered in the coverage prediction. The uplink TCH Eb⁄Nt threshold and downlink TCH Eb⁄Nt threshold (or uplink TCH C⁄I threshold and downlink TCH C⁄I threshold) defined for the service’s 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 Eb⁄Nt or C⁄I 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 Eb⁄Nt coverage predictions. Mobility: The mobility type to be considered in the coverage prediction. The uplink TCH Eb⁄Nt threshold and downlink TCH Eb⁄Nt threshold (or uplink TCH C⁄I threshold and downlink TCH C⁄I threshold), defined in the selected service’s R99 bearer, corresponding to the selected mobility type are used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service proper-
1045
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
ties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters. • • •
Timeslot: The 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 11.47: Condition settings for an effective service area (Eb⁄Nt) 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 11.48).
Figure 11.48: Effective service area (Eb⁄Nt) coverage prediction
11.2.10.8.4
Studying Downlink Total Noise This coverage prediction enables you to study the downlink total noise. In the Coverage by Total Noise Level (DL) prediction, Atoll calculates and displays the areas where the downlink total noise exceeds a set threshold. The downlink total noise is based on the cumulate effect of all downlink powers, including P-CCPCH.
1046
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
To make a downlink total noise prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Total Noise Level Analysis (DL) and click OK. The Total Noise Level Analysis (DL) 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.49). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set: • • • •
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The downlink total noise calculation does not depend on the mobility type. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best", Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
Timeslot: The downlink total noise coverage predictions can be performed for any downlink timeslot. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 11.49: 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
1047
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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 11.50).
Figure 11.50: Downlink total noise coverage prediction
11.2.10.8.5
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 1048. "Studying UpPCH Interference" on page 1049.
Studying Cell-to-Cell Interference If cells have different timeslot configurations assigned to them, the difference in the switching point between the uplink and the downlink parts of the subframe might cause interference between the two links, up and down, i.e., on the same timeslot, a cell receiving data in the uplink is interfered by nearby cells transmitting in the downlink. The Cell to Cell Interference Zones coverage prediction displays the level of interference received by a cell. The coverage prediction sums the interfering signals in the downlink received by the victim cell in the uplink over the selected timeslot. Interference is calculated using the total transmitted power of the timeslot. To make a cell-to-cell interference zones coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Cell to Cell Interference Zones and click OK. The Cell to Cell Interference Zones Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group By button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Conditions tab (see Figure 11.51). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set: •
1048
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
• • •
Service: The R99 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. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
Timeslot: The 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 11.51: 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 43.
7. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window. Studying UpPCH Interference UpPCH is used for uplink synchronisation (SYNC_UL). This channel is usually carried by the UpPTS timeslot. However, if the interference on UpPTS is high, there is a risk of uplink synchronisation failure, i.e., the SYNC_UL might not be detected. Unsynchronised DwPTS or TS0 timeslots of other cells might cause interference on UpPTS. Lack of synchronisation between the DwPTS or TS0 and UpPTS occurs in wide and flat areas where there are no obstacles to wave propagation. For cells located in such areas, it is possible to shift the UpPCH channel from the UpPTS to any other uplink timeslot which might be less interfered. This is called UpPCH shifting. Without shifting, the UpPCH, or UpPTS, starts at the 96th chip after the DwPCH on DwPTS. The UpPCH can be shifted to TS1, TS2, or TS3. However, in Atoll, the UpPCH can only be shifted to TS1 on the uplink. It can be shifted by selecting the corresponding timeslot configuration at cell level. If some cells in a network use UpPCH shifting, you can use this coverage prediction to study the interference generated by traffic on other cells, in other words, the mobiles connected to the TS1 uplink timeslot of other cells, on the shifted UpPCH of these cells. Atoll calculates and displays the areas where the interference on the TS1 uplink timeslot, which is used for the UpPCH, exceeds a set threshold. To make an UpPCH interference zones prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears.
1049
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select UpPCH Interference Zones and click OK. The UpPCH Interference Zones Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.52). 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 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 "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
Timeslot: The 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 11.52: 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 11.53).
1050
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Figure 11.53: UpPCH interference zones coverage prediction
11.2.10.8.6
Making a Baton Handover Coverage Prediction In the baton handover coverage prediction, Atoll calculates and displays the zones where a baton handover can be made. For a handover to be possible, there must be a potential serving transmitter, and the service chosen by the user must be available. The serving cell is first determined for each pixel. The serving cell is the one whose P-CCPCH RSCP at a given pixel is above the P-CCPCH RSCP T_Add and is the highest among all the cells that satisfy the T_Add criterion. Then, all the cells whose P-CCPCH RSCP are higher than the P-CCPCH RSCP T_Drop are added to a preliminary handover set. Next, from among the cells listed in the preliminary handover set using the P-CCPCH RSCP T_Drop, only the cells whose P-CCPCH RSCP is within the range defined by the P-CCPCH RSCP from the best server and the P-CCPCH RSCP T_Comp margin are kept in the handover set. The number of potential neighbours per pixel displayed on the map is calculated from this set. The P-CCPCH RSCP T_Comp is set per cell. To make a baton handover coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Baton Handover Zones and click OK. The prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.54). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set: • • •
•
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. P-CCPCH RSCP T_Add, and P-CCPCH RSCP T_Drop defined in the mobility properties are used to define the signal level range for transmitters to enter the preliminary handover set. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• • •
Timeslot: The baton handover coverage prediction is performed for TS0. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
1051
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Figure 11.54: 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 11.55).
Figure 11.55: Baton handover zones coverage prediction
11.2.10.9 HSDPA Quality and Throughput Analysis The HSDPA coverage prediction allows you to study HSDPA-related parameters. The parameters used as input for the HSDPA coverage prediction are the HSDPA power, and the total transmitted power for each timeslot. For information about the cell and timeslot parameters, see "Cell Description" on page 985. For information on the formulas used to calculate different throughputs, see the Technical Reference Guide. To make an HSDPA coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select HSDPA Quality and Throughput Analysis and click OK. The HSDPA Quality and Throughput Analysis Properties dialogue appears.
1052
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.56). 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 Ec⁄Nt threshold defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: You can select the carrier to be studied, or select "Best". For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select "Best," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmitters.
• •
• •
Timeslot: The 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 11.56: 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 Conditions tab, you can set the following parameters: •
The HS-PDSCH RSCP relative to the RSCP threshold: Select one of the following in the Field list: • • •
•
The HS-PDSCH Ec⁄Nt relative to the Ec⁄Nt 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 Ec⁄Nt Average HS-PDSCH Ec⁄Nt Max HS-PDSCH Ec⁄Nt
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.
1053
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
•
© Forsk 2012
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 Conditions tab, you can set the following parameters: •
The uplink and downlink A-DPCH qualities: Select one of the following in the Field list: • •
•
The HS-SCCH power, reception level, or quality: Select one of the following in the Field list: •
•
• •
HS-SCCH power: Atoll determines the HS-SCCH power required per pixel to get an HS-SCCH Ec/Nt better than the minimum required HS-SCCH Ec/Nt. The coverage is limited by the HS-SCCH Ec/Nt threshold defined for the selected mobility type. HS-SCCH RSCP: Atoll determines the HS-SCCH RSCP using the HS-SCCH power required per pixel to get an HSSCCH Ec/Nt better than the minimum required HS-SCCH Ec/Nt. The coverage is limited by the HS-SCCH Ec/Nt threshold defined for the selected mobility type. HS-SCCH Ec/Nt: Atoll determines the HS-SCCH Ec/Nt per pixel. The coverage is limited by the HS-SCCH Ec/Nt threshold defined for the selected mobility type.
The HS-SICH power, reception level, or quality: Select one of the following in the Field list: •
•
• •
Max DL A-DPCH Eb⁄Nt (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 Eb⁄Nt (dB): Atoll determines uplink A-DPCH quality at the receiver for the maximum terminal power allowed.
HS-SICH power: Atoll determines the HS-SICH power required per pixel to get an HS-SICH Ec/Nt better than the minimum required HS-SICH Ec/Nt. The coverage is limited by the HS-SICH Ec/Nt threshold defined for the selected mobility type. HS-SICH RSCP: Atoll determines the HS-SICH RSCP using the HS-SICH power required per pixel to get an HSSICH Ec/Nt better than the minimum required HS-SICH Ec/Nt. The coverage is limited by the HS-SICH Ec/Nt threshold defined for the selected mobility type. HS-SICH Ec/Nt: Atoll determines the HS-SICH Ec/Nt per pixel. The coverage is limited by the HS-SICH Ec/Nt threshold defined for the selected mobility type.
The HS-PDSCH reception level or quality: Select one of the following in the Field list: • •
HS-PDSCH RSCP: Atoll determines the HS-PDSCH RSCP using the HS-PDSCH power of the timeslot. HS-PDSCH Ec/Nt: Atoll determines the HS-PDSCH Ec/Nt using the HS-PDSCH power of the timeslot.
For information on defining display properties, see "Display Properties of Objects" on page 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the prediction, the results are displayed in the map window.
11.2.10.10 Printing and Exporting Coverage Prediction Results Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. •
•
•
Printing coverage prediction results: Atoll offers several options allowing you to customise and optimise the printed coverage prediction results. Atoll supports printing to a variety of paper sizes, including A4 and A0. For more information on printing coverage prediction results, see "Printing a Map" on page 84. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 59. Exporting coverage prediction results: In Atoll, you can export the coverage areas of a coverage prediction in raster or vector formats. In raster formats, you can export in BMP, TIF, JPEG 2000, ArcView© grid, or Vertical Mapper (GRD and GRC) formats. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 GB. In vector formats, you can export in ArcView©, MapInfo©, or AGD formats. For more information on exporting coverage prediction results, see "Exporting Coverage Prediction Results" on page 67.
11.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
1054
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
carriers, with 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. 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 Zone or Hot Spot for a Coverage Prediction Report" on page 1025. For information on grouping transmitters in the explorer window, see "Grouping Data Objects" on page 89. In this section, the following are explained: • • • • •
"Setting up N-Frequency Mode" on page 1055. "Allocating Frequencies Automatically" on page 1055. "Checking Automatic Frequency Allocation Results" on page 1056. "Allocating Carrier Types per Transmitter" on page 1056. "Checking the Consistency of the Frequency Allocation Plan" on page 1057.
11.2.11.1 Setting up N-Frequency Mode In Atoll, you can define whether transmitters are compatible with the N-frequency mode or not. To set up N-frequency mode: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table from the context menu. The Transmitters table appears. 4. In the Transmitters table, select the N-frequency mode check box for transmitters that are compatible with the Nfrequency mode and will be taken into account in the automatic frequency allocation. For more information on transmitter properties, see "Transmitter Description" on page 981. 5. Click the Close button (
) to close the table.
For more information on automatic frequency allocation, see "Allocating Frequencies Automatically" on page 1055.
11.2.11.2 Allocating Frequencies Automatically Atoll can automatically allocate master and slave carriers to N-frequency mode compatible transmitters in a TD-SCDMA network. Atoll allocates carriers to transmitters according to the distance between transmitters and their orientation (azimuths). Two automatic allocation features are available: one for the allocation of all the carriers in co-N-frequency and diff-N-frequency modes, and another for the allocation of master carriers. To automatically allocate all carriers: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select N-Frequency Mode > Automatic Allocation of All Carriers from the context menu. The Automatic Carrier Allocation dialogue appears. 4. Select the carrier allocation strategy: •
Co-N-frequency allocation: The same carriers are allocated to cells of N-frequency mode compatible co-site transmitters. Co-site transmitters using different frequency bands are not allocated carriers in co-N-frequency mode.
•
Diff-N-frequency allocation: Different carriers are allocated to cells of N-frequency mode compatible co-site transmitters.
5. Click Calculate. 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 transmitter’s 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.
1055
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select 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 Calculate. 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 transmitter’s 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.
11.2.11.3 Checking Automatic Frequency Allocation Results You can verify the results of automatic frequency allocation in the following ways: • •
11.2.11.3.1
"Displaying Frequency Allocation on the Map" on page 1056. "Displaying the Coverage of the Master Carrier" on page 1056.
Displaying Frequency Allocation on the Map You can view the master carrier allocation directly on the map. Atoll can display the master carrier number for every Nfrequency compatible transmitter. To display the master carrier number on the map: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. 4. Click the Display tab. 5. Select "Discrete values" as Display type and "Cells: Carrier type" as Field. 6. Select "Cells: Carrier type" as Label. 7. Click OK. The transmitters are coloured according to the carrier type, and the master carrier number is displayed on the map with each transmitter.
11.2.11.3.2
Displaying the Coverage of the Master Carrier By combining the display characteristics of a coverage prediction with the carrier type display options, Atoll can display the coverage areas of a transmitter’s master carrier. To display the coverage of the master carrier of a transmitter: •
Create, calculate, and display a coverage prediction by P-CCPCH best server, with the Display type set to "Discrete values" and the Field set to "Cells: Carrier type". For information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 1018.
11.2.11.4 Allocating Carrier Types per Transmitter Although you can let Atoll allocate frequencies and carrier types automatically, you can adjust the overall allocation of carriers by allocating carrier types to transmitters using the Cells tab of the Transmitter Properties dialogue. To allocate TD-SCDMA carrier types using the Cells tab of the transmitter’s Properties dialogue: 1. On the map, right-click the transmitter whose carrier types you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, there is a column for each cell. Select the carrier type for each cell of the transmitter from the Carrier type list.
1056
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
5. Click OK.
11.2.11.5 Checking the Consistency of the Frequency Allocation Plan You can perform an audit of the current frequency allocation plan. To perform an audit of the allocated frequency plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select N-Frequency Mode > Audit from the context menu. The N-Frequency Mode Audit dialogue appears. 4. The audit checks the following points: •
Master carriers: • • •
•
Stand-alone carriers: •
•
Transmitters in N-frequency mode: The transmitters that are not N-frequency mode compatible. One master carrier per transmitter: The transmitters that have either no or more than one master carrier. Defined P-CCPCH power: The transmitters whose master carriers do not have a P-CCPCH power defined. Defined P-CCPCH power: The transmitters whose stand-alone carriers do not have a P-CCPCH power defined.
Slave Carriers: • • •
Linked to a master carrier: The transmitters whose slave carriers are not linked to any master carrier. In other words, the transmitters that do not have any master carrier, but have slave carriers. P-CCPCH, DwPCH, and Other CCH fields empty: The transmitters whose slave carriers have P-CCPCH, DwPCH, and other CCH powers defined. Timeslot configurations, Scrambling codes, and Neighbours same as the master carrier: Select this check box if you want the audit to check for slave carriers that do not have the same timeslot configurations, scrambling codes, and neighbours as the master carrier.
5. Click Calculate. Atoll performs the audit and lists the results under Problems occurred during the audit: X transmitters have inconsistencies, where X is the number of transmitters with problems. The list includes: • • • • • • •
Several master carriers: Transmitters that have more than one master carrier. Master P-CCPCH power not defined: Transmitters whose master carrier does not have a P-CCPCH power defined. Stand-alone P-CCPCH power not defined: Transmitters whose stand-alone carriers do not have P-CCPCH powers defined. Slaves without masters: Transmitters that have only slave carriers and no master carrier. Slave power defined: Transmitters whose slave carriers have P-CCPCH, DwPCH, or other CCH powers defined. Master-slave attribute differences: Transmitters whose slave carriers have different timeslot configurations, scrambling codes, and neighbours than the master carrier. Inconsistency: N-frequency mode⁄carrier 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.
11.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 define. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as potential neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as potential 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 explorer 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 "The Focus Zone and Hot Spots" on page 56. For information on grouping transmitters in the explorer window, see "Grouping Data Objects" on page 89. 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.
1057
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
•
© Forsk 2012
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: • • • • • • • • •
"Importing Neighbours" on page 1058 "Defining Exceptional Pairs" on page 1058 "Configuring Importance Factors for Neighbours" on page 1058 "Allocating Neighbours Automatically" on page 1059 "Checking Automatic Allocation Results" on page 1061 "Allocating and Deleting Neighbours per Cell" on page 1064 "Calculating the Importance of Existing Neighbours" on page 1067 "Checking the Consistency of the Neighbour Plan" on page 1068 "Exporting Neighbours" on page 1069.
11.2.12.1 Importing Neighbours You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table. To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Network explorer. b. Right-click the Transmitters folder. The context menu appears. c. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 82.
11.2.12.2 Defining Exceptional Pairs In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs can be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Select the Network explorer. 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 cell’s 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. Click the Edit button on the bottom-right of the dialogue. The exceptional pair list becomes editable. b. Select the cell from the list in the Neighbours column. c. In the Status column, select one of the following: • •
Forced: The selected cell will always be a neighbour of the reference cell. Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair. 9. Click OK. You can also create exceptional pairs using the Intra-technology Exceptional Pairs table. You can open this table by right-clicking the Transmitters folder and selecting Neighbours > Intra-technology > Exceptional Pairs.
11.2.12.3 Configuring Importance Factors for Neighbours You can define the relative importance of the factors that Atoll uses to evaluate potential neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide).
1058
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
To configure the importance factors for neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. On the Intra-technology Neighbours tab, you can set the following importance factors: • • •
•
Distance factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency factor will be used if you select the Force adjacent cells as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 1059. 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 cells as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 1059.
5. Click OK. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual.
11.2.12.4 Allocating Neighbours Automatically Atoll can automatically allocate neighbours in a TD-SCDMA network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. For N-frequency mode compatible transmitters, neighbours are only stored for the master carriers. The slave carriers have the same neighbours as their master carrier. Neighbours are not allocated for standalone carriers (non-N-frequency mode compatible). To automatically allocate TD-SCDMA neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. On the Neighbours tab, you can set the following parameters: • • •
Max inter-site distance: Set the maximum distance between the reference transmitter and a possible neighbour. Max no. of neighbours: Set the maximum number of intra-technology neighbours that can be allocated to a transmitter. This value can be either set here for all transmitters, or specified for each transmitter in the Cells table. Coverage conditions: The coverage conditions must be respected for a transmitter to be considered as a neighbour. Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the following parameters: • •
•
•
• •
Resolution: You can enter the resolution used to calculate the coverage areas of transmitters for 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 transmitter. If there is more than one transmitter whose P-CCPCH RSCP is higher than the PCCPCH RSCP T_Add, the transmitter with the highest P-CCPCH RSCP is kept as the serving transmitter. P-CCPCH RSCP T_Drop: Enter the P-CCPCH RSCP T_Drop, which defines the minimum P-CCPCH RSCP required for transmitters to enter a preliminary handover set. All the transmitters 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 transmitters listed in the preliminary handover set using the P-CCPCH RSCP T_Drop, only the transmitters whose P-CCPCH RSCP is within the range defined by the P-CCPCH RSCP from the best server and the P-CCPCH RSCP T_Comp margin are kept in the handover set. Shadowing taken into account: If 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.
1059
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
•
© Forsk 2012
% min covered area: Enter the minimum, in percentage, that a possible neighbour transmitter’s coverage area must overlap the reference transmitter’s 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 transmitters located on the same site as the reference transmitter to be automatically considered as neighbours. Force adjacent cells as neighbours: Select the Force adjacent cells 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 transmitter’s coverage area where the possible neighbour transmitter 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 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 possible neighbour 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 1058. 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 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 "Configuring Importance Factors for Neighbours" on page 1058 Cause: The reason Atoll has allocated the possible neighbour transmitter, as identified in the Neighbour column, to the reference transmitter, as identified in the Cell column. • Co-site • Adjacency • Symmetry • Coverage • Existing Coverage: The amount of reference transmitter’s 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.
7. Select the Commit check box for each neighbour you want to assign to a transmitter. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. 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: • • • •
1060
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.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
8. 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 cell’s Properties dialogue. •
•
•
•
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. 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. However, if the neighbour relation is forced in one direction and forbidden in the other one, symmetry cannot be respected. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Saving a User Configuration" on page 101.
Atoll also enables you to automatically allocate neighbours to a single base station or transmitter: • •
11.2.12.4.1
"Allocating Neighbours to a New Base Station" on page 1061 "Allocating Neighbours to a New Transmitter" on page 1061.
Allocating Neighbours to a New Base Station When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects the coverage area of the cells of the new base station. To allocate neighbours to a new base station: 1. In the Network explorer, group the transmitters by site, as explained in "Grouping Data Objects" on page 89. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Neighbours > Intra-technology > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 1059.
11.2.12.4.2
Allocating Neighbours to a New Transmitter When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new transmitters and other cells whose coverage area intersects the coverage area of the cells of the new transmitter. To allocate neighbours to a new transmitter: 1. Select the Network explorer. 2. In the Transmitters folder, right-click the new transmitter. The context menu appears. 3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 1059.
11.2.12.5 Checking Automatic Allocation Results You can verify the results of automatic neighbour allocation in the following ways: • •
11.2.12.5.1
"Displaying Neighbour Relations on the Map" on page 1061. "Displaying the Coverage of Each Neighbour of a Cell" on page 1063.
Displaying Neighbour Relations on the Map You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
2. Select Display Options from the context menu. The Neighbour Display dialogue appears. 3. Under Intra-technology Neighbours, select the Display Links check box.
1061
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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 cell’s 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 cell’s neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s neighbours according to their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting factors. YYou 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 Type’s Data Table" on page 71.
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 43. 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 tip text. 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 links: Select the Symmetric links 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 Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 14. Click the Edit Relations on the Map button (
) in the Radio Planning toolbar.
15. Select a transmitter to show its neighbour links: •
•
•
1062
In the Transmitters folder of the Network explorer: Select the transmitter in the Transmitters folder. The selected transmitter is centred in the map and all its neighbours are indicated. Atoll displays the selected transmitter in the Neighbours table if it is open. On the map: Select the transmitter on the map. The neighbours of the selected transmitter are displayed on the map. 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 41). Atoll displays the selected transmitter in the Neighbours table if it is open. In the Neighbours table: Select the transmitter-neighbour relation you want to display by clicking in the left margin of the table row to select the entire row. The selected transmitter is centred in the map with the selected transmitter-neighbour relation (see Figure 11.57). The selected transmitter is also displayed in the Transmitters folder of the Network explorer.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Figure 11.57: Selecting a transmitters in the Neighbours table Atoll displays the following information (see Figure 11.58) 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 11.58.). 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 11.58.).
In Figure 11.58, 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 11.58: Neighbours of Site 22_3(0) - Display According to the Neighbour You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
11.2.12.5.2
Displaying the Coverage of Each Neighbour of a Cell By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cell’s neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a coverage by P-CCPCH best server, with the Display Type set to "Discrete Values" and the Field set to "Transmitter." For information on creating a coverage by transmitter prediction, see "Making a Cover-
1063
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
age Prediction by P-CCPCH Best Server" on page 1018. 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
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 cell’s 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 cell’s neighbours according to a value from the Intra-technology Neighbours table. Value intervals: Select "Value intervals" to colour the coverage area of a cell’s neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s 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 tip text. This information will be displayed on each coverage area. 9. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 11. Click the Edit Relations on the Map button (
) in the Radio Planning 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 41). 13. In order to restore colours and cancel the neighbour display, click the Edit Relations on the Map button ( Radio Planning toolbar.
) in the
11.2.12.6 Allocating and Deleting Neighbours per Cell Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of the Transmitter Properties dialogue. This section explains the following: • • •
"Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1064. "Allocating or Deleting Neighbours Using the Neighbours Table" on page 1065. "Allocating or Deleting Neighbours on the Map" on page 1066.
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 transmitter’s 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 transmitter’s Properties dialogue appears. 3. Click the Cells tab. 4. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours. The cell’s Properties dialogue appears. 5. Click the Intra-technology Neighbours tab. 6. If desired, you can enter the Max number of neighbours. To allocate a new neighbour: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Under List, select the cell from the list in the Neighbour column in the row marked with the New row icon (
1064
).
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
c. 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 Source to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. Select Make Symmetrical 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 symmetrical neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click the left margin of the table row containing the neighbour to select the entire row. c. Press Del to delete the neighbour. 7. Click OK. Allocating or Deleting Neighbours Using the Neighbours Table To allocate or delete TD-SCDMA neighbours using the Neighbours table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears. For information on working with data tables, see "Working with Data Tables" on page 69.
To allocate a neighbour: a. In the row marked with the New row icon (
), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column. c. Click another cell of the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Source to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Select the neighbour in the Neighbour column. The context menu appears. b. Select Make Symmetrical 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 Make Symmetrical from the context menu.
1065
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To take into consideration all exceptional pairs: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. You can add or delete either some forced neighbours or some forbidden neighbours using the Intra-technology Exceptional Pairs 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 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 the left margin of the table row containing the neighbour to select the entire row. b. Press Del to delete the neighbour. Allocating or Deleting Neighbours on the Map You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 1061. 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. • •
1066
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.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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. •
•
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 41). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
11.2.12.7 Calculating the Importance of Existing Neighbours After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Calculate Importance from the context menu. The Neighbour Importance Evaluation dialogue appears. 4. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as potential neighbours. 5. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 1058): • •
Take into account the adjacency factor: Select the Take into account the adjacency factor check box to verify that neighbours are adjacent to their reference cells when calculating importance. Take into account the co-site factor: Select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.
6. Under Coverage conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: •
• •
Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. • P-CCPCH RSCP T_Add: Enter the P-CCPCH RSCP T_Add, which defines the minimum P-CCPCH RSCP required for the serving cell. If there is more than one cell whose P-CCPCH RSCP is higher than the P-CCPCH RSCP T_Add, the cell with the highest P-CCPCH RSCP is kept as the serving cell. • P-CCPCH RSCP T_Drop: Enter the P-CCPCH RSCP T_Drop, which defines the minimum P-CCPCH RSCP required for cells to enter a preliminary handover set. All the cells whose P-CCPCH RSCP is higher than the P-CCPCH RSCP T_Drop are added to the set. • P-CCPCH RSCP T_Comp: Enter the P-CCPCH RSCP T_Comp, which defines the handover set limit. From among the cells listed in the preliminary handover set using the P-CCPCH RSCP T_Drop, only the cells whose P-CCPCH RSCP is within the range defined by the P-CCPCH RSCP from the best server and the P-CCPCH RSCP T_Comp margin are kept in the handover set. Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell edge coverage probability. Indoor coverage: If desired, select the Indoor coverage check box. Atoll will then calculate additional losses for indoor coverage.
7. Click OK to save your modifications and close the Coverage Conditions dialogue. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated.
1067
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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 1058 Cause: The reason Atoll has allocated value in the Importance column. • • • •
• • •
Co-site Adjacency Symmetry Coverage
Coverage: The amount of reference cell’s 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. Distance: The distance in kilometres between the reference cell and the neighbour.
9. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
11.2.12.8 Checking the Consistency of the Neighbour Plan You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the intra-technology neighbour allocation plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Define the parameters of the audit: • • •
• • • • •
Average no. of neighbours: Select the Average no. of neighbours check box if you want to verify the average number of neighbours per cell. Empty lists: Select the Empty lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full lists: Select the Full lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list) and set the value in the Default max number text box. Lists > max number: Select the Lists > max number check box if you want to verify which cells have more than the maximum number of neighbours allowed and set the value in the Default max number text box. Missing co-sites: Select the Missing co-sites check box if you want to verify which cells have no co-site neighbours. Missing symmetrics: Select the Missing symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional pairs: Select the Exceptional pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance between neighbours: Select the Distance between neighbours check box and enter the distance between neighbours that should not be exceeded.
5. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: •
Average number of neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty lists: x⁄X; x number of cells out of a total of X have no neighbours (or empty neighbours list). Syntax:
•
Full lists (default max number = Y): x⁄X; x number of cells out of a total of X have 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 have more than Y number of neighbours listed in their respective neighbours lists. Syntax:
1068
|CELL|
|CELL|
|NUMBER|
|MAX NUMBER|
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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:
•
|NEIGHBOUR| |TYPE|
|REASON|
|CELL|
|NEIGHBOUR|
Existing forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
•
|CELL|
Missing forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|NEIGHBOUR|
Non-symmetric links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
•
|CELL|
|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.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. Select the Network explorer. 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 > Open Table: This table contains the data for the intra-technology neighbours in the current Atoll document. Inter-technology > Open Table: This table contains the data for the inter-technology neighbours in the current Atoll document. Intra-technology > Exceptional Pairs: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document. Inter-technology > Exceptional Pairs: This table contains the data for the inter-technology exceptional pairs (forced and forbidden) in the current Atoll document.
4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files and Spreadsheets" on page 80.
11.2.13 Planning Scrambling Codes In TD-SCDMA, 128 scrambling codes (or P-CCPCH midamble codes) of 16-bit lengths are available, numbered from 0 to 127. Although TD-SCDMA scrambling codes are displayed in decimal format by default, they can also be displayed and calculated in hexadecimal format, in other words using the numbers 0 to 9 and the letters A to F. Atoll facilitates the management of scrambling codes by letting you create groups of scrambling codes and domains, where each domain is a defined set of groups. You can also assign scrambling codes manually or automatically to any cell in the network. Once allocation is complete, you can audit the scrambling codes, view scrambling code reuse on the map, and analyse the distribution of scrambling codes. Downlink synchronisation, SYNC_DL, codes are assigned to cells in order to distinguish nearby cells, and for synchronization purposes. There are 32 different SYNC_DL codes of 64 bit lengths defined for the whole system in downlink. According to 3GPP specifications, the 127 possible scrambling codes can be broken down into 32 groups, each containing 4 codes. Because the term "group" in Atoll refers to user-defined sets of scrambling codes, these groups of 4 codes each are referred to as "clusters" in Atoll. Each cluster of scrambling codes is related to a SYNC_DL code used by a base station. For N-frequency mode compatible transmitters, scrambling codes are only allocated and stored for master carriers. The slave carriers have the same scrambling codes as their master carrier. The procedure of planning scrambling codes for a TD-SCDMA project is: •
Preparing for scrambling code allocation • • •
"Defining the Scrambling Code Format" on page 1070. "Creating Scrambling Code Domains and Groups" on page 1070. "Defining Exceptional Pairs for Scrambling Code Allocation" on page 1071.
1069
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
• •
© Forsk 2012
"Defining Scrambling Code Relativity Clusters" on page 1071.
Allocating scrambling codes • •
"Automatically Allocating Scrambling Codes to TD-SCDMA Cells" on page 1072. "Allocating Scrambling Codes to TD-SCDMA Cells Manually" on page 1074.
•
"Checking the Consistency of the Scrambling Code Plan" on page 1074.
•
Displaying the allocation of scrambling codes • • • • •
"Using Find on Map to Display Scrambling Code Allocation" on page 1075. "Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 1075. "Grouping Transmitters by Scrambling Code" on page 1076. "Displaying the Scrambling Code Allocation Histogram" on page 1076. "Studying Scrambling Code Collision" on page 1077.
11.2.13.1 Defining the Scrambling Code Format Scrambling codes can be displayed in decimal or hexadecimal format. The selected format is used to display scrambling codes in dialogues and tables such as in the Domains and Groups tables, the Cells table, and the Scrambling Code Allocation dialogue. The decimal format is the default format in Atoll. The accepted decimal values are from 0 to 127. The decimal format is also used, even if you have chosen the hexadecimal format, to store scrambling codes in the database and to display scrambling code distribution or the results of a scrambling code audit. The hexadecimal format uses the numbers 0 to 9 and the letters A to F for its base characters. In Atoll, hexadecimal values are indicated by a lower-case "h" following the value. For example, the hexadecimal value "3Fh" is "63" as a decimal value. You can convert a hexadecimal value to a decimal value with the following equation, where X, Y, and Z are decimal values within the hexadecimal index ranges: 2
X × 16 + Y × 16 + Z
For example, the hexadecimal value "3Fh" would be calculated as shown below: 2
0 × 16 + 3 × 16 + 15 = 63
To define the scrambling code format for an Atoll document: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Scrambling Codes folder. The context menu appears. 4. Select Format from the context menu and select either Decimal or Hexadecimal.
11.2.13.2 Creating Scrambling Code Domains and Groups Atoll facilitates the management of scrambling codes by letting you create domains, each containing groups of scrambling codes. The procedure for managing scrambling codes in a TD-SCDMA document consists of the following steps: 1. Creating a scrambling code domain, as explained in this section. 2. Creating groups, each containing a range of scrambling codes, and assigning them to a domain, as explained in this section. 3. Assigning a scrambling code domain to a cell or cells. If there is no scrambling code domain, Atoll will consider all 128 possible scrambling codes when assigning codes. To create a scrambling code domain: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Scrambling Codes folder. 4. Right-click Domains in the Scrambling Codes folder. The context menu appears. 5. Select Open Table from the context menu. The Domains table appears. 6. In the row marked with the New row icon (
), enter a Name for the new domain.
7. Click another cell of the table to create the new domain and add a new blank row to the table. 8. Double-click the domain to which you want to add a group. The domain’s Properties dialogue appears. 9. Under Groups, enter the following information for each group you want to create.
1070
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
• •
• • • •
Name: Enter a name for the new scrambling code group. Min: Enter the lowest available scrambling code in this group’s 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 1070. Max: Enter the highest available scrambling code in this group’s 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, 3–6" means that the extra scrambling codes are "1, 2, 3, 4, 5, 6".
10. Click another cell of the table to create the new group and add a new blank row to the table.
11.2.13.3 Defining Exceptional Pairs for Scrambling Code Allocation You can also define pairs of cells which cannot have the same scrambling code. These pairs are referred to as exceptional pairs. Exceptional pairs are used along with other constraints, such as neighbours, reuse distance, and domains, in allocating scrambling codes. To create a pair of cells that cannot have the same scrambling code: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Scrambling Codes > Exceptional Pairs. The Exceptional Separation Constraints table appears. For information on working with data tables, see "Working with Data Tables" on page 69. 4. In the row marked with the New Row icon ( ), select one cell of the new exceptional pair in the Cell column and the second cell of the new exceptional pair from the Cell_2 column. 5. Click another cell of the table to create the new exceptional pair and add a new blank row to the table.
11.2.13.4 Defining Scrambling Code Relativity Clusters Some of the scrambling codes are not fully mutually orthogonal. Some may have a relatively high correlation and may interfere each other. The principal aim of scrambling code planning is to allocate scrambling codes to cells in such a manner so as to avoid any confusion in the detection of these scrambling codes by user equipment. In other words, geographically adjacent cells should be allocated highly orthogonal scrambling codes in order to avoid any error in scrambling code detection. 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. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select 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.
11.2.13.5 Allocating Scrambling Codes Atoll can automatically assign scrambling codes to the cells of a TD-SCDMA network according to set parameters. For example, it takes into account the definition of groups and domains of scrambling codes, the selected scrambling code allocation strategy (clustered, distributed per cell, distributed per site, and one SYNC_DL per site), minimum code reuse distance, and any constraints imposed by neighbours. You can also allocate scrambling codes manually to the cells of a TD-SCDMA network. In this section, the following methods of allocating scrambling codes are described: • • •
"Defining Automatic Allocation Constraint Violation Costs" on page 1072 "Automatically Allocating Scrambling Codes to TD-SCDMA Cells" on page 1072. "Allocating Scrambling Codes to TD-SCDMA Cells Manually" on page 1074.
1071
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Defining Automatic Allocation Constraint Violation Costs You can define the costs of the different types of constraints used in the automatic scrambling code allocation algorithm. To define the different constraint violation costs: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Scrambling Codes > Constraint Costs. The Constraint Violation Costs dialogue appears. In this dialogue you can define the following costs of constraint violations for the automatic allocation process (the cost is a value from 0 to 1): •
• • • •
Under Intra-technology neighbours, you can set the constraint violation costs for Close neighbours, 1st order, 2nd order, and 3rd order neighbours. The close neighbour constraint violation cost should be higher than the 1st order neighbour constraint violation cost, which should be higher than the 2nd order and the 3rd order should be the lowest among all of these costs. Under Distributed per site strategy, you can set the constraint violation cost for intra-technology neighbours that are 1st or 2nd order using the same cluster. Reuse distance: Enter the maximum cost for reuse distance constraint violations. Exceptional pair: Enter the cost for exceptional pair constraint violations. Common inter-technology neighbour: Enter the cost for inter-technology neighbour constraint violations.
4. Click OK. The constraint violation costs are stored and will be used in the automatic allocation. Automatically Allocating Scrambling Codes to TD-SCDMA Cells The allocation algorithm enables you to automatically allocate scrambling code to cells in the current network. You can choose among several automatic allocation strategies. The actual automatic allocation strategies available will depend on your network and options selected in the atoll.ini file. For more information on the atoll.ini file, see the Administrator Manual. For more information on automatic allocation strategies, see the Technical Reference Guide. • • •
•
Clustered: The purpose of this strategy is to choose for a group of mutually constrained cells, scrambling codes among a minimum number of clusters. In this case, Atoll will preferentially allocate all the codes from the same cluster. Distributed per cell: This strategy consists in using as many clusters as possible. Atoll will preferentially allocate codes from different clusters. One SYNC_DL code per site: This strategy allocates one SYNC_DL code to each base station, then, one code of the cluster associated with the SYNC_DL code to each cell of each base station. When all the SYNC_DL codes have been allocated and there are still base stations remaining to be allocated, Atoll reuses the SYNC_DL codes at another base station. Select this strategy if you want to allocate the same scrambling code to the master and the slave carriers. For more information on master and slave carriers, see "Planning Frequencies" on page 1054. 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. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select 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 1057.
1072
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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 1133. •
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 1071.
•
From the Strategy list, you can select an automatic allocation strategy: • • • •
• •
Clustered Distributed per cell One SYNC_DL code per site Distributed per site
Carrier: Select the carrier on which you want to run the allocation. You may choose one carrier (Atoll will assign scrambling codes to transmitters using the selected carrier) or all of them. No. of codes per SYNC_DL: According to 3GPP specifications, the number of scrambling codes per SYNC_DL is 4. If you want, you can change the number of codes per SYNC_DL. When the allocation is based on a distributed strategy (distributed per cell or distributed per site), this parameter can also be used to define the interval between the scrambling codes assigned to cells on a same site. The defined interval is applied by setting an option in the atoll.ini file. For more information about setting options in the atoll.ini file, see the Administrator Manual.
•
•
Use a max of codes: Select the Use a max of codes check box to make Atoll use the maximum number of codes. For example, if there are two cells using the same domain with two scrambling codes, Atoll will assign the remaining code to the second cell even if there are no constraints between these two cells (for example, neighbour relations, reuse distance, etc.). If you do not select this option, Atoll only checks the constraints, and allocates the first ranked code in the list. Delete existing codes: Select the Delete existing codes check box if you want Atoll to delete currently allocated scrambling codes and recalculate all scrambling codes. If you do not select this option, Atoll keeps the currently allocated scrambling codes and only allocates scrambling codes to cells that do not yet have codes allocated.
5. Click Calculate. 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.
1073
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
• • • •
© Forsk 2012
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. Atoll allocates the same scrambling code to each carrier of a transmitter.
6. Click Commit. The scrambling codes are stored in the cell properties. You can save automatic scrambling code allocation parameters in a user configuration. For information on saving automatic scrambling code allocation parameters in a user configuration, see "Saving a User Configuration" on page 101.
•
•
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 transmitter’s context menu. If you need to allocate scrambling codes to all the cells in a group of transmitters, you can allocate them automatically by selecting Scrambling Codes > Automatic Allocation from the transmitter group’s context menu.
Allocating Scrambling Codes to TD-SCDMA Cells Manually When you allocate scrambling codes to a large number of cells, it is easiest to let Atoll allocate scrambling codes automatically, as described in "Automatically Allocating Scrambling Codes to TD-SCDMA Cells" on page 1072. However, if you want to add a scrambling code to one cell or to modify the scrambling code of a cell, you can do it by accessing the properties of the cell. After allocation, you can use the audit tool to check the reuse scrambling code distances between cells and the compatibility of the domains of the cells for each base station. To allocate a scrambling code to a TD-SCDMA cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate a scrambling code. The context menu appears. 2. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 3. Select the Cells tab. 4. Enter a Scrambling code in the cell’s column. 5. Click OK.
11.2.13.6 Checking the Consistency of the Scrambling Code Plan Once you have completed allocating scrambling codes, you can verify whether the allocated scrambling codes respect the specified constraints by performing an audit of the plan. The scrambling code audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Scrambling Codes > Audit. The Code and SYNC_DL Audit dialogue appears. 4. In the Code and SYNC_DL Audit dialogue, select the allocation criteria that you want to check: • •
No. of codes per SYNC_DL: Enter the number of scrambling codes per SYNC_DL. This number is set to 4 by default, which is the number of scrambling codes attached to each SYNC_DL. Neighbours: Select Neighbours in order to check scrambling code constraints between cells and their neighbours and then choose the neighbourhood level to take into account. First order: Atoll will check that no cell has the same scrambling code as any of its neighbours. Second order: Atoll will check that no cell has the same scrambling code as any of its neighbours or any of the neighbours of its neighbours. Third order: Atoll will check that no cell has the same scrambling code as any of its neighbours or any of the neighbours of its neighbours or any of the neighbours of its second order neighbours.
1074
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
The report will list the cells and the neighbours that do not meet one of these constraints. In addition, it will indicate the allocated primary scrambling code and the neighbourhood level. •
•
•
• •
•
Neighbours in different SYNC_DLs: If you select the Neighbours in different SYNC_DLs check box, Atoll will check that neighbour cells have scrambling codes from different SYNC_DLs. The report will list any neighbour cells that has scrambling codes from the same SYNC_DL. Domain compliance: If you select the Domain compliance check box, Atoll will check if allocated scrambling codes belong to domains assigned to cells. The report will list any cells with scrambling codes that do not belong to domains assigned to the cell. Site domains not empty: If you select the Site domains not empty check box, Atoll will check for and list base stations for which the allocation domain (i.e., the list of possible scrambling codes, with respect to the configured allocation constraints) is empty. One SYNC_DL per site: If you select the One SYNC_DL per site check box, Atoll will check for and list base stations whose cells have scrambling codes coming from more than one SYNC_DL. Distance: If you select the Distance check box and set a reuse distance, Atoll will check for and list the cell pairs that do not respect the reuse distance condition. For any cell pair, Atoll uses the lowest of the reuse distance values among the ones defined for the two cells in their properties and the value that you set in the Code and SYNC_DL Audit dialogue. Cell pairs that do not respect the reuse distance condition are listed according to the distance between them, from the closest to the furthest away. The scrambling code and the reuse distance are also listed for each cell pair. Exceptional pairs: If you select the Exceptional pairs check box, Atoll will check for and display pairs of cells that are listed as exceptional pairs but have the same scrambling code allocated.
5. Click OK. Atoll displays the results of the audit in a text file called CodeCheck.txt. For each selected criterion, Atoll gives the number of detected inconsistencies and the details of each.
11.2.13.7 Displaying the Allocation of Scrambling Codes Once you have completed allocating scrambling codes, you can verify several aspects of scrambling code allocation. You have several options for displaying scrambling codes: • • • • •
"Using Find on Map to Display Scrambling Code Allocation" on page 1075. "Displaying Scrambling Code Allocation Using Transmitter Display Settings" on page 1075. "Grouping Transmitters by Scrambling Code" on page 1076. "Displaying the Scrambling Code Allocation Histogram" on page 1076. "Studying Scrambling Code Collision" on page 1077.
Using Find on Map to Display Scrambling Code Allocation In Atoll, you can search for scrambling codes and scrambling code groups using the Find on Map tool. Results are displayed in the map window in red. If you have already calculated and displayed a coverage prediction by transmitter based on the best server P-CCPCH, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. For information, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 1018. Scrambling codes and scrambling code groups and any potential problems will then be clearly visible. To find scrambling codes or scrambling code groups using the Find on Map tool: 1. Click Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "Scrambling Code." 3. Select what you what you want to search for: • •
Scrambling code: If you want to find a scrambling code, select Scrambling code and select it from the list. SC group: If you want to find a scrambling code group, select SC group and select it from the list.
4. Select the carrier you want to search on from the For carrier list, or select "(All)" to search in all carriers. 5. Click Search. Transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match the search criteria are displayed as grey lines. To restore the initial transmitter colours, click the Reset display button in the Find on Map window. Displaying Scrambling Code Allocation Using Transmitter Display Settings You can use the display characteristics of transmitters to display scrambling code-related information. To display scrambling code-related information on the map: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears.
1075
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
4. Click the Display tab. You can display the following information per transmitter: • • •
Scrambling code: Select "Discrete values" as the Display type and "Cells: Scrambling code" as the Field. Ranges of scrambling codes: Select "Value intervals" as the Display type and "Cells: Scrambling code" as the Field. Scrambling code domain: Select "Discrete values" as the Display type and "Cells: Scrambling code domain" as the Field.
You can display the following information in the transmitter label or tip text by clicking the Label or Tip text browse button ( • •
):
Scrambling code: Select "Cells: Scrambling Code" from the Label or Tip Text Field Definition 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 43. Grouping Transmitters by Scrambling Code You can group transmitters in the Network explorer by their scrambling code or scrambling code domain. To group transmitters by scrambling code: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: • •
Scrambling code domain Scrambling code
7. Click to add the parameter to the Grouping fields list. The selected parameter is added to the list of parameters on which the transmitters will be grouped. 8. If you do not want the transmitters to be sorted by a certain parameter, select it in the Grouping fields list and click . The selected parameter is removed from the list of parameters on which the transmitters will be grouped. 9. Arrange the parameters in the Grouping fields list in the order in which you want the transmitters to be grouped: a. Select a parameter and click
to move it up to the desired position.
b. Select a parameter and click
to move it down to the desired position.
10. Click OK to save your changes and close the Group dialogue. If a transmitter has more than one cell, Atoll cannot arrange the transmitter by cell. Transmitters that cannot be grouped by cell are arranged in a separate folder under the Transmitters folder. Displaying the Scrambling Code Allocation Histogram You can use a histogram to analyse the use of allocated scrambling codes in a network. The histogram represents the scrambling codes or SYNC_DLs as a function of the frequency of their use. To display the scrambling code histogram: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Scrambling Codes > Code Distribution. The Distribution Histograms dialogue appears. Each bar represents a scrambling code or a SYNC_DL code, its height depending on the frequency of its use. 4. Select Scrambling codes to display scrambling code use and Clusters to display SYNC_DL code use.
1076
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
5. Move the pointer over the histogram to display the frequency of use of each scrambling code or SYNC_DL. The results are highlighted simultaneously in the Zoom on selected values list. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. Studying Scrambling Code Collision You can make a scrambling code collision zones coverage prediction to view areas covered by cells using the same scrambling code. The coverage prediction displays areas where transmitters other than the best server, whose received signal level is within the pollution margin set in the coverage prediction properties, interfere the best server signal. The interfered pixels are coloured according to the interfered scrambling code. To make a scrambling code collision zone coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Scrambling Code Collision Zones and click OK. The prediction Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Conditions tab (see Figure 11.59). The coverage prediction parameters on the Conditions tab allow you to define the signals that will be considered for each pixel. You can set: • • • •
Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the terminal properties are used. Service: The service to be considered in the coverage prediction. The body loss defined in the service properties is used. Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP threshold defined in the mobility properties is used as the minimum requirement for the coverage prediction. Carrier: The carrier to be considered in the coverage prediction. For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist in a transmitter, there will not be any pixels covered by this transmitter.
• • • •
Timeslot: The scrambling code collision coverage prediction is performed for TS0. If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses. 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 11.59: Condition settings for a Scrambling Code Collision Zones coverage prediction 7. Click the Display tab.
1077
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
For a scrambling code collision analysis coverage prediction, the Display type "Value intervals" based on the Field "Interfered scrambling code" is available. Each interference zone will then be displayed in a colour corresponding to the interfered scrambling code per pixel. For information on defining display properties, see "Display Properties of Objects" on page 43. 8. Click OK to save your settings. 9. Click the Calculate button ( ) in the Radio Planning toolbar to calculate the scrambling code collision zone coverage prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 11.60).
Figure 11.60: Condition settings for a Scrambling Code Collision 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 Find on Map tool. For more information on using the Find on Map tool for scrambling code collision analysis, see "Using Find on Map to Display Scrambling Code Allocation" on page 1075.
11.3 Studying Network Capacity A TD-SCDMA network automatically regulates power on both uplink and downlink with the objective of minimising interference and maximising network capacity. In the case of HSDPA, the network uses fast link adaptation (in other words, the selection of an HSDPA bearer) in the downlink. Atoll can simulate these network regulation mechanisms, thereby enabling you to study the capacity of the TD-SCDMA network. In Atoll, a simulation is based on a realistic distribution of users at a given point in time. The distribution of users at a given moment is referred to as a snapshot. Based on this snapshot, Atoll calculates various network parameters such as the active set for each mobile, the required power of the mobile, the total DL power, and the UL load. Simulations are calculated in an iterative fashion. When several simulations are performed at the same time using the same traffic information, the distribution of users will be different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snapshot to another. To create snapshots, services and users must be modelled. As well, certain traffic information in the form of traffic maps must be provided. Once services and users have been modelled and traffic maps have been created, you can make simulations of the network traffic. In this section, the following are explained: • • • • •
"Calculating TD-SCDMA Network Capacity" on page 1078. "Defining Multi-service Traffic Data" on page 1080. "Creating a Traffic Map" on page 1081. "Calculating and Displaying Traffic Simulations" on page 1091. "Making Coverage Predictions Using Simulation Results" on page 1107.
11.3.1 Calculating TD-SCDMA Network Capacity TD-SCDMA cell capacity is the number of resource units available on the uplink and downlink. There can be a maximum of 16 users (16 OVSF codes) per timeslot. This means that each timeslot has 16 resource units. With 6 timeslots per subframe, which can be used in uplink or downlink, different combinations of uplink and downlink timeslots are possible. These combinations
1078
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
are referred to as timeslot configurations that can be defined per cell. The following table lists the capacity of a cell for different possible timeslot configurations: Timeslot Configuration
Resource Units in Uplink
Resource Units in Downlink
UDDDDD
16
80
UUDDDD
32
64
UUUDDD
48
48
UUUUDD
64
32
UUUUUD
80
16
UpUDDDD
16
64
UpUUDDD
32
48
TS0 is not used for traffic. TS1 is not used for traffic either in case of UpPCH shifting.
Assuming ideal dynamic channel allocation (DCA), all the resource units within a subframe, i.e., 6 x 16 = 96, can be allocated and used. The total resource units in a network, i.e., the network capacity, is given by: Network Capacity = Number of Timeslots per Subframe × Number of Codes per Timeslot × Number of Carriers
Resource units from different carriers can be shared and allocated to the same mobile connected to an N-frequency mode compatible transmitter. This section explains the network capacity and network dimensioning analysis tools: • • •
"Calculating Available Network Capacity" on page 1079. "Calculating Required Network Capacity" on page 1079. "Displaying the Network Capacity on the Map" on page 1080.
11.3.1.1 Calculating Available Network Capacity You can calculate the available capacity of your TD-SCDMA network in Atoll using the Network Capacity Estimation dialogue. To calculate the available network capacity: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Calculations > Network Capacity from the context menu. The Network Capacity Estimation dialogue appears. The dialogue lists the numbers of uplink and downlink resource units for each cell. The last row in this dialogue displays the total uplink and downlink resource units. The uplink and downlink resource units overhead defined for each timeslot for each cell is considered when calculating the number of available resource units. 4. Click Close to close the dialogue.
11.3.1.2 Calculating Required Network Capacity You can calculate the number of required resource units according to a given traffic demand, compare it with the network capacity (see "Calculating Available Network Capacity" on page 1079), and analyse how many resource units each cell requires using the dimensioning tool. The dimensioning tool takes traffic data from the selected traffic maps as input before calculating the number of required resources. To calculate the required network capacity: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Calculations > Network Dimensioning from the context menu. The Dimensioning dialogue appears. On the Source Traffic tab, enter: •
Global scaling factor: If desired, enter a scaling factor to increase user density.
1079
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of users (for environment and user profile traffic maps) or the rates per users (for live traffic maps per sector). • •
Select traffic maps to be used: Select the traffic maps you want to use for dimensioning. Under Coverage, select the P-CCPCH best server coverage prediction to be used to distribute the traffic among the cells of the network.
4. Click Calculate. Atoll distributes the traffic among cells using the information from traffic maps and the coverage prediction, calculates the capacity of each cell, and displays the results in the Results per Cell tab. The Results per Cell tab has five columns which list the names of the cells in the network, and the numbers of uplink and downlink resource units available and required per cell. The last row in this 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 calculate the coverage by P-CCPCH best server again and run the dimensioning calculations based on the new coverage prediction.
11.3.1.3 Displaying the Network Capacity on the Map You can create a coverage prediction by P-CCPCH best server in order to display the available network capacity, required network capacity, or the resource unit usage of your TD-SCDMA network on the map. To display the available or required 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 1018, with the following display parameters: 2. In step 7., set the Display type to "Value intervals" and depending on what you would like to display, set the Field to "Available DL Resource Units", "Available UL Resource Units", "Cells: Required DL Resource Units", "Cells: Required UL Resource Units", "Required DL Resource Units (%)", or "Required UL Resource Units (%)". Each coverage zone will then be displayed according to the number of available, required, or used resource units for the cell (carrier used for the coverage prediction). A high percentage of resource unit usage percentage can indicate dimensioning problems.
Figure 11.61: Network capacity coverage prediction (Display tab) When Atoll has finished calculating the prediction, the results are displayed in the map window.
11.3.2 Defining Multi-service Traffic Data The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment used.
1080
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
The following services and users are modelled in Atoll in order to create simulations: •
•
•
•
R99 radio bearers: Bearer services are used by the network for carrying information. The R99 Radio Bearer table lists all the available radio bearers. You can create new R99 radio bearers and modify existing ones using the R99 Radio Bearer table. For information on defining R99 radio bearers, see "Defining R99 Radio Bearers" on page 1142. 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 1033. Mobility types: In TD-SCDMA, information about receiver mobility is important to accurately model the channel characteristics: a mobile used in a speeding car or by a pedestrian will not necessarily undergo the same radio wave behaviour. Eb⁄Nt or C⁄I targets for uplink and downlink are largely dependent on mobile speed. For information on creating a mobility type, see "Creating a Mobility Type" on page 1035. 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 car’s on-board navigation device. For information on creating a terminal, see "Modelling Terminals" on page 1036.
11.3.3 Creating a Traffic Map The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atollprovides three types of traffic maps for TD-SCDMA projects. • • •
Sector traffic map User profile traffic map User density traffic map (number of users per km2)
These maps can be used for different types of traffic data sources as follows: •
Sector traffic maps can be used if you have live traffic data from the OMC (Operation and Maintenance Centre). The OMC (Operations and Maintenance Centre) collects data from all cells in a network. This includes, for example, the number of users or the throughput in each cell and the traffic characteristics related to different services. Traffic is spread over the best server coverage area of each transmitter and each coverage area is assigned either the throughputs in the uplink and in the downlink or the number of users per activity status or the total number of users (including all activity statuses). For more information, see "Creating a Sector Traffic Map" on page 1081.
•
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 1084, "Importing a User Profile Environment Based Traffic Map" on page 1086 and "Creating a User Profile Environment Based Traffic Map" on page 1086.
•
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 1088, "Creating a User Density Traffic Map" on page 1088, see "Converting 2G Network Traffic" on page 1089 and "Exporting Cumulated Traffic" on page 1090.
11.3.3.1 Creating a Sector Traffic Map The section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands in the uplink and in the downlink or the number of users per activity status or the total number of users including all activity statuses. A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 1018. To create a sector traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector traffic map. 5. Select the type of traffic information you want to input. You can choose between Uplink and downlink throughputs, Total number of users (all activity statuses) or Number of users per activity status. 6. Click the Create button. The Sector Traffic Map dialogue appears.
1081
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
You can also import a traffic map from a file by clicking the Import button. You can import AGD (Atoll Geographic Data) format files that you have exported from another Atoll document. 7. Select a coverage prediction by P-CCPCH best server from the list of available coverage predictions. 8. Enter the data required in the Sector Traffic Map dialogue: • • •
If you selected Uplink and Downlink Throughputs, 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. 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 82.
9. Click OK. The Sector Traffic Map Properties dialogue appears. 10. Select the Traffic tab. Enter the following: 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 Maps folder. You can modify the sector traffic map after it has been created. To modify the sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 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 P-CCPCH best server. For more information, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 1018. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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 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.
1082
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
6. Click OK. The Sector Traffic Map Properties dialogue appears. 7. If desired you can update the values under Terminals (%), Mobilities (%), and Clutter distribution. 8. 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 1089.
11.3.3.2 Creating a User Profile Traffic Map The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There can also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create user profile traffic maps. A user profile models the behaviour of different subscriber categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for circuit-switched calls), or uplink and downlink volume (for packet-switched calls). Environment classes are used to describe the distribution of subscribers on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of subscribers with the same profile per km²). The sections "Importing a User Profile Traffic Map" on page 1084, "Importing a User Profile Environment Based Traffic Map" on page 1086 and "Creating a User Profile Environment Based Traffic Map" on page 1086 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 1083. "Modelling Environments" on page 1084.
Modelling User Profiles You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user might be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles New Element Properties dialogue appears. 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 1033. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 1036. Calls⁄hour: For circuit-switched services, enter the average number of calls per hour for the service. The number of calls per hour is used to calculate the activity probability. For circuit-switched services, one call lasting 1000 seconds presents the same activity probability as two calls lasting 500 seconds each. For packet-switched services, the Calls⁄Hour value is defined as the number of sessions per hour. A session is like a call in that it is defined as the period of time between when a user starts using a service and when he stops using a service. In packet-switched services, however, he may not use the service continually. For example, with a webbrowsing service, a session starts when the user opens his browsing application and ends when he quits the browsing application. Between these two events, the user might be downloading web pages and other times he may 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.
1083
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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 profile⁄mobility combination that this TD-SCDMA 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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
For example: An area of 10 km² has a subscriber density of 100⁄km². Therefore, in this area, there are 1000 subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in the Building clutter class. 10. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simulation, an additional loss will be added to the indoor users path loss.
11.3.3.2.1
Importing a User Profile Traffic Map User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscribers⁄km, or polygons with a number of subscribers⁄km²) with a user profile, mobility type, and traffic density assigned to each vector.
1084
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
To create a user profile traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile densities from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1086. 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 map’s properties dialogue appears. 11. Select the Traffic tab (see Figure 11.62). Under Traffic fields, you can specify the user profiles to be considered, their mobility type (km⁄h), and their density. If the file you are 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 11.62: Traffic map properties dialogue – Traffic tab Define each of the following: •
•
•
User profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points.
1085
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
The name of the imported user profile or mobility type must match the corresponding name in the Traffic Parameters folder in the Parameters explorer. 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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
13. If you want, you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simulation, an additional loss will be added to the indoor users path loss. 14. Click OK to finish importing the traffic map.
11.3.3.2.2
Importing a User Profile Environment Based Traffic Map Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1086. 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 map’s 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 Traffic Parameters in the Parameters explorer. For more information, see "Modelling Environments" on page 1084. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 43.
11.3.3.2.3
Creating a User Profile Environment Based Traffic Map Atoll enables you to create a user profile environment traffic map based on by drawing it in the map window.
1086
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
To draw a traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 11.63).
Draw Polygon
Delete Polygon
Figure 11.63: 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.3.2.4
Displaying Statistics on a User Profile Environment Traffic Map You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears. The Statistics window lists the surface (Si in km²) and the percentage of surface (% of i) for each environment class "i" S
i - × 100 within the focus zone. The percentage of surface is given by: % of i = -------------
Sk k
You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.
11.3.3.3 Creating User Density Traffic Maps (No. Users/km2) User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit surface, i.e., the density of users, as input. This can be either the density of users per activity status or the density of users including all activity statuses. In this section, the following ways of creating a user density traffic map are explained: • •
"Importing a User Density Traffic Map" on page 1088 "Creating a User Density Traffic Map" on page 1088.
User density traffic maps can be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. For more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 1089.
1087
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
11.3.3.3.1
© Forsk 2012
Importing a User Density Traffic Map The user density traffic map defines the density of users per pixel. For a traffic density of X users per km², Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined in the Traffic tab of the traffic map’s properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User density traffic map (no. users/km2). 5. Select the type of traffic information: • • • • •
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. 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 1086. 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 map’s 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. 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 Maps folder.
11.3.3.3.2
Creating a User Density Traffic Map Atoll enables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User density traffic map (number of users per km2). 5. Select the type of traffic information. You can choose between:
1088
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
• • • • •
All activity statuses: Select All activity statuses if the map you are importing provides a density of users with any activity status. Active in uplink: Select Active in uplink if the map you are importing provides a density of users active in the uplink only. Active in downlink: Select Active in downlink if the map you are importing provides a density of users active in the downlink only. Active in uplink and downlink: Select Active in uplink and downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.
6. Click the Create button. The traffic map’s 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 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 Maps 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 Editor toolbar in order to draw contours. For more information on how to edit contours, see "Editing Polygons, Lines, and Points" on page 61. Atoll creates an item called Density values in the User Density Map folder. 16. Press ESC to end editing contours. 17. Right-click the Density values item. The context menu appears. 18. Select Open Table from the context menu. 19. In the table, enter a traffic density value (i.e., the number of users per km2) for each contour you have drawn.
11.3.3.3.3
Creating User Density Traffic Maps from Sector Traffic Maps You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. To create user density traffic maps from a sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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.
11.3.3.4 Converting 2G Network Traffic Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km² for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as user density traffic maps into your TD-SCDMA document. These maps can then be used in traffic simulations like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 1090, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1088.
1089
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To import a 2G traffic map into a TD-SCDMA document: 1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 438. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 1090. 3. Import the traffic exported in step 2 to your TD-SCDMA document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1088.
11.3.3.5 Exporting Cumulated Traffic Atoll allows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user density. The cumulated traffic is exported in 32-bit BIL, ArcView© Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears. 4. Enter a file name and select the file format. 5. Click Save. The Export dialogue appears. 6. Under Region, select the area to export: • •
The entire project area: This option allows you to export the cumulated traffic of the entire project. The computation zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone, whether or not the computation zone is visible.
7. Define a Resolution in metres. The resolution must be an integer and the minimum resolution allowed is 1. 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. • • • •
Terminal: Select the type of terminal to be exported or select "All" to export traffic using any terminal. Service: Select the service to be exported, or select "All circuit services" to export traffic using any circuit service, or "All packet services" to export traffic using any packet service. Mobility: Select the mobility type to 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, independently of their 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.
11.3.4 Exporting a Traffic Map To export a traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save.
1090
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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.5 Calculating and Displaying Traffic Simulations Once you have modelled the network services and users and have created traffic maps, you can create simulations. The simulation process consists of two steps: 1. Obtaining a realistic user distribution: Atoll generates a user distribution using a Monte Carlo algorithm; this user distribution is based on the traffic database and traffic maps and is weighted by a Poisson distribution between simulations of a same group. Each user is assigned a service, a mobility type, and an activity status by random trial, according to a probability law that uses the traffic database. The user activity status is an important output of the random trial and has direct consequences on the next step of the simulation and on the network interferences. A user can be either active or inactive. Both active and inactive users consume radio resources and create interference. Then, Atoll randomly assigns a shadowing error to each user using the probability distribution that describes the shadowing effect. Finally, another random trial determines user positions in their respective traffic zone (according to the clutter weighting and the indoor ratio per clutter class). 2. Modelling dynamic channel allocation and power control: Atoll performs dynamic channel allocation and power control for mobiles generated in the previous step. The power control simulation algorithm is described in "The Monte Carlo Simulation Algorithm" on page 1091.
11.3.5.1 The Monte Carlo Simulation Algorithm The dynamic channel allocation (DCA) simulates the way a TD-SCDMA network allocates resource units to users accessing different services. The power control algorithm (see Figure 11.64) simulates the way a TD-SCDMA network regulates itself by using uplink and downlink power control in order to minimise interference and maximise capacity. HSDPA users (i.e., Packet (HSDPA) and Packet (HSPA) service users) are linked to the A-DPCH radio bearer (an R99 radio bearer). Therefore, the network uses uplink and downlink power control on A-DPCH, and then performs fast link adaptation on downlink in order to select an HSDPA radio bearer. Atoll simulates these network regulation mechanisms for each user distribution. During each iteration of the algorithm, all the mobiles selected during the user distribution generation attempt to connect one by one to network transmitters. The process is repeated until the network is balanced, i.e., until the convergence criteria (on UL and DL) are satisfied.
1091
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Figure 11.64: Schematic view of simulation algorithm As shown in Figure 11.64, the simulation algorithm is divided in three parts. All users are evaluated by the R99 part of the algorithm. HSDPA bearer users, unless they have been rejected during the R99 part of the algorithm, are then evaluated by the HSDPA part of the algorithm. Description of the R99 Part of the Simulation The R99 part of the algorithm simulates power control, congestion and radio resource control performed for R99 bearers for both R99 and HSDPA users. Atoll considers each user in the order in which the users are generated, and determines his best server. Atoll then selects the cell and the timeslot to be allocated to each user as follows: •
Atoll selects the preferred carrier defined in the properties of the service being used by the user if the preferred carrier is available on the best server and if there are enough resources available on it to accommodate the user. Otherwise, Atoll selects the carrier according to the selected DCA strategy.
•
Load: The least loaded cell or timeslot is selected. •
• •
Available RUs: The cell or timeslot with the most available resource units is selected. • •
•
Cell: Atoll calculates the number of available resource units for all the timeslots of all the cells of the user’s best server. Next, Atoll selects the carrier with most number of available resource units. Timeslot: Atoll selects the timeslots with the most available resource units.
Direction of Arrival: The cell or timeslot selected is the one which does not have an interfering mobile located nearby at the same angle as the direction of arrival of the targeted mobile. •
1092
Cell: Atoll calculates the ISCP (Interference Signal Code Power) for all the timeslots of all the cells of the user’s best server considering the effect of smart antenna equipment, if any. Next, Atoll selects the carrier with the lowest ISCP and the lowest load that has enough free timeslots to support the user’s service. Timeslot: Atoll selects the least loaded timeslots that have enough free OVSF codes for the user’s service.
Cell: Atoll calculates the number of interfering mobiles which are located in the same direction as the targeted user for all the timeslots of all the cells of the user’s best server. Next, Atoll selects the carrier with the lowest number of interfering mobiles in the direction of the targeted user.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
• •
Timeslot: Atoll selects the timeslots with the lowest number of interfering mobiles in the direction of the targeted user.
Sequential: Cells and timeslots are selected in a sequential order. • •
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 Eb⁄Nt or C⁄I threshold required by the service in the uplink, followed by the required traffic channel power in order to reach the Eb⁄Nt or C⁄I 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"
Even if constraints above are respected, the network (cell and timeslot) can be saturated: • • •
The maximum uplink load factor is exceeded (at admission or congestion): the status is either "Admission Rejection" or "UL Load Saturation" There are not enough resource units in the cell: the status is "RU Saturation" There is not enough power for cells: the status is "DL Load Saturation"
Description of the HSDPA Part of the Simulation In the HSDPA part, Atoll processes all HSDPA bearer users. The HSDPA part of the algorithm simulates fast link adaptation, the scheduling of HSDPA users, and radio resource control on downlink. Two fast link adaptations are done, one before mobile scheduling and one after. HSDPA bearer selection is based on look-up tables available in the HSDPA Bearer Selection tab of the reception equipment properties. The HSDPA and HS-SCCH powers of a cell are evaluated before calculating HS-PDSCH Ec⁄Nt. The HSDPA power (the power dedicated to HS-SCCH and HS-PDSCH of HSDPA bearer users) of a cell can be either fixed (statically allocated) or dynamically allocated. If it is dynamically allocated, the power allocated to HSDPA depends on how much power is required to serve R99 traffic. In other words, the power available after all common channels and all R99 traffic have been served is allocated to HS-PDSCH and HS-SCCH of HSDPA bearer users. Similarly, the power per HS-SCCH can be either fixed or dynamically allocated in order to attain the HS-SCCH Ec⁄Nt threshold. Using the HS-SCCH and HSDPA powers, Atoll evaluates the HS-PDSCH power (the difference between the HSDPA power and the HS-SCCH power), calculates the HS-PDSCH Ec⁄Nt and, from that, the HSDPA bearer defined for the terminal reception equipment and the user mobility). Similarly, the terminal power per HS-SICH in the uplink can be either fixed or dynamically allocated in order to attain the HS-SICH Ec⁄Nt threshold. Before mobile scheduling, each user is processed as if he is the only user in the cell. This means that Atoll determines the HSDPA bearer for each HSDPA user by considering the entire HSDPA power available of the cell. During scheduling, cell radio resources are shared between HSDPA users by the scheduler. The scheduler simultaneously manages the maximum number of users within each cell and ranks them according to the selected scheduling technique: •
• •
Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by the HS-PDSCH Ec⁄Nt. 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
1093
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
according to a random parameter which corresponds to a combination of the user rank in the simulation and the HS-PDSCH Ec⁄Nt. After mobile scheduling, Atoll carries out a second fast link adaptation. HSDPA users are processed in the order defined by the scheduler and the cell’s HSDPA power is shared among them.
11.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. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a 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 in the Network explorer. 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. When you are working on very large radio-planning projects, you can reduce memory consumption by selecting Only the average simulation and statistics under Information to retain.
6. Under Load constraints on the General tab, you can set the constraints that Atoll must respect during the simulation: •
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 max-
• •
imum uplink load factor defined for each timeslot in a cell, click the button ( ) beside the box and select Defined per timeslot. 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 timeslot.
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 "Smart Antenna Systems" on page 1137.
1094
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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 1091. 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 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 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 1081.
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. 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 "Network Settings" on page 1135. 15. Once you have defined the simulation, you can calculate it immediately or you can save it to calculate it later: • •
Calculate: Click Calculate to save the defined simulation and calculate it immediately OK: Click OK to save the defined simulation without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
All simulations created at the same time are grouped together in a folder in the Network explorer. You can now use the completed simulations for coverage predictions (see "Making Coverage Predictions Using Simulation Results" on page 1107).
11.3.5.3 Displaying the Traffic Distribution on the Map Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to service, activity status, or pilot signal strength. You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 43. In this section are the following examples of traffic distribution: • • •
"Displaying the Traffic Distribution by Activity Status" on page 1096. "Displaying the Traffic Distribution by Connection Status" on page 1096. "Displaying the Traffic Distribution by Service" on page 1097.
1095
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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 Windows" on page 38.
11.3.5.3.1
Displaying the Traffic Distribution by Activity Status In this example, the traffic distribution is displayed by the activity status. To display the traffic distribution by the activity status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "DL activity status" or "UL activity status" as the Field. 5. Click OK. The traffic distribution is now displayed by downlink or uplink activity status (see Figure 11.65).
Figure 11.65: Displaying the traffic distribution by downlink activity status
11.3.5.3.2
Displaying the Traffic Distribution by Connection Status In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Connection status" as the Field. 5. Click OK. The traffic distribution is now displayed by connection status (see Figure 11.66).
1096
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Figure 11.66: Displaying the traffic distribution by connection status
11.3.5.3.3
Displaying the Traffic Distribution by Service In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 11.67).
Figure 11.67: Displaying the traffic distribution by service
11.3.5.4 Displaying the User Best Server on the Map Atoll enables you to display on the map the best serving transmitter for each user generated by a simulation. To display the best server for a user: •
On the map, click and hold the icon of the user whose best server you want to display. The user’s best server is connected to the user with a line of the same colour as the serving transmitter. The best server is indicated with the number "1". Figure 11.68 shows a user with its best server.
1097
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Figure 11.68: The best server of a user
11.3.5.5 Displaying the Results of a Single Simulation After you have created a simulation, as explained in "Creating Simulations" on page 1094, you can display the results. To access the results of a single simulation: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. 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.
Results: Under Results, you will find data on connection results: • •
• •
•
The number of iterations that were run in order to converge. The number and the percentage of rejected users is given along with the reason for rejection. These figures include rejected users only. These figures are determined at the end of the simulation and depend on the network design. The number and the percentage of delayed users is given along with the reason for delay. The number and percentage of R99 bearer users connected to a cell, the number of users per activity status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPAbearer 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. Packet (HSDPA), and Packet (HSPA) service users are considered because they all request an HSDPA bearer.
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: • •
1098
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.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
• • • • • • •
Transmission loss (dB): The transmission loss as defined in the transmitter properties. Noise figure (dB): The noise figure as defined in the transmitter properties. Max power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties. P-CCPCH power [TS0] (dBm): The P-CCPCH power as defined in the cell properties. DwPCH power [DwPTS] (dBm): The DwPCH power as defined in the cell properties. Other CCH power [DL Traffic TS] (dBm): The power of other common channels per timeslot. DL load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total transmitted power and the maximum power (powers stated in W). When the constraint "DL load" is set, the DL Load cannot Used exceed the user-defined maximum DL load. P Cell =
PTimeslot Used
i
i ∈ DL
• •
DL traffic power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot. UL load factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between the UL – Load UL – Load = Avg ( F Timeslot ) uplink total interference and the uplink total noise. F Cell i ∈ UL
• •
i
UL noise rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget). DL load factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio between DL – Load DL – Load = Avg ( F Timeslot ) the downlink total interference and the downlink total noise. F Cell i ∈ DL
• •
•
• • • • • • • • • •
i
DL noise rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget). Number of DL radio links: The number of downlink radio links corresponds to the number of user-transmitter links on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive mobiles). This data indicates the number of users connected to the cell on the downlink. Number of UL radio links: The number of uplink radio links corresponds to the number of user-transmitter links on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive mobiles). This data indicates the number of users connected to the cell on the uplink. Connection success rate (%): The connection success rate gives the ratio of connected users to the total number of users in the cell. UL total requested throughput (kbps): The sum of all the uplink throughputs requested by the mobiles attempting to connect to a carrier. DL total requested rhroughput (kbps): The sum of all the downlink throughputs requested by mobiles attempting to connect to a carrier. UL total obtained throughput (kbps): The traffic carried by the cell in terms of throughput in the uplink. DL total obtained throughput (kbps): The traffic carried by the cell in terms of throughput in the downlink. Required UL resource units: The number of resource units required to carry the traffic demand in the uplink. UL resource units: The number of resource units used in the cell in the uplink. Required DL resource units: The number of resource units required to carry the traffic demand in the downlink. DL resource units: The number of resource units used in the cell in the downlink. Connection success rate (%) for each service: For each service, the connection success rate gives the ratio of connected users to the total number of users of that service in the cell.
The Timeslots tab: The Timeslots tab contains the following information, per site, transmitter, carrier, and timeslot: • • • • • • • • • •
•
•
•
Gain (dBi): The gain as defined in the antenna properties for that transmitter. Reception loss (dB): The reception loss as defined in the transmitter properties. Transmission loss (dB): The transmission loss as defined in the transmitter properties. Noise figure (dB): The noise figure as defined in the transmitter properties. Max power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties. P-CCPCH power [TS0] (dBm): The P-CCPCH power as defined in the cell properties. Resource units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a maximum of 16 resource units. Other CCH power (dBm): The power of other common channels per timeslot. DL traffic power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot. Available HS-PDSCH power (dBm): The available HS-PDSCH power as defined in the timeslot properties. This is the power available for the HS-PDSCH of HSDPA users. The value is either defined when the HS-PDSCH power is allocated statically, or determined by a simulation when the option HS-PDSCH dynamic power allocation is selected. Transmitted HSDPA power (dBm): The power transmitted by the cell to serve users connected to HSDPA radio bearers. If HSDPA power is allocated statically, the transmitted HSDPA power is equal to the available HSDPA power. If HSDPA power is allocated dynamically, the transmitted HSDPA power is the remaining power after allocation of power to the users connected to R99 radio bearers, and the power headroom. Angular distribution of UL and DL loads: The angular distribution of downlink transmitted power and uplink loads computed for cells whose transmitters have smart antenna equipment. This field contains binary data if you are using a third-party smart antenna model. Max DL load (% Pmax): The maximum percentage of downlink power that a cell can use. It is defined either in the cell properties or in the simulation creation dialogue.
1099
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
•
•
• • • •
© Forsk 2012
DL load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total transmitted power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL Load cannot exceed the user-defined Max DL Load. Max UL load factor (%): The maximum uplink load factor not to be exceeded. This limit is taken into account during the simulation if the option UL Load is selected. If the UL load option is not selected during a simulation, this value is not taken into consideration. UL load factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between the uplink total interference and the uplink total noise. UL noise rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget). DL load factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio between the downlink total interference and the downlink total noise. DL noise rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget).
The Mobiles tab: The Mobiles tab contains the following information: • • • • • • • • • •
• • • •
•
•
Name: The name of the mobile as assigned during the random user generation. X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second random trial). Service: The service assigned during the first random trial, during the generation of the user distribution. Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal and the user profile. User profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal and the user profile. Mobility: The mobility type assigned during the first random trial during the generation of the user distribution. DL activity status: The activity status on the downlink assigned during the first random trial, during the generation of the user distribution. UL activity status: The activity status on the uplink assigned during the first random trial, during the generation of the user distribution. Indoor: This field indicates whether indoor losses have been added or not. Connection status: The connection status indicates whether the user is connected or rejected at the end of the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection cause is given. HSDPA connection status: The connection status indicates whether the user is connected to an HSDPA radio bearer, delayed, or rejected at the end of the simulation. Best server: The user’s best server. P-CCPCH RSCP: The received signal code power on the P-CCPCH pilot channel. UL total requested throughput (kbps): For an R99 user, the uplink total requested 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 throughput (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 throughput (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 throughput (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 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.
•
•
1100
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,
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
• •
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 1094, 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: The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as explained in "Creating Simulations" on page 1094, you select "Detailed information about mobiles" under Information to retain. • • • • •
Name: The name assigned to the mobile. Value at receiver (dB): The value of the shadowing margin at the receiver. Clutter: The clutter class on which the mobile is located. Path to: The name of the potential transmitter. Value (dB): The shadowing value for the potential link in the corresponding Path to column. These values depend on the model standard deviation per clutter type on which the receiver is located and are randomly distributed on a gaussian curve.
The Initial Conditions tab: The Initial Conditions tab contains the following information: •
The global transmitter parameters: • • • •
•
The input parameters specified when creating the simulation: • • • • • • •
•
The spreading width 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 Eb⁄Nt or C⁄I, DL Eb⁄Nt or C⁄I, and UL Eb⁄Nt or C⁄I).
The parameters related to the clutter classes, including the default values.
1101
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
11.3.5.6 Displaying the Average Results of a Group of Simulations After you have created a group of simulations, as explained in "Creating Simulations" on page 1094, you can display the average results of the group. If you want to display the results of a single simulation of a group, see "Displaying the Results of a Single Simulation" on page 1098. To access the averaged results of a group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the group of simulations whose results you want to access. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation. The Statistics tab: The Statistics tab contains the following two sections: •
Request: Under Request, you will find data on the connection requests: • • •
•
Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; power control has not yet finished. The result depends on the traffic description and traffic input. During the first random trial, each user is assigned a service and an activity status. The number of users per activity status and the UL and DL rates that all users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and UL and DL rates) is given.
Results: Under Results, you will find data on connection results: • •
• •
•
The number of iterations that were run in order to converge. The number and the percentage of rejected users is given along with the reason for rejection. These figures include rejected users only. These figures are determined at the end of the simulation and depend on the network design. The number and the percentage of delayed users is given along with the reason for delay. The number and percentage of R99 bearer users connected to a cell, the number of users per activity status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPA 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 activity status, and the DL total rate that they generate. Packet (HSDPA), and Packet (HSPA) service users are considered because they all request an HSDPA bearer.
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: • • • • • • • • •
Gain (dBi): The gain as defined in the antenna properties for that transmitter. Reception loss (dB): The reception loss as defined in the transmitter properties. Transmission loss (dB): The transmission loss as defined in the transmitter properties. Noise figure (dB): The noise figure as defined in the transmitter properties. Max power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties. P-CCPCH power [TS0] (dBm): The P-CCPCH power as defined in the cell properties. DwPCH power [DwPTS] (dBm): The DwPCH power as defined in the cell properties. Other CCH power [DL Traffic TS] (dBm): The power of other common channels per timeslot. DL load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total transmitted power and the maximum power (powers stated in W). When the constraint "DL load" is set, the DL Load cannot Used exceed the user-defined maximum DL load. P Cell =
PTimeslot Used
i
i ∈ DL
• •
DL traffic power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot. UL load factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between the UL – Load UL – Load = Avg ( F Timeslot ) uplink total interference and the uplink total noise. F Cell i ∈ UL
1102
i
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
• •
UL noise rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget). DL load factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio between DL – Load DL – Load = Avg ( F Timeslot ) the downlink total interference and the downlink total noise. F Cell i ∈ DL
• •
•
• • • • • • • • • •
i
DL noise rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal degradation due to cell load (interference margin in the link budget). Number of DL radio links: The number of downlink radio links corresponds to the number of user-transmitter links on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive mobiles). This data indicates the number of users connected to the cell on the downlink. Number of UL radio links: The number of uplink radio links corresponds to the number of user-transmitter links on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive mobiles). This data indicates the number of users connected to the cell on the uplink. Connection success rate (%): The connection success rate gives the ratio of connected users to the total number of users in the cell. UL total requested throughput (kbps): The sum of all the uplink throughputs requested by the mobiles attempting to connect to a carrier. DL total requested rhroughput (kbps): The sum of all the downlink throughputs requested by mobiles attempting to connect to a carrier. UL total obtained throughput (kbps): The traffic carried by the cell in terms of throughput in the uplink. DL total obtained throughput (kbps): The traffic carried by the cell in terms of throughput in the downlink. Required UL resource units: The number of resource units required to carry the traffic demand in the uplink. UL resource units: The number of resource units used in the cell in the uplink. Required DL resource units: The number of resource units required to carry the traffic demand in the downlink. DL resource units: The number of resource units used in the cell in the downlink. Connection success rate (%) for each service: For each service, the connection success rate gives the ratio of connected users to the total number of users of that service in the cell.
The Timeslots tab: The Timeslots tab contains the following information, per site, transmitter, carrier, and timeslot: • • • • • • • • • •
•
•
• •
•
• • • •
Gain (dBi): The gain as defined in the antenna properties for that transmitter. Reception loss (dB): The reception loss as defined in the transmitter properties. Transmission loss (dB): The transmission loss as defined in the transmitter properties. Noise figure (dB): The noise figure as defined in the transmitter properties. Max power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties. P-CCPCH power [TS0] (dBm): The P-CCPCH power as defined in the cell properties. Resource units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a maximum of 16 resource units. Other CCH power (dBm): The power of other common channels per timeslot. DL traffic power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic timeslot. Available HS-PDSCH power (dBm): The available HS-PDSCH power as defined in the timeslot properties. This is the power available for the HS-PDSCH of HSDPA users. The value is either defined when the HS-PDSCH power is allocated statically, or determined by a simulation when the option HS-PDSCH dynamic power allocation is selected. Transmitted HSDPA power (dBm): The power transmitted by the cell to serve users connected to HSDPA radio bearers. If HSDPA power is allocated statically, the transmitted HSDPA power is equal to the available HSDPA power. If HSDPA power is allocated dynamically, the transmitted HSDPA power is the remaining power after allocation of power to the users connected to R99 radio bearers, and the power headroom. Angular distribution of UL and DL loads: The angular distribution of downlink transmitted power and uplink loads computed for cells whose transmitters have smart antenna equipment. This field contains binary data if you are using a third-party smart antenna model. Max DL load (% Pmax): The maximum percentage of downlink power that a cell can use. It is defined either in the cell properties or in the simulation creation 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).
1103
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
The Initial Conditions tab: The Initial Conditions tab contains the following information: •
The global transmitter parameters: • • • •
•
The input parameters specified when creating the simulation: • • • • • • •
•
The spreading width 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 Eb⁄Nt or C⁄I, DL Eb⁄Nt or C⁄I, and UL Eb⁄Nt or C⁄I).
The parameters related to the clutter classes, including the default values.
11.3.5.7 Updating Cell and Timeslot Values with Simulation Results After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 1094, you can update values for each cell with the results calculated during the simulation. The following values are updated: •
Cell: • •
•
Required resource units in uplink and downlink Number of HSDPA users
Timeslot: • • • • •
DL traffic power UL load factor UL reuse factor Available HSDPA power Angular distribution of UL and DL loads
To update cell and timeslot values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Select the Network explorer. b. Click the Expand button ( ) to expand the Simulations folder. c. Right-click the group of simulations whose results you want to access. d. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain simulation results for all simulations, both averaged and as a standard deviation. To display the results for a single simulation: a. Select the Network explorer. b. Click the Expand button ( ) to expand the Simulations folder. c. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. d. Select Properties from the context menu. A simulation properties dialogue appears. 2. Click the Timeslots tab. 3. On the Timeslots tab, click the Commit results button. The cell and timeslot values will be updated with the simulation or the average simulation results.
1104
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
11.3.5.8 Adding New Simulations to an Atoll Document When you have created a simulation or group of simulations, you can re-examine the same conditions by adding new simulations to the Atoll document. In Atoll, you can add new simulations in the following ways: •
Adding to a group: When you add one or more simulations to an existing group of simulations, Atoll reuses the same input (radio, traffic, and simulation parameters) as those used to generate the group of simulations. It then generates a new user distribution and performs the power control simulation. To add a simulation to a group of simulations, see "Adding a Simulation to a Group of Simulations" on page 1105.
•
Replaying a group: When you replay an existing group of simulations, Atoll uses the same user distribution (users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shadowing error distribution between simulations is different. Traffic parameter changes (such as maximum and minimum traffic channel powers allowed, Eb⁄Nt or C⁄I thresholds, etc.) can be taken into account. Finally, radio data modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during the power control (or rate/power control) simulation. To replay a group of simulations, see "Replaying a Simulation or Group of Simulations" on page 1105.
•
Using the Generator Initialisation Number: When you create groups of simulations using the same generator initialisation number (which must be an integer other than 0) Atoll generates the same user and shadowing error distributions (user with a service, a mobility, an activity status, and a shadowing error) in all groups using the same number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers allowed, Eb⁄Nt or C⁄I thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during the power control simulation. By creating and calculating one group of simulations, making a change to the network and then creating and calculating a new group of simulations using the same generator initialisation number, you can see the difference your parameter changes make. To create a new simulation to a group of simulations using the generator initialisation number, see "Adding a Simulation to a Group of Simulations" on page 1105.
•
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 1106.
Adding a Simulation to a Group of Simulations To add a simulation to an existing group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Right-click the group of simulations to which you want to add a simulation. The context menu appears. 4. Select New from the context menu. The properties dialogue of the group of simulations appears. 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 enter the Number of simulations to add to this group of simulations. 7. Click OK. Atoll immediately begins the simulation. Replaying a Simulation or Group of Simulations To replay an existing simulation or group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Right-click the group of simulations you want to replay. The context menu appears. 4. Select Replay from the context menu. The properties dialogue of the group of simulations appears.
1105
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
When replaying an existing group of simulations, most parameters used to calculate the group of simulations are reused for the replayed group. Consequently, few parameters can be changed for the replayed group. 5. On the General tab of the dialogue, you can set the following parameters: • •
From the Information to retain list, select the level of detail that will be available in the output as explained in "Creating Simulations" on page 1094. Under Load constraints, you can set the constraints that Atoll must respect during the simulation as explained in "Creating Simulations" on page 1094.
6. On the Source Traffic tab of the dialogue, select the Refresh traffic parameters check box if you want to take traffic parameter changes (such as maximum and minimum traffic channel powers allowed, Eb/Nt thresholds, etc.) into account in the replayed simulation. 7. On the Advanced tab, you can set the following parameters: • • • •
Max number of iterations: Enter the maximum number of iterations that Atoll should run to make convergence. 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 Eb/Nt or C/I. For more information on the quality threshold type, see "Network Settings" on page 1135.
8. On 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 "Smart Antenna Systems" on page 1137. 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 1091. Calculate interference between mobiles: Select the check box and enter a maximum distance to be considered between interfering mobiles in the Max distance box.
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. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. 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 1094. 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 1106. Duplicating a Group of Simulations To duplicate an existing group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Right-click the group of simulations you want to duplicate. The context menu appears. 4. Select Duplicate from the context menu. The properties dialogue for the duplicated group of simulations appears.
1106
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
You can change the parameters for the duplicated group of simulations as explained in "Creating Simulations" on page 1094.
11.3.5.9 Estimating a Traffic Increase When you create a simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increased traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates or users (for sector traffic maps). To change the global scaling factor: 1. Create a simulation or group of simulations by: • •
Creating a new simulation or group of simulations as described in "Creating Simulations" on page 1094. Duplicating an existing simulation or group of simulations as described in "Adding New Simulations to an Atoll Document" on page 1105.
2. Click the Source Traffic tab of the properties dialogue. 3. Enter a Global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates⁄users (for sector traffic maps).
11.3.6 Making Coverage Predictions Using Simulation Results When no simulations are available, Atoll uses the UL load factor, the DL total power, the UL reuse factor, the available HSDPA power, and the number of HSDPA users defined for each cell to make coverage predictions. For information on cell properties, see "Cell Description" on page 985; for information on modifying cell properties, see "Creating or Modifying a Cell" on page 989. Once you have made simulations, Atoll can use this information instead of the user-defined parameters in the cell properties to make coverage predictions where each pixel is considered as a probe user with a terminal, mobility, user profile, and service. To base a coverage prediction on a simulation or group of simulations, store the results of a simulation or the average results of a group of simulations in the Cells and Cell Parameters per Timeslot tables as explained in: •
"Updating Cell and Timeslot Values with Simulation Results" on page 1104.
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 Eb⁄Nt or C⁄I, or on a service Eb⁄Nt or C⁄I: • • • • •
•
Coverage predictions on noise and interference: • • •
•
Total Noise Level Analysis (DL): For information on making a downlink total noise coverage prediction, see "Studying Downlink Total Noise" on page 1046. 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 1048. UpPCH Interference Zones: For information on making a coverage analysis for UpPCH interference in case of UpPCH shifting, see "Studying UpPCH Interference" on page 1049.
A coverage prediction for baton handover analysis: •
•
P-CCPCH Quality Analysis (Eb⁄Nt) or P-CCPCH Quality Analysis (C⁄I): For information on making a P-CCPCH reception analysis, see "Making a Pilot Signal Quality Prediction" on page 1038. DwPCH Quality Analysis (C⁄I): For information on making a DwPCH reception analysis, see "Making a DwPCH Signal Quality Prediction" on page 1039. Service Area Analysis (Eb⁄Nt) (DL) or Service Area Analysis (C⁄I) (DL): For information on making a coverage prediction the downlink service area, see "Studying Downlink and Uplink Service Areas" on page 1043. Service Area Analysis (Eb⁄Nt) (UL) or Service Area Analysis (C⁄I) (UL): For information on making a coverage prediction the uplink service area, see "Studying Downlink and Uplink Service Areas" on page 1043. Effective Service Area Analysis (Eb⁄Nt) or Effective Service Area Analysis (C⁄I): For information on making a coverage analysis for the effective service area, see "Studying the Effective Service Area" on page 1045.
Baton Handover Zones: For information on making a baton handover coverage prediction, see "Making a Baton Handover Coverage Prediction" on page 1051.
An HSDPA coverage prediction to analyse HS-PDSCH quality and HSDPA data rate: •
HSDPA Quality and Throughput Analysis: For information on making an HSDPA coverage prediction, see "HSDPA Quality and Throughput Analysis" on page 1052.
1107
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
11.4 Verifying Network Capacity An important step in the process of creating a TD-SCDMA network is verifying the capacity of the network. This is done using measurements of the P-CCPCH RSCP in different locations within the area covered by the network. This collection of measurements is called a drive test data path. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: • • • • • • •
"Importing a Drive Test Data Path" on page 1108 "Displaying Drive Test Data" on page 1110 "Defining the Display of a Drive Test Data Path" on page 1111 "Network Verification" on page 1111 "Exporting a Drive Test Data Path" on page 1116 "Extracting CW Measurements from Drive Test Data" on page 1116 "Printing and Exporting the Drive Test Data Analysis Tool" on page 1117.
11.4.1 Importing a Drive Test Data Path In Atoll, you can analyse drive tests by importing drive test data in the form of ASCII text files (with tabs, commas, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: • •
The position of drive test data points: When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells): In TD-SCDMA networks, a cell is identified by its scrambling code. Therefore, you must indicate during the import process which columns contain the cells’ scrambling code and the scrambling code format (decimal or hexadecimal) used in the file. Because a scrambling code can belong to several groups, you can also indicate the group from which the scrambling code has been selected.
You can import a single drive test data file or several drive test data files at the same time. If you regularly import drive test data files of the same format, you can create an import configuration. The import configuration contains information that defines the structure of the data in the drive test data file. By using the import configuration, you will not need to define the data structure each time you import a new drive test data file. To import one or several drive test data files: 1. Select the Network explorer. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the file or files you want to open. You can import one or several files. If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing Shift and clicking the last file you want to import. You can select non-contiguous files by pressing Ctrl and clicking each file you want to import. 5. Click Open. The Import of Measurement Files dialogue appears. Files with the extension PLN, as well as some FMT files (created with previous versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue. 6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Import configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Import configuration, select an import configuration from the Import configuration list. b. Continue with step 9.
1108
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
•
When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. If several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters: • • •
Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement conditions, • •
Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document.
8. Click the Setup tab (see Figure 11.69).
Figure 11.69: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st measurement row, select the data Separator, and select the Decimal symbol used in the file. b. Click the Setup button to link file columns and internal Atoll fields. The Drive Test Data Setup dialogue appears. c. Under Measurement point position, select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in the drive test data file. You can also identify the columns containing the XY coordinates of each point in the drive test data file by selecting them from the Field row of the table on the Setup tab.
If you are importing data using Scrambling codes as cell identifiers: i.
Select By scrambling sode under Transmitter identification.
i.
In the Scrambling code identifier box, enter a string that is found in the column names identifying the scrambling code of scanned cells. For example, if the string "SC" is found in the column names identifying the scram-
1109
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
bling code of scanned cells, enter it here. Atoll will then search for columns with this string in the column name. ii. From the SC format list, select the scrambling code format, either "Decimal" or "Hexadecimal." iii. In the Scrambling code group identifier box, enter a string that is found in the column names identifying the scrambling code group of scanned cells. For example, if the string "SC_Group" is found in the column names identifying the scrambling code group of scanned cells, enter it here. Atoll will then search for columns with this string in the column name. If there is no scrambling code group information contained in the drive test data file, leave the Scrambling Code Group Identifier box empty. If you are importing data using Cell ID as cell identifiers: i.
Select By Cell ID under Transmitter identification.
i.
In the Cell ID identifier box, enter a string found in the column name identifying the Cell Ids of scanned cells. For example, if the string "Cell_ID" is found in the column names identifying the Cell_ID of scanned cells, enter it here. Atoll will then search for the column with this string in the column name.
d. Click OK to close the Drive Test Data Setup dialogue. •
•
If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Setup dialogue, Atoll should recognise all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "". If a column is marked with "", it will not be imported. The data in the file must be structured so that the columns identifying the scrambling code group and the scrambling code are placed before the data columns for each cell. Otherwise Atoll will not be able to properly import the file.
If you want to save the definition of the data structure so that you can use it again, you can save it as an import configuration: a. On the Setup tab, under Import configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll’s installation folder. If you cannot write into that folder, you can click the Browse button to choose a different location. c. Enter a Configuration name and an Extension of the files that this import configuration will describe (for example, "*.csv"). d. Click OK. Atoll will now select this import configuration automatically every time you import a drive test data path file with the selected extension. If you import a file with the same structure but a different extension, you will be able to select this import configuration from the Import configuration list. • •
•
You do not have to complete the import procedure to save the import configuration and have it available for future use. When importing a measurement file, you can expand the NumMeasINIfile.ini file by clicking the Expand button ( ) in front of the file under Import configuration to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Import configuration and clicking the Delete button.
9. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The drive test data are imported into the current Atoll document.
11.4.2 Displaying Drive Test Data When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see information about the active set at that location.
1110
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
To display information about a single drive test data point: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Select the display check box beside the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want active set information. Atoll displays an arrow pointing towards the serving cells (see Figure 11.73 on page 1115), 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 44.
11.4.3 Defining the Display of a Drive Test Data Path You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to manage permanent labels on the map, tip text and the legend. In other words, the display of measurement path are managed in the same way as sites, transmitters, etc. To display the Display tab of a drive test data path’s Properties dialogue: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path whose display you want to manage. The context menu appears. 4. Select Properties from the context menu, 5. Click the Display tab. Each point can be displayed by a unique attribute or according to: • •
a text or integer attribute (discrete value) a numerical value (value interval).
In addition, you can display points by more than one criterion at a time using the Advanced option in the Display Type list. When you select Advanced from the Display type list, a dialogue opens in which you can define the following display for each single point of the measurement path: • • •
a symbol according to any attribute a symbol colour according to any attribute a symbol size according to any attribute
You can, for example, display a signal level in a certain colour, choose a symbol type for Transmitter 1 (a circle, triangle, cross, etc.) and a symbol size according to the altitude. • • •
•
Fast display forces Atoll to use the lightest symbol to display the points. This is useful when you have a very large number of points. You can not use Advanced if the Fast display check box has been selected. You can sort drive test data paths in alphabetical order in the Network explorer by right-clicking the drive test data path and selecting Sort Alphabetically from the context menu. You can save the display settings (such as colours and symbols) of a drive test data path in a user configuration file to make them available for use on another drive test data path. To save or load the user configuration file, click the Actions button on the Display tab of the path properties dialogue and select Save or Load from the Display Configuration submenu.
11.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 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 1112 "Predicting the Signal Level on Drive Test Data Points" on page 1112
1111
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
• • •
© Forsk 2012
"Displaying Statistics Over a Drive Test Data Path" on page 1113 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 1114 "Analysing Data Variations Along the Path" on page 1114.
11.4.4.1 Filtering Incompatible Points Along Drive Test Data Paths When using a drive test data path, some measured points may present values that are too far outside the median values to be useful. As well, drive test data paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from the more lightly populated region between the two. You can filter out unreliable measurement points from the drive test data path you are studying either geographically, by filtering by clutter classes and the focus zone, or by using an advanced filter. To filter out measurement points by clutter class: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to filter out measurement points. The context menu appears. 4. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 5. Under Clutter classes, clear the check boxes of the clutter classes you want to exclude. Measurement points located on the excluded clutter classes will be filtered out. 6. Select the Use focus zone to filter check box to use the focus zone as part of the filter. Measurement points located outside the focus zone will be filtered out. 1. If you want to permanently delete the measurement points outside the filter, select the Delete points outside the filter check box. • •
You can apply a filter on all the drive test data paths in the Drive Test Data folder by selecting Filter from the context menu of the folder. If you want to use the measurement points that you permanently deleted, you will have to import the drive test data path again.
To filter out measurement points using an advanced filter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to filter out measurement points. The context menu appears. 4. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 5. Click More. The Filter dialogue appears. For more information on using the Filter dialogue, see "Advanced Data Filtering" on page 96. You can update heights (of the DTM, and clutter heights) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones by selecting Refresh Geo Data from the context menu of the Drive Test Data Paths folder.
11.4.4.2 Predicting the Signal Level on Drive Test Data Points To predict the signal level on drive test data points: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to create the point prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Point predictions, select Point Signal Level and click OK. The Point Signal Level Properties dialogue appears (see Figure 11.70).
1112
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Figure 11.70: Point Signal Level Properties dialogue The errors between measured and predicted signal levels can be calculated and added to the drive test data table. 6. If you want to calculate errors between measured and predicted signal levels, under Select signal levels for error calculations, select the names of the columns representing measured signal level values in the drive test data table for which you want to calculate the errors (see Figure 11.71). If you do not want to add this information to the drive test data table, continue with step 7.
Figure 11.71: Selecting Measured Signal Levels for which Errors will be Calculated 7. Click OK. A new point prediction is created for the selected drive test data path. 8. Right-click the drive test data path. The context menu appears. 9. Select Calculations > Calculate All the Predictions from the context menu. If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the drive test data table for the predicted point signal level from the serving cell and the errors between the measured and predicted values.
Figure 11.72: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations) New columns are also added for the predicted point signal level from each neighbour cell and the errors between the predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Data Variations Along the Path" on page 1114. The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main matrix. For more information on propagation models, see Chapter 5: Working with Calculations in Atoll.
11.4.4.3 Displaying Statistics Over a Drive Test Data Path Assuming some predictions have been calculated along a Drive Test Data path, you can display the statistics between the measured and the predicted values on a specific measurement path.
1113
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To display the statistics for a specific Drive Test Data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to display comparative statistics. The context menu appears. 4. Select Display Statistics from the context menu. The Measurement and Prediction Fields Selection dialogue appears. 5. Under For the following transmitters, select one or more transmitters to include in the statistics. 6. Under Select the predicted values, select the fields that contain the predicted values that you wish to use in the statistics. 7. Under Select the measured values, select the fields that contain the measured values that you wish to use in the statistics. 8. Enter the Measured values range for the statistics. Only the measured values within this range will be included in the statistics. 9. Click OK. Atoll opens a window listing statistics of comparison between measured and predicted values.
11.4.4.4 Extracting a Field From a Drive Test Data Path for a Transmitter You can extract a specific field for a specific transmitter on each point of an existing drive test data path. The extracted information will be added to a new column in the table for the drive test data. To extract a field from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to extract a field. The context menu appears. 4. Select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter dialogue appears. 5. Under On the transmitter, select the transmitter for which you wish to extract a field. 6. Under For the fields, select the fields that you wish to extract for the selected transmitter. 7. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitter and with the selected values.
11.4.4.5 Analysing Data Variations Along the Path In Atoll, you can analyse variations in data along any drive test data path using the Drive Test Data analysis tool. You can also use the Drive Test Data analysis tool to see which cell is the serving cells of points.
1114
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
To analyse data variations using the Drive Test Data analysis tool. 1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears (see Figure 11.73).
Figure 11.73: The Drive Test Data analysis tool 2. In the Drive Test Data analysis tool, click the Display button. The Display Parameters dialogue appears (see Figure 11.74).
Figure 11.74: Drive test data display parameters 3. In the Display Parameters dialogue: • • •
Select the check box next to each field you want to display in the Drive Test Data analysis tool. If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new colour from the palette that appears. Click OK to close the Display Parameters dialogue. You can change the display status or the colour of more than one field at the same time by selecting several fields. You can select contiguous fields by clicking the first field, pressing Shift and clicking the last field. You can select non-contiguous fields by pressing Ctrl and clicking each field. You can then change the display status or the colour by right-clicking on the selected fields and selecting the choice from the context menu. The selected fields are displayed in the Drive Test Data analysis tool.
1115
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
4. You can display the data in the drive test data path in the following ways: • •
Click the values in the Drive Test Data analysis tool. Click the points on the drive test data path in the map window.
5. The drive test data path appears in the map window as an arrow pointing towards the serving cell, with a number identifying the best server (see Figure 11.73 on page 1115). 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 44. 6. You can display a secondary Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters dialogue. You select the value to be displayed from the right-hand list at the top of the Drive Test Data analysis tool. The values are displayed in the colour defined in the Display Parameters dialogue. 7. You can zoom in on the graph displayed in the Drive Test Data analysis tool in the following ways: •
Zoom in or out: i.
Right-click the Drive Test Data analysis tool. The context menu appears.
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 analysis tool on one end of the range of data you want to zoom in on. The context menu appears.
ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data analysis tool on the other end of the range of data you want to zoom in on. The context menu appears. iv. Select Last Zoom Point from the context menu. The Drive Test Data analysis tool zooms in on the data between the first zoom point and the last zoom point. 8. Click the data in the Drive Test Data analysis tool to display the selected point in the map window. Atoll will centre the map window on the selected point if it is not presently visible. If you open the table for the drive test data you are displaying in the Drive Test Data analysis tool, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data analysis tool (see Figure 11.73 on page 1115).
11.4.5 Exporting a Drive Test Data Path You can export drive test data paths to vector files. To export a drive test data path to a vector file: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path you want to export. The context menu appears. 4. Select Export from the context menu. The Save As dialogue appears. 5. Enter a File name for the drive test data path and select a format from the Save as type list. 6. Click Save. The drive test data path is exported and saved in the file.
11.4.6 Extracting CW Measurements from Drive Test Data You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path from which you wish to export CW measurements. The context menu appears. 4. Select Extract CW Measurements from the context menu. The CW Measurement Extraction dialogue appears.
1116
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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 Extraction parameters of CW measurement paths: a. Enter the Min. number of points to extract per measurement path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured signal levels. CW measurements are created with drive test data points where the signal levels are within this specified range. 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.
11.4.7 Printing and Exporting the Drive Test Data Analysis Tool You can print and export the contents of the Drive Test Data analysis tool. To print or export the contents of the Drive Test Data analysis tool: 1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears (see Figure 11.73 on page 1115). 2. Define the display parameters and zoom level as explained in "Analysing Data Variations Along the Path" on page 1114. 3. Right-click the Drive Test Data analysis tool. The context menu appears. • •
To print the Drive Test Data analysis tool, select Print from the context menu. To export the Drive Test Data window, select Copy from the context menu, then paste.
11.5 Co-planning TD-SCDMA Networks with Other Networks Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a TD-SCDMA and a GSM network for the same area in Atoll, and then work with Atoll’s co-planning features to study the mutual impacts of the two networks. Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other network’s Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In this section, the following are explained: • • • • •
"Switching to Co-planning Mode" on page 1117. "Working with Coverage Predictions in a Co-Planning Project" on page 1119. "Performing Inter-technology Neighbour Allocation" on page 1122. "Creating a TD-SCDMA Sector From a Sector in the Other Network" on page 1133. "Ending Co-planning Mode" on page 1133.
11.5.1 Switching to Co-planning Mode Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a TD-SCDMA Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, the TD-SCDMA document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document.
1117
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems.
To switch to co-planning mode: 1. Open the main document. •
Select File > Open or File > New > From an Existing Database.
2. Link the other document with the open main document. a. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document. b. Select Document > 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]. 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 Atoll’s co-planning features are now available. When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll synchronises the display for the following: • • • •
Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.
Displaying Both Networks in the Same Atoll Document After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 1117, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the explorer window of the linked document to the explorer window of the main document (e.g., you can display GSM sites and measurement paths in a TD-SCDMA document). To display sites from the linked document in the main document: 1. Click the linked document’s map window. The linked document’s map window becomes active and the explorer window shows the contents of the linked document. 2. Select the Network explorer. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In from the context menu, and select the name of the main document from the submenu that opens. The Sites folder of the linked document is now available in the main document. The explorer window of the main document now contains a folder named Sites in [linked document], where [linked document] is the name of the linked document. If you want the Sites folder of the linked document to appear in the main document automatically, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual. The same process can be used to link other folders in one document, folders such as CW Measurements, Drive Test Data, Clutter Classes, Traffic, and Digital Terrain Model, etc., in the other document. Once the folders are linked, you can access their properties and the properties of the items in the folders from either of the two documents. Any changes you make in the linked document are taken into account in the both the linked and main docu-
1118
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
ments. However, because working document is the main document, any changes made in the main document are not automatically taken into account in the linked document. If you close the linked document, Atoll displays a warning icon (
) in the main document’s explorer window, and the linked
items are no longer accessible from the main document. You can load the linked document in Atoll again by right-clicking the linked item in the explorer window of the main document, and selecting Open Linked Document. The administrator can create and set a configuration file for the display parameters of linked and main document transmitters in order to enable you to distinguish them on the map and to be able to select them on the map using the mouse. If such a configuration file has not been set up, you can choose different symbols, sizes and colours for the linked and the main document transmitters. For more information on folder configurations, see "Folder Configurations" on page 105. You can also set the tip text to enable you to distinguish the objects and data displayed on the map. For more information on tip text, see "Defining the Object Type Tip Text" on page 46. 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 Windows" on page 39. Figure 11.75 shows an example of TD-SCDMA transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in tip text.
Figure 11.75: GSM and TD-SCDMA Transmitters displayed on the map
11.5.2 Working with Coverage Predictions in a Co-Planning Project Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: • •
"Updating Coverage Predictions" on page 1119 "Analysing Coverage Predictions" on page 1120.
11.5.2.1 Updating Coverage Predictions You can access the properties of the coverage predictions in the linked Predictions folder in the main document’s explorer window. After modifying the linked coverage prediction properties, you can update them from the main document. To update a linked coverage prediction: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears.
1119
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button (
) in the Radio Planning toolbar.
When you click the Calculate button, Atoll first calculates uncalculated and invalid path loss matrices and then unlocked coverage predictions in the main and linked Predictions folders. When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions" on page 218. 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 Radio Planning toolbar.
When you click the Force Calculate button, Atoll first removes existing path loss matrices, recalculates them and then calculates unlocked coverages predictions defined in the main and linked Predictions folders. To prevent Atoll from calculating coverage predictions in the linked Predictions folder, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual.
11.5.2.2 Analysing Coverage Predictions In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tip text to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which coverage predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following are explained: • • • • •
11.5.2.2.1
"Co-Planning Coverage Analysis Process" on page 1120 "Displaying the Legend Window" on page 1121 "Comparing Coverage Prediction Results Using Tip Text" on page 1121 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 1121 "Studying Differences Between Coverage Areas" on page 1122.
Co-Planning Coverage Analysis Process The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes. The recommended process for analysing coverage areas, and the effect of parameter modifications in one network on the other, is as follows: 1. Create and calculate a Coverage by 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 1018 and "Making a Coverage Prediction by P-CCPCH RSCP" on page 1017. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tip text contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage prediction’s 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 1118. 5. Optimise the main network by changing parameters such as antenna azimuth and tilt or the pilot power.
1120
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
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 1121 and "Studying Differences Between Coverage Areas" on page 1122. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.
11.5.2.2.2
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to Legend check box on the Display tab. To display the Legend window: •
11.5.2.2.3
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction in the main and linked Predictions folders, identified by the name of the coverage prediction.
Comparing Coverage Prediction Results Using Tip Text You can compare coverage predictions by by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. Atoll displays information for all displayed coverage predictions in both the working and the linked documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Co-Planning Coverage Analysis Process" on page 1120). To get coverage prediction results in the form of tip text: •
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 11.28). The tip text for the working document is on top and the tip text for the linked document, with the linked document identified by name is on the bottom.
Figure 11.76: Comparing coverage prediction results using tip text
11.5.2.2.4
Comparing Coverage Areas by Overlaying Coverage Predictions You can compare the coverage areas of the main and linked documents by overlaying coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is dislayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 43.
1121
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The coverage prediction is dislayed on the map. 11. Right-click the coverage prediction. The context menu appears. 12. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 13. Modify the display parameters of the coverage prediction. 14. Calculate the two coverage predictions again, if needed. To more easily view differences between the coverage areas, you can also change the order of the Predictions folders in the explorer window. For more information on changing the order of items in the explorer window, see "Working with Layers Using the Explorer Windows" on page 39.
11.5.2.2.5
Studying Differences Between Coverage Areas You can compare coverage predictions to find differences in coverage areas. To compare coverage predictions: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 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 document’s Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 1029.
11.5.3 Performing Inter-technology Neighbour Allocation The following sections describe the features available in Atoll that help the RF planner to carry out inter-technology neighbour planning. For example, handovers between a TD-SCDMA and a GSM network can be studied in Atoll by allocating neighbour GSM sectors to TD-SCDMA cells. In this section, the following are explained: • • • • • • •
"Setting Inter-technology Exceptional Pairs" on page 1122 "Configuring Importance Factors for Inter-technology Neighbours" on page 1124 "Allocating Inter-technology Neighbours Automatically" on page 1125 "Displaying Inter-technology Neighbours on the Map" on page 1127 "Allocating and Deleting Inter-technology Neighbours per Cell" on page 1127 "Calculating the Importance of Existing Inter-technology Neighbours" on page 1130 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 1132.
In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Coplanning Mode" on page 1117.
11.5.3.1 Setting Inter-technology Exceptional Pairs You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears.
1122
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
4. Select Neighbours > Inter-technology > Exceptional Pairs from the context menu. The Inter-technology Exceptional Pairs table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list. c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. 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 cell’s inter-technology neighbours and exceptional pairs by using its Properties dialogue. To open a cell’s Properties dialogue: 1. Select the Network explorer. 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 cell’s Properties dialogue appears. 5. Click the Inter-technology Neighbours tab. In GSM, the Inter-technology Neighbours tab is found on the transmitter’s Properties dialogue. Displaying Inter-technology Exceptional Pairs on the Map You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table. To display exceptional pairs defined between the main and the linked documents: 1. Click the main document’s map window. 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
3. Select Display Options from the menu. The Neighbour Display 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 links: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines.
6. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
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 Edit Relations on the Map button ( ) in the Radio Planning toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Edit Relations on the Map 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 41).
1123
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the map. Adding and Removing Inter-technology Exceptional Pairs on the Map You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-technology Exceptional Pairs on the Map" on page 1123. 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. 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 41).
11.5.3.2 Configuring Importance Factors for Inter-technology Neighbours You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Inter-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. In a GSM project, you must select Neighbours > Inter-technology > Configure Importance from the Transmitters folder’s context menu.
1124
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: • • •
Distance factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. 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 1125.
5. Click OK.
11.5.3.3 Allocating Inter-technology Neighbours Automatically Atoll can automatically determine handover relations between networks of different technologies, for example, TD-SCDMA and GSM. In this case, inter-technology handovers from TD-SCDMA to GSM may occur when the TD-SCDMA coverage is not continuous. The network’s overall coverage is extended by a TD-SCDMA-to-GSM handover. Atoll can automatically determine neighbours in the linked document for cells in the main document and vice versa. 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 document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > 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 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.
1125
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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 cell’s coverage area that the neighbour’s 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
Description
When
Exceptional Pair
Neighbour relation is defined as an exceptional pair.
Force exceptional pairs is selected
Co-site
The neighbour is located at the same site as the reference cell.
Force co-site as neighbours is selected
Distance
The neighbour is within the maximum distance from the reference cell.
Use coverage overlapping is not selected
% of covered area and overlapping area
Neighbour relation that fulfils coverage conditions.
Use coverage overlapping is selected
Existing
The neighbour relation existed before running the automatic allocation.
Reset is not selected
12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: •
Click Compare. The list of automatically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: • • • •
The document name and the neighbour allocation type, 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.
1126
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
14. Click Close.
11.5.3.4 Displaying Inter-technology Neighbours on the Map You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios. To display neighbours in the linked document for cells in the main document: 1. Click the main document’s map window. 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
3. Select Display Options from the menu. The Neighbour Display dialogue appears. 4. Under Inter-technology Neighbours, select the Display links check box. 5. Under Advanced, select the neighbour links to display: •
•
•
Outwards non-symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards non-symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric links: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines.
6. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) on the Radio Planning toolbar. A menu
7. Select Neighbours as the type of neighbour links to display. 8. Click the Edit Relations on the Map button ( ) on the Radio Planning toolbar. Neighbours are now displayed on the map until you click the Edit Relations on the Map button again. 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, 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 41). If you select the Display links check box under Intra-technology neighbours, Atoll displays both inter-technology and intratechnology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.
11.5.3.5 Allocating and Deleting Inter-technology Neighbours per Cell Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the transmitter Properties dialogue, or using the Inter-technology Neighbours table.
1127
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
This section explains the following: • • •
"Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1128. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 1128. "Allocating and Removing Inter-technology Neighbours on the Map" on page 1129.
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 transmitter’s Properties dialogue: 1. On the main document’s map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitter’s 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 cell’s Properties dialogue appears. 5. Click the Inter-technology Neighbours tab. 6. If desired, you can enter the Max number of neighbours. 7. Allocate or delete a neighbour. To allocate a new neighbour: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Under List, select the cell from the list in the Neighbour column in the row marked with the New row icon (
).
c. 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 Source to "manual." To create a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. Select Make Symmetrical 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Press DEL to delete the neighbour. 8. Click OK. In GSM, the Inter-technology Neighbours tab is available in each transmitter’s Properties dialogue. Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears.
1128
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
4. Select Neighbours > Inter-technology > Neighbours from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour. 6. Allocate or delete a neighbour. To allocate an inter-technology neighbour: a. In the row marked with the New row icon (
), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Source to "manual." To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Make Symmetrical 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 Make Symmetrical from the context menu. 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. You can add or delete either forced neighbours or forbidden neighbours using the Intertechnology Exceptional Pairs 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 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 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. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press Del to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector). Allocating and Removing Inter-technology Neighbours on the Map You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-technology Neighbours on the Map" on page 1127.
1129
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press Shift and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press Shift and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press Ctrl and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter. T remove an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press Ctrl and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference transmitter from the list of inter-technology neighbours of the other transmitter. To add an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. There can be two cases: • •
If the two transmitters already have a symmetric neighbour relation, press Ctrl and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation. If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour relation by pressing Shift and clicking the transmitter with which you want to create a symmetric relation. Then press Ctrl and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric inter-technology neighbour relation.
To remove an inwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press Shift and click the transmitter you want to remove from the list of neighbours. Atoll removes the transmitter from the inter-technology neighbours list of the other transmitter. 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 41).
11.5.3.6 Calculating the Importance of Existing Inter-technology Neighbours After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone and in the selected folder. To calculate the importance of existing inter-technology neighbours: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 5. Select the Inter-technology Neighbours tab. 6. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as potential neighbours. 7. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance.
1130
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
8. Clear the Use overlapping coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 10. Otherwise, select the Use overlapping coverage check box if you want to base the neighbour importance calculation on coverage conditions. 9. Under Coverage conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for cells in the main document. The 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. 10. If you cleared the Use overlapping coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max inter-site distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated. 11. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. •
Cell: The name of the reference cell.
1131
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
• • •
© Forsk 2012
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.
12. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
11.5.3.7 Checking the Consistency of the Inter-technology Neighbour Plan You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Neighbours tab. 5. Define the parameters of the audit: • • •
• • • • •
Average no. of neighbours: Select the Average no. of neighbours check box if you want to verify the average number of neighbours per cell. Empty lists: Select the Empty lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full lists: Select the Full lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list) and set the value in the Default max number text box. Lists > max number: Select the Lists > max number check box if you want to verify which cells have more than the maximum number of neighbours allowed and set the value in the Default max number text box. Missing co-sites: Select the Missing co-sites check box if you want to verify which cells have no co-site neighbours. Missing symmetrics: Select the Missing symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance between neighbours: Select the Distance between neighbours check box and enter the distance between neighbours that should not be exceeded.
6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: •
Average number of neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty lists: x⁄X; x number of cells out of a total of X have no neighbours (or empty neighbours list). Syntax:
•
Full lists (default max number = Y): x⁄X; x number of cells out of a total of X have Y number of neighbours listed in their respective neighbours lists. Syntax:
•
|CELL|
|CELL|
|NUMBER|
|MAX NUMBER|
Lists > max number (default max number = Y): x⁄X; x number of cells out of a total of X have more than Y number of neighbours listed in their respective neighbours lists. Syntax:
|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:
•
|NEIGHBOUR|
Non-symmetric links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
1132
|CELL|
|CELL|
|NEIGHBOUR| |TYPE|
|REASON|
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
Missing forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|NEIGHBOUR|
Existing forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
•
|CELL|
|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.5.4 Creating a TD-SCDMA Sector From a Sector in the Other Network You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main document’s map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new TD-SCDMA transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document. To update the display settings of the new sector: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder of the main document. The context menu appears. 4. Select Update Folder Configuration from the context menu.
Figure 11.77: New sector – Before and after applying the configuration The azimuths and mechanical tilts of secondary antennas or remote antennas are not included when you select Update Folder Configuration and have to be set up manually.
11.5.5 Ending Co-planning Mode once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents.
1133
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select Document > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.
11.6 Advanced Configuration In this section, the following advanced configuration options are explained: • • • • • • • •
"Modelling Inter-carrier Interference" on page 1134 "Defining Frequency Bands" on page 1134 "Network Settings" on page 1135 "Smart Antenna Systems" on page 1137 "Defining HSDPA Radio Bearers" on page 1143 "Creating Site Equipment" on page 1143 "Receiver Equipment" on page 1144 "Modelling Shadowing" on page 1145.
11.6.1 Modelling Inter-carrier Interference If you want Atoll to take into account the interference between two carriers, you must create a carrier pair with an interference reduction factor. Atoll will take the interference reduction factor into account on both the uplink and the downlink. To define the interference reduction factor between a pair of carriers: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Frequencies folder. 4. In the Frequencies folder, right-click Inter-carrier Interference Reduction Factors. The context menu appears. 5. Select Open Table. The Inter-carrier Interference Reduction Factors table appears. 6. For each carrier pair for which you want define inter-carrier interference: a. Enter the first carrier of the pair in the 1st carrier column. b. Enter the second carrier of the pair in the 2nd carrier column. c. Enter an interference reduction factor in the Reduction factor (dB) column. When Atoll calculates interference, it subtracts the interference reduction factor from the calculated interference. An interference reduction factor of 0 dB means that the interference between the pair of carriers is the same as between cells using the same carrier. The interference reduction factor must be a positive value.
For every pair of carriers that is not defined, Atoll assumes that there is no inter-carrier interference. d. Press Enter to create the carrier pair and to create a new row.
11.6.2 Defining Frequency Bands To define frequency bands: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Frequencies folder. 4. In the Frequencies folder, right-click Bands. The context menu appears. 5. Select Open Table. The Frequency Bands table appears.
1134
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
6. In the Frequency Bands table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each frequency band, enter: • • • •
Name: Enter a name for the frequency, for example, "Band 2010." This name will appear in other dialogues when you select a frequency band. Average frequency (MHz): Enter the average frequency. First carrier: Enter the number of the first carrier in this frequency band. Last carrier: Enter the number of the last carrier in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First carrier field. When you have more than one frequency band, the carriers must be numbered sequentially, contiguously (i.e., you cannot skip numbers in a range of carriers, and the range of carriers in one band cannot overlap the range of carriers in another), and uniquely (i.e., you can only use each number once). For example: Band 2010: First carrier: 0; Last carrier 1 and Band 900: First carrier: 2; Last carrier: 2
7. When you have finished adding frequency bands, click the Close button (
).
You can also access the properties dialogue of each individual frequency band by double-clicking the left margin of the row with the frequency band.
11.6.3 Network Settings Atoll allows you to set network level parameters which are common to all the transmitters and cells in the network. These parameters are used in coverage predictions as well as during Monte Carlo simulations by the radio resource management and scheduling algorithms. This section explains the options available on the Global Parameters and Calculation Parameters tabs of the Network Settings folder properties, and explains how to access the tabs: • • •
"The Options on the Global Parameters Tab" on page 1135. "The Options on the Calculation Parameters Tab" on page 1136 "Modifying Global Network Settings" on page 1137.
11.6.3.1 The Options on the Global Parameters Tab The global TD-SCDMA parameters 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. Atoll converts the power values defined in the cell properties (i.e., DwPCH and other common channel powers) when you change the option. On the other hand, the values for the minimum and maximum traffic channel powers have to be modified manually. Quality threshold type: Under Quality threshold type, you can select whether the signal quality thresholds entered in the mobility types and radio bearers are Eb⁄Nt or C⁄I. 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 Eb⁄Nt, all the signal quality thresholds are considered to be defined in terms of Eb⁄Nt. If you calculate a C⁄I-based coverage prediction or simulation, Atoll converts the thresholds from Eb⁄Nt to C⁄I, by removing the processing gain from the Eb⁄Nt values, in order to calculate and compare C⁄I. Similarly, if the Quality threshold type is set to C⁄I, and the calculations are performed for Eb/Nt, Atoll converts all C⁄I thresholds to Eb⁄Nt 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.
1135
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
Processing Gain Calculation Example The processing gain is the ratio between the chip rate transmitted on the air interface and the data rate of a service. G P = Processing Gain = W ----R
Where W is the chip rate for TD-SCDMA, and R is the data rate per timeslot of the service. TS
The chip rate is calculated from the number of data chips per timeslot ( N Data Chips ) and the subframe duration ( D Subframe ): TS
N Data Chips 704 W = -------------------------= --------------- = 140800 bps 0.005 D Subframe
If the downlink and uplink data rates of a service are 384 kbps and 64 kbps respectively, the service data rates per timeslot can be calculated by dividing by the number of timeslots (here, 3 in downlink and 1 in uplink): R
DL
UL 384000 64000 = -------------------- = 128000 bps and R = ---------------- = 64000 bps 3 1
The uplink and downlink processing gains will be: DL
GP
•
•
•
UL 140800 140800 = -------------------- = 1.1 = 0.414 dB and G P = -------------------- = 2.2 = 3.4242 dB 128000 64000
Spreading factor: Under Spreading factor, you have the minimum and maximum spreading factors allowed in TD-SCDMA: • Min: The lowest spreading factor that can be used (1). • Max: The highest spreading factor that can be used (16). Interference: Under Interference, you can define the parameter used to calculate interference on the downlink. • Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus thermal noise, or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the signal of the studied cell. HSDPA: Under HSDPA, you can define how total noise is calculated for HSDPA. • Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus thermal noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the signal of the studied cell.
Other non-modifiable parameters are shown for information: •
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).
11.6.3.2 The Options on the Calculation Parameters Tab The Calculation Parameters tab has the following options: •
1136
Min interferer reception threshold: This value is used by Atoll to limit the input of interferers in calculations. The performance of TD-SCDMA-specific coverage predictions and Monte Carlo simulations can be improved by setting a high
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
•
• •
value of the minimum interferer reception threshold. This value is used as a filter criterion on the signal level received from interferers. Atoll will discard all interferers with a signal level lower than this value. Min P-CCPCH RSCP threshold: The minimum P-CCPCH RSCP threshold. The value is used as a filter criterion on the received P-CCPCH RSCP when calculating TD-SCDMA-specific predictions. Atoll does not display any result on the pixel if the best server P-CCPCH RSCP is lower than the defined minimum P-CCPH RSCP threshold. Height: The receiver height at which the path loss matrices and coverage predictions are calculated. Calculations made on mobile users (from traffic maps) in Monte Carlo simulations are also carried out at this receiver height. Max range: The maximum coverage range of transmitters in the network. Each transmitter in a TDD network has a maximum coverage range. This maximum system range is defined by the distance after which the uplink and downlink signals can interfere with each other. The default value for the maximum system range is 11250 m, which is the distance corresponding to the duration of the guard period in the pilot timeslot. The maximum system range can be calculated as follows: Each subframe of 5 ms duration contains 1 pilot timeslot and 7 downlink or uplink timeslots. The pilot timeslot is divided into a downlink pilot timeslot (DwPTS), a guard period (GP), and uplink pilot timeslot (UpPTS). The lengths of DwPTS, GP, and UpPTS are 96, 96, and 160 chips, respectively. Each of the other 7 timeslots contains 704 data chips, 144 midamble chips, and 16 guard period chips. All in all, a 5 ms subframe contains 6400 chips. The duration of the guard period of the pilot can be calculated as: 0.005 D GP = --------------- × 96 = 75 μs 6400
The maximum system range is half the distance that the RF signal can travel in DGP: 8
75 μs × 3 × 10 m/s R System = ----------------------------------------------------- = 11250 m 2
11.6.3.3 Modifying Global Network Settings You can change global network settings in the Network Settings Properties dialogue. To change global network settings: 1. Select the Parameters explorer. 2. Right-click the Network Settings folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Global Parameters tab. In this tab you can set the following parameters: DL powers (Absolute or Relative to pilot), Quality threshold type (Eb/Nt or C/I), Spreading rate, P-CCPCH processing gain, Spreading factor (Min and Max), Nt in Interference calculations (Total noise or Without useful signal). 5. Select the Calculation Parameters tab. On this tab you can set the following parameters: • • •
Calculation limitation: In the Calculation limitation section, you can enter the Min interferer reception threshold and Min P-CCPCH RSCP threshold. Receiver: In the Receiver section, you can enter the receiver Height. System: In the System section, select the Max range check box if you want to apply a maximum system range limit, and enter the maximum system range in the text box to the right.
11.6.4 Smart Antenna Systems Smart antenna systems use digital signal processing with more than one antenna element in order to locate and track various types of signals to dynamically minimise interference and maximise the useful signal reception. Different types of smart antenna modelling techniques exist, including beam switching, beam steering, beamforming, etc. Adaptive antenna systems are capable of using adaptive algorithms to cancel out interfering signals. Atoll includes the following smart antenna models: •
Beam-switching smart antennas Also referred to as grid of beams (GOB). For more information, see "Grid of Beams (GOB)" on page 1138.
•
Beam-steering smart antennas For more information, see "Adaptive Beam Model" on page 1139.
•
Beamforming smart antennas For more information, see "Conventional Beamformer" on page 1140 and "Optimum Beamformer" on page 1140
•
Other smart antenna models
1137
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
For more information on statistical modelling, see "Statistical Model" on page 1140, and for more information on 3rdparty smart antenna modelling, see "Third-Party Smart Antenna Models" on page 1141. Grid of beams, optimum beamformer, conventional beamformer, adaptive beam, and third-party models require Monte Carlo simulations to simulate the effect of the dynamic channel allocation (DCA) and power control. The results generated by the Monte Carlo simulations using the smart antenna equipment based on any of these methods are stored in the TD-SCDMA document, and can be reused for coverage predictions. The statistical model does not require Monte Carlo simulations. Statistical modelling is based on simulation results in terms of probabilities of C⁄I gains, and can be used directly in coverage predictions. The smart antenna equipment that uses statistical modelling contains a list of C⁄I gain graphs that depend on the spreading angle. The following section explains how to work with smart antenna equipment in Atoll: •
"Smart Antenna Equipment" on page 1141.
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 1091.
11.6.4.1 Grid of Beams (GOB) In Atoll TD-SCDMA, a list of beams (antenna patterns) can be used to create grid of beams smart antenna equipment. A GOB in Atoll comprises a list of antenna patterns. Each antenna pattern usually has a different azimuth. All the antenna 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 folder’s 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. Although the number of beams in a GOB is not limited, calculation times with a large number of beams will be longer.
11.6.4.1.1
Working with Grid of Beams (GOB) The following sections explain how to create and import grids of beams: • • • •
"Creating a Grid of Beams (GOB)" on page 1138. "Adding Antennas to a Grid of Beams (GOB)" on page 1139. "Importing a Grid of Beams (GOB)" on page 1139. "The Grid of Beams (GOB) Import Format" on page 1139.
Creating a Grid of Beams (GOB) In Atoll, a grid of beams is a list of antennas. A list of antennas can include any number of antennas listed in the Antennas folder. To create an antenna list: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click the Antennas folder. The context menu appears. 4. Select Antenna List > Open Table from the context menu. The Antenna Lists table appears. 5. Create a new antenna list in the row marked with the New row icon (
).
6. Click the Properties button. The New Antenna List Properties dialogue appears. 7. Select the antennas from the Antennas column to add to the antenna list in each new row. 8. Click OK. 9. Click the Close button (
) 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.
1138
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
Adding Antennas to a Grid of Beams (GOB) You can add antennas, or beams, from the antennas folder to an existing grid of beams or antenna list. To add antennas to an antenna list: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Click the Expand button ( ) to expand the Antennas folder. 4. Right-click the antenna that you want to add to an antenna list. The context menu appears. 5. Select Add the Antenna to a List from the context menu. The Antenna Addition in a List dialogue appears. 6. Select the antenna list to which you want to add the antenna from the Antenna list. 7. Click OK to add the antenna to the list. You can also add all the antennas in the Antennas folder or a view to an antenna list by selecting Antenna List > Add Antennas to a List from the folder’s context menu. Importing a Grid of Beams (GOB) You can import existing antenna lists to be used as grids of beams in Atoll. To import an antenna list: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Right-click the Antennas folder. The context menu appears. 4. Select Antenna List > Import Antennas from a List from the context menu. The Open dialogue appears. 5. Select an Index file to import. 6. Click Open to import the antenna list to Atoll. The Import of antennas from a list dialogue appears. 7. Enter a name for the new antenna list. 8. Click OK to import the antenna list. Atoll adds the antennas referred to in the index file to the Antennas folder, and adds the new antenna list to the Antenna Lists table. The Grid of Beams (GOB) Import Format Atoll supports standard, Planet-like antenna list format for export and import. An index file contains the list of files containing the horizontal antenna patterns and a file containing the vertical antenna pattern. The horizontal antenna pattern files have the following format: • • • • • • • •
NAME: Name of the antenna MAKE: Name of manufacturer FREQUENCY: Operating frequency (in MHz) H_WIDTH: Horizontal beamwidth (in degrees) FRONT_TO_BACK: Front to back gain ratio (in dB) GAIN: Antenna gain (in dBi) HORIZONTAL: Horizontal pattern range (in degrees) DEGREE: Attenuation (this row is repeated for every degree value)
The vertical antenna pattern file has the following format: • • • •
NAME: Name of the antenna V_WIDTH: Vertical beamwidth (in degrees) VERTICAL: Vertical pattern range (in degrees) DEGREE: Attenuation (this row is repeated for every degree value)
11.6.4.2 Adaptive Beam Model The ideal adaptive beam model available in Atoll TD-SCDMA makes use of a selected beam (antenna) pattern. You can create adaptive beam smart antenna equipment and assign it an antenna pattern from the antennas available in the Antennas folder. During Monte Carlo simulations, Atoll orients the selected antenna pattern horizontally towards each mobile generated in order to maximise the received signal.
1139
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
In downlink, all the interfering signals received at each mobile are attenuated according to the antenna pattern of the adaptive beam. If the targeted and interfered users are in the same direction with respect to the beam directed towards the targeted user, the interference will be high. Otherwise, the interfering signals will be attenuated. In uplink, the interfering signals received at the cell are attenuated according to the antenna pattern of the adaptive beam. The results given by adaptive beam modelling correspond to those that would be obtained under ideal conditions. The targeted user will have maximum gain and all the interference will be successfully cancelled.
11.6.4.3 Conventional Beamformer The conventional beamformer performs beamforming in downlink and uplink. The smart antenna model dynamically calculates and applies weights on each antenna element in order to create beams in the direction of served users. The antenna patterns created for transmission and reception have a main beam pointed in the direction of the useful signal. The smart antenna model supports linear adaptive array systems. You can create smart antenna equipment by defining how many antenna elements the equipment has and assigning it a single element pattern from the antennas available in the Antennas folder. During Monte Carlo simulations, smart antenna equipment using this model form beams towards each served mobile by calculating the complex weights of the steering vector.
11.6.4.4 Optimum Beamformer The optimum beamformer performs beamforming in downlink, and beamforming and interference cancellation in the uplink using an MMSE (Minimum Mean Square Error) algorithm. The smart antenna model dynamically calculates and applies weights on each antenna element in order to create beams in the direction of served users. In uplink, the Minimum Mean Square Error algorithm models the effect of null steering towards interfering mobiles. The antenna patterns created for downlink transmission have a main beam pointed in the direction of the useful signal. In the uplink, in addition to the main beam pointed in the direction of the useful signal, there can also be one or more nulls in the directions of the interfering signals. If the optimum beamformer uses L antenna elements, it is possible to create L–1 nulls and, thereby, cancel L–1 interfering signals. In a mobile environment where the sources of interference are not stationary, the antenna patterns are adjusted so that the nulls remain in the direction of the moving interference sources. The smart antenna model supports linear adaptive array systems. You can create smart antenna equipment by defining how many antenna elements the equipment has and assigning it a single element pattern from the antennas available in the Antennas folder. During Monte Carlo simulations, smart antenna equipment using this model form a beam towards each served mobile in the downlink by calculating the complex weights of the steering vector. In the uplink, apart from forming a beam in the direction of each served mobile, the smart antenna equipment is also capable of cancelling interference by steering nulls (high attenuation points formed by the smart antenna) towards the interferers.
11.6.4.5 Statistical Model 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 C⁄I 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 C⁄I gain to take into account in the prediction. The C⁄I gain considered in the coverage prediction is determined using the probability threshold set. The C⁄I gain used corresponds to the cumulative probability, i.e., 100% less the probability threshold entered. For example, for a probability threshold of 80%, the cumulative probability is 20%. If an exact value of C⁄I gain is not available for the calculated cumulative probability, Atoll performs linear interpolation between the two available values on either side. If no C⁄I 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 C⁄I 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).
1140
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
11.6.4.6 Third-Party Smart Antenna Models If you have a third-party smart antenna model available, you can use it in Atoll TD-SCDMA using Atoll’s smart antenna API. Atoll’s smart antenna enables you to interface with any external smart antenna module with Atoll. Any external smart antenna models available are listed in the Smart Antenna Models folder in the Parameters explorer. Atoll is fully capable of using the features of any external smart antenna model, MMSE-based (Minimum Mean Square Error), EBBbased (Eigen-Beam Beamforming), etc.
11.6.4.7 Smart Antenna Equipment 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. You can use several types of smart antenna equipment in your TD-SCDMA document based on different smart antenna modelling methods. To create new smart antenna equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Click the Expand button ( ) to expand the Smart Antennas folder. 4. Right-click Smart Antenna Equipment. The context menu appears. 5. Select Open Table. The Smart Antenna Equipment table appears. 6. In the table, create one piece of smart antenna equipment per row. For information on using data tables, see "Working with Data Tables" on page 69. For each piece of smart antenna equipment, enter a Name and some Comments, if you want, and select an Smart antenna model. The available smart antenna models are Grid of Beams (GOB), Adaptive Beam, Optimum Beamformer, Conventional Beamformer, Statistical, and any 3rd-party models that you might have installed. If you selected Grid of Beams (GOB), Adaptive Beam, Optimum Beamformer, Conventional Beamformer, or Statistical as the Smart Antenna Model, continue with step 7. If you selected any 3rd party model as the Smart Antenna Model, continue with step 12. 7. Right-click a smart antenna equipment in the table. The context menu appears. 8. Select Record Properties. The smart antenna properties dialogue appears. 9. On the General tab of this dialogue, you can modify the Name, Smart antenna model, and Comments. 10. Under Smart antenna model, click the Parameters button. A dialogue opens with the parameters specific to the selected smart antenna model. •
If you selected Grid of Beams (GOB) or Adaptive Beam as smart antenna model, this dialogue lets you select the downlink and uplink beam patterns (from the Antennas Lists table). You can also view the beam patterns. •
•
•
You can use the combined antenna pattern display to understand any inconsistencies in smart antenna results. If the beams and the main antenna do not have the same gains, the smart antenna could provide worse results than the main antenna for traffic timeslots.
If you selected Conventional Beamformer or Optimum Beamformer as the smart antenna model, this lets you define the number of elements in the smart antenna array and select a single element pattern to be used in downlink as well as uplink. If you selected Statistic as smart antenna model, this dialogue lets you define the probability threshold used to read the C⁄I gain graphs, and the C⁄I gain graphs for different spreading angles.
11. Click OK to close the smart antenna properties dialogue. 12. Click the Close button (
) to close the Smart Antenna Equipment table.
Properties of external third-party smart antenna models may vary. You can access their properties from the Smart Antenna Models folder in the Parameters explorer.
1141
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
11.6.5 Radio Bearers Bearers are used by the network for carrying information. In this section, the following are explained: • •
"Defining R99 Radio Bearers" on page 1142 "Defining HSDPA Radio Bearers" on page 1143
11.6.5.1 Defining R99 Radio Bearers Bearer services are used by the network for carrying information. The R99 Radio Bearer table lists all the available radio bearers. You can create new R99 radio bearers and modify existing ones by using the R99 Radio Bearer table. Only the following R99 radio bearer parameters are used in predictions: • • • •
Max TCH power Uplink and downlink TCH RSCP thresholds per mobility Uplink and downlink TCH Eb/Nt thresholds or uplink and downlink TCH C/I thresholds per mobility The type of bearer. You can select whether the TCH thresholds you define are Eb/Nt or C/I thresholds. For more information, see "Network Settings" on page 1135.
To create or modify an R99 radio bearer: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Radio Bearers folder. 4. Right-click the R99 Radio Bearers folder. The context menu appears. 5. Select Open Table from the context menu. The R99 Radio Bearers table appears. 6. In the R99 Radio 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. Nominal downlink rate (kbps): Enter or modify the nominal downlink rate. Type: Select or modify the service type. There are four classes: Conversational, Streaming, Interactive, and Background. This field corresponds to the QoS (quality of service) class or traffic class that the bearer will belong to. Min TCH power (dBm): Enter the minimum downlink traffic channel power. The minimum and maximum traffic channel power make up the dynamic range for downlink power control. Max TCH power (dBm): Enter the maximum downlink traffic channel power. The maximum and minimum traffic channel powers can be either absolute values or values relative to the pilot power. For more information, see "Network Settings" on page 1135.
• • • •
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.
To define the number of downlink and uplink timeslots for different spreading factors: 7. Right-click an R99 bearer in the table. The context menu appears. 8. Select Record Properties. The R99 bearer’s properties dialogue appears. 9. Under Resource units, click the Browse button ( tion dialogue appears.
) to the right of the timeslot field. The Resource Unit Consump-
10. In the Resource Unit Consumption dialogue, you can enter the number of OVSF codes of each length used for each timeslot. This information is used to carry out network dimensioning and to simulate the Dynamic Channel Allocation (DCA) algorithm. For information on calculating network capacity, see "Calculating TD-SCDMA Network Capacity" on page 1078. For information on the dynamic channel allocation, see "The Monte Carlo Simulation Algorithm" on page 1091. 11. Click OK.
1142
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
12. Click the Close button (
) to close the table.
11.6.5.2 Defining HSDPA Radio Bearers In each cell, the scheduler selects the HSDPA resource per UE and per TTI (Transmission Time Interval). This HSDPA resource is called a TFRC (Transport Format Resource Combination) and is the set of parameters such as the transport format, the modulation scheme, and the number of used HS-PDSCH channels. In Atoll, the TFRC are referred to as HSDPA radio bearers. During a simulation, and for the HSDPA coverage prediction, Atoll selects a suitable HSDPA radio bearer and uses its RLC peak rate. The HSDPA radio bearer selection is based on UE capabilities (maximum number of HS-PDSCH channels, transport block size, modulation supported), cell capabilities (maximum number of HS-PDSCH channels), and reported CQI. The HSDPA Radio Bearer table lists the available HSDPA radio bearers. You can create new HSDPA radio bearers and modify existing ones by using the HSDPA Radio Bearer table. To open the HSDPA Radio Bearer table: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Radio Bearers folder. 4. Right-click the HSDPA Radio Bearers folder. The context menu appears. 5. Select Open Table from the context menu. The HSDPA Radio Bearers table appears with the following information: • • • • • • •
Radio bearer index: The bearer index number. Transport block size (Bits): The transport block size in bits. Modulation: The modulation used. You can choose between QPSK or 16QAM. Number of HS-PDSCH channels used per TS: The number of HS-PDSCH channels used per used timeslot. 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. UE category: The HSDPA user equipment category that supports the HSDPA radio bearer.
6. Click the Close button (
) to close the table.
11.6.5.3Defining HSUPA Radio Bearers The HSUPA Radio Bearers table lists the available HSUPA radio bearers. You can create new HSUPA radio bearers and modify existing ones by using the HSUPA Radio Bearer table. To open the HSUPA Radio Bearers table: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Radio Bearers folder. 4. Right-click the HSUPA Radio Bearers folder. The context menu appears. 5. Select Open Table from the context menu. The HSUPA Radio Bearers table appears with the following information: • • • • • • •
Radio bearer index: The bearer index number. Transport block size (Bits): The transport block size in bits. Number of E-PUCH channels used per TS: The number of E-PUCH channels used per used timeslot. 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 HSUPA radio bearer. HSUPA UE category: The HSUPA user equipment category that supports the HSUPA radio bearer. Modulation: The modulation used. You can choose between QPSK or 16QAM.
6. Click the Close button (
) to close the table.
11.6.6 Creating Site Equipment To create a new piece of TD-SCDMA site equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Radio Resource Management folder. 4. Right-click Site Equipment. The context menu appears.
1143
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
5. Select Open Table from the context menu. The Site Equipment table appears. 6. In the Equipment table, each row describes a piece of equipment. For information on working with data tables, see "Working with Data Tables" on page 69. 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. If MCJD is not supported by the equipment, enter 0 as value.
7. Click the Close button (
) to close the table.
11.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 UE categories. In this section the following are explained: • • •
"Creating or Modifying Reception Equipment" on page 1144. "HSDPA UE Categories" on page 1145. "HSUPA UE Categories" on page 1145.
11.6.7.1 Creating or Modifying Reception Equipment In Atoll, reception equipment models the reception characteristics of user terminals and is used when you create a terminal. The graphs defined for each reception equipment are used for quality predictions and for selecting bearers. To create or modify reception equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Reception Equipment folder. 4. Double-click the reception equipment type you want to modify. The reception equipment type’s Properties dialogue appears. You can create a new reception equipment type by right-clicking the Reception Equipment folder and selecting New from the context menu.
5. Click the General tab. On the General tab, you can define the Name of the reception equipment. 6. Click the R99 Bearer Selection tab. On the R99 Bearer Selection tab, you can define downlink and uplink Eb⁄Nt or C⁄I requirements (in dB) and the TCH thresholds (in dBm). The Eb⁄Nt, or C⁄I, quality targets are used to determine the coverage area for the service, and the TCH thresholds must be reached to provide users with the service. These parameters depend on the mobility type. Using Transmission and Reception diversity results in a quality gain on received downlink and uplink Eb⁄Nt or C⁄I. You can specify gains on received downlink and uplink Eb⁄Nt or C⁄I for each diversity configuration. Atoll considers them when transmission and reception diversity configurations are assigned to transmitters. • • • • • • • • • •
1144
R99 bearer: Select an R99 bearer from the list. Mobility: Select a mobility type from the list. Uplink TCH Eb/Nt Threshold (dB) or Uplink TCH C/I Threshold (dB): Enter or modify the uplink Eb⁄Nt 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 Eb⁄Nt 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.
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
AT312_UM_E1
7. Click the HSDPA Bearer Selection tab. On the HSDPA Bearer Selection tab, you can enter the values of the Required HS-PDSCH Ec/Nt for the Radio bearer index of each HSDPA radio bearer for different Mobility types. If you leave the Mobility column empty, the same value will be considered valid for all mobility types. 8. Click the HSUPA Bearer Selection tab. On the HSUPA Bearer Selection tab, you can enter the values of the Required E-PUCH Ec/Nt for the Radio bearer index of each HSDPA radio bearer for different Mobility types. If you leave the Mobility column empty, the same value will be considered valid for all mobility types. 9. Click OK to close the reception equipment type’s Properties dialogue.
11.6.7.2 HSDPA UE Categories HSDPA user equipment capabilities are standardised into 15 different categories according to 3GPP specifications. To edit an HSDPA user equipment category: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the UE Categories folder. 4. Right-click HSDPA UE Categories. The context menu appears. 5. Select Open Table from the context menu. The HSDPA UE Categories table appears. 6. The HSDPA UE Categories table has the following columns: • • • • • •
Index: Each HSDPA UE category is a separate record in the table and has a unique index. Category name: Name of the HSDPA UE category. Max number of HS-PDSCH channels used by HSDPA TS: The maximum number of HS-PDSCH channels allowed to be used by HSDPA timeslots for the category. Max transport block size (bits): The maximum transport block size allowed for the category. Highest modulation: The highest modulation supported by the UE category. Max number of HS-PDSCH TS per TTI: The maximum number of HS-PDSCH timeslots allowed within a TTI (transmission time interval).
11.6.7.3 HSUPA UE Categories HSUPA user equipment capabilities are standardised into 6 different categories according to 3GPP specifications. To edit an HSUPA user equipment category: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the UE Categories folder. 4. Right-click HSUPA UE Categories. The context menu appears. 5. Select Open Table from the context menu. The HSUPA UE Categories table appears. 6. The HSUPA UE Categories table has the following columns: • • • • • •
Index: Each HSUPA UE category is a separate record in the table and has a unique index. Category name: Name of the HSUPA UE category. Max number of E-PUCH channels used by HSUPA TS: The maximum number of E-PUCH channels allowed to be used by HSUPA timeslots for the category. Max transport block size (bits): The maximum transport block size allowed for the category. Highest modulation: The highest modulation supported by the UE category. Max number of HS-PUCH TS per TTI: The maximum number of E-PUCH timeslots allowed within a TTI (transmission time interval).
11.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
1145
Atoll 3.1.2 User Manual Chapter 11: TD-SCDMA Networks
© Forsk 2012
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 Eb⁄Nt values. For information on setting the model standard deviation and the Eb⁄Nt standard deviations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. Shadowing can be taken into consideration when Atoll calculates the signal level and Eb⁄Nt for: • •
A point analysis (see "Making a Point Analysis to Study the Profile" on page 1006). A coverage prediction (see "Studying Signal Level Coverage" on page 1007).
Atoll always takes shadowing into consideration when calculating a Monte Carlo-based TD-SCDMA simulation. You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per Clutter Class" on page 1146.
11.6.8.1 Displaying the Shadowing Margins per Clutter Class To display the shadowing margins per clutter class: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins dialogue appears. 4. You can set the following parameters: • •
Cell edge coverage probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard deviation: Select the type of standard deviation to be used to calculate the shadowing margin or macrodiversity gains: • • • •
From model: The model standard deviation. Atoll will display the shadowing margin of the signal level. P-CCPCH Eb⁄Nt or C⁄I: The P-CCPCH Eb⁄Nt or C⁄I standard deviation. Atoll will display the P-CCPCH Eb⁄Nt or C/ I shadowing margin. DL Eb⁄Nt or C⁄I: The DL Eb⁄Nt or C⁄I standard deviation. Atoll will display the DL Eb⁄Nt or C⁄I shadowing margin. UL Eb⁄Nt or C⁄I: The UL Eb⁄Nt or C⁄I standard deviation. Atoll will display the UL Eb⁄Nt or C⁄I shadowing margin
5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.
1146
Chapter 12 WiMAX BWA Networks This chapter provides the information to use Atoll to design, analyse, and optimise a WiMAX BWA network.
In this chapter, the following are explained: •
"Designing a WiMAX Network" on page 1149
•
"Planning and Optimising WiMAX Base Stations" on page 1150
•
"Configuring Network Parameters Using the AFP" on page 1230
•
"Studying Network Capacity" on page 1240
•
"Optimising Network Parameters Using the ACP" on page 1270
•
"Verifying Network Capacity" on page 1272
•
"Co-planning WiMAX Networks with Other Networks" on page 1283
•
"Advanced Configuration" on page 1300
•
"Tips and Tricks" on page 1319
•
"Glossary of WiMAX Terms" on page 1327
Atoll 3.1.2 User Manual Chapter 12: Starting a Project
1148
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12 WiMAX BWA Networks WiMAX (Wireless Interoperability for Microwave Access) refers to a group of broadband wireless access (BWA) standards that use the SOFDMA (Scalable Orthogonal Frequency Division Multiple Access) technology. The WiMAX air interface is described in the IEEE 802.16e standard. 802.16e networks are mobile broadband wireless access networks which use SOFDMA, support handovers, and user speeds of up to 100 km/hr. Atoll enables you to design IEEE 802.16e broadband wireless access networks. Atoll can predict radio coverage, manage mobile and fixed subscriber data, and evaluate network capacity. Atoll WiMAX also supports smart antennas and MIMO. Atoll enables you to model fixed and mobile users in WiMAX environments. The data input corresponding to fixed subscribers, which is an important requirement of fixed wireless access networks, is modelled using a subscriber database. 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 and subscriber data. Atoll uses these user distributions as input for the simulations. You can create coverage predictions to analyse the following and other parameters for WiMAX channels in downlink and in uplink: • • •
Signal levels The carrier-to-interference-and-noise ratio Service areas and radio bearer coverage
Coverage predictions that depend on the network’s traffic loads can be created from either Monte Carlo simulation results or from a user-defined network load configuration (uplink and downlink traffic loads, and uplink noise rise). GSM GPRS EDGE, CDMA2000, UMTS HSPA, TD-SCDMA, and LTE networks can be planned in the same Atoll session. Before working with the Atoll WiMAX module for the first time, it is highly recommended to go through the "Glossary of WiMAX Terms" on page 1327. This will help you get accustomed to the terminology used in Atoll.
12.1 Designing a WiMAX Network Figure 12.1 depicts the process of creating and planning a WiMAX network. The steps involved in planning a WiMAX network are described below. The numbers refer to Figure 12.1. 1. Open an existing radio-planning document or create a new one ( 1 ). • •
You can open an existing Atoll document by selecting File > Open. Creating a new Atoll document is explained in Chapter 2: Starting an Atoll Project.
2. Configure the network by adding network elements and changing parameters ( 2 ). You can add and modify the following elements of base stations: • • •
"Creating or Modifying a Site" on page 1158. "Creating or Modifying a Transmitter" on page 1158. "Creating or Modifying a Cell" on page 1159.
You can also add base stations using a base station template (see "Placing a New Base Station Using a Station Template" on page 1159). 3. Carry out basic coverage predictions ( 3 ). • •
"Making a Point Analysis to Study the Profile" on page 1175. "Studying Signal Level Coverage" on page 1176 and "Signal Level Coverage Predictions" on page 1185.
4. Allocate neighbours ( 4 ). •
"Planning Neighbours" on page 1217.
5. Allocate frequencies ( 5 ). •
"Planning Frequencies" on page 1233.
6. Allocate preamble indexes ( 6 ). •
"Planning Preamble Indexes" on page 1234.
1149
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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 1240). You can define cell load conditions manually either on the Cells tab of each transmitter’s Properties dialogue or in the Cells table (see "Creating or Modifying a Cell" on page 1159) ( 7d ).
8. Make WiMAX-specific signal quality coverage predictions using the defined cell load conditions ( 8 ). •
"WiMAX Coverage Predictions" on page 1199.
9. If necessary, modify network parameters to study the network with a different frequency plan ( 10 ). After modifying the network’s frequency plan, you must perform steps 7 and 8 again. 1
2
3
4
5
6 7a
7d
7c
7b 7
8
9
10
Figure 12.1: Planning a WiMAX network - workflow
12.2 Planning and Optimising WiMAX Base Stations As described in Chapter 2: Starting an Atoll Project, you can create an Atoll document from a template, with no base stations, or from a database with an existing set of base stations. As you work on your Atoll document, you will still need to create base stations and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any other additional equipment, such as the TMA, feeder cables, etc. In a WiMAX project, you must also add cells to each transmitter. A cell refers to the characteristics of an RF channel on a transmitter. Atoll lets you create one site, transmitter, or cell at a time, or create several at once using station templates. In Atoll, a base station refers to a site and a transmitter with its antennas, equipment, and cells.
1150
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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 creating services, users, user profiles, traffic environments, and terminals. This data can be then used to make coverage predictions that depend on network load, such as C/(I+N), service area, radio bearer, and throughput coverage predictions. In this section, the following are explained: • • • • • • • • • • • • •
"Creating a WiMAX Base Station" on page 1151. "Creating a Group of Base Stations" on page 1165. "Modifying Sites and Transmitters Directly on the Map" on page 1166. "Display Tips for Base Stations" on page 1166. "Creating a Multi-band WiMAX Network" on page 1167. "Creating a Repeater" on page 1167. "Creating a Remote Antenna" on page 1171. "Setting the Working Area of an Atoll Document" on page 1174. "Studying a Single Base Station" on page 1175. "Studying Base Stations" on page 1178. "Planning Neighbours" on page 1217. "Planning Frequencies" on page 1233. "Planning Preamble Indexes" on page 1234.
12.2.1 Creating a WiMAX Base Station When you create a site, you create only the geographical point; you must add the transmitters and cells afterwards. The site with a transmitter and its antennas, equipment, and cells is called a base station. In this section, each element of a base station is described. If you want to add a new base station, see "Placing a New Base Station Using a Station Template" on page 1159. If you want to create or modify one of the elements of a base station, see "Creating or Modifying a Base Station Element" on page 1157. If you need to create a large number of base stations, Atoll allows you to import them from another Atoll document or from an external source. For information, see "Creating a Group of Base Stations" on page 1165. This section explains the various parts of the base station creation process: • • • • •
"Definition of a Base Station" on page 1151. "Creating or Modifying a Base Station Element" on page 1157. "Placing a New Base Station Using a Station Template" on page 1159. "Managing Station Templates" on page 1160. "Duplicating an Existing Base Station" on page 1164.
12.2.1.1 Definition of a Base Station A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. You will usually create a new base station using a station template, as described in "Placing a New Base Station Using a Station Template" on page 1159. This section describes the following elements of a base station and their parameters: • • •
12.2.1.1.1
"Site Description" on page 1151 "Transmitter Description" on page 1152 "Cell Description" on page 1155.
Site Description The parameters of a site can be found in the site’s Properties dialogue. The Properties dialogue has the following tab: •
The General tab (see Figure 12.2): • •
Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If you want to change the default name that Atoll gives to new sites, see the Administrator Manual. Position: By default, Atoll places the new site at the centre of the map window. You can modify the location of the site here. While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 41.
1151
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
•
© Forsk 2012
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.
Figure 12.2: New Site dialogue
12.2.1.1.2
Transmitter Description The parameters of a transmitter can be found in the transmitter’s 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 1155), the Propagation tab (see Chapter 5: Working with Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 43). •
The General tab: •
•
•
•
Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You can enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names transmitters, see the Administrator Manual. Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can click the Browse button ( ) to access the properties of the site. For information on the site Properties dialogue, see "Site Description" on page 1151. You can click the New button to create a new site for the transmitter. Shared antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the same site or on sites with the same position and that share the same antenna. The entry in the field must be the same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. This field is also used for dual-band transmitters to synchronise antenna parameters for different frequency bands. Under Antenna position, you can modify the position of the antennas (main and secondary): • •
1152
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 this option if you want to enter the coordinates of the antenna, and then enter the x-axis and y-axis coordinates of the antenna, X and Y, respectively.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
The Transmitter tab (see Figure 12.3):
Figure 12.3: Transmitter dialogue - Transmitter tab •
Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed with a specific icon in the Transmitters folder of the Network explorer. Only active transmitters are taken into consideration during calculations.
•
Transmitter type: If you want Atoll to consider the transmitter as a potential server as well as an interferer, set the transmitter type to Intra-network (Server and interferer). If you want Atoll to consider the transmitter only as an interferer, set the type to Inter-network (Interferer only). No coverage for an interferer-only transmitter will be calculated for coverage predictions and it will not serve any mobile in Monte Carlo simulations. This enables you to model the co-existence of different networks in the same geographic area. For more information on how to study interference between co-existing networks, see "Modelling the Co-existence of Networks" on page 1327.
•
•
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 12.4), 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 176.
•
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 176. Transmitter: You can select transmitter equipment from the Transmitter list. You can click the Browse button
•
• •
( ) to access the properties of the transmitter equipment. For information on creating transmitter equipment, see "Defining Transmitter Equipment" on page 176. 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.
1153
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.4: The Equipment Specifications dialogue Any loss related to the noise due to a transmitter’s repeater is included in the calculated losses. Atoll always considers the values in the Real boxes in coverage predictions even if they are different from the values in the Computed boxes. The information in the real Noise figure box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Total losses at transmission and reception and the real Noise figure at reception. Any value you enter must be positive. •
Antennas: •
•
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site given by the DTM. If the transmitter is situated on a building, the height entered must include the height of building. AAS power combining gain: The AAS power combining gain is calculated automatically depending on the number of antenna elements of the smart antenna equipment, if any, assigned to the transmitter. This gain is applied to the downlink transmission power for preamble and other signals transmitted using the main antenna. Main antenna: Under Main antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens a dialogue displaying all the possible antennas based on the same physical antenna as the currently selected one. Selecting the Electrical tilt of the antenna model displays the appropriate antennas under Available antennas. Selecting the antenna under Available antennas and clicking OK assigns the antenna to the transmitter. The other fields, Azimuth, Mechanical downtilt, and Additional electrical downtilt, display additional antenna parameters. • • •
•
•
•
1154
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. The mechanical and additional electrical downtilts defined for the main antenna are also used for the calculations of smart antennas.
Smart antenna: Under Smart antenna, the smart antenna equipment is available in the Equipment list. You can click the Browse button ( ) to access the properties of the smart antenna equipment. When you select 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 1313. 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 1315. 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.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
• • •
•
•
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
The transmission power is divided among the main and secondary antennas. This is not compatible with smart antennas. You must not assign smart antennas to transmitters with secondary antennas, and vice versa. In calculations, repeaters and remote antennas are transparent to the donor transmitters and the served users. For example, beamforming smart antennas at donor transmitters create beams directly towards the served users, and not towards the repeater or remote antenna that covers the users. This results in a combined signal level received from the transmitter using the smart antenna and from the repeater or remote antenna. If this approach does not match how your equipment works, you must not assign smart antennas to transmitters with repeaters and remote antennas, and vice versa. This is also true for MIMO.
The main antenna is used to transmit the preamble. Coverage predictions based on the preamble signal are performed using the main antenna. The main antenna is also used for traffic signals if there is no smart antenna equipment selected for the transmitter, or if the permutation zones do not support AAS. If a smart antenna equipment is assigned to the transmitter and the permutation zones support AAS, traffic data is transmitted and received using the smart antenna, whereas the preamble is transmitted using the main antenna.
12.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. When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently selected station template. The following explains the parameters of a WiMAX cell. You can, if you want, modify these parameters. The properties of a WiMAX cell are found on Cells tab of the Properties dialogue of the transmitter to which it belongs. 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. 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 Network Settings" on page 1301. BSID: The base station ID. Frequency band: The cell’s 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. Preamble index: The preamble index of the cell. It is an integer value from 0 to 113. The preamble indices are defined in the IEEE 802.16 specifications. They provide the segment number and cell permbase (IDCell for the first permutation zone of the frame). Segment: 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.
1155
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
•
•
• •
• •
• • • •
• •
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: Whether the segment number corresponding to the current preamble index is locked or not. If the segment is not locked, the AFP might change the cell’s preamble index depending on the preamble index status. If the segment is locked, the AFP can only change the cell’s preamble index such that the cell’s segment number does not change. DL zone permbase: The zone permbase for a downlink permutation zone. It is an integer value from 0 to 31. DL zone permbase status: The status of the downlink permutation zone permbase currently assigned to the cell: • Not allocated: The current permbase has neither been allocated automatically nor manually. The AFP considers that a Not allocated permbase is modifiable. • Allocated: The current permbase has been allocated either automatically or manually. The AFP considers that an Allocated permbase is modifiable but only if absolutely necessary. • Locked: The current permbase has been allocated either automatically or manually. The AFP considers that a Locked permbase is not modifiable. UL zone permbase: The zone permbase for an uplink permutation zone. It is an integer value from 0 to 69. UL zone permbase status: The status of the uplink permutation zone permbase currently assigned to the cell: • Not allocated: The current permbase has been allocated neither automatically nor manually. The AFP considers that a Not allocated permbase is modifiable. • Allocated: The current permbase has been allocated automatically or manually. The AFP considers that an Allocated permbase is modifiable but only if absolutely necessary. • Locked: The current permbase has been allocated automatically or manually. The AFP considers that a Locked permbase is not modifiable. Preamble index domain: The preamble index domain to which the allocated preamble index belongs. This and the reuse distance are used by the AFP for preamble index allocation. Reuse distance: The reuse distance after which the channel, preamble index, downlink, or uplink permbases assigned to this cell can be assigned to another cell by the AFP. Preamble power (dBm): The cell’s 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 cell’s transmitter has a smart antenna equipment assigned, the transmission powers of cell increase by 10 × Log ( n ) (in dB), where n is the number of antenna elements of the smart antenna. This gain in the transmission power is referred to as the AAS power combining gain.
• •
• •
• • •
•
•
1156
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 or C/(I+N) threshold, according to the option set in the Advanced parameters ("The Global Network Settings" on page 1301), 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 1315. Reception equipment: You can select the cell’s reception equipment from the reception equipment list. For more information, see "Defining WiMAX Reception Equipment" on page 1306. 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 1309. Max number of users: The maximum number of simultaneous users supported by the cell. Frame Configuration: The cell’s frame configuration selected from the list. For more information on frame configurations, see "Defining Frame Configurations" on page 1304. 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 cell’s 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 Network Settings" on page 1301. Max traffic load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a downlink traffic load greater than this maximum. Traffic load (DL) (%): The downlink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
Segmentation usage (DL) (%): You can set the percentage of the total downlink traffic load that corresponds to the segmented part of the frame. For example, if the downlink traffic load is 80%, and you set the segmentation usage to 50%, it means that 40% downlink traffic load is on the segmented part of the frame while the other 40% is on the nonsegmented part. You can set the value of segmentation usage manually or store a calculated value from simulation results. To see examples of how to set up cells with and without segmentation, and how to set up cells with PUSC, FUSC, and permutation zones of other subchannel allocation modes, see "Tips and Tricks" on page 1319.
•
•
• • •
•
•
•
•
•
• • •
Segmentation switching point (DL): The number of downlink OFDM symbol durations that correspond to the average length of the segmented permutation zone. This column is automatically calculated from Segmentation usage (DL) (%). Max traffic load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink traffic load greater than this maximum. Traffic load (UL) (%): The uplink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations. 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. Segmented zone UL noise rise (dB): The uplink noise rise in dB for the segmented permutation zone, if any. Zone 8 (PUSC UL) can be segmented in the frame configuration properties. This can be user-defined or an output of Monte Carlo simulations. Angular distributions of interference (AAS): This field stores the simulation results generated for transmitters using a smart antenna. During Monte Carlo simulations, both smart antenna models available in Atoll, conventional beamformer and optimum beamformer, perform beamforming in downlink. In uplink, the conventional beamformer performs beamforming only whereas the optimum beamformer uses the MMSE (Minimum Mean Square Error) algorithm to cancel interference. After the simulations, the smart antenna results can be stored in the cell properties. The results stored in this field are the angular distributions of the downlink traffic power spectral density and the uplink noise rise. You can view these patterns in the Cells table. You can display the downlink results diagram taking into account the effect of the antenna pattern of the single element. For more information, see the Administrator Manual. AAS usage (DL) (%): This is the percentage of the total downlink traffic load that corresponds to the traffic loads of the users supported by the smart antenna equipment. For example, if the downlink traffic load is 80%, and you set the AAS usage to 50%, it means that 40% downlink traffic load is supported by the smart antenna equipment while the other 40% is supported by the main antenna. AAS usage is calculated during Monte Carlo simulations, and cannot be modified manually because the AAS usage values correspond to the angular distributions of interference. 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 interferencebased calculations involving this cell in Monte Carlo simulations. It is not used in predictions where Atoll calculates the uplink total interference from the uplink noise rise which includes inter-technology uplink interference. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 1317. 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 1317. Max number of intra-technology neighbours: The maximum number of WiMAX neighbours that the cell can have. Max number of inter-technology neighbours: The maximum number of other technology neighbours that the cell can have. Neighbours: You can access a dialogue in which you can set both intra-technology and inter-technology neighbours by clicking the Browse button ( page 1217.
). For information on defining neighbours, see "Planning Neighbours" on
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.
12.2.1.2 Creating or Modifying a Base Station Element A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: • • •
"Creating or Modifying a Site" on page 1158 "Creating or Modifying a Transmitter" on page 1158 "Creating or Modifying a Cell" on page 1159
1157
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
12.2.1.2.1
© Forsk 2012
Creating or Modifying a Site You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 1151, through the site’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create a new site: 1. Select the Network explorer. 2. Right-click the Sites folder. The context menu appears. 3. Select New from the context menu. The Sites: New Element Properties dialogue appears (see Figure 12.2 on page 1152). 4. Modify the parameters described in "Site Description" on page 1151. 5. Click OK. To modify the properties of an existing site: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Sites folder. 3. Right-click the site you want to modify. The context menu appears. 4. Select Properties from the context menu. The site’s Properties dialogue appears. 5. Modify the parameters described in "Site Description" on page 1151. 6. Click OK. If you are creating several sites at the same time, or modifying several existing sites, you can do it quickly by editing or pasting the data directly in the Sites table. You can open the Sites table by right-clicking the Sites folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
12.2.1.2.2
Creating or Modifying a Transmitter You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio Planning toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 1152, through the transmitter’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create a new transmitter: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select New from the context menu. The Transmitters: New Element Properties dialogue appears (see Figure 12.3). 4. Modify the parameters described in "Transmitter Description" on page 1152. 5. Click OK. When you create a new transmitter, Atoll automatically creates a cell based on the default station template. For information on creating a cell, see "Creating or Modifying a Cell" on page 1159. To modify the properties of an existing transmitter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Modify the parameters described in "Transmitter Description" on page 1152. 6. Click OK.
1158
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
•
12.2.1.2.3
If you are creating several transmitters at the same time, or modifying several existing transmitters, you can do it more quickly by editing or pasting the data directly in the Transmitters table. You can open the Transmitters table by rightclicking the Transmitters folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77. If you want to add a transmitter to an existing site on the map, you can add the transmitter by right-clicking the site and selecting New Transmitter from the context menu.
Creating or Modifying a Cell You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Description" on page 1155, through the Properties dialogue of the transmitter where the cell is located. How you access the Properties dialogue depends on whether you are creating a new cell or modifying an existing cell. To create or modify a cell: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Description" on page 1155. 7. Click OK. •
•
If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder in the Network explorer and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 77), or import data into the table (see "Importing Tables from Text Files" on page 82). If you want to add a cell to an existing transmitter on the map, you can add the cell by right-clicking the transmitter and selecting New Cell from the context menu.
12.2.1.3 Placing a New Base Station Using a Station Template In Atoll, a base station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing base stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template: 1. In the Radio Planning toolbar, select a template from the list.
2. Click the New Transmitter or Station button (
) in the Radio Planning 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 pointer’s current location are visible in the status bar.
4. Click to place the station.
1159
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
•
•
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 49. 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 "Modifying a Station Template" on page 1161. To place a series of base stations within a defined area: 1. In the Radio Planning toolbar, select a template from the list. 2. Click the Hexagonal Design button ( ), to the right of the template list. A hexagonal design is a group of base stations created from the same station template. 3. Draw a zone delimiting the area where you want to place the series of base stations: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. Atoll fills the delimited zone with new base stations and their hexagonal shapes. Base station objects such as sites and transmitters are also created and placed into their respective folders. You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for example, another antenna to a transmitter. Placing a Station on an Existing Site When you place a new station using a station template as explained in "Placing a New Base Station Using a Station Template" on page 1159, the site is created at the same time as the station. However, you can also place a new station on an existing site. To place a base station on an existing site: 1. In the Network explorer, clear the display check box beside the Hexagonal Design folder. 2. In the Radio Planning toolbar, select a template from the list. 3. Click the New Transmitter or Station button (
) in the Radio Planning 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.
12.2.1.4 Managing Station Templates Atoll comes with WiMAX station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio Planning toolbar (see Figure 12.5).
Figure 12.5: The Radio Planning toolbar In this section, the following are explained: • • • • •
12.2.1.4.1
"Creating a Station Template" on page 1160 "Modifying a Station Template" on page 1161 "Copying Properties from One Station Template to Another" on page 1164 "Modifying a Field in a Station Template" on page 1164 "Deleting a Station Template" on page 1164.
Creating a Station Template When you create a station template, you can do so by selecting an existing station template that most closely resembles the station template you want to create and making a copy. Then you can modify the parameters that differ. To create a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder.
1160
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the Station Templates table, right-click the station template that most closely resembles the station template you want to create. The context menu appears. 6. Select Copy from the context menu. 7. Right-click the row marked with the New row icon (
). The context menu appears.
8. Select Paste from the context menu. The station template you copied in step 5. is pasted in the new row, with the Name of the new station template given as the same as the template copied but preceded by "Copy of". 9. Edit the parameters of the new station template in the table or as explained in "Modifying a Station Template" on page 1161.
12.2.1.4.2
Modifying a Station Template You can modify a station template directly in the Station Templates table, or you can open the Properties dialogue for that station template and modify the parameters in the dialogue. To modify a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. Right-click the station template you want to modify. The context menu appears. 6. Select Record Properties from the context menu. The station template’s Properties dialogue appears. 7. Click the General tab of the Properties dialogue. In this tab (see Figure 12.6), 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: 1st sector azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Height/ground of the antennas from the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of the building), the Mechanical downtilt, and the Additional electrical downtilt for the antennas. • •
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide.
Under Main antenna, you can select the main antenna Model, under Smart antenna, you can select the smart antenna Equipment used by the transmitter, and under Number of MIMO Antennas, you can enter the number of antennas used for Transmission and for Reception for MIMO. •
•
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information on propagation models, see Chapter 5: Working with Calculations in Atoll. Under Comments, you can add additional information. The information you enter will be the default information in the Comments field of any transmitter created using this station template.
1161
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.6: Station Template Properties dialogue – General tab 8. Click the Transmitter tab. On this tab (see Figure 12.7), if the Active check box is selected, you can modify the following under Transmission/Reception: you can click the Equipment button to open the Equipment Specifications dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or transmitter equipment. For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 1152. 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 12.4 on page 1154). Any loss related to the noise due to a transmitter’s 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 computed Noise figure box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Noise figure at reception if you want. Any value you enter must be positive.
Figure 12.7: Station Template Properties dialogue – Transmitter tab 9. Click the WiMAX tab. On this tab (see Figure 12.8), you can modify the following: •
1162
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.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
You can assign channel and preamble index 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.
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 grid, assign a channel number and a preamble index 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, Reuse distance, Reception equipment, Scheduler, Max number of users, Frame configuration, Preamble C/N threshold, 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. 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 1317.
Figure 12.8: Station Template Properties dialogue – WiMAX tab 10. Click the Neighbours tab. On this tab (see Figure 12.9), you can modify the following: •
Under Max number of neighbours, you can set the maximum numbers of Intra-technology and Inter-technology neighbours.
Figure 12.9: Station Template Properties dialogue – Neighbours tab 11. 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. 12. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.
1163
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
12.2.1.4.3
© Forsk 2012
Copying Properties from One Station Template to Another You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the 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.
12.2.1.4.4
Modifying a Field in a Station Template You can add, delete, and edit user-defined data table fields in the Station Templates table. If you want to add a user-defined field to the station templates, you must have already added it to the Sites table for it to appear as an option in the station template properties To access the station templates data table field definition dialogue: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Properties from the context menu. The Station Template Properties dialogue appears. 5. Select the Table tab. 6. For information on adding, deleting, and editing user-defined fields, see "Adding, Deleting, and Editing Data Table Fields" on page 70). 7. When you have finished, Click OK.
12.2.1.4.5
Deleting a Station Template To delete a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Station Templates folder. 4. In the Station Templates folder, right-click the station template you want to delete. The context menu appears. 5. Select Delete from the context menu. The template is deleted.
12.2.1.5 Duplicating an Existing Base Station You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same transmitter, and cell parameter values as the original base station. If no site exists where you place the duplicated base station, Atoll will create a new site with the same parameters as the site of the original base station. Duplicating a base station allows you to: • •
Quickly create a new base station with the same settings as an original one in order to study the effect of a new station on the coverage and capacity of the network, and Quickly create a new homogeneous network with base stations that have the same characteristics.
To duplicate an existing base station: 1. Select the Network explorer. 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 > Without Neighbours from the context menu, if you want to duplicate the base station without the intra- and inter-technology neighbours of its transmitters. Select Duplicate > With Outward Neighbours from the context menu, if you want to duplicate the base station along with the lists of intra- and inter-technology neighbours of its transmitters.
5. Place the new base station on the map using the mouse:
1164
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
Creating a duplicate base station and site: In the map window, move the pointer over the map to where you would like to place the duplicate. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 12.10).
Figure 12.10: Creating a duplicate base station and site •
Placing the duplicate base station on an existing site: In the map window, move the pointer over the existing site where you would like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 12.11).
Figure 12.11: Placing a new base station •
•
To place the station more accurately, you can zoom in on the map before you select Duplicate from the context menu. For information on using the zooming tools, see "Changing the Map Scale" on page 49. 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. If the duplicate base station was placed on a new site, the site, transmitters, and cells of the new base station have the same names as the site, transmitters, and cells of the original base station with each name marked as "Copy of." The site, transmitters, and cells of the duplicate base station have the same settings as those of the original base station. If the duplicate base station was placed on an existing site, the transmitters, and cells of the new base station have the same names as the transmitters, and cells of the original base station with each name preceded by the name of the site on which the duplicate was placed. All the remote antennas and repeaters of any transmitter on the original site are also duplicated. Any duplicated remote antennas and repeaters will retain the same donor transmitter as the original. If you want the duplicated remote antenna or repeater to use a transmitter on the duplicated base station, you must change the donor transmitter manually. You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to place each duplicate station. For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 1151.
12.2.2 Creating a Group of Base Stations You can create base stations individually as explained in "Creating a WiMAX Base Station" on page 1151, or you can create one or several base stations by using station templates as explained in "Placing a New Base Station Using a Station Template" on page 1159. However, if you have a large project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations.
1165
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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 121. You can import base station data in the following ways: •
Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. The table you copy 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 77. •
Importing data: If you have base station data in text or comma-separated value (CSV) format, you can import it into the tables in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80. For information on importing table data, see "Importing Tables from Text Files" on page 82.
12.2.3 Modifying Sites and Transmitters Directly on the Map In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu in the Network explorer. However, in a complex radio-planning project, it can be difficult to find the data object in the Network explorer, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. You can also select a site to display all of the transmitters located on it in the Site Configuration window. When selecting a transmitter, if there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: • • • • • •
"Working with the Site Configuration Window" on page 37 "Selecting One of Several Transmitters" on page 41 "Moving a Site Using the Mouse" on page 41 "Moving a Site to a Higher Location" on page 42 "Changing the Azimuth of the Antenna Using the Mouse" on page 42 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42.
12.2.4 Display Tips for Base Stations Atoll allows to you to display information about base stations in a number of ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations: •
•
1166
Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object type’s data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information in the label will make it harder to distinguish the information you are looking for. For information on defining the label, see "Defining the Object Type Label" on page 46. Tip text: You can display information about each object, such as each site or transmitter, in the form of tip text that is only visible when you move the pointer over the object. You can choose to display more information than in the label, because the information is only displayed when you move the pointer over the object. You can display information from any field in that object type’s data table, including from fields that you add. For information on defining the tip text, see "Defining the Object Type Tip Text" on page 46.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
•
Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example, you can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active transmitters. You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns a colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding it. For information on defining the transmitter colour, see "Defining the Display Type" on page 44. Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can select a symbol that graphically represents the antenna half-power beamwidth (
). If you have two transmitters on the
same site with the same azimuth, you can differentiate them by selecting different symbols for each ( For information on defining the transmitter symbol, see "Defining the Display Type" on page 44.
and
).
12.2.5 Creating a Multi-band WiMAX Network In Atoll, you can model a multi-band WiMAX network, for example, a network consisting of 3.3 GHz, 5.8 GHz, and 2.5 GHz cells, in one document. Creating a multi-band WiMAX network consists of the following steps: 1. Defining the frequency bands in the document (see "Defining Frequency Bands" on page 1300). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Working with Calculations in Atoll). 3. Assigning a frequency band to each cell and a relevant propagation model to each transmitter (see "Creating or Modifying a Cell" on page 1159 and "Creating or Modifying a Transmitter" on page 1158).
12.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 value and the noise rise generated at the donor transmitter by the repeater. In calculations, repeaters are transparent to the donor transmitters and the served users. For example, beamforming smart antennas at donor transmitters create beams directly towards the served users, and not towards the repeater that covers the users. This results in a combined signal level received from the transmitter using the smart antenna and from the repeater. If this approach does not match how your equipment works, you must not assign smart antennas to transmitters with repeaters and vice versa. This is also true for MIMO.
In this section, the following are explained: • • • • • •
"Opening the Repeaters Table" on page 1167 "Creating and Modifying Repeater Equipment" on page 1168 "Placing a Repeater on the Map Using the Mouse" on page 1168 "Creating Several Repeaters" on page 1168 "Defining the Properties of a Repeater" on page 1169 "Tips for Updating Repeater Parameters" on page 1171. Atoll assumes that all carriers from the WiMAX donor transmitter are amplified.
12.2.6.1 Opening the Repeaters Table Repeaters and their defining parameters are stored in the Repeaters table. To open the Repeaters table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Repeaters > Open Table from the context menu. The Repeaters table appears.
1167
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
12.2.6.2 Creating and Modifying Repeater Equipment You can define repeater equipment to be assigned to each repeater in the network. To create or modify repeater equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Repeater Equipment. The context menu appears. 4. Select Open Table from the context menu. The Repeater Equipment table appears. 5. Define the following in an existing record or in the row marked with the New row icon (
):
a. Enter a Name and Manufacturer for the new equipment. b. Enter a Noise figure (dB). The repeater causes a rise in noise at the donor transmitter, so the noise figure is used to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive value. c. Enter minimum and maximum repeater amplifier gains in the Min. gain and Max gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if there are any. d. Enter a Gain increment. Atoll uses the increment value when you increase or decrease the repeater amplifier gain using the buttons to the right of the Amplifier gain box ( logue.
) on the General tab of the repeater Properties dia-
e. Enter the maximum power that the equipment can transmit on the downlink in the Max downlink power column. This parameter enables Atoll to ensure that the downlink power after amplification does not exceed the limit of the equipment. f. If desired, enter a Max uplink power, an Internal delay and Comments. These fields are for information only and are not used in calculations.
12.2.6.3 Placing a Repeater on the Map Using the Mouse In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site, or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater or of a remote antenna. To create a repeater and place it using the mouse: 1. Select the donor transmitter, repeater, or remote antenna. You can select it from the Transmitters folder in the Network explorer, or directly on the map. 2. Click the arrow next to New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
3. Select Repeater from the menu. 4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty icon. By default, the repeater has the same azimuth as the donor. Its tip text and label display the same information as displayed for the donor. As well, its tip text identifies the repeater and the donor. In the explorer window, the repeater is found in the Transmitters folder of the Network explorer under its donor transmitter, repeater, or remote antenna. For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on page 1169. •
•
When the donor is a transmitter, you can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. Click it again to hide the link. When the donor is a repeater or a remote antenna, Atoll displays a spider-type link showing the entire chain down to the donor transmitter. The same spider-type link is displayed when any of the items belonging to the chain is clicked (donor transmitter, any repeater, or any remote antenna).
12.2.6.4 Creating Several Repeaters In Atoll, the characteristics of each repeater are stored in the Repeaters table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document.
1168
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
To paste the information into the Repeaters table: 1. Open the Repeaters table as explained in "Opening the Repeaters Table" on page 1167. 2. Copy the data from the source document and paste it into the Repeaters table. 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 77.
12.2.6.5 Defining the Properties of a Repeater To define the properties of a repeater: 1. Right-click the repeater either directly on the map, or in the Repeaters table (for information on opening the Repeaters table, see "Opening the Repeaters Table" on page 1167). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
You can change the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned as the repeater when it was created. If the donor is a remote antenna or another repeater, then "RepZ" is preceded by "RemA_" or "RepB_" where "A" and "B" identify the donor remote antenna and the donor repeater.
•
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, a remote antenna, or another repeater. Clicking the Browse button (
• •
•
• •
) opens the Properties dialogue of the selected donor.
You can change the Site on which the repeater is located. Clicking the Browse button (
) opens the Properties
dialogue of the selected site. You can enter a value in the Shared antenna (coverage side) field for the repeater. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna position, you can define the position of the repeater, if it is not located on the site itself: • Relative to site: Select Relative to site, if you want to define the position of the repeater relative to the site itself and then enter the XY offsets. • Coordinates: Select Coordinates, if you want to define the position of the repeater by its XY coordinates. You can select equipment from the Equipment list. Clicking the Browse button ( ) opens the Properties dialogue of the equipment. You can change the Amplifier Gain. The amplifier gain is used in the link budget to evaluate the repeater total gain.
4. Click the Donor side tab. You can modify the following parameters: •
Under Donor-repeater link, select a Link type. • •
If you select Microwave link, enter the Link losses and proceed to step 5. If you select Air, select a Propagation model and enter the Propagation losses or click Calculate to determine the actual propagation losses between the donor and the repeater. If you do not select a propagation model, the propagation losses between the donor transmitter and the repeater are calculated using the ITU 526-5 propagation model. When you create an off-air repeater, it is assumed that the link between the donor transmitter and the repeater has the same frequency as the network. If you want to create a remote antenna, you must select Optical Fibre Link.
•
If you selected Air under Donor-repeater link, enter the following information under Antenna:
1169
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
Model: The type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the repeater. Based on the selected physical antenna and on the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the repeater.
•
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of building. Mechanical Azimuth and Mechanical Downtilt display additional antenna parameters. You can click the Calculate button to update the mechanical azimuth and mechanical downtilt values after changing the repeater donor side antenna height or the repeater location. If you choose another site or change site coordinates in the General tab, click Apply before clicking the Calculate button.
•
If you selected Air under Donor-repeater link, enter the following information under Feeders: • •
Type: The type of feeder is visible in the Type list. You can click the Browse button ( erties of the feeder. Length: Enter the Length of the feeder cable at Transmission and at Reception.
) to access the prop-
5. Click the Coverage Side tab. You can modify the following parameters: • •
Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Network explorer) are calculated. Under Total 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 total gain values to calculate the signal level received from and at the repeater. The downlink total gain is applied to preamble, traffic, and pilot powers. The uplink total gain is applied to the terminal power. The total gains take into account losses between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna gain and transmission feeder losses).
•
Under Antennas, you can modify the following parameters: •
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of building. Main antenna: Under Main antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the repeater. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the repeater.
• •
Mechanical 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. • • •
1170
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. •
Under Losses, Atoll displays the Loss related to repeater noise rise.
6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propagation parameters. On the Propagation tab, you can modify the following: the Propagation model, Radius, and Resolution for both the Main matrix and the Extended matrix. By default, the propagation characteristics of the repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
12.2.6.6 Tips for Updating Repeater Parameters Atoll provides you with a few shortcuts that you can use to change certain repeater parameters: • •
You can update the calculated azimuth and downtilt of the donor-side antennas of all repeaters by selecting Repeaters > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu. You can update the UL and DL total gains of all repeaters by selecting Repeaters > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected repeaters by creating a custom Boolean field named "FreezeTotalGain" in the Repeaters table and setting the value of the field to "True." Afterwards, when you select Repeaters > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for repeaters with the custom field "FreezeTotalGain" set to "False."
• •
You can update the propagation losses of all off-air repeaters by selecting Repeaters > Calculate Donor Side Propagation Losses from the Transmitters context menu. You can select a repeater on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
12.2.7 Creating a Remote Antenna Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder cable. A remote antenna is connected to the base station with an optical fibre. Remote antennas allow you to ensure radio coverage in an area without a new base station. In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a remote antenna, as opposed to a repeater, does not have any equipment and generates neither amplification nor noise. In certain cases, you may want to model a remote antenna with equipment or a remote antenna connected to a base station that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a Repeater" on page 1167. In calculations, remote antennas are transparent to the donor transmitters and the served users. For example, beamforming smart antennas at donor transmitters create beams directly towards the served users, and not towards the remote antenna that covers the users. This results in a combined signal level received from the transmitter using the smart antenna and from the remote antenna. If this approach does not match how your equipment works, you must not assign smart antennas to transmitters with remote antennas and vice versa. This is also true for MIMO. In this section, the following are explained: • • • • •
"Opening the Remote Antennas Table" on page 1172 "Placing a Remote Antenna on the Map Using the Mouse" on page 1172 "Creating Several Remote Antennas" on page 1172 "Defining the Properties of a Remote Antenna" on page 1173 "Tips for Updating Remote Antenna Parameters" on page 1174.
1171
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
12.2.7.1 Opening the Remote Antennas Table The remote antennas and their defining parameters are stored in the Remote Antennas table. To open the Remote Antennas table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Remote Antennas > Open Table from the context menu. The Remote Antennas table appears.
12.2.7.2 Placing a Remote Antenna on the Map Using the Mouse In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it to an existing base station without antennas, or have Atoll automatically create a new site. To create a remote antenna and place it using the mouse: 1. Select the donor transmitter. You can select it from the Transmitters folder in the Network explorer, or directly on the map. Ensure that the remote antenna’s donor transmitter does not have any antennas.
2. Click the arrow next to New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
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 the same symbol and colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its tip text and label display the same information as displayed for the donor transmitter. As well, its tip text identifies the remote antenna and the donor transmitter. For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote Antenna" on page 1173. •
•
When the donor is a transmitter, you can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter. Click it again to hide the link. When the donor is a repeater or a remote antenna, Atoll displays a spider-type link showing the entire chain down to the donor transmitter. The same spider-type link is displayed when any of the items belonging to the chain is clicked (donor transmitter, any repeater, or any remote antenna).
12.2.7.3 Creating Several Remote Antennas In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in your current Atoll document. To paste the information into the Remote Antennas table: 1. Open the Remote Antennas table as explained in "Opening the Remote Antennas Table" on page 1172. 2. Copy the data from the source document and paste it into the Remote Antennas table. The table you copy data from must have the same column layout as the table you are pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
1172
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.2.7.4 Defining the Properties of a Remote Antenna To define the properties of a remote antenna: 1. Right-click the remote antenna either directly on the map, or in the Remote Antennas table (for information on opening the Remote Antennas table, see "Opening the Remote Antennas Table" on page 1172). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RemZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the remote antenna when it was created. If the donor is a repeater or another remote antenna, then "RemZ" is preceded by "RepA_" or "RemB_" where "A" and "B" identify the donor repeater and the donor remote antenna.
•
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another remote antenna or a repeater. Clicking the Browse button (
• •
•
) opens the Properties dialogue of the selected donor.
You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens the Properties dialogue of the selected site. You can enter a value in the Shared antenna (coverage side) field for the remote antenna. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna position, you can define the position of the remote antenna, if it is not located on the site itself: • •
Relative to site: Select Relative to site, if you want to define the position of the remote antenna relative to the site itself and then enter the XY offsets. Coordinates: Select Coordinates, if you want to define the position of the remote antenna by its XY coordinates. A remote antenna does not have equipment.
4. Click the Donor Side tab. You can modify the following parameters: •
Under Donor-Repeater Link, select Optical fibre link and enter the Fibre losses.
5. Click the Coverage Side tab. You can modify the following parameters: • •
Select the Active check box. Only active remote antennas (displayed in red in the Transmitters folder in the Network explorer) 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 total gain values to calculate the signal level received from and at the remote antenna. The downlink total gain is applied to preamble, traffic, and pilot powers. The uplink total gain is applied to the terminal power. The total gains take into account losses between the donor transmitter and the remote antenna.
•
Under Antennas, you can modify the following parameters: •
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the remote antenna is situated on a building, the height entered must include the height of building. Main antenna: Under Main antenna, the type of antenna is visible in the Model list. You can click the Browse button (
) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection
Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the remote antenna. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas.
1173
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the remote antenna. • •
Mechanical 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. • • •
•
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. 6. Click the Propagation tab. Since remote antennas are taken into account during calculations, you must set propagation parameters, as with transmitters. On the Propagation tab, you can modify the following: the Propagation model, Radius, and Resolution for both the Main matrix and the Extended matrix. By default, the propagation characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
12.2.7.5 Tips for Updating Remote Antenna Parameters Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters: •
You can update the UL and DL total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected remote antennas by creating a custom Boolean field named "FreezeTotalGain" in the Remote Antennas table and setting the value of the field to "True." Afterwards, when you select Remote Antennas > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for remote antennas with the custom field "FreezeTotalGain" set to "False."
•
You can select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
12.2.8 Setting the Working Area of an Atoll Document When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the base stations that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of base stations covered by a coverage prediction, each with its own advantages: •
Filtering the desired base stations You can simplify the selection of base stations to be studied by using a filter. You can filter base stations according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 107. This enables you to keep only the base stations with the characteristics you want for your calculations. The filtering zone is taken into account whether or not it is visible. For information on filtering, see "Filtering Data" on page 95.
1174
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
Setting a computation zone Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated predictions in order to see the effects of small changes in site configuration, the savings in time is considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus zone or hot spot is the area taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 1183.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.
12.2.9 Studying a Single Base Station As you create a base station, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of base stations can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the base station you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of base stations once you have optimised the settings for each individual base station. Before studying a base station, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates propagation losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Any coverage prediction you make on a base station uses the propagation model to calculate its results. In this section, the following are explained: • •
"Making a Point Analysis to Study the Profile" on page 1175. "Studying Signal Level Coverage" on page 1176.
12.2.9.1 Making a Point Analysis to Study the Profile In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a user. Before studying a base station, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on the selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 1181. You can make a point analysis to: • • •
study the reception in real time along a profile between a reference transmitter and a WiMAX user, study the interference along a profile between a reference transmitter and a user, and evaluate the signal levels coming from the surrounding transmitters at a given point (using existing path loss matrices).
To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis button ( pointer changes (
) in the Radio Planning toolbar. The Point Analysis window appears and the
) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: • • •
Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: • Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. • Target Site: Select a site from the list to place the receiver directly on a site.
4. Select the Profile view. The profile analysis appears in the Profile view of the Point Analysis 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.
1175
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
The results of the analysis are displayed at the top of the Profile view: • • • •
The received signal strength from the selected transmitter for the cell with the highest preamble power The propagation model used The shadowing margin and the indoor loss (if selected) The distance between the transmitter and the receiver.
You can change the following options using the Profile view toolbar: •
Transmitter: Select the transmitter from the list. You can click the Properties button ( properties dialogue.
•
Options: Click the Options button ( • • • •
) to open the transmitter
) to display the Calculation Options dialogue. In this dialogue, you can:
Change the X and Y coordinates to change the current position of the receiver. Select the Shadowing taken into account check box and enter a Cell edge coverage probability. Select Signal level, Path loss, or Total losses from the Result type list. You can select the Indoor coverage check box to add indoor losses.
•
Geographic Profile: Click the Geographic Profile button ( ) if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate or display signal levels and losses.
•
Link Budget: Click the Link Budget button (
•
Detailed Report: Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis. The detailed report is only available for the Standard Propagation Model.
) to display a dialogue with the link budget.
You can select a different transmitter.
Displays data, including received signal, shadowing margin, cell edge coverage probability, propagation model used, and transmitter-receiver distance.
Fresnel ellipsoid
Line of sight
Attenuation with diffraction
Figure 12.12: Point Analysis - Profile view 5. To end the point analysis, click the Point Analysis button (
) in the Radio Planning toolbar again.
12.2.9.2 Studying Signal Level Coverage As you are building your radio-planning project, you might want to check the coverage of a new base station without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single base station. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. For a transmitter with more than one cell, the signal level is calculated for the cell with the highest preamble power. You can use the same procedure to study the signal level coverage of several base stations by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 89. To study the signal level coverage of a single base station: 1. Select the Network explorer. 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.
1176
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
If you want to study only sites by their status, at this step you could group them by status.
3. Select the propagation parameters to be used in the coverage prediction: 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 Prediction from the context menu. The Prediction Types dialogue appears. The Prediction Types dialogue lists the coverage prediction types available. They are divided into Standard Predictions, supplied with Atoll, and Customised Predictions. Unless you have already created some customised predictions, the Customised Predictions list will be empty. 5. Select Coverage by Signal Level and click OK. A coverage prediction properties dialogue appears. 6. You can configure the following parameters in the Properties dialogue: •
General tab: You can change the assigned Name of the coverage prediction, the Resolution, and the storage Folder for the coverage prediction, and add some Comments. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient: Size of the Coverage Prediction
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
According to the size of the country
If you create a new coverage prediction from the context menu of the Predictions folder, you can select the sites using the Group By, Sort, and Filter buttons under Display configuration. However, if you create a new coverage prediction from the context menu of the Transmitters folder, only the Filter button is available, because, by creating a coverage prediction directly from the Transmitters folder, you have effectively already selected the target sites. •
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 12.13). •
At the top of the Condition tab, you can set the signal level range to be considered.
1177
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
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 12.13: Condition settings for a coverage prediction by signal level •
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." You can change the value intervals and their displayed colour. For information on changing display properties, see "Display Properties of Objects" on page 43.
•
You can create tip text with information about the coverage prediction by clicking the Browse button ( next to the Tip text box and selecting the fields you want to display in the tip text. You can select the Add to legend check box to add the displayed value intervals to the legend.
•
)
If you change the display properties of a coverage prediction after you have calculated it, you may make the coverage prediction invalid. You will then have to recalculate the coverage prediction to obtain valid results. 7. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the 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 in the Network explorer. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button (
) beside the coverage prediction in the Predictions
), Atoll only calculates unlocked coverage predictions (
).
12.2.10 Studying Base Stations When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects the rectangle containing the computation zone.
1178
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.14 gives an example of a computation zone. In Figure 12.14, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction. Site 130 is within the coverage zone but has no active transmitters. Therefore, it will not be taken into consideration either.
Figure 12.14: 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 12.14) 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 1179. "Assigning a Propagation Model" on page 1181. "The Calculation Process" on page 1183. "Creating a Computation Zone" on page 1183. "Setting Transmitters or Cells as Active" on page 1184. "Signal Level Coverage Predictions" on page 1185. "Analysing a Coverage Prediction" on page 1190. "WiMAX Coverage Predictions" on page 1199. "Printing and Exporting Coverage Prediction Results" on page 1217.
12.2.10.1 Path Loss Matrices In addition to the distance between the transmitter and the received, path loss is caused by objects in the transmitter-receiver path. In Atoll, the path loss matrices must be calculated before predictions and simulations can be made. Storing Path Loss Matrices Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radioplanning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning project. In this case, the radio data is stored in a database and the path loss matrices are read-only and are
1179
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: • • •
One file per transmitter with the extension LOS for its main path loss matrix. A DBF file with validity information for all the main matrices. A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions 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 Private directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally. Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private directory.
When you save the path loss files externally, the external files are updated as soon as calculations are performed. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it if you have updated the path loss matrices. •
Shared directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see the Administrator Manual.
5. Click OK. Checking the Validity of Path Loss Matrices Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available results table. You have the following display options: • •
Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available results table lists the following information for each displayed path loss matrix: • • • •
1180
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. Reason for invalidity: If the path loss matrix is indicated as being invalid, the reason is given here.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
• •
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 12.15) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.
Figure 12.15: Path loss matrices statistics
12.2.10.2 Assigning a Propagation Model In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 1182, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 1182, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 1181, this is the propagation model that will be used for all transmitters, except for those to which you will later assign a propagation model either individually or as part of a group. When you assign a propagation model globally, you override any selection you might have made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 201, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following are explained: • • •
"Assigning a Propagation Model to All Transmitters" on page 1181. "Assigning a Propagation Model to a Group of Transmitters" on page 1182. "Assigning a Propagation Model to One Transmitter" on page 1182.
For more information about the available propagation models, see Chapter 5: Working with Calculations in Atoll. Assigning a Propagation Model to All Transmitters In Atoll, you can choose a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears.
1181
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
4. Click the Propagation tab. 5. Under Main matrix: • •
Select a Propagation model Enter a Radius and Resolution.
6. If desired, under Extended matrix: • •
Select a Propagation model Enter a Radius and Resolution.
7. Click OK. The selected propagation models will be used for all transmitters. Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 1182 will override this entry.
Assigning a Propagation Model to a Group of Transmitters Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters and then assigning the propagation model. To define a main and extended propagation model for a defined group of transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. From the Group By submenu of the context menu, select the property by which you want to group the transmitters. The objects in the folder are grouped by that property. You can group transmitters by several properties by using the Group By button on the Properties dialogue. For more information, see "Advanced Grouping" on page 90.
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 Main resolution Extended propagation model Extended calculation radius Extended resolution
To enter the same values in one column for all transmitters in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button (
) in the Table toolbar. For more information on working with tables in Atoll,
see "Working with Data Tables" on page 69. Assigning a Propagation Model to One Transmitter If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters.
1182
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previously made globally. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main matrix: • •
Select a Propagation model. Enter a Radius and Resolution.
7. If desired, under Extended matrix: • •
Select a Propagation model. Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter. 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.
12.2.10.3 The Calculation Process When you create a coverage prediction and click the Calculate button (
), Atoll follows the following process:
1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button (
).
3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( Predictions folder. •
You can stop any calculations in progress by clicking the Stop Calculations button (
•
) beside the coverage prediction in the
) in the Radio Planning toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.
12.2.10.4 Creating a Computation Zone To create a computation zone: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Computation Zone. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the zone.
ii. Click once on the map to define each point on the map where the border of the zone changes direction. iii. Click twice to finish drawing and close the zone. •
Draw Rectangle
1183
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
i.
© Forsk 2012
Click the point on the map that will be one corner of the rectangle that will define the zone.
ii. Drag to the opposite corner of the rectangle that will define the zone. When you release the mouse, the zone will be created from the rectangle defined by the two corners. The computation zone is delimited by a red line. If you clear the computation zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a computation zone with one of the following methods: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor 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. You can also combine an existing computation zone with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Computation Zone from the context menu. 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 in the Geo explorer and selecting Import from the context menu. Fit Zone to Map Window: You can create a computation zone the size of the map window by right-clicking the Computation Zone in the Geo explorer and selecting Fit Zone to Map Window from the context menu. You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the computation zone in the user configuration: For information on saving the computation zone in the user configuration, see "Saving a User Configuration" on page 101. Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone in the Geo explorer and selecting Export from the context menu.
12.2.10.5 Setting Transmitters or Cells as Active When you make a coverage prediction, Atoll considers all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Therefore, before you define a coverage prediction, you must ensure that all the transmitters on the base stations you want to study have been activated. In the explorer window, active transmitters are indicated with an on icon (
) in the Transmitters
folder and with the defined colour on the map and inactive transmitters are indicated with an off icon ( ters folder and empty symbol on the map.
) in the Transmit-
In Atoll, you can also set the cell on a transmitter as active or inactive. You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by activating them from the Transmitters context menu, by activating the transmitters’ cells from the Cells table, or by selecting the transmitters with a zone and activating them from the zone’s context menu. To set an individual transmitter as active: 1. Select the Network explorer. 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. Select the Network explorer. 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 rightclick the group of transmitters you want to set as active. The context menu appears.
3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one transmitter as active using the Transmitters table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table. The Transmitters table appears with each transmitter’s parameters in a row.
1184
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cell’s 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. Select the Geo explorer. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder. 3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 54.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Working with Calculations in Atoll. Calculating path loss matrices can be 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.
12.2.10.6 Signal Level Coverage Predictions Atoll offers a series of standard coverage predictions based on the measured signal level at each pixel; other factors, such as interference, are not taken into consideration. Coverage predictions specific to WiMAX are covered in "WiMAX Coverage Predictions" on page 1199. Once you have created and calculated a coverage prediction, you can use the coverage prediction’s context menu to make the coverage prediction into a customised prediction which will appear in the Prediction Types dialogue. You can also select Duplicate from the coverage prediction’s context menu to create a copy. By duplicating an existing prediction that has the parameters you want to study, you can create a new coverage prediction more quickly than by creating a new coverage prediction. If you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the coverage prediction with the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the calculated coverage prediction. You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to load it into a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predictions are saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations, see "Saving a User Configuration" on page 101. The following standard coverage predictions are explained in this section: • • •
12.2.10.6.1
"Making a Coverage Prediction by Signal Level" on page 1185 "Making a Coverage Prediction by Transmitter" on page 1187 "Making a Coverage Prediction on Overlapping Zones" on page 1188.
Making a Coverage Prediction by Signal Level A coverage prediction by signal level allows you to predict coverage zones by the transmitter signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest preamble power. To make a coverage prediction by signal level: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 5. Click the General tab.
1185
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 12.16). On the Condition tab, you can define the signals that will be considered for each pixel. • •
At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration.
• •
If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 12.16: 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 43. 8. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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 12.17).
1186
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.17: Coverage prediction by signal level
12.2.10.6.2
Making a Coverage Prediction by Transmitter A coverage prediction by transmitter allows the user to predict coverage zones by transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest preamble power. To make a coverage prediction by transmitter: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Transmitter and click OK. The Coverage by Transmitter Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group by button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Condition tab (see Figure 12.18). On the Condition tab, you can define the signals that will be considered for each pixel. •
At the top of the Condition tab, you can set the range of signal level to be considered.
•
Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration.
•
If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability.
•
You can select the Indoor coverage check box to add indoor losses.
1187
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.18: 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 12.19).
Figure 12.19: Coverage prediction by transmitter
12.2.10.6.3
Making a Coverage Prediction on Overlapping Zones Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction on overlapping zones on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest preamble power.
1188
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
To make a coverage prediction on overlapping zones: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 12.20). On the Condition tab, you can define the signals that will be considered for each pixel. •
At the top of the Condition tab, you can set the range of signal level to be considered.
•
Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration.
• •
If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 12.20: 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 43. When creating a coverage prediction displaying the number of servers, you can not export the values per pixel.
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately.
1189
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 12.21).
Figure 12.21: Coverage prediction on overlapping zones
12.2.10.7 Analysing a Coverage Prediction Once you have completed a prediction, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 1176). If several coverage predictions are visible on the map, it can be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following tools are explained: • • • • • • •
12.2.10.7.1
"Displaying the Legend Window" on page 1190. "Displaying Coverage Prediction Results Using the Tip Text" on page 1190. "Using the Point Analysis Reception View" on page 1191. "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1192. "Displaying a Coverage Prediction Report" on page 1193. "Viewing Coverage Prediction Statistics" on page 1195. "Comparing Coverage Predictions: Examples" on page 1196.
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to legend check box on the Display tab. To display the Legend window: •
12.2.10.7.2
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction identified by the name of the coverage prediction.
Displaying Coverage Prediction Results Using the Tip Text You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 1176). To get coverage prediction results in the form of tip text: •
1190
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined in the Display tab of the coverage prediction properties (see Figure 12.22).
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.22: Displaying coverage prediction results using tip text
12.2.10.7.3
Using the Point Analysis Reception View Once you have calculated the coverage prediction, you can use the Point Analysis tool. At any point on the map, the Reception view gives you information on the preamble, traffic, and pilot signal levels, C/(I+N), bearers, throughputs, etc. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility, and a service. The analysis is based on: •
• • •
The preamble signal levels, used to determine the best server for the pixel. The best serving transmitter is determined according to the received preamble signal level from the cell with the highest preamble power. If more than one cell covers the pixel, the one with the highest layer is selected as the serving (reference) cell. The preamble C/N or C/(I+N), used to determine the permutation zone assigned to each pixel and used to determine whether SU-MIMO or STTD/MRC is used for AMS, and whether MU-MIMO can be used in uplink or not. The downlink traffic signal levels, downlink traffic loads, segmentation usage, angular distributions of interference, and AAS usage, for determining the downlink traffic C/(I+N), bearer, and throughputs. The uplink signal levels, uplink noise rise values, and angular distributions of interference, for determining the uplink C/(I+N), bearer, and throughputs.
The downlink and uplink load conditions can be taken from the Cells table or from Monte Carlo simulations. You can make a reception analysis to verify a coverage prediction. If so, before you make the reception 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 (
) on the Radio Planning toolbar. The Point Analysis window appears (see
Figure 12.23) and the pointer changes (
) to represent the receiver.
2. Select the Reception view. 3. At the top of the Reception view, select "Cells table" from Load. 4. Select the signal to be displayed from the Display list. 5. 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. Click the Options button ( ) in the Reception view toolbar to display the Calculation Options dialogue. The Calculation Options 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.
c. Click OK to close the Calculation Options dialogue. 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. The line from the pointer to its best server is slightly thicker than the other lines. The best server of the pointer is the transmitter from which the pointer receives the highest preamble 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.
1191
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Select the load conditions to use in this analysis from simulations or from the Cells table.
The preamble signal level from the best server (topmost bar) and all interfering cells. Solid bars indicate signal levels above the preamble C/N threshold.
The connection status for the current point. : Successful : Failed
Select the parameters of the probe user to be studied. Figure 12.23: Point analysis tool: Reception view The bar graph displays the following information: • • •
The preamble, traffic, or pilot signal levels or C/N (depending on the selection made from the Display list) from different transmitters (the colour of the bar corresponds to the colour of the transmitter on the map). The preamble C/N thresholds: The empty portion of the bar indicates signal levels below the preamble C/N thresholds. The availability of preamble coverage, and service in downlink and uplink.
If there is at least one successful connection (for preamble, downlink, or uplink), double-clicking the icons in the righthand frame opens a dialogue with additional information about the best server: • • •
Preamble: Azimuth and tilt of the receiver, total losses, received preamble power, preamble total noise, preamble C/(I+N). Downlink: Permutation zone, diversity mode, pilot and traffic received powers, traffic total noise, 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, C/(I+N), bearer, channel throughputs, cell capacities, and allocated bandwidth throughputs.
To get all this information in a single report: •
Click the Report button in the Reception view toolbar. The Analysis Report dialogue appears.
8. Click the Point Analysis button (
12.2.10.7.4
) on the Radio Planning toolbar again to end the point analysis.
Creating a Focus Zone or Hot Spot for a Coverage Prediction Report The focus and hot spots define the area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spots in addition to the focus zone. It is important not to confuse the computation zone and the focus and hot spots. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus and hot spots are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spots. To define a focus zone or hot spot: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Focus Zone or Hot Spots folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the focus zone or hot spot.
ii. Click once on the map to define each point on the map where the border of the focus zone or hot spot changes direction. iii. Click twice to finish drawing and close the focus zone or hot spot. •
Draw Rectangle i.
1192
Click the point on the map that will be one corner of the rectangle that will define the focus zone or hot spot.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
ii. Drag to the opposite corner of the rectangle that will define the focus zone or hot spot. When you release the mouse, the focus zone or hot spot will be created from the rectangle defined by the two corners. A focus zone is delimited by a green line; a hot spot is delimited by a heavy black line. If you clear the zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot by right-clicking it and selecting Use As > Focus Zone or Use As > Hot Spot from the context menu. You can also combine an existing focus zone or hot spot with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Focus Zone or Add To > 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. You can import it by right-clicking the Focus Zone or Hot Spots folder in the Geo explorer and selecting Import from the context menu. When you import hot spots, you can import the name given to each zone as well. Fit Zone to Map Window: You can create a focus or hot spot the size of the map window by selecting Fit Zone to Map Window from the context menu. •
You can save the focus zone or hot spots, so that you can use it in a different Atoll document, in the following ways: •
•
12.2.10.7.5
Saving the focus zone in the user configuration: For information on saving the focus zone in the user configuration, see "Saving a User Configuration" on page 101. • Exporting the focus zone or hot spots: You can export the focus zone or hot spots by right-clicking the Focus Zone or the Hot Spots folder in the Geo explorer and selecting Export from the context menu. You can include population statistics in the focus or hot spot by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137.
Displaying a Coverage Prediction Report Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage prediction’s Properties dialogue. The coverage prediction report is displayed in a table. For information on working with tables, see "Working with Data Tables" on page 69. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 74. Atoll bases the report on the area covered by the focus zone and hot spots; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot must be defined before you display a report; it is not necessary to define it before calculating coverage. The focus zone or hot spot does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1192. Once you have generated a report, you can export it to a text file or to an Excel spreadsheet. For more information on exporting a coverage prediction report, see "Exporting a Coverage Prediction Report" on page 1195. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Select the Network explorer. 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:
1193
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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 up or
to move it down. You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spots and on the focus zone if available or on the hot spots and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Select the Network explorer. 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 up or
to move it down. You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spots by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137. Normally, Atoll takes all geo data into consideration, whether it is displayed or not. However, for the population statistics to be used in a report, the population map has to be displayed. To include population statistics in the focus zone or hot spots: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. 2. Select the Network explorer. 3. Right-click the Predictions folder. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Select the following columns, where "Population" is the name of the folder in the Geo explorer 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.
6. Click OK.
1194
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Atoll saves the names of the columns you select and will automatically select them the next time you create a coverage prediction report. 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 154.
12.2.10.7.6
Exporting a Coverage Prediction Report Once you have generated a coverage prediction report as explained in "Displaying a Coverage Prediction Report" on page 1193, you can export it to a text file or to a spreadsheet. To export a coverage prediction report: 1. Right-click the report and select Export from the context menu or click the Export button ( The Save As dialogue appears.
) in the Table toolbar.
2. In the Save As dialogue, enter the File name and select the format from the Save as type list: • • • •
TXT: To save the report as a text file. CSV: To save the report as a comma-separated values file. XLS: To save the report as an Excel spreadsheet. XML Spreadsheet 2003: To save the report as an XML spreadsheet.
3. Click Save to export the coverage prediction report.
12.2.10.7.7
Viewing Coverage Prediction Statistics Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage prediction colours, interval steps, and shading as defined on the Display tab of the coverage prediction’s Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spots are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before calculating coverage. For information on defining a focus zone, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1192. To display the statistics on a coverage prediction: 1. Select the Network explorer. 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 12.24). • •
• • •
Under Histogram based on covered areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Zoom on selected values section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics based on prediction conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.
1195
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.24: Histogram of a coverage prediction by signal level
12.2.10.7.8
Comparing Coverage Predictions: Examples Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison in one of the following ways: • •
•
Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both predictions are displayed in red). Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and pixels covered by only one prediction are blue). Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for example, pixels covered by both predictions are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).
To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction. 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 1196 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 1198.
Example 1: Studying the Effect of a New Base Station If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can verify if a newly added base station improves coverage. A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 1185. The results are displayed in Figure 12.25. An area with poor coverage is visible on the right side of the figure.
1196
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.25: 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 1151, or by placing a station template, as explained in "Placing a New Base Station Using a Station Template" on page 1159. 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 12.26).
Figure 12.26: 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.
1197
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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 12.27, shows clearly the area covered only by the new base station.
Figure 12.27: Comparison of both signal level coverage predictions Example 2: Studying the Effect of a Change in Transmitter Tilt If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can see how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 1187. The results are displayed in Figure 12.28. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated by a red oval in Figure 12.28.
Figure 12.28: 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 12.29).
1198
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.29: 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 12.30, shows clearly the increase in coverage due at the change in antenna tilt.
Figure 12.30: Comparison of both transmitter coverage predictions
12.2.10.8 WiMAX Coverage Predictions Two types of WiMAX coverage predictions are available in Atoll: coverage predictions used to analyse the effective signal levels, and coverage predictions used to analyse the signal quality.
1199
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Effective signal analysis coverage predictions can be used to analyse different signals (preamble, traffic, etc.) in the downlink as well as in the uplink once the user-end gains and losses have been considered. These coverage predictions do not depend on the network load conditions. The cell coverage areas for these predictions are only limited by the cell preamble C/N thresholds. 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. The cell coverage areas for preamble and pilot signal quality predictions are only limited by the cell preamble C/N thresholds. However, the cell coverage areas for traffic signal quality predictions, service area, throughput, and quality indicator predictions are limited by both the cell preamble C/N thresholds and the bearer selection thresholds of the lowest available bearer. 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 1200.
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 1202. "Analysing the Signal Quality" on page 1204.
You can also use the Point Analysis tool 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: •
12.2.10.8.1
"Analysing Interference Areas Using a Point Analysis" on page 1216.
Service and User Modelling Atoll can base its signal quality coverage predictions on the DL traffic loads and the UL noise rise entered in the Cells table (for more information, see "Setting the Traffic Loads and the UL Noise Rise" on page 1205). Before you can model services, you must define WiMAX radio bearers. For more information on WiMAX radio bearers, see "Defining WiMAX Radio Bearers" on page 1306. In this section, the following are explained: • • •
"Modelling Services" on page 1200. "Modelling Mobility Types" on page 1201. "Modelling Terminals" on page 1201.
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: • • • • •
Highest bearer Lowest bearer Throughput scaling factor Throughput offset Body loss
To create or modify a service: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services: New Element Properties dialogue appears. You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.
5. 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. • • • •
1200
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-Real-Time Polling Service), and BE (Best Effort). The information about the QoS class used by any service is used by the schedulers for
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
• • • • •
•
resource allocation. For more information about how schedulers work in Atoll, see "Defining WiMAX Schedulers" on page 1309. Activity factor: The uplink and downlink activity factors are used to determine the probability of activity for users accessing the service during Monte Carlo simulations. For Voice services, this parameter is used when working with sector traffic maps and user density traffic maps. For Data services, Atoll distributes the users according to the activity factors when importing user density traffic maps for all activity statuses. Highest bearer: Select the highest bearer that the service can use in the uplink and downlink. This is considered as an upper limit during bearer determination. Lowest bearer: Select the lowest bearer that the service can use in the uplink and downlink. This is considered as a lower limit during bearer determination. Max throughput demand: Enter the highest throughput that the service can demand in the uplink and downlink. This value is not considered for services UGS as the quality of service. Min throughput demand: Enter the minimum required throughput that the service should have in order to be available in the uplink and downlink. This value is not considered for BE services. Average requested rate: Enter the average requested throughput for uplink and downlink. The average requested throughput is used in a simulation during user distribution generation in order to calculate the number of users attempting a connection. Application throughput: Under Application throughput, you can set a Scaling factor between the application throughput and the MAC (Medium Access Control) throughput and a throughput Offset. These parameters model the header information and other supplementary data that does not appear at the application level. The application throughput parameters are used in throughput coverage predictions and for application throughput calculation.
•
Body loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For example, in a voice connection the body loss, due to the proximity of the user’s head, is estimated to be 3 dB.
6. Click OK. Modelling Mobility Types In WiMAX, information about the receiver mobility is required for determining which bearer selection threshold and quality graph to use from the reception equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking speeds do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely dependent on mobile speed. To create or modify a mobility type: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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 car’s onboard navigation device. To create or modify a terminal: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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.
1201
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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. Reception equipment: Select a reception equipment from the list of available equipment. For more information on reception equipment, see "Defining WiMAX Reception Equipment" on page 1306. 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. 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. Diversity support: Select the type of antenna diversity techniques supported by the terminal. Antenna diversity gains will be applied to the users using any terminal type depending on the supported antenna diversity techniques, i.e., AAS, MIMO, or AAS+MIMO. If a terminal that supports AAS+MIMO is connected to a permutation zone that supports both antenna diversity techniques, both AAS and MIMO gains will be applied. Under MIMO, enter the Number of transmission antennas and the Number of reception antennas available in the terminal.
6. Click OK.
12.2.10.8.2
Analysing the Effective Signal Levels Atoll offers a couple of WiMAX coverage predictions which can be based on the predicted signal level from the best server and the thermal background noise at each pixel, i.e., received carrier power (C) and the carrier-to-noise ratio (C/N). This section explains the coverage predictions available for analysing the effective signal levels. Downlink and uplink effective signal analysis coverage predictions predict the effective signal levels of different types of WiMAX signals, such as preamble, traffic, etc., in the part of the network being studied. Atoll calculates the serving transmitter for each pixel depending on the downlink preamble signal level. The serving transmitter is determined according to the received preamble signal level from the cell with the highest preamble power. In a prediction for the "Best" layer, if more than one cell covers the pixel, the one with the highest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the effective signal (C or C/N for preamble, traffic, etc.). Pixels are coloured if the display threshold condition is fulfilled (in other words, if the C or C/N is higher than the C or C/ N threshold). To make an effective signal analysis coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Effective Signal Analysis (DL) or Effective Signal Analysis (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 12.31).
1202
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
On the Condition tab, you can select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The effective signal analysis coverage prediction is always a best server coverage prediction. The Noise figure defined in the terminal type’s 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 reception equipment, see "Modelling Services" on page 1200, "Modelling Terminals" on page 1201, "Modelling Mobility Types" on page 1201, and "Defining WiMAX Reception Equipment" on page 1306, respectively. If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. The shadowing margin for the effective signal analysis calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor coverage into consideration.
Figure 12.31: 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" to display the coverage prediction by permutation zones or segment numbers. Value intervals: Select "Value intervals" to display the coverage prediction by signal levels or C/N levels.
For information on adjusting the display, see "Display Properties of Objects" on page 43. 9. Click the Result Export tab. If, on the Display tab, you have selected to display the results by value intervals and, if you are not displaying the results by the number of servers, you can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 12.32 and Figure 12.33).
1203
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.32: Downlink traffic C/N coverage prediction
Figure 12.33: Uplink C/N coverage prediction
12.2.10.8.3
Analysing the Signal Quality In WiMAX, the capacity and the effective service coverage areas of cells are influenced by network loads. As the network load increases, the area where a cell provides service decreases. For this reason, network loads must be defined in order to calculate these coverage predictions. Atoll offers a series of coverage predictions which are based on the predicted signal level from the best server and the predicted signal levels from other cells (interference) at each pixel, i.e., carrier-to-interference-and-noise ratio, or C/(I+N). The downlink interference received from different cells of the network is weighted by their respective downlink traffic loads. The measure of uplink interference for each cell is provided by the uplink noise rise. If you have traffic maps, you can do a Monte Carlo simulation to determine the downlink traffic loads and the uplink noise rise values for a generated user distribution. If you do not have traffic maps, Atoll can calculate these coverage predictions using the downlink traffic loads and the uplink noise rise values defined for each cell. In this section, these coverage predictions will be calculated using downlink traffic loads and the uplink noise rise values defined at the cell level. Before making a prediction, you will have to set the downlink traffic loads and the uplink noise rise, and the parameters that define the services and users. These are explained in the following sections: •
1204
"Setting the Traffic Loads and the UL Noise Rise" on page 1205.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Several signal quality coverage predictions are explained in this section. The following coverage predictions are explained: • • • • • • •
"Making a Coverage Prediction by C/(I+N) Level" on page 1205. "Making a Downlink or Uplink Service Area Analysis" on page 1208. "Studying the Effective Service Area" on page 1210. "Making a Coverage Prediction by Throughput" on page 1211. "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1213. "Making a Coverage Prediction by Quality Indicator" on page 1214. "Analysing Interference Areas Using a Point Analysis" on page 1216.
Setting the Traffic Loads and the UL Noise Rise If you are setting the traffic loads and the uplink noise rise for a single transmitter, you can set these parameters on the Cells tab of the transmitter’s Properties dialogue. However, you can set the traffic loads and the uplink noise rise for all the cells using the Cells table. To set the traffic loads and the uplink noise rise using the Cells table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Enter a value in the following columns: • • • •
Traffic load (DL) (%) Segmentation usage (DL) (%) UL noise rise (dB) Segmented zone UL noise rise (dB)
Although, you can also set a value for the Traffic load (UL) (%) column as an indication of cells’ uplink loads, this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink is given by the uplink noise rise values. For a definition of the values, see "Cell Description" on page 1155. To enter the same values in one column for all cells in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69. Making a Coverage Prediction by C/(I+N) Level Downlink and uplink coverage predictions by C/(I+N) level predict the interference levels and signal-to-interference levels in the part of the network being studied. Atoll calculates the best server for each pixel depending on the downlink preamble signal level or preamble C/(I+N). The serving transmitter is determined according to the received preamble signal level from the cell with the highest preamble power. In a prediction for the "Best" layer, if more than one cell covers the pixel, the one with the highest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the interference from other cells, and finally calculates the C/(I+N). The pixel is coloured if the display threshold condition is fulfilled (in other words, if the C/(I+N) is higher than C/(I+N) threshold). Coverage prediction by C/(I+N) level calculates the co-channel interference as well as the adjacent channel interference, which is reduced by the adjacent channel suppression factor defined in the Frequency Bands table. For more information on frequency bands, see "Defining Frequency Bands" on page 1300. The preamble C/(I+N) is calculated using the preamble power and the main antenna. Interference on the preamble does not depend on the cell load conditions. It depends only on the probabilities of collision between the subcarriers used to transmit the preamble. The downlink traffic C/(I+N) is calculated using the traffic power, the main antenna or the smart antenna equipment, downlink traffic load, the segmentation usage ratio, and any angular distributions of interference stored either in the cell properties or in the selected simulation results. The uplink C/(I+N) is calculated using the terminal power calculated after power control, the main antenna or the smart antenna equipment, uplink noise rise values, and any angular distributions of interference stored either in the cell properties or in the selected simulation results. The downlink traffic and uplink C/(I+N) also take into account the probabilities of collision between subcarriers when segmentation is used.
1205
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
To make a coverage prediction by C/(I+N) level: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 12.34). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the cell loads stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The C/(I+N) coverage prediction is a best server coverage prediction. The Noise figure defined in the terminal type’s 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 reception equipment, see "Modelling Services" on page 1200, "Modelling Terminals" on page 1201, "Modelling Mobility Types" on page 1201, and "Defining WiMAX Reception Equipment" on page 1306, 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 12.34: Condition settings for a coverage prediction by C/(I+N) level 7. Click the Display tab. 8. From the Display type list, select "Value intervals" to display the coverage prediction by C/(I+N) levels or total noise (I+N) levels.
1206
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
9. For information on adjusting the display, see "Display Properties of Objects" on page 43. 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 1309. 10. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 11. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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 12.35 and Figure 12.36).
Figure 12.35: Coverage prediction by downlink traffic C/(I+N)
Figure 12.36: Coverage prediction by uplink C/(I+N)
1207
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Making a Downlink or Uplink Service Area Analysis Downlink and uplink service area analysis coverage predictions calculate and display the WiMAX radio bearers based on C⁄(I+N) for each pixel. In the coverage predictions, the downlink or uplink service areas are limited by the bearer selection thresholds of the highest and lowest bearers of the selected service. To make a coverage prediction on service area: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Service Area Analysis (DL) or Service Area Analysis (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 12.37). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the downlink traffic load, uplink noise rise values, and any angular distributions of interference stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The best bearer coverage prediction is always based on the best server. The Noise figure defined in the terminal type’s 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 reception equipment. This reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection threshold graph to use. You can make Atoll use only the bearers for which selection thresholds are defined in both the terminal’s and the cell’s reception equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1200, "Modelling Terminals" on page 1201, "Modelling Mobility Types" on page 1201, and "Defining WiMAX Reception Equipment" on page 1306, 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.
1208
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.37: Condition settings for a coverage prediction on WiMAX bearers 7. Click the Display tab. 8. From the Display type list, select display by bearer or modulation. For information on adjusting the display, see "Display Properties of Objects" on page 43. 9. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 12.38 and Figure 12.39).
Figure 12.38: Downlink service area analysis display by bearer
1209
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.39: Uplink service area analysis display by bearer Studying the Effective Service Area The effective service area is the intersection zone between the uplink and downlink service areas. In other words, the effective service area prediction calculates where a service is actually available in both downlink and uplink. The service availability depends upon the bearer selection thresholds of the highest and lowest bearers as defined in the properties of the service selected for the prediction. To make an effective service area coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Effective Service Area Analysis (DL+UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the 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 cell loads defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The best bearer coverage prediction is always based on the best server. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1200, "Modelling Terminals" on page 1201, "Modelling Mobility Types" on page 1201, and "Defining WiMAX Reception Equipment" on page 1306, 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.
1210
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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 is available in both downlink and uplink. For information on defining display properties, see "Display Properties of Objects" on page 43. When creating a coverage prediction by unique values, you can not export the values per pixel.
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Making a Coverage Prediction by Throughput Downlink and uplink throughput coverage predictions calculate and display the channel throughputs and cell capacities based on C⁄(I+N) and bearer calculations for each pixel. These coverage predictions can also display aggregate cell throughputs if Monte Carlo simulation results are available. For more information on making aggregate cell throughput coverage predictions using simulation results, see "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1213. To make a coverage prediction by throughput: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 12.40). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the downlink traffic load, uplink noise rise values, and any angular distribution of interference stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The throughput coverage prediction is always based on the best server. The Noise figure defined in the terminal type’s 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 reception equipment. This reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the serving transmitter for the uplink coverage predictions. 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. You can make Atoll use only the bearers for which selection thresholds are defined in both the terminal’s and the cell’s reception equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual.
1211
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1200, "Modelling Terminals" on page 1201, "Modelling Mobility Types" on page 1201, and "Defining WiMAX Reception Equipment" on page 1306, 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 12.40: Condition settings for a throughput coverage prediction 7. Click the Display tab. 8. From the Display type list, select "Value intervals" to display the coverage prediction by peak MAC, effective MAC, or application throughputs. For information on adjusting the display, see "Display Properties of Objects" on page 43. 9. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the 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 reception equipment defined in the selected terminal for downlink or the reception equipment of the cell of the serving transmitter for uplink. The application throughput is the effective MAC throughput reduced by the overheads of the different layers between the MAC and the Application layers. The cell capacity display types let you calculate and display the throughputs available on each pixel of the coverage area taking into account the maximum traffic load limits set for each cell. In other words, the cell capacity is equal to channel throughput when the maximum traffic load is set to 100%, and is equal to a throughput limited by the maximum allowed traffic loads otherwise. Cell capacities are, therefore, channel throughputs scaled down to respect the maximum traffic load limits. The 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
1212
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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 Network Settings" on page 1301. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Figure 12.41: Coverage prediction by downlink channel throughput
Figure 12.42: Coverage prediction by uplink channel throughput Making an Aggregate Throughput Coverage Prediction Using Simulation Results Atoll calculates the aggregate peak MAC, effective MAC, and application cell throughputs during Monte Carlo simulations. The aggregate cell throughputs are the sums of the cell’s user throughputs. You can create a coverage prediction that calculates and displays the surface area covered by each cell, and colours the coverage area of each cell according to its aggregate throughput.
1213
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
To create an aggregate throughput coverage prediction: 1. Create and run a Monte Carlo simulation. For more information on creating Monte Carlo simulations, see "Calculating and Displaying Traffic Simulations" on page 1255. 2. Create a coverage prediction by throughput as explained in "Making a Coverage Prediction by Throughput" on page 1211, with the following exceptions: a. On the Condition tab, select a simulation or group of simulations from the Load conditions list. The coverage prediction will display the results based on the selected simulation or on the average results of the selected group of simulations. b. On the Display tab, you can display results by Peak MAC aggregate throughput, Effective MAC aggregate throughput, or Aggregate application throughput. The coverage prediction results will be in the form of thresholds. For information on defining the display, see "Display Properties of Objects" on page 43. This coverage prediction displays the surface area covered by each cell and colours it according to its aggregate throughput. For more information on using simulation results in coverage predictions, see "Making Coverage Predictions Using Simulation Results" on page 1269. Making a Coverage Prediction by Quality Indicator Downlink and uplink quality indicator coverage predictions calculate and display the values of different quality indicators (BLER, BER, etc.) based on the best WiMAX radio bearers and on C⁄(I+N) for each pixel. To make a coverage prediction by quality indicator: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Quality Indicator (DL) or Coverage by Quality Indicator (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 12.37). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the downlink traffic load, uplink noise rise values, and any angular distribution of interference stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The quality indicator coverage prediction is always based on the best server. The Noise figure defined in the terminal type’s 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 reception equipment, and the quality indicator graphs from the reception equipment are used to determine the values of the selected quality indicator on each pixel. The reception 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. You can make Atoll use only the bearers for which selection thresholds are defined in both the terminal’s and the cell’s reception equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1200, "Modelling Terminals" on page 1201, "Modelling Mobility Types" on page 1201, and "Defining WiMAX Reception Equipment" on page 1306, respectively.
1214
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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 12.43: Condition settings for a coverage prediction by quality indicators 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 1306. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 43. 8. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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 12.44 and Figure 12.45).
Figure 12.44: Coverage prediction by downlink BLER
1215
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.45: Coverage prediction by uplink BLER
12.2.10.8.4
Analysing Interference Areas Using a Point Analysis In Atoll, you can study the interferers of a transmitter using the Point Analysis tool. At any point on the map, the Interference view gives you information on interference received on any downlink channel. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility, and a service. The downlink and uplink load conditions can be taken from the Cells table or from Monte Carlo simulations. You can make a reception analysis to verify a coverage prediction. If you do, before you make the point analysis, ensure the coverage prediction you want to verify is displayed on the map. To make an interference analysis: 1. Click the Point Analysis button (
) in the Radio Planning toolbar. The Point Analysis window appears (see
Figure 12.46) and the pointer changes (
) to represent the receiver.
2. Select the Interference view. 3. At the top of the Interference view, select "Cells table" from Load. 4. Select the channel on which you want to study the interference from the Display list. 5. If you are making an interference 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. Click the Options button ( • • •
) in the Interference view toolbar. The Calculation Options 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.
c. Click OK to close the Calculation Options dialogue. 6. Move the pointer over the map to make an interference analysis for the current location of the pointer. In the map window, an thick arrow from the pointer to its best server is displayed. Thinner arrows are also displayed from the interfering cells towards the pointer. 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 tip text. 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.
1216
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Select the load conditions to use in this analysis from simulations or from the Cells table.
The best server signal level (top-most bar), total noise (black bar), and interference from other cells.
Select the parameters of the probe user to be studied. Figure 12.46: Point analysis tool: Interference view The Interference view displays, in the form of a bar graph, the signal level from the best server, a black bar indicating the total noise (I+N) received by the receiver, and bars representing the interference received from each interferer. You can change the following options in the Interference view: •
AtollIntra-technology: You can select the Intra-technology check box if you want Atoll to display the intra-technology interference.
To get the details about the best server and all the interferers in the form of a report: •
Click the Report button (
) in the Interference view toolbar. The Analysis Report dialogue appears.
8. Click the Details view. The Details view displays, for each cell received, the cell’s name, its distance from the receiver, its preamble index, and the preamble C, and C/N for all cells. Additionally, the interference from all the cells other than the best server is displayed. 9. Click the Point Analysis button (
) on the Radio Planning toolbar again to end the point analysis.
12.2.10.9 Printing and Exporting Coverage Prediction Results Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. •
•
•
Printing coverage prediction results: Atoll offers several options allowing you to customise and optimise the printed coverage prediction results. Atoll supports printing to a variety of paper sizes, including A4 and A0. For more information on printing coverage prediction results, see "Printing a Map" on page 84. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 59. Exporting coverage prediction results: In Atoll, you can export the coverage areas of a coverage prediction in raster or vector formats. In raster formats, you can export in BMP, TIF, JPEG 2000, ArcView© grid, or Vertical Mapper (GRD and GRC) formats. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 GB. In vector formats, you can export in ArcView©, MapInfo©, or AGD formats. For more information on exporting coverage prediction results, see "Exporting Coverage Prediction Results" on page 67.
12.2.11 Planning Neighbours You can set neighbours for each cell manually, or you can let Atoll automatically allocate neighbours, based on the parameters that you define. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as potential neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as potential neighbours all the active and filtered cells whose propagation zone intersects the rectangle containing the computation zone. If there is no focus zone, Atoll allocates 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 explorer 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,
1217
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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 "The Focus Zone and Hot Spots" on page 56. For information on grouping transmitters in the explorer window, see "Grouping Data Objects" on page 89. Atoll supports the following neighbour types in a WiMAX network: • •
Intra-technology neighbours: Intra-technology neighbours are cells defined as neighbours that also use WiMAX. Inter-technology neighbours: Inter-technology neighbours are cells defined as neighbours that use a technology other than WiMAX.
In this section, the following are explained: • • • • • • • • •
"Importing Neighbours" on page 1218 "Defining Exceptional Pairs" on page 1218 "Configuring Importance Factors for Neighbours" on page 1219 "Allocating Neighbours Automatically" on page 1219 "Checking Automatic Allocation Results" on page 1222 "Allocating and Deleting Neighbours per Cell" on page 1225 "Calculating the Importance of Existing Neighbours" on page 1227 "Checking the Consistency of the Neighbour Plan" on page 1228 "Exporting Neighbours" on page 1229.
12.2.11.1 Importing Neighbours You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table. To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Network explorer. b. Right-click the Transmitters folder. The context menu appears. c. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 82.
12.2.11.2 Defining Exceptional Pairs In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs might be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Select the Network explorer. 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 cell’s 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. Click the Edit button on the bottom-right of the dialogue. The exceptional pair list becomes editable. b. Select the cell from the list in the Neighbours column. c. In the Status column, select one of the following: • •
Forced: The selected cell will always be a neighbour of the reference cell. Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair. 9. Click OK. You can also create exceptional pairs using the Intra-technology Exceptional Pairs table. You can open this table by right-clicking the Transmitters folder and selecting Neighbours > Intra-technology > Exceptional Pairs.
1218
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.2.11.3 Configuring Importance Factors for Neighbours You can define the relative importance of the factors that Atoll uses to evaluate potential neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. On the Intra-technology Neighbours tab, you can set the following importance factors: • • •
•
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency factor will be used if you select the Force adjacent transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 1219. 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 1219.
5. Click OK. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual.
12.2.11.4 Allocating Neighbours Automatically Atoll can automatically allocate neighbours in a WiMAX network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. Depending on the best server selection method defined in the network settings, the automatic neighbour allocation can be based on coverage areas calculated for best servers based on the preamble C or the preamble C/(I+N). For more information, see "The Global Network Settings" on page 1301. To allocate WiMAX neighbours automatically: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > 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. Global preamble C/N threshold: Select the Global 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 value here, Atoll will either use this value or the Preamble C/N threshold value defined for each cell, 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 12.47). 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 12.47). The value entered for the Handover end must be greater than the value for the Handover start. The higher the value entered for the Handover end, the longer the list of potential neighbours. The area between the Handover start and the Handover end constitutes the area within which Atoll will search for neighbours.
1219
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
The preamble signal level threshold (in dBm) is calculated for each cell from its preamble C/N threshold (in dB) considering the channel bandwidth of the cell and using the terminal that has the highest difference between its gain and losses so that the most number of potential neighbours can be processed. •
•
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 defined per clutter class in the calculations. % min covered area: Enter the minimum surface area, in percentage, that a possible neighbour cell’s coverage area must overlap the reference cell’s 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 cell’s 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 1218. 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 12.47: The handover area between the reference cell and the possible neighbour 7. 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 "Configuring Importance Factors for Neighbours" on page 1219 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: • •
1220
Co-site Adjacency
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
• •
• Symmetry • Coverage • Existing Relation type: The type of the neighbour relation: intra-carrier or inter-carrier. Cells whose channels have the same start frequency, the same channel width, and the same total number of subcarriers are intra-carrier neighbours. Other cells are inter-carrier neighbours. Coverage: The amount of reference cell’s 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 Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: •
Click Compare. The list of automatically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: • • • •
The document name and the neighbour allocation type, 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 cell’s Properties dialogue. •
•
•
•
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. 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. However, if the neighbour relation is forced in one direction and forbidden in the other, the symmetry cannot be respected. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Saving a User Configuration" on page 101.
Atoll also enables you to automatically allocate neighbours to a single base station or transmitter: • •
12.2.11.4.1
"Allocating Neighbours to a New Base Station" on page 1221 "Allocating Neighbours to a New Transmitter" on page 1222.
Allocating Neighbours to a New Base Station When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects the coverage area of the cells of the new base station. To allocate neighbours to a new base station: 1. In the Network explorer, group the transmitters by site, as explained in "Grouping Data Objects" on page 89. 2. In the Transmitters folder, right-click the new base station. The context menu appears. 3. Select Neighbours > Intra-technology > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 1219.
1221
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
12.2.11.4.2
© Forsk 2012
Allocating Neighbours to a New Transmitter When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new transmitters and other cells whose coverage area intersects the coverage area of the cells of the new transmitter. To allocate neighbours to a new transmitter: 1. Select the Network explorer. 2. In the Transmitters folder, right-click the new transmitter. The context menu appears. 3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 1219.
12.2.11.5 Checking Automatic Allocation Results You can verify the results of automatic neighbour allocation in the following ways: • •
12.2.11.5.1
"Displaying Neighbour Relations on the Map" on page 1222. "Displaying the Coverage of Each Neighbour of a Cell" on page 1224.
Displaying Neighbour Relations on the Map You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
2. Select Display Options from the context menu. The Neighbour Display dialogue appears. 3. Under Intra-technology neighbours, select the Display links check box. 4. Click the Browse button ( appears.
) beside the Display links check box. The Intra-technology Neighbour Display dialogue
5. From the Display type list, choose one of the following: • •
•
Unique: Select "Unique" if you want Atoll to colour all neighbour links of a cell with a unique colour. Discrete values: Select "Discrete values", and then a value from the Field list, if you want Atoll to colour the cell’s 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 cell’s neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s neighbours according to the importance, as determined by the weighting factors. 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 Type’s Data Table" on page 71.
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 43. 6. Select the Add to legend check box to add the displayed neighbour links to the legend. 7. Click the Browse button ( ) next to Tip text and select the neighbour characteristics to be displayed in the tip text. This information will be displayed on each neighbour link. 8. Click OK to save your settings. 9. Under Advanced, select which neighbour links to display: •
1222
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.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
• •
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 links: Select the Symmetric links check box to display neighbour relations that are symmetric between the selected cell and the neighbour.
10. Click OK to save your settings. 11. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
12. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 13. Click the Edit Relations on the Map button (
) in the Radio Planning toolbar.
14. Select a transmitter to show its neighbour links: •
•
•
In the Transmitters folder of the Network explorer: Select the transmitter in the Transmitters folder. The selected transmitter is centred in the map and all its neighbours are indicated. Atoll displays the selected transmitter in the Neighbours table if it is open. On the map: Select the transmitter on the map. The neighbours of the selected transmitter are displayed on the map. 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 41). Atoll displays the selected transmitter in the Neighbours table if it is open. In the Neighbours table: Select the transmitter-neighbour relation you want to display by clicking in the left margin of the table row to select the entire row. The selected transmitter is centred in the map with the selected transmitter-neighbour relation (see Figure 12.48). The selected transmitter is also displayed in the Transmitters folder of the Network explorer.
Figure 12.48: Selecting a transmitters in the Neighbours table Atoll displays the following information (see Figure 12.49) 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 12.49.). The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (see Site9_3(0)) in Figure 12.49.).
In Figure 12.49, 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.
1223
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.49: Neighbours of Site 22_3(0) - Display according to the neighbour You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
12.2.11.5.2
Displaying the Coverage of Each Neighbour of a Cell By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cell’s neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a "Coverage by Transmitter" prediction, with the Display type set to "Discrete values" and the Field set to "Transmitter" (for information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by Transmitter" on page 1187). 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
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 ( dialogue appears.
) beside the Display coverage areas check box. The Intra-technology Neighbour Display
6. From the Display type list, choose one of the following: • • •
Unique: Select "Unique" if you want Atoll to colour the coverage area of a cell’s neighbours with a unique colour. Discrete values: Select "Discrete values", and then a value from the Field list, if you want Atoll to colour the coverage area of a cell’s neighbours according to a value from the Intra-technology Neighbours table. Value intervals: Select "Value intervals" to colour the coverage area of a cell’s neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s neighbours according to the importance, as determined by the weighting factors.
7. Click the Browse button ( ) next to Tip text and select the neighbour characteristics to be displayed in the tip text. This information will be displayed on each coverage area. 8. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
9. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 10. Click the Edit Relations on the Map button (
) in the Radio Planning toolbar.
11. 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 41). 12. In order to restore colours and cancel the neighbour display, click the Edit Relations on the Map button ( Radio Planning toolbar.
1224
) in the
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.2.11.6 Allocating and Deleting Neighbours per Cell Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of a transmitter’s Properties dialogue. This section explains the following: • • •
"Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1225. "Allocating or Deleting Neighbours Using the Neighbours Table" on page 1225. "Allocating or Deleting Neighbours on the Map" on page 1226.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue To allocate or delete WiMAX neighbours using the Cells tab of the transmitter’s 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 transmitter’s Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, click the Browse button (
) beside Neighbours. The cell’s Properties dialogue appears.
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. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Under List, select the cell from the list in the Neighbour column in the row marked with the New row icon (
).
c. 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 Source to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. Select Make Symmetrical 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Press DEL to delete the neighbour. 8. Click OK. Allocating or Deleting Neighbours Using the Neighbours Table To allocate or delete WiMAX neighbours using the Neighbours table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears.
1225
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
For information on working with data tables, see "Working with Data Tables" on page 69.
4. Allocate or delete a neighbour. To allocate a new neighbour: a. In the row marked with the New row icon (
), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Source to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Make Symmetrical 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 Make Symmetrical from the context menu. To take into consideration all exceptional pairs: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. You can add or delete either selected forced neighbours or selected forbidden neighbours using the Intra-technology Exceptional Pairs table. You can open this table, select the exceptional pairs to be considered, right-click the table and select Force Exceptional Pairs in the context menu. To delete a symmetric neighbour relation: a. Click in the left margin of the table row containing the neighbour to select entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. To delete several symmetric neighbour relations: a. Click in the left margins of the table rows containing the neighbours to select entire rows. You can select contiguous rows by clicking the first row, pressing Shift and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. Allocating or Deleting Neighbours on the Map You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 1222.
1226
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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. •
•
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 41). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
12.2.11.7 Calculating the Importance of Existing Neighbours After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours in the AFP process. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 4. Select the Intra-technology Neighbours tab. 5. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as potential neighbours. 6. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 1219):
1227
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
• •
© Forsk 2012
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. 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.
7. Under Coverage conditions, you can set the coverage conditions between neighbours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage Conditions dialogue, you can change the following parameters: • •
• • • •
Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Global preamble C/N threshold: Select the Global 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 value here, Atoll will either use this value or the Preamble C/N threshold value defined for each cell, 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.
8. Click OK to save your modifications and close the Coverage Conditions dialogue. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated. 9. 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 Relation type: The type of the neighbour relation: intra-carrier or inter-carrier. Cells whose channels have the same start frequency, the same channel width, and the same total number of subcarriers are intra-carrier neighbours. Other cells are inter-carrier neighbours. Coverage: The amount of reference transmitter’s 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.
10. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
12.2.11.8 Checking the Consistency of the Neighbour Plan You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the neighbour allocation plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Audit from the context menu. The Neighbour Audit dialogue appears.
1228
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
4. Click the Intra-technology Neighbours tab. 5. Define the parameters of the audit: • • •
•
• • • •
Average no. of neighbour: Select the Average no. of neighbours check box if you want to verify the average number of neighbours per cell. Empty lists: Select the Empty lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full lists: Select the Full lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all the cells, or specified for each cell in the Cells table. Lists > max number: Select the Full lists check box if you want to verify which cells have more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all the cells, or specified for each cell in the Cells table. Missing co-sites: Select the Missing co-sites check box if you want to verify which cells have no co-site neighbours. Missing symmetrics: Select the Missing symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional pairs: Select the Exceptional pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance between neighbours: Select the Distance between neighbours check box and enter the distance between neighbours that should not be exceeded.
6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: •
Average number of neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax:
•
Full lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax:
•
|CELL|
|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| 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:
•
Non symmetric links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
Existing forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Missing forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
|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|
12.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. Select the Network explorer. 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:
1229
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
• • • •
© Forsk 2012
Intra-technology > Open Table: This table contains the data for the intra-technology neighbours in the current Atoll document. Inter-technology > Open Table: This table contains the data for the inter-technology neighbours in the current Atoll document. Intra-technology > Exceptional Pairs: This table contains the data for the intra-technology exceptional pairs (forced and forbidden) in the current Atoll document. Inter-technology > Exceptional Pairs: This table contains the data for the inter-technology exceptional pairs (forced and forbidden) in the current Atoll document.
4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text Files and Spreadsheets" on page 80.
12.3 Configuring Network Parameters Using the AFP Atoll Automatic Frequency Planning (AFP) enables radio engineers designing WiMAX networks to automatically configure network parameters such as the frequency channels, preamble indexes, and permbases. The AFP can perform fractional frequency planning through automatic configuration of the segment number in preamble index planning. In this section, the following are explained: • • • • •
"AFP Prerequisites" on page 1230 "Planning Frequencies" on page 1233 "Planning Preamble Indexes" on page 1234 "Planning Permutation Zone PermBases" on page 1236 "Displaying and Analysing the AFP Results" on page 1237.
12.3.1 AFP Prerequisites In Atoll, you can use an Automatic Frequency Planning (AFP) module to allocate frequencies, preamble indexes, and permbases. The AFP module attempts to allocate resources in a way that minimises interference and complies with a set of user-defined constraints. The AFP assigns a cost to each constraint and then uses a cost-based algorithm to evaluate possible allocation plans and propose the allocation plan with the lowest costs. In this section, the AFP input elements are explained. The quality of the results given by the AFP depend on the accuracy of the input, therefore it is important to prepare the input before running the AFP. In this section, the following are explained: • • • •
"Interference Matrices" on page 1230 "Neighbour Importance" on page 1232 "Resources Available for Allocation" on page 1232 "Constraint Weights" on page 1233.
12.3.1.1 Interference Matrices In Atoll, the probability of interference between pairs of cells is stored in an interference matrix. An interference matrix can be thought of as the probability that a user in a cell will receive interference higher than a defined threshold. You can calculate, import, edit, and store more than one interference matrix in the Interference Matrices folder in the Network explorer. In this section, the following are explained: • • •
12.3.1.1.1
"Calculating Interference Matrices" on page 1230 "Importing and Exporting Interference Matrices" on page 1231 "Viewing and Editing Interference Matrices" on page 1231.
Calculating Interference Matrices Atollcalculates interference matrices in the form of co- and adjacent channel interference probabilities for each interfered and interfering cell pair. The probabilities of interference are stated in terms of percentages of the interfered area. In other words, it is the ratio of the interfered surface area to the best server coverage area of an interfered cell. When Atoll calculates interference matrices, it calculates the value of the preamble C/(I+N) for each pixel of the interfered service area between two cells (the interfered cell and the interfering cell). For co-channel interference, a pixel is considered interfered if the C/(I+N) is lower than the preamble C/N threshold defined for the interfered cell. For adjacent channel 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).
1230
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
To calculate interference matrices: 1. Select the Network explorer. 2. Right-click the Interference Matrices folder. The context menu appears. 3. Select New. The Interference Matrices Properties dialogue appears. 4. On the General tab, you can set the following parameters: • • • • •
Name: Enter a name for the new interference matrix. Resolution: Enter the resolution used to calculate the coverage areas of cells for the interference matrix calculation. Type: The type is set to Calculated for calculated interference matrices. Quality margin: Enter a quality margin. Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell edge coverage probability.
5. Once you have created the new interference matrix, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined interference matrix and calculate it immediately. OK: Click OK to save the defined interference matrix without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once calculated, the new interference matrix is available in the Interference Matrices folder and will be available for use the next time you run the AFP. You can modify the properties of an existing interference matrix by selecting Properties from the interference matrix context menu. An existing interference matrix can be calculated again by selecting Calculate from the interference matrix context menu.
12.3.1.1.2
Importing and Exporting Interference Matrices You can import interference matrices from external sources, such as the OAM, in Atoll from from TXT (text), CSV (comma separated value), and IM2 files. In the interference matrix file you want to import, the interference matrix entries must have the following syntax: The separator can be a tab, a comma, a semicolon, or space. If the interference matrix file being imported contains the same interfered-interferer pair more than once, Atoll keeps the last description of the pair. Atoll does not perform a validity check on the imported interference file; you must therefore ensure that the imported information is consistent with the current configuration. Furthermore, Atoll only imports interference matrices for active transmitters. To import an interference matrix: 1. Select the Network explorer. 2. Right-click the Interference Matrices folder. The context menu appears. 3. Select Import. The Open dialogue appears. 4. Select the file containing the interference matrix and click Open. The table Import dialogue appears. For more information on importing table data, see "Importing Tables from Text Files" on page 82. To export an interference matrix: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Interference Matrices folder. 3. Right-click the interference matrix you want to export. The context menu appears. 4. Select Export. The Export dialogue appears. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80.
12.3.1.1.3
Viewing and Editing Interference Matrices Interference matrices store co- and adjacent channel interference probabilities for each interfered and interfering cell pair.
1231
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
To view or edit the contents of an interference matrix: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Interference Matrices folder. 3. Right-click the interference matrix whose contents you want to view. The context menu appears. 4. Select Properties. The Interference Matrices Properties dialogue appears. 5. Click the Interference Matrices tab. The co- and adjacent channel interference probabilities are available in the form of a table for each interfered and interfering cell pair. You can edit the interference probabilities, add new interfered and interfering cell pairs and their probabilities, and copy interference probabilities from another source, such as the OAM, directly in this table. 6. Click OK, once you have viewed or edited the probabilities.
12.3.1.2 Neighbour Importance In Atoll, neighbour importance values are calculated by the automatic neighbour allocation process and can be used by the AFP for frequency, preamble index, and permbase allocation. For information on configuring neighbour importance weighting, see "Configuring Importance Factors for Neighbours" on page 1219. For more information on calculating neighbour importance values, see "Calculating the Importance of Existing Neighbours" on page 1227. For more details on the calculation of neighbour importance values, see the Technical Reference Guide.
12.3.1.3 Resources Available for Allocation The AFP allocates resources from a pool of available resources. For automatic frequency planning, the available resources are defined by the channel numbers available in the frequency band assigned to any cell. In the frequency band properties, the first and last channel numbers define the range of available channel numbers in the band. Channel numbers within this range can be set as unavailable by listing them in the excluded channels list. For more information, see "Defining Frequency Bands" on page 1300. start here For automatic preamble index planning, Atoll facilitates the management of preamble indexes by letting you create domains, each containing groups of preamble indexes. The procedure for managing preamble indexes in a WiMAX document consists of the following steps: 1. Creating a preamble index domain, as explained in this section. 2. Creating groups, each containing a range of preamble indexes, and assigning them to a domain, as explained in "Planning Preamble Indexes" on page 1234. 3. Assigning a preamble index domain to a cell or cells. If there is no preamble index domain, Atoll will consider all 114 possible preamble indexes when assigning them automatically. To create a preamble index domain: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the Network Settings folder.
3. Click the Expand button (
) to expand the Preamble Indexes folder.
4. Right-click Domains in the Preamble Indexes folder. The context menu appears. 5. Select Open Table from the context menu. The Domains table appears. 6. In the row marked with the New Row icon (
), enter a Name for the new domain.
7. Click in another cell of the table to create the new domain and add a new blank row to the table. 8. Double-click the domain to which you want to add a group. The domain’s Properties dialogue appears. 9. Under Groups, enter the following information for each group you want to create. • • • • • •
Name: Enter a name for the new preamble index group. Min.: Enter the lowest available preamble index in this group’s range. Max: Enter the highest available preamble index in this group’s range. Step: Enter the separation interval between each preamble index . Excluded: Enter the preamble index in this range that you do not want to use. Extra: Enter any additional preamble index (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 preamble indexes separated by either a comma, semi-colon, or a space. You can also enter a range of preamble indexes separated by a hyphen. For example, entering, "1, 2, 3-5" means that the extra preamble indexes are "1, 2, 3, 4, 5."
10. Click in another cell of the table to create the new group and add a new blank row to the table.
1232
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
The available resources can also be defined for all the cells globally in the AFP dialogue by selecting Custom for the Allocation domain, and entering the list of Excluded resources. For more information, see "Planning Preamble Indexes" on page 1234.
12.3.1.4 Constraint Weights You can define the constraint weights for the AFP cost components that Atoll uses to evaluate possible frequency and preamble index plans. To configure the AFP constraint weights: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select AFP > Configure Constraint Weights from the context menu. The Constraint Weights dialogue appears. This dialogue enables you to define the relative weights of the cost components. The absolute values of the constraint weights are calculated by the AFP using these relative weights. For more information, see the Technical Reference Guide. 4. Click the Frequency Allocation tab. On the Frequency Allocation tab, you can set the constraint weights for the Neighbours, Interference matrices, and Distance cost components. 5. Click the Preamble Index Allocation tab. 6. On the Preamble Index Allocation tab, you can set the constraint weights for the 1st order neighbours, 2nd order neighbours, Neighbours of a common cell, Interference matrices, and Distance cost components, as well as for the Preamble index constraint, Segment constraint, and Cell permbase constraint. •
•
•
You can move the slider all the way to the left to set the relative weight of a constraint to 0 %. The constraint will no longer have any effect in the evaluation of the AFP cost. You can move the slider all the way to the right to set the relative weight to 100 %. The constraint will have the highest weight compared to the other constraints involved in the evaluation of the AFP cost. You can click the Reset button to set the weights to their default values.
7. Click OK.
12.3.2 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. To allocate frequencies, the AFP can take into account interference matrices, reuse distance, and any constraints imposed by neighbours. To automatically allocate frequencies: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select AFP > Automatic Frequency Allocation. The Resource Allocation dialogue appears. 4. Under Allocate, select Frequencies to perform automatic frequency planning. 5. Under Relations, you can set the constraints to take into account in automatic allocation. •
•
•
Interference matrices: Select the Interference matrices check box if you want the AFP to take interference matrices into account for the allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account, they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, imported, and edited in the Interference Matrices folder. For more information on interference matrices, see "Interference Matrices" on page 1230. Existing neighbours: Select the Existing neighbours check box if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different frequencies to a cell and its neighbours. Atoll can only take neighbour relations into account if neighbours have already been allocated. For information on allocating neighbours, see "Planning Neighbours" on page 1217. Reuse distance: Select this check box if you want the AFP to take relations based on distance into account for the allocation. You can enter a Default reuse distance within which two cells must not have the same channel assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the
1233
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
size of the cell’s coverage area and the network density around the cell. If defined, a cell-specific reuse distance is used instead of default the value entered here. 6. Under Results, Atoll displays the Total cost of the current frequency allocation taking into account the parameters set in step 5. You can modify the parameters and click Update 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 number of the cell before automatic allocation. Segment: The segment number of the cell after automatic allocation. Initial cell permbase: The cell permbase of the cell before automatic allocation. Cell permbase: The cell permbase of the cell after automatic allocation. Cost: The cost of the new allocation plan of the cell. Preamble index status: The value of the Preamble index status of the cell. Locked segment: Whether the segment was locked for this allocation or not.
8. Click Commit. The proposed frequency plan is assigned to the cells of the network. When you allocate frequencies to a large number of cells, it is easiest to let Atoll allocate them automatically. However, if you want to assign a frequency to one cell or to modify it, you can do it by accessing the properties of the cell. To allocate the frequency to a cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate the frequency. The context menu appears. 2. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 3. Select the Cells tab. 4. Select a Frequency band and Channel number for the cell. 5. You can set the Channel allocation status to Locked if you want to lock the frequency that you assigned. 6. Click OK.
12.3.3 Planning Preamble Indexes In WiMAX, 114 preamble indexes are available, numbered from 0 to 113. There are as many pseudo-noise sequences defined in the IEEE specifications. A PN sequence is transmitted on the preamble subcarriers corresponding to each preamble index using BPSK1/2. Mobiles recognise their serving cells by comparing the received PN sequences with the 114 sequences stored in their memory. The preamble index of the serving cell is simply the number of the PN sequence received with the highest power. The preamble index provides the segment number (0, 1, or 2) and the cell permbase (DL_PermBase of the first downlink PUSC zone, also called ID_Cell, which is a value from 0 to 31.) Therefore, the mobile knows which subcarriers to listen to for the FCH, DCD, UCD, DL-MAP, and UL-MAP. Because the cell search and selection depend on the preamble index of the cells, preamble indexes must be intelligently allocated to cells in order to avoid unnecessary interference on the preamble. The subcarriers used for preamble transmission are divided into 3 carrier sets. Preamble carrier sets are defined by the equation: Preamble Carrier Set n = n + 3 × k
Where n is the segment number (0, 1, or 2), and k is a running index from 0 to 567, 0 to 283, 0 to 142, and 0 to 35 for FFT sizes 2048, 1024, 512, and 128, respectively. Therefore, each preamble carrier set uses every third subcarrier. Atoll facilitates the management of preamble indexes by letting you create groups of preamble indexes and domains, where each domain is a defined set of groups. For more information, see "Resources Available for Allocation" on page 1232. You can assign preamble indexes manually or automatically to any cell in the network. Once allocation is completed, you can audit the preamble indexes, view preamble index reuse on the map, and make an analysis of preamble index distribution. Atoll can automatically assign preamble indexes to the cells taking into account the selected cell permbase allocation strategy (free or same per site), allowed allocation domain, interference matrices, reuse distance, and any constraints imposed by neighbours.
1234
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
To automatically allocate preamble indexes: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select AFP > Automatic Preamble Index Allocation. The Resource Allocation dialogue appears. 4. Under Allocate, select Preamble index to allocate preamble indexes to cells automatically. 5. Select the Allocation domain. You can choose Per cell to allocate preamble indexes from the preamble index domain defined per cell, you can choose to allocate preamble indexes from the Entire (0-113) domain, a Restricted (0-95) domain, or you can choose Custom and enter the Excluded resources to exclude some preamble indexes from the allocation. You can enter non-consecutive preamble indexes separated with a comma, or you can enter a range of preamble indexes separating the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5"). 6. Under Allocation strategies, you can select: •
• •
Cell permbase: Select Same per site if you want the AFP to allocate the same cell permbase to all the cells of a site. If allocating the same cell permbase to cells of a site causes collisions of preamble indexes, the constraint of allocating the same cell permbase per site can be broken. Select Free if you want the AFP to ignore the cell permbase collisions. With free allocation, the cell permbase will not necessarily be the same for all the cells of a site. Uniform distribution: Select Strict if you want the AFP to distribute the preamble indexes uniformly. Select Inactive if a non-uniform distribution is acceptable. Allocate same segment to co-transmitter cells: Select this 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 Relations, you can set the constraints to take into account in automatic allocation. •
•
•
Interference matrices: Select the Interference matrices check box if you want the AFP to take interference matrices into account for the allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account, they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, imported, and edited in the Interference Matrices folder. For more information on interference matrices, see "Interference Matrices" on page 1230. Existing neighbours: Select the Existing neighbours check box if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different preamble indexes to a cell and its neighbours. The AFP can take neighbours into account only if neighbours have already been allocated. If you want the AFP to take both first and second order neighbours into account, you must set an option in the atoll.ini file (see the Administrator Manual). For information on allocating neighbours, see "Planning Neighbours" on page 1217. Reuse distance: Select this check box if you want the AFP to take relations based on distance into account for the allocation. You can enter a Default reuse distance within which two cells must not have the same preamble index assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the size of the cell’s coverage area and the network density around the cell. If defined, a cell-specific reuse distance is used instead of default the value entered here.
8. Under Results, Atoll displays the Total cost of the current preamble index allocation taking into account the parameters set in step 7. You can modify the parameters and click Update cost to see the change in the total cost. 9. 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 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 number of the cell before automatic allocation. Segment: The segment number of the cell after automatic allocation. Initial cell permbase: The cell permbase of the cell before automatic allocation. Cell permbase: The cell permbase of the cell after automatic allocation. Cost: The cost of the new allocation plan of the cell. Preamble index status: The value of the Preamble index status of the cell. Locked segment: Whether the segment was locked for this allocation or not.
10. Click Commit. The proposed preamble index plan is assigned to the cells of the network.
1235
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
When you allocate preamble indexes to a large number of cells, it is easiest to let Atoll allocate them automatically. However, if you want to assign a preamble index to one cell or to modify it, you can do it by accessing the properties of the cell. To allocate a preamble index to a WiMAX cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate a preamble index. The context menu appears. 2. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 3. Select the Cells tab. 4. Enter a Preamble index in the cell’s 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.
12.3.4 Planning Permutation Zone PermBases In WiMAX, downlink permutation zones use seeds for the permutation sequence to determine the correspondence between physical and logical subcarrier numbers and the subcarriers belonging to different subchannels. These permutation seeds are called permbases. The first downlink PUSC permutation zone, that carries the FCH, the DL-MAP, the UL-MAP, uses the permbase mapped to the preamble index of the cell. This permbase is called the cell permbase in Atoll, and is allocated when a preamble index is allocated to a cell. Other permutation zones use different permbases. Atoll supports one additional zone permbase in downlink and one in uplink. These permbases are called zone permbases in Atoll. There are 32 possible permbases in downlink, numbered from 0 to 31, and 70 in uplink, numbered from 0 to 69. You can assign zone permbases manually or automatically to any cell in the network. Once allocation is completed, you can view zone permbase reuse on the map. Atoll can automatically assign zone permbases to the cells taking into account the allowed allocation domain, interference matrices, reuse distance, and any constraints imposed by neighbours. To automatically allocate permutation zone permbases: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select AFP > Automatic DL Zone PermBase Allocation or AFP > Automatic UL Zone PermBase Allocation. The Resource Allocation dialogue appears. 4. Under Allocate, select DL zone permbase or UL zone permbase to allocate downlink or uplink permutation zone permbases to cells. 5. Select the Allocation domain. You can choose to allocate permbases from Entire (0-31) for downlink permutation zone permbase or Entire (0-69) for uplink permutation zone permbase, or you can choose Custom and enter the Excluded resources to exclude some permbases from the allocation. You can enter non-consecutive permbases separated with a comma, or you can enter a range of permbases separating the first and last with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5"). 6. Under Relations, you can set the constraints to take into account in automatic allocation. •
•
•
Interference matrices: Select the Interference matrices check box if you want the AFP to take interference matrices into account for the allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account, they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, imported, and edited in the Interference Matrices folder. For more information on interference matrices, see "Interference Matrices" on page 1230. Existing neighbours: Select the Existing neighbours check box if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different permbases to a cell and its neighbours. The AFP can take neighbours into account only if neighbours have already been allocated. If you want the AFP to take both first and second order neighbours into account, you must set an option in the atoll.ini file (see the Administrator Manual). For information on allocating neighbours, see "Planning Neighbours" on page 1217. Reuse distance: Select this check box if you want the AFP to take relations based on distance into account for the allocation. You can enter a Default reuse distance within which two cells must not have the same zone permbase assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the size of the cell’s coverage area and the network density around the cell. If defined, a cell-specific reuse distance is used instead of default the value entered here.
7. Under Results, Atoll displays the Total cost of the current permbase allocation taking into account the parameters set in step 6. You can modify the parameters and click Update cost to see the change in the total cost. 8. Click Calculate. Atoll begins the process of allocating permbases. Once Atoll has finished allocating permbases, the indexes are visible under Results.
1236
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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. Channel number: The channel number of the cell after automatic allocation. Initial DL or UL zone permbase: The downlink or uplink zone permbase of the cell before automatic allocation. DL or UL zone permbase: The downlink or uplink zone permbase of the cell after automatic allocation. Cost: The cost of the new allocation plan of the cell. DL or UL zone permbase status: The value of the DL zone permbase status or UL zone permbase status of the cell.
9. Click Commit. The proposed permbase plan is assigned to the cells of the network. When you allocate permutation zone permbases to a large number of cells, it is easiest to let Atoll allocate them automatically. However, if you want to assign a permutation zone permbase to one cell or to modify it, you can do it by accessing the properties of the cell. To allocate a permutation zone permbase to a WiMAX cell manually: 1. On the map, right-click the transmitter to whose cell you want to allocate a preamble index. The context menu appears. 2. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 3. Select the Cells tab. 4. Enter a DL zone permbase or UL zone permbase in the cell’s column. 5. You can set the DL zone permbase status or UL zone permbase status to Locked if you want to lock the permutation zone permbase that you assigned. 6. Click OK.
12.3.5 Displaying and Analysing the AFP Results You can display and analyse AFP results in several ways: • • • • • •
"Using Find on Map to Display AFP Results" on page 1237. "Displaying AFP Results Using Transmitter Display Settings" on page 1238. "Grouping Transmitters by Channels, Preamble Indexes, Zone PermBases" on page 1239. "Analysing the Frequency Allocation Using Coverage Predictions" on page 1239. "Checking the Consistency of the Preamble Index Plan" on page 1240. "Displaying the Preamble Index Allocation Histogram" on page 1240.
12.3.5.1 Using Find on Map to Display AFP Results In Atoll, you can search for frequency bands, channel numbers, preamble indexes, segment numbers, and cell permbases, using Find on Map. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. The current allocation plan and any potential problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 1187. To find a frequency band using Find on Map: 1. Select Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "WiMAX Channel." 3. From the Band list, select a frequency band. 4. From the Channel list, select "All." 5. Click Search. Transmitters whose cells use the selected frequency band are displayed in red in the map window and are listed under Results in the Find on Map window. Transmitters with cells using other frequency bands are displayed as grey lines in the map window. To restore the initial transmitter colours, click the Reset display button in the Find on Map window. To find a channel number using Find on Map: 1. Select Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "WiMAX Channel." 3. From the Band list, select a frequency band.
1237
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
4. From the Channel list, select the channel number. By default, Find on Map displays only co-channel transmitter cells. If you want adjacent channels to be displayed as well, select the Adjacent channels check box. 5. Click Search. Transmitters whose cells use the selected frequency band and channel number are displayed in red. Transmitters with cells using two adjacent channel numbers in the same frequency band (i.e., a channel higher and a channel lower) are displayed in yellow. Transmitters with cells using a lower adjacent channel number in the same frequency band are displayed in green. Transmitters with cells using a higher adjacent channel number in the same frequency band are displayed in blue. All other transmitters are displayed as grey lines. If you cleared the Adjacent channels check box, transmitters with cells using the same channel number are displayed in red, and all others, including transmitters with adjacent channels, are displayed as grey lines. To restore the initial transmitter colours, click the Reset display button in the Find on Map tool window. By including the frequency band and channel number of each cell in the transmitter label, the search results will be easier to understand. For information on defining the label, see "Defining the Object Type Label" on page 46. To find a preamble index, segment number, or cell permbase using Find on Map: 1. Click Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "Preamble Index." 3. Select what you what you want to search for: • • •
Preamble index: If you want to find a preamble index, select Preamble index and select the preamble index from the list. Segment: If you want to find a segment number, select Segment and select the segment number from the list: "All," "0," "1," or "2." Cell permbase: If you want to find a cell permbase, select Cell permbase and select the cell permbase from the list.
4. Click Search. When you select a preamble index or a cell permbase, transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match the search criteria are displayed as grey lines. When you select a specific segment number, transmitters whose cells use the selected segment are displayed in red. Transmitters with cells that use other segments are displayed as grey lines. When you choose to search for all segments, transmitters whose first cells use segment 0 are displayed in red, transmitters whose first cells use segment 1 are displayed in yellow, and transmitters whose first cells use segment 2 are displayed in green. To restore the initial transmitter colours, click the Reset display button in the Search Tool window. •
•
By including the preamble index of each cell in the transmitter label, the search results will be easier to understand. For information on defining the label, see "Defining the Object Type Label" on page 46. Transmitters with more than one cell may use different segments in different cells. Therefore, the search for all segments is only valid for single-cell transmitters.
12.3.5.2 Displaying AFP Results Using Transmitter Display Settings You can display the frequency and preamble index allocation on transmitters by using the transmitters’ display characteristics. To display the frequency allocation on the map: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. 5. Select "Discrete values" as the Display type and "Cells: Channel number" as the Field. 6. Click OK. Transmitters will be displayed by channel number. You can also display the frequency band and channel number in the transmitter label or tip text by selecting "Cells: Frequency band" and "Cells: Channel number" from the Label or Tip Text Field Definition dialogue.
1238
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
To display preamble index allocation on the map: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. 5. Select "Discrete values" as the Display type and "Cells: Preamble index" as the Field. 6. Click OK. Transmitters will be displayed by preamble index. You can also display the preamble index in the transmitter label or tip text by selecting "Cells: Preamble index" from the Label or Tip Text Field Definition dialogue. To display the downlink or uplink permutation zone permbase allocation on the map: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. 5. Select "Discrete values" as the Display type and "Cells: DL zone permbase" or "Cells: UL zone permbase" as the Field. 6. Click OK. Transmitters will be displayed by the downlink or uplink permutation zone permbase. You can also display the permutation zone permbase in the transmitter label or tip text by selecting "Cells: DL zone permbase" and "Cells: UL zone permbase" from the Label or Tip Text Field Definition dialogue. For information on display options, see "Display Properties of Objects" on page 43.
12.3.5.3 Grouping Transmitters by Channels, Preamble Indexes, Zone PermBases You can group transmitters in the Network explorer by their frequency bands, channel numbers, or preamble indexes. To group transmitters by frequency bands, channel numbers, or preamble indexes: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available fields, scroll down to the Cells section. 6. Select the parameter you want to group transmitters by: • • • • •
Frequency band Channel number Preamble index DL zone permbase UL zone permbase
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 grouped by a certain parameter, select the parameter in the Group these fields in this order list and click transmitters will be grouped.
. The selected parameter is removed from the list of parameters on which the
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
to move it up to the desired position.
b. Select a parameter and click
to move it down to the desired position.
10. Click OK to save your changes and close the Group dialogue.
12.3.5.4 Analysing the Frequency Allocation Using Coverage Predictions You can create and compare preamble and traffic C/(I+N) coverage predictions before and after the automatic frequency allocation in order to analyse and compare the improvements brought about by the AFP. For more information on creating refer-
1239
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
ence signal C/(I+N) coverage predictions, see "Making a Coverage Prediction by C/(I+N) Level" on page 1205. For more information on comparing two coverage predictions, see "Comparing Coverage Predictions: Examples" on page 1196.
12.3.5.5 Checking the Consistency of the Preamble Index Plan Once you have completed allocating preamble indexes, you can verify whether the allocated preamble indexes respect the specified constraints and relations by performing an audit of the plan. The preamble index audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select AFP > Preamble Index Audit. The Preamble Index Audit dialogue appears. 4. In the Preamble Index Audit dialogue, select the allocation criteria that you want to verify: •
•
• •
•
•
•
Distance: If you select the Distance check box, Atoll will check for and list cells that do not respect the reuse distance defined in their properties. For cells that do not have a reuse distance defined in their properties, the value entered in this dialogue will be used for the audit. Neighbours: If you select the Neighbours check box, Atoll will check that no cell has the same preamble index as any of its neighbours, and that no two neighbours of a cell have the same preamble index. The report will list any cell that does have the same preamble index as one of its neighbours. Same cell permbase at a site: If you select the Same cell permbase at a site check box, Atoll will check for and list base stations whose cells have preamble indexes that correspond to different cell permbases. Segments of co-transmitter cells: If you select the Segments of co-transmitter cells check box and select Different, Atoll will check for and list co-transmitter cells that do not match the criterion, i.e., the co-transmitter cells with preamble indexes that correspond to the same segment numbers. If you select Same, Atoll will check for and list co-transmitter cells with preamble indexes that correspond to different segment numbers. Segments of co-site cells: If you select the Segments of co-site cells check box and select Different, Atoll will check for and list co-site cells with preamble indexes that do not match the criterion, i.e., the co-site cells with preamble indexes that correspond to the same segment numbers. If you select Same, Atoll will check for and list co-site cells with preamble indexes that correspond to the same segment numbers. Per-cell domain compliance: If you select the Per-cell domain compliance check box, Atoll will check if allocated preamble indexes belong to domains assigned to cells. The report will list any cells with preamble indexes that do not belong to domains assigned to the cell. Allocation domain: If you select the Allocation domain check box, Atoll will check whether the currently allocated preamble indexes are within the selected range. You can choose from Entire (0-113), Restricted (0-95), or Custom. If you select Custom, you can enter the preamble indexes not part of the domain in the Excluded resources box. 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").
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.
12.3.5.6 Displaying the Preamble Index Allocation Histogram You can use a histogram to analyse the use of allocated preamble indexes in a network. The histogram represents the preamble indexes as a function of the frequency of their use. To display the preamble index histogram: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select AFP > Preamble Index Distribution. The Distribution Histograms dialogue appears. Each bar represents a preamble index, its height depending on the frequency of its use. 4. Move the pointer over the histogram to display the frequency of use of each preamble index. The results are highlighted simultaneously in the Zoom on selected values list. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values.
12.4 Studying Network Capacity Interference is the major limiting factor in the performance of WiMAX networks. It has been recognised as the major bottleneck in network capacity and is often responsible for poor performance. Frequency reuse means that in a given coverage area there are several cells that use a given set of frequencies. The cells that use the same frequency are called co-channel cells,
1240
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
and the interference from users with the same channel in the other co-channel cells is called co-channel interference. Unlike thermal noise which can be overcome by increasing the signal-to-noise ratio (SNR), co-channel interference cannot be countered by simply increasing the carrier power of a transmitter. This is because an increase in carrier transmission power will increase the interference to neighbouring co-channel cells. To reduce co-channel interference, co-channel cells must be physically separated sufficiently by a distance, called the reuse distance. For a network with a limited number of frequency channels, a large reuse distance can guarantee a high QoS for the system, but the capacity will be decreased. Another type of interference in WiMAX networks is adjacent channel interference. Adjacent channel interference results from imperfect receiver filters which allow nearby frequencies to interfere with the used frequency channel. Adjacent channel interference can be minimised through careful filtering and channel assignment. In Atoll, a simulation is based on a realistic distribution of users at a given point in time. The distribution of users at a given moment is referred to as a snapshot. Based on this snapshot, Atoll calculates various network parameters such as the downlink and uplink traffic loads, the uplink noise rise values, the user throughputs, etc. Simulations are calculated in an iterative fashion. When several simulations are performed at the same time using the same traffic information, the distribution of users will be different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snapshot to another. To create snapshots, services and users must be modelled. As well, certain traffic information in the form of traffic maps or subscriber lists must be provided. Once services and users have been modelled and traffic maps and subscriber lists have been created, you can make simulations of the network traffic. In this section, the following are explained: • • • • • •
"Defining Multi-service Traffic Data" on page 1241. "Creating a Traffic Map" on page 1241. "Exporting a Traffic Map" on page 1251. "Working with a Subscriber Database" on page 1251. "Calculating and Displaying Traffic Simulations" on page 1255. "Making Coverage Predictions Using Simulation Results" on page 1269.
12.4.1 Defining Multi-service Traffic Data The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: •
•
• •
WiMAX radio bearers: Radio bearers are used by the network for carrying information. The WiMAX Radio Bearer table lists all the available radio bearers. You can create new radio bearers and modify existing ones by using the WiMAX Radio Bearer table. For information on defining radio bearers, see "Defining WiMAX Radio Bearers" on page 1306. 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 1200. Mobility types: In WiMAX, information about receiver mobility is important to determine the user’s radio conditions and throughputs. For information on modelling mobility types, see "Modelling Mobility Types" on page 1201. Terminals: In WiMAX, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a car’s on-board navigation device. For information on modelling terminals, see "Modelling Terminals" on page 1201.
12.4.2 Creating a Traffic Map The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atollprovides three types of traffic maps for WiMAX projects. • • •
Sector traffic map User profile traffic map User density traffic map (number of users per km2)
These maps can be used for different types of traffic data sources as follows: •
Sector traffic maps can be used if you have live traffic data from the OMC (Operation and Maintenance Centre). The OMC (Operations and Maintenance Centre) collects data from all cells in a network. This includes, for example, the number of users or the throughput in each cell and the traffic characteristics related to different services. Traffic is spread over the best server coverage area of each transmitter and each coverage area is assigned either the throughputs in the uplink and in the downlink or the number of users per activity status or the total number of users (all activity statuses). For more information, see "Creating a Sector Traffic Map" on page 1242.
1241
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
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 1245, "Importing a User Profile Environment Based Traffic Map" on page 1247 and "Creating a User Profile Environment Based Traffic Map" on page 1247.
•
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 "Creating User Density Traffic Maps (No. Users/km2)" on page 1248, "Importing a User Density Traffic Map" on page 1248, "Converting 2G Network Traffic" on page 1250 and "Exporting Cumulated Traffic" on page 1250.
12.4.2.1 Creating a Sector Traffic Map This section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands in the uplink and in the downlink or the number of users per activity status or the total number of users (all activity statuses). A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by Transmitter" on page 1187. To create a sector traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector traffic map. 5. Select the type of traffic information you want to input. You can choose between 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. You can also import a traffic map from a file by clicking the Import button. You can import AGD (Atoll Geographic Data) format files that you have exported from another Atoll document. 7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter. 8. Enter the data required in the Sector Traffic 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 Total number of users (all activity statuses), enter the number of connected users for each sector and for each listed service. If you have selected Number of users per activity status, enter the number of inactive users, the number of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each service. You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 82.
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: • •
1242
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.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
11. Click OK. Atoll creates the traffic map in the Traffic Maps folder. You can modify the sector traffic map after it has been created. To modify the sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 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 modified values. You can update the information, throughput demands and the number of users, on the map afterwards. You must first recalculate the coverage prediction by transmitter. For more information, see "Making a Coverage Prediction by Transmitter" on page 1187. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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 1250.
12.4.2.2 Creating a User Profile Traffic Map The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There may also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create traffic maps based on user profiles and environments. A user profile models the behaviour of different user categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for calls of the type "voice") or uplink and downlink volume (for calls of the type "data"). Environment classes are used to describe the distribution of users on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of users with the same profile per km²). The sections "Importing a User Profile Traffic Map" on page 1245, "Importing a User Profile Environment Based Traffic Map" on page 1247 and "Creating a User Profile Environment Based Traffic Map" on page 1247 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 1243. "Modelling Environments" on page 1244.
Modelling User Profiles You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user might be considered a business user during the day, with video conferencing and voice, but no
1243
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles: New Element Properties dialogue appears. 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 1200. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 1201. 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 webbrowsing service, a session starts when the user opens his browsing application and ends when he quits the browsing application. Between these two events, the user might be downloading web pages and other times he may not be using the application, or he might be browsing local files, but the session is still considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and not by the time. In order for all the services defined for a user profile to be taken into account during traffic scenario elaboration, the sum of activity probabilities must be lower than 1.
• • •
Duration (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 environment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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 environment. 7. In the row marked with the New row icon ( tion that this environment will describe:
1244
), set the following parameters for each user profile/mobility combina-
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
• • •
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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
For example: An area of 10 km² with a 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 want you can specify a percentage of indoor users for each clutter class. During a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss. 11. Click OK.
12.4.2.2.1
Importing a User Profile Traffic Map User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscribers⁄km, or polygons with a number of subscribers⁄km²) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile densities from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1247. 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 map’s properties dialogue appears. 11. Select the Traffic tab (see Figure 12.50). 12. Under Traffic fields, you can specify the user profiles to be considered, their mobility type (km⁄h), and their density. If the file you are 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.
1245
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.50: Traffic map properties dialogue - Traffic tab Define each of the following: •
•
•
User profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the Traffic Parameters folder of the Parameter tab, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points. When you import user profile or mobility information from the file, the values in the file must be exactly the same as the corresponding names in the Traffic Parameters folder in the Parameters explorer. If the imported user profile or mobility does not match, Atoll will display a warning.
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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
14. If you want, you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss. 15. Click OK to finish importing the traffic map.
1246
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.4.2.2.2
Importing a User Profile Environment Based Traffic Map Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1247. 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 map’s 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 Traffic Parameters in the Parameters explorer. For more information, see "Modelling Environments" on page 1244. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 43. 14. Click OK.
12.4.2.2.3
Creating a User Profile Environment Based Traffic Map Atollenables you to create a user profile environment traffic map based on by drawing it in the map window. To draw a traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 12.51).
Draw Map
Delete Map
Figure 12.51: 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.
1247
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
12.4.2.2.4
© Forsk 2012
Displaying Statistics on a User Profile Environment Traffic Map You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears. The Statistics window lists the surface (Si in km²) and the percentage of surface (% of i) for each environment class "i" S
i - × 100 within the focus zone. The percentage of surface is given by: % of i = -------------
Sk k
You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.
12.4.2.3 Creating User Density Traffic Maps (No. Users/km2) User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit surface, i.e., the density of users, as input. This can be either the density of users per activity status or the total density of users (all activity statuses). In this section, the following ways of creating a user density traffic map are explained: • •
"Importing a User Density Traffic Map" on page 1248 "Creating a User Density Traffic Map" on page 1249.
User density traffic maps can be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. For more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 1250.
12.4.2.3.1
Importing a User Density Traffic Map The user density traffic map defines the density of users per pixel. For a traffic density of X users per km², Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined in the Traffic tab of the traffic map’s properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select 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.
1248
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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 1247. 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 map’s 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 percentage must equal 100. 13. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 14. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 15. Under Clutter distribution, enter for each clutter class the percentage of indoor users. 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. 16. Click OK. Atoll creates the traffic map in the Traffic Maps folder.
12.4.2.3.2
Creating a User Density Traffic Map Atollenables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User density traffic map (Number of users per km2). 5. Select the type of traffic information you input. You can choose from: • • • • •
All activity statuses: Select All activity statuses if the map you are importing provides a density of users with any activity status. Active in uplink: Select Active in uplink if the map you are importing provides a density of users active in the uplink only. Active in downlink: Select Active in downlink if the map you are importing provides a density of users active in the downlink only. Active in uplink and downlink: Select Active in uplink and downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.
6. Click the Create button. The traffic map’s 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 Maps folder. 13. Right-click the traffic map. The context menu appears. 14. Select Edit from the context menu.
1249
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
15. Use the tools available in the Vector Editor toolbar in order to draw contours. For more information on how to edit contours, see "Editing Polygons, Lines, and Points" on page 61. 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.
12.4.2.3.3
Creating User Density Traffic Maps from Sector Traffic Maps You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. To create user density traffic maps from a sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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.
12.4.2.4 Converting 2G Network Traffic Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km² for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as user density traffic maps into your WiMAX document. These maps can then be used in traffic simulations like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 1250, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1248. To import a 2G traffic map into a WiMAX document: 1. Create a sector traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 438. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 1250. 3. Import the traffic exported in step 2 to your WiMAX document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1248.
12.4.2.5 Exporting Cumulated Traffic Atoll allows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user densities. The cumulated traffic is exported in 32-bit BIL, ArcView© Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Select the Geo explorer. 2. Right-click the Traffic Maps 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: • •
1250
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.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
7. Define a Resolution in metres. The resolution must be an integer and the minimum resolution allowed is 1. 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. 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.
12.4.3 Exporting a Traffic Map To export a traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save. If you are exporting a raster traffic map, you have to define: •
The Export region: • • •
•
Entire project area: Saves the entire traffic map. Only pending changes: Saves only the modifications made to the map. Computation zone: Saves only the part of the traffic map inside the computation zone.
An export Resolution.
12.4.4 Working with a Subscriber Database The WiMAX module includes a subscriber database for modelling fixed user distributions in a network. The subscriber database consists of subscriber lists. You can create subscriber lists in Atoll by adding subscribers to the list using the mouse, or by copying data from any other source such as a spreadsheet. You can also directly import subscriber lists in Atoll from text (TXT) and comma separated value (CSV) files. Atoll can allocate reference or serving base stations (cells) to subscribers. You can also have the subscriber antenna oriented towards its serving cell to decrease interference. The automatic server allocation performs a number of calculations on the subscriber locations. In this section, the following are explained: • •
"Creating a Subscriber List" on page 1251. "Performing Calculations on Subscriber Lists" on page 1255.
12.4.4.1 Creating a Subscriber List You create subscribers in Atoll in two steps. First, you create a subscriber list, and then you add subscribers to the list. You can add subscribers to the list directly on the map using the mouse. For more information, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 1254.
1251
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
If you need to create a large number of subscribers, Atoll allows you to import them from another Atoll document or from an external source. For more information, see "Importing a Subscriber List" on page 1254. To create a subscriber list: 1. Select the Network explorer. 2. Right-click the Subscribers folder. The context menu appears. 3. Select New List from the context menu. The Subscriber List N Properties dialogue appears (see Figure 12.52), where N is an incremental digit.
Figure 12.52: 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 93. Filter: Click the Filter button to filter the data in the subscriber list. For information on filtering, see "Filtering Data" on page 95.
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 43. 6. Click OK. Atoll creates a new subscriber list. The following parameters are available by default in a new subscriber list: • • • • •
•
• • • •
1252
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 subscriber’s location is always fixed. Height: The altitude of the subscriber antenna with respect to the ground (DTM). 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 1243. Terminal: The default terminal (CPE) is the user equipment with an antenna, reception 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. Clutter: The name of the clutter class where the subscriber is located. This is a non-editable field whose contents are automatically updated. Indoor: This field indicates whether the subscriber is indoor or outdoor.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
•
• •
•
• • • • • • • • • • • •
• •
•
• • • • • •
• • •
•
Best server: 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 highest layer is selected as the reference cell. Distance: The distance of the subscriber from its serving base station. This is a non-editable field whose contents are automatically updated. 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. 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. 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 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. 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. 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): The downlink permutation zone allocated to the subscriber. BLER (DL): The Block Error Rate read from the subscriber’s terminal type’s reception 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. 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. 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. 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): The uplink permutation zone allocated to the subscriber. BLER (UL): The Block Error Rate read from the reference cell’s reception 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 subscriber’s 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.
1253
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
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 1255. For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations on Subscriber Lists" on page 1255. 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 1254. You can open the subscriber list table containing all the subscribers and their parameters. To open the subscriber list table: 1. Select the Network explorer. 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 69.
12.4.4.1.1
Adding Subscribers to a Subscriber List Using the Mouse You can use the mouse to add subscribers to an existing subscriber list. Atoll applies the default parameters defined in the Table tab of the subscriber list Properties dialogue to all the subscribers you add to the list. For more information on the Table tab, see "Creating a Subscriber List" on page 1251. To add subscribers to a subscriber list using the mouse: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Subscribers folder. 3. Right-click the subscriber list to which you want to add subscribers. The context menu appears. 4. Select Add Subscribers from the context menu. The pointer changes to subscriber addition mode (
).
5. Move the mouse over the map window, and click once to add each subscriber. 6. Press ESC or click the normal pointer button (
) to finish adding subscribers.
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 49.
12.4.4.1.2
Importing a Subscriber List You can also import subscriber lists from text files (TXT) or comma separated value files (CSV), including Microsoft Excel files exported in CSV format. To import a subscriber list: 1. Select the Network explorer. 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 more information on importing table data, see "Importing Tables from Text Files" on page 82. You can also export subscriber lists. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80.
1254
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.4.4.1.3
Selecting the Columns to Display in the Subscriber Lists You can select the columns to display in the Properties dialogue of the Subscribers folder from those in "Creating a Subscriber List" on page 1251. To select the columns to display in subscriber lists: 1. Select the Network explorer. 2. Right-click the Subscribers folder. The context menu appears. 3. Select Properties from the context menu. The Subscribers Properties dialogue appears. 4. Click the Column Selection tab. 5. Under Configuration, you can Load an existing configuration of the columns to display, Save the current settings in an existing configuration file, or Save as a new configuration file. 6. Select the columns you want to display: a. Select the column in the Available columns list and click b. Select a column in the Columns to display list and click
to move it to the Columns to display list. to move it to the Available columns list.
c. Change the order of the columns by selecting a column and clicking
or
to move it up or down in the list.
7. Click OK to close the Subscribers Properties dialogue.
12.4.4.2 Performing Calculations on Subscriber Lists You can perform calculations on subscriber lists without having to carry out simulations first. Atoll does not base calculations performed on subscriber lists on the path loss matrices calculated for transmitters. This is because the path loss matrices are calculated for a given receiver height (1.5 m by default) defined on the Calculation Parameters tab of the Properties dialogue of the Network Settings folder, but each subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates the path loss, received power, and other output for each subscriber when you perform calculations based on subscribers. Atoll includes an automatic server allocation which performs the following for all the subscribers in a list. To perform calculations on a subscriber list: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Subscribers folder. 3. Right-click the subscriber list on which you want to perform calculations. The context menu appears. 4. Select Calculations > Automatic Server Allocation from the context menu. The Automatic Server Allocation dialogue appears. If you want the calculations to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. The shadowing margin for signal level calculations is based on the model standard deviation, and the shadowing margin for C/(I+N) calculations is based on the C/I standard deviation. 5. Click Calculate. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. 6. Once the calculations are finished, click Close to close the Event Viewer. 7. Click Commit to store the results in the subscriber list. For the list of results that are available after the calculations, see "Creating a Subscriber List" on page 1251.
12.4.5 Calculating and Displaying Traffic Simulations To plan and optimise WiMAX networks, you will need to study the network capacity and to study the network coverage taking into account realistic user distribution and traffic demand scenarios. In Atoll, a simulation corresponds to a given distribution of WiMAX users. It is a snapshot of a WiMAX network. The principal outputs of a simulation are a geographic user distribution with a certain traffic demand, resources allocated to each user of this distribution, and cell loads. You can create groups for one or more simulations and carry out as many simulations as required. A new simulation for each different traffic scenario can help visualise the network’s response to different traffic demands. Each user distribution (each simulation generates a new user distribution) is a Poisson distribution of the number of active users. Therefore, each simulation may have a varying number of users accessing the network. WiMAX simulation results can be displayed on the map as well as listed in tabular form for analysis. Simulation outputs include results related to sites, cells, and mobiles.
1255
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
WiMAX simulation results can be stored in the cells table and used in C/(I+N) based coverage predictions. In this section, the following are explained: • • • • • •
"WiMAX Traffic Simulation Algorithm" on page 1256. "Creating Simulations" on page 1257. "Displaying the Traffic Distribution on the Map" on page 1259. "Displaying the Results of a Single Simulation" on page 1262. "Updating Cell Load Values With Simulation Results" on page 1268. "Estimating a Traffic Increase" on page 1269.
12.4.5.1 WiMAX Traffic Simulation Algorithm Figure 12.53 shows the WiMAX simulation algorithm. The simulation process in WiMAX consists of the following steps: 1. Mobile Generation and Distribution Simulations require traffic data, such as traffic maps (raster, vector, or live traffic data) and subscriber lists. Atoll generates a user distribution for each simulation using a Monte Carlo algorithm. This user distribution is based on the traffic data input and is weighted by a Poisson distribution. Each mobile generated during the simulations is assigned a service, a mobility type, and a terminal according to the user profile assigned to it. A transmission status is determined according to the activity probabilities. The transmission status is an important output of the simulation as it has a direct impact on the next step of the simulation process, i.e., the radio resource management (RRM), and has an impact on the interference level in the network. The geographical location of each mobile is determined randomly for the mobiles generated based on the traffic data from traffic maps. The mobiles generated based on the traffic data from subscriber lists are located on the subscriber locations.
Figure 12.53: WiMAX simulation algorithm 2. Best Server Determination
1256
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Atoll determines the best server for each mobile based on the preamble signal level or preamble C/(I+N) in the downlink. For multi-cell transmitters, the best serving transmitter is determined according to the received preamble signal level or preamble C/(I+N) from the cell with the highest preamble power. If more than one cell covers the mobile, the one with the highest layer is selected as the serving (reference) cell. 3. Downlink Calculations 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. Segmentation is performed if the frame configuration, selected for a cell, supports segmentation. Interference calculation is based on the probabilities of collision between segments. 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. 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 cell’s 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.
12.4.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. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name for this simulation or group of simulations.
1257
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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 in the Network explorer. 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 use the maximum uplink traffic load as defined in the properties for each cell, click the button ( Defined per cell.
) beside the box and select
7. You can enter some Comments if you want. 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 1241. 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: •
Generator initialisation: Enter an integer as the generator initialisation value. If you enter "0," the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value. Using the same generated user and shadowing error distribution for several simulations can be useful when you want to compare the results of several simulations where only one parameter changes.
•
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.
10. Once you have defined the simulation, you can calculate it immediately or you can save it to calculate it later: • •
Calculate: Click Calculate to save the defined simulation and calculate it immediately. OK: Click OK to save the defined simulation without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
All simulations created at the same time are grouped together in a folder in the Network explorer. 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 1269.
1258
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.4.5.3 Displaying the Traffic Distribution on the Map Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to activity status, service, reference cell, or throughputs. You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 43. In this section are the following examples of traffic distribution: • • • • • •
"Displaying the Traffic Distribution by Activity Status" on page 1259. "Displaying the Traffic Distribution by Connection Status" on page 1259. "Displaying the Traffic Distribution by Service" on page 1260. "Displaying the Traffic Distribution by Throughput" on page 1260. "Displaying the Traffic Distribution by Uplink Transmission Power" on page 1261. "Displaying Traffic Simulation Results Using Tip Text" on page 1261. 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 Windows" on page 38.
12.4.5.3.1
Displaying the Traffic Distribution by Activity Status In this example, the traffic distribution is displayed by the activity status. To display the traffic distribution by the activity status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Activity status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 12.54).
Figure 12.54: Displaying the traffic distribution by activity status
12.4.5.3.2
Displaying the Traffic Distribution by Connection Status In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Connection status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 12.55).
1259
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.55: Displaying the traffic distribution by connection status
12.4.5.3.3
Displaying the Traffic Distribution by Service In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 12.56).
Figure 12.56: Displaying the traffic distribution by service
12.4.5.3.4
Displaying the Traffic Distribution by Throughput In this example, the traffic distribution is displayed by throughput. To display the traffic distribution by throughput: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value intervals" as the Display type and one of the following throughput types as the Field:
1260
•
In the downlink: • Peak MAC, effective MAC, or application channel throughput • Peak MAC, effective MAC, or application cell capacity • Peak MAC, effective MAC, or application user throughput
•
In the uplink: • Peak MAC, effective MAC, or application channel throughput • Peak MAC, effective MAC, or application cell capacity • Peak MAC, effective MAC, or application allocated bandwidth throughput
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
Peak MAC, effective MAC, or application user throughput
5. Click OK. The traffic distribution is now displayed by throughput (see Figure 12.57).
Figure 12.57: Displaying the traffic distribution by throughput
12.4.5.3.5
Displaying the Traffic Distribution by Uplink Transmission Power In this example, the traffic distribution is displayed by the uplink transmission power of the mobiles. You can analyse the effect of the uplink power control. To display the traffic distribution by uplink transmission power: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value intervals" as the Display type and "Transmission power (UL) (dBm)" as the Field. 5. Click OK. The traffic distribution is now displayed by uplink transmission power (see Figure 12.58).
Figure 12.58: Displaying the traffic distribution by uplink transmission power
12.4.5.3.6
Displaying Traffic Simulation Results Using Tip Text You can display information by placing the pointer over a mobile generated during a simulation to read the information displayed in the tip text. The information displayed is defined by the settings you made on the Display tab. For information on defining the tip text, see "Defining the Object Type Tip Text" on page 46. To display simulation results in the form of tip text: •
In the map window, place the pointer over the user that you want more information on. After a brief pause, the tip text appears with the information defined in the Display tab of the Simulations folder properties (see Figure 12.59).
1261
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.59: Displaying the traffic simulation results using tip text
12.4.5.4 Displaying the Results of a Single Simulation After you have created a simulation, as explained in "Creating Simulations" on page 1257, you can display the results. To access the results of a single simulation: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. 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.
Results: Under Results, is data on the connection results: • • •
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: • • • • • • • •
1262
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected in the downlink in all the cells of the site. Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink in all the cells of the site. Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in the downlink in all the cells of the site. Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected in the uplink in all the cells of the site. Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink in all the cells of the site. Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in the uplink in all the cells of the site. Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site. Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink, or downlink and uplink both.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
• • • • • • • • • • • • • • • •
Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink both. Number of connected users (DL): The number of users connected to any cell of the site in downlink. Number of connected users (UL): The number of users connected to any cell of the site in uplink. No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the downlink in all the cells of the site. Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the downlink in all the cells of the site. Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site. Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the uplink in all the cells of the site. Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the uplink in all the cells of the site. Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site. Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site.
The Cells tab: 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. Segmentation usage (DL) (%): The percentage of the downlink traffic load that corresponds to the first downlink PUSC zone, if it is segmented. Traffic load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation. UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation. Segmented zone UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation for the segmented uplink permutation zone. Angular distributions of interference (AAS): The simulation results generated for transmitters using a smart antenna. The results stored in this field are the angular distributions of the downlink traffic power spectral density and the uplink noise rise. You can make the display of the downlink results diagram take into account the effect of the antenna pattern of the single element. For more information, see the Administrator Manual. AAS usage (DL) (%): The percentage of the downlink traffic load that corresponds to the traffic carried by the smart antennas. AAS usage (UL) (%): The percentage of the uplink traffic load that corresponds to the traffic carried by the smart antennas. MU-MIMO capacity gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected in the downlink. Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink. Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in the downlink. Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected in the uplink. Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink. Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in the uplink. Connection success rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both. Number of connected users (DL): The number of users connected to the cell in downlink. Number of connected users (UL): The number of users connected to the cell in uplink.
1263
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
• • • • • • • • • • • • •
© Forsk 2012
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." Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the downlink. Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the downlink. Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink. Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the uplink. Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the uplink. Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink. Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with respect to the number of users covered by the cell.
The Mobiles tab: The Mobiles tab contains the following information: • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • •
1264
X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second random trial). Height: The height of the user terminal (antenna). User profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal and the user profile. Subscriber ID: The ID of the user if the user is generated from a subscriber list and not from a traffic map. Subscriber list: The subscriber list of the user if the user is generated from a subscriber list and not from a traffic map. Service: The service assigned during the first random trial during the generation of the user distribution. Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal and the user profile. Mobility: The mobility type assigned during the first random trial during the generation of the user distribution. Activity status: The assigned activity status. It can be Active DL, Active UL, Active DL+UL, or Inactive. Connection status: The connection status indicates whether the user is connected or rejected at the end of the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection cause is given. Clutter class: The code of the clutter class where the user is located. Indoor: This field indicates whether indoor losses have been added or not. Best server: The best server of the user. Reference cell: The reference cell of the serving transmitter of the subscriber. Azimuth: The orientation of the user’s terminal antenna in the horizontal plane. Azimuth is always considered with respect to the North. Atoll points the user antenna towards its best server. Downtilt: The orientation of the user’s terminal antenna in the vertical plane. Mechanical downtilt is positive when it is downwards and negative when upwards. Atoll points the user antenna towards its best server. Path loss (dB): The path loss from the best server calculated for the user. 2nd best server: The second best server of the user. 2nd best server path loss (dB): The path loss from the second best server calculated for the user. 3rd best server: The third best server of the user. 3rd best server path loss (dB): The path loss from the third best server calculated for the user. Received preamble power (DL) (dBm): The preamble signal level received at the user location in the downlink. Received traffic power (DL) (dBm): The traffic signal level received at the user location in the downlink. Received pilot power (DL) (dBm): The pilot signal level received at the user location in the downlink. Preamble C/(I+N) (DL) (dB): The preamble C/(I+N) at the user location in the downlink. Traffic C/(I+N) (DL) (dB): The traffic C/(I+N) at the user location in the downlink. Pilot C/(I+N) (DL) (dB): The pilot C/(I+N) at the user location in the downlink. Preamble total noise (I+N) (DL) (dBm): The sum of the preamble interference and noise experienced at the user location in the downlink. Traffic total noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced at the user location in the downlink. Bearer (DL): The highest WiMAX bearer available for the traffic C/(I+N) level at the user location in the downlink.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
• • • • •
•
• • •
• • • • • • • • • • •
•
• •
•
• • •
Permutation zone (DL): The downlink permutation zone allocated to the user. BLER (DL): The Block Error Rate read from the user terminal’s reception equipment for the traffic C/(I+N) level at the user location in the downlink. Diversity mode (DL): The diversity mode supported by the cell or permutation zone in downlink. Peak MAC channel throughput (DL) (kbps): The maximum MAC channel throughput attainable using the highest bearer available at the user location in the downlink. Effective MAC channel throughput (DL) (kbps): The effective MAC channel throughput attainable using the highest bearer available at the user location in the downlink. It is calculated from the peak MAC throughput and the BLER. Application channel throughput (DL) (kbps): The application throughput is the net throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput scaling factor of the service and the throughput offset. Peak MAC user throughput (DL) (kbps): The maximum MAC user throughput attainable using the highest bearer available at the user location in the downlink. Effective MAC user throughput (DL) (kbps): The effective MAC user throughput attainable using the highest bearer available at the user location in the downlink. It is calculated from the peak MAC throughput and the BLER. Application user throughput (DL) (kbps): The application throughput is the net throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput scaling factor of the service and the throughput offset. Received power (UL) (dBm): The signal level received at the serving transmitter from the user terminal in the uplink. C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the user in the uplink. Total noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter of the user in the uplink. Bearer (UL): The highest WiMAX bearer available for the C/(I+N) level at the serving transmitter of the user in the uplink. Permutation zone (UL): The uplink permutation zone allocated to the user. BLER (UL): The Block Error Rate read from the reference cell’s reception equipment for the C/(I+N) level at the serving transmitter of the user in the uplink. Diversity mode (UL): The diversity mode supported by the cell or permutation zone in uplink. Transmission power (UL) (dBm): The transmission power of the user terminal after power control in the uplink. Allocated bandwidth (UL) (No. of Subchannels): The bandwidth allocated to the user in terms of the number of subchannels allocated in the uplink after subchannelisation. 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. •
•
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 network settings: •
Frame duration
1265
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
• • • • • • • •
Cyclic prefix ratio Uplink and downlink fixed overheads Uplink and downlink variable overheads TDD-specific parameters: DL:UL ratio, TTG, and RTG Uplink power control margin Serving cell layer selection method Adaptive MIMO switching criterion
The input parameters specified when creating the simulation: • • • • • •
•
© Forsk 2012
Maximum number of iterations Global scaling factor Generator initialisation value Uplink and downlink traffic load convergence thresholds Uplink noise rise convergence threshold Names of the traffic maps and subscriber lists used.
The parameters related to the clutter classes, including the default values.
12.4.5.5 Displaying the Average Results of a Group of Simulations After you have created a group of simulations, as explained in "Creating Simulations" on page 1257, you can display the average results of the group. If you want to display the results of a single simulation in a group, see "Displaying the Results of a Single Simulation" on page 1262. To display the averaged results of a group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Right-click the group of simulations whose results you want to display. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the simulation results. Other tabs in the simulation properties dialogue contain the averaged results for all simulations of the group. The Statistics tab: The Statistics tab contains the following sections: •
Request: Under Request is data on the connection requests: •
• • •
Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; radio resource allocation has not yet finished. The result depends on the traffic description and traffic input. During the first random trial, each user is assigned a service and an activity status. The number of users per activity status and the UL and DL throughput demands that all users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and UL and DL throughput demands) is given.
Results: Under Results is data on the connection results: • • •
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 average information per site: • • • • • • • •
1266
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected in the downlink in all the cells of the site. Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink in all the cells of the site. Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in the downlink in all the cells of the site. Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected in the uplink in all the cells of the site. Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink in all the cells of the site. Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in the uplink in all the cells of the site. Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site. Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink, or downlink and uplink both.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
• • • • • • • • • • • • • • • •
Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink both. Number of connected users (DL): The number of users connected to any cell of the site in downlink. Number of connected users (UL): The number of users connected to any cell of the site in uplink. No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the downlink in all the cells of the site. Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the downlink in all the cells of the site. Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site. Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the uplink in all the cells of the site. Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the uplink in all the cells of the site. Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site. Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site.
The Cells (Average) tab: The Cells (Average) tab contains the following average information per cell: • • • • • •
• • • • • • • • • • • • • •
Traffic load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation. Segmentation usage (DL) (%): The percentage of the downlink traffic load that corresponds to the first downlink PUSC zone, if it is segmented. Traffic load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation. UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation. Segmented zone UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation for the segmented uplink permutation zone. Angular distributions of interference (AAS): The simulation results generated for transmitters using a smart antenna. The results stored in this field are the angular distributions of the downlink traffic power spectral density and the uplink noise rise. You can make the display of the downlink results diagram take into account the effect of the antenna pattern of the single element. For more information, see the Administrator Manual. AAS usage (DL) (%): The percentage of the downlink traffic load that corresponds to the traffic carried by the smart antennas. AAS usage (UL) (%): The percentage of the uplink traffic load that corresponds to the traffic carried by the smart antennas. MU-MIMO capacity gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected in the downlink. Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink. Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in the downlink. Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected in the uplink. Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink. Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in the uplink. Connection success rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both. Number of connected users (DL): The number of users connected to the cell in downlink. Number of connected users (UL): The number of users connected to the cell in uplink.
1267
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
• • • • • • • • • • • • •
© Forsk 2012
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." Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the downlink. Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the downlink. Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink. Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the uplink. Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the uplink. Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink. Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with respect to the number of users covered by the cell.
The Initial Conditions tab: The Initial Conditions tab contains the following information: •
The global network settings: • • • • • • • •
•
The input parameters specified when creating the simulation: • • • • • •
•
Frame duration Cyclic prefix ratio Uplink and downlink fixed overheads Uplink and downlink variable overheads TDD-specific parameters: DL:UL ratio, TTG, and RTG Uplink power control margin Serving cell layer selection method Adaptive MIMO switching criterion Maximum number of iterations Global scaling factor Generator initialisation value Uplink and downlink traffic load convergence thresholds Uplink noise rise convergence threshold Names of the traffic maps and subscriber lists used.
The parameters related to the clutter classes, including the default values.
12.4.5.6 Updating Cell Load Values With Simulation Results After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 1257, you can update cell load values for each cell with the results calculated during the simulation. To update cell values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Select the Network explorer. b. Click the Expand button ( ) to expand the Simulations folder. c. Right-click the group of simulations whose results you want to access. d. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain average simulation results for all simulations.
1268
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
To display the results for a single simulation: a. Select the Network explorer. b. Click the Expand button ( ) to expand the Simulations folder. c. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. 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) (%) Segmentation usage (DL) (%) Traffic load (UL) (%) UL noise rise (dB) Segmented zone UL noise rise (dB) Angular distributions of interference (AAS) AAS usage (DL) (%) MU-MIMO capacity gain (UL)
12.4.5.7 Estimating a Traffic Increase When you create simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increase of traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a simulation or group of simulations as described in "Creating Simulations" on page 1257. 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).
12.4.6 Making Coverage Predictions Using Simulation Results In Atoll, you can analyse simulation results by making coverage predictions using simulation results. In a coverage prediction each pixel is considered as a non-interfering probe user with a defined terminal, mobility, and service. The analyses can be based on a single simulation or on an averaged group of simulations. When no simulations are available, Atoll uses the downlink traffic load, uplink noise rise, and any angular distribution of interference stored for each cell to make coverage predictions. For information on cell properties, see "Cell Description" on page 1155; for information on modifying cell properties, see "Creating or Modifying a Cell" on page 1159. Once you have made simulations, Atoll can use the information from the simulations instead of the defined parameters in the cell properties to make coverage predictions. For each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a group of simulations, which uses the average of all simulations in the group. The coverage predictions that can use simulation results are: • • • • •
Coverage by C/(I+N) Level: For information on making a downlink or uplink coverage by C/(I+N) level, see "Making a Coverage Prediction by C/(I+N) Level" on page 1205. Service Area Analysis: For information on making a downlink or uplink service area analysis, see "Making a Downlink or Uplink Service Area Analysis" on page 1208. Effective Service Area Analysis: For information on making an effective service area analysis, see "Making a Downlink or Uplink Service Area Analysis" on page 1208. Coverage by Throughput: For information on making a downlink or uplink coverage by throughput, see "Making a Coverage Prediction by Throughput" on page 1211. Coverage by Quality Indicator: For information on making a downlink or uplink coverage by quality indicator, see "Making a Coverage Prediction by Quality Indicator" on page 1214.
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.
1269
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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.
12.5 Optimising Network Parameters Using the ACP Atoll Automatic Cell Planning (ACP) enables radio engineers designing WiMAX networks to automatically calculate the optimal network settings in terms of network coverage and quality. The ACP can also be used to add sites from a list of candidate sites or to remove unnecessary sites or sectors. Atoll ACP can also be used in co-planning projects where networks using different radio access technologies must be taken into consideration when calculating the optimal network settings. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and cell pilot power. ACP can also be used during the initial planning stage of a WiMAX network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP not only takes transmitters into account in optimisations but also any repeaters and remote antennas. Atoll ACP can also be used to measure and optimise the EMF exposure created by the network. This permits the optimisation of power and antenna settings to reduce excessive EMF exposure in existing networks and optimal site selection for new transmitters. ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have defined the objectives and the network parameters to be optimised, Atoll ACP uses an efficient global search algorithm to test many network configurations and propose the reconfigurations that best meet the objectives. The ACP presents the changes ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the suggested changes. The ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 6: Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how you can view the results of an optimisation. In this section, only the concepts specific to WiMAX networks are explained: • • •
"WiMAX Optimisation Objectives" on page 1270 "WiMAX Quality Parameters" on page 1270 "The WiMAX Quality Analysis Predictions" on page 1272.
12.5.1 WiMAX Optimisation Objectives ACP optimises the network using user-defined objectives to evaluate the quality of the network reconfiguration. The objectives are dependent on the technology used by the project and are consistent with the corresponding coverage predictions in Atoll. In projects using WiMAX, either alone, or in a co-planning or multi-RAT project, the following objectives are used: • •
Coverage Preamble CINR
For information on setting objective parameters, see "Setting Objective Parameters" on page 242 of Chapter 6: Automatic Cell Planning.
12.5.2 WiMAX Quality Parameters When you create an optimisation setup, you define how the ACP evaluates the objectives. The quality parameters are technology dependent. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own predictions. However, if you have saved the display options of an ACP prediction 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. In projects using WiMAX, either alone, or in a co-planning project, the following quality parameters are used: • • • • •
Overlap Signal level Preamble C Preamble C⁄N Preamble CINR
To define the quality parameters for WiMAX: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233 in Chapter 6: Automatic Cell Planning. 2. Click the Objectives tab.
1270
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
3. Under Criteria, in the left-hand pane, under Parameters, expand WiMAX. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own predictions. However, if you have saved the display options of an ACP prediction 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 prediction display options as the default, see "Changing the Display Properties of ACP Predictions" on page 284. For information on saving a configuration file, see "Configuring Default Settings" on page 231. If you want to use a coverage prediction, the coverage prediction must have already been calculated.
4. Click Overlap. In the right-hand pane, you can define how the ACP will evaluate overlapping coverage. 5. Select what the objective evaluation will be based on from the Base prediction settings on list: • •
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, define an Overlap threshold margin and a Minimum signal level. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate overlapping coverage using the same parameters that were used to calculate the coverage prediction.
6. Under WiMAX in the left-hand pane under Parameters, select Signal Level. 7. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box 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. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate the signal level using the same parameters that were used to calculate the coverage prediction.
8. Under WiMAX in the left-hand pane under Parameters, select Preamble C. 9. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box 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. Additionally you must define the Service and Terminal used to evaluate the preamble C. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate the preamble C using the same parameters that were used to calculate the coverage prediction.
10. Under WiMAX in the left-hand pane under Parameters, select Preamble C⁄N. 11. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box 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. Additionally you must define the Service and Terminal used to evaluate the preamble C⁄N. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate preamble C⁄N using the same parameters that were used to calculate the coverage prediction.
12. Under WiMAX in the left-hand pane under Parameters, select Preamble CINR. 13. Select what the objective evaluation will be based on from the Base prediction settings on list: •
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box 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 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). Under Calculation Method, define how the preamble CINR will be calculated. Select Using frequency plan if you want the frequency plan to be taken into consideration when calculating the preamble CINR. If you select Using frequency plan, you can additionally opt to apply segmentation by selecting the Apply segmentation check box. Select Ignoring frequency plan & segmentation if you want the preamble CINR to be calculated without taking the frequency plan and segmentation into consideration.
1271
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate the preamble CINR using the same parameters that were used to calculate the coverage prediction.
12.5.3 The WiMAX Quality Analysis Predictions The quality analysis predictions enable you to display the signal quality predictions in the Atoll map window. These predictions are the same as those displayed on the Quality tab of the optimisation’s Properties dialogue. The quality analysis predictions are the equivalent of predictions created by different Atoll coverage predictions: • •
The preamble coverage predictions correspond to the Atoll coverage by C⁄I level in WiMAX. For more information, see "Making a Coverage Prediction by C/(I+N) Level" on page 1205. The overlapping zones predictions correspond to the Atoll overlapping zones coverage prediction. For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 1188.
Making these predictions available within ACP enables you to quickly validate the optimisation results without having to commit the results and then calculate a coverage prediction in Atoll. The ACP predictions display results very similar to those that Atoll would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before basing any decision to commit the optimisation results on the predictions produced by ACP, you should keep the following recommendations in mind: • • • •
You should verify the results with a different Atoll coverage prediction, such as the overlapping zones prediction. ACP generated predictions are generated using the entire set of proposed changes. They do not take into account the change subset defined on the Change Details tab. Multiple carriers are not supported by ACP; the predictions are only provided for the requested carrier. Even after committing the optimisation results, differences can remain between the ACP predictions and the predictions resulting from Atoll coverage predictions.
You can view the exact preamble CINR value on any pixel by letting the pointer rest over the pixel. The preamble CINR value is then displayed in a tip text. For the overlapping zones prediction, you can set the best server threshold on the User Preferences tab of the ACP Properties dialogue (see "Defining the Storage Location of ACP Settings" on page 230) or by setting the CellOverlap parameter in the acp.ini file. For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network state, and a prediction showing the changes between the initial and final state.
12.6 Verifying Network Capacity An important step in the process of creating a WiMAX network is verifying the capacity of the network. This is done using measurements of the strength of the preamble and traffic signals and C/(I+N) in different locations within the area covered by the network. This collection of measurements is called drive test data. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: • • • • • • •
"Importing a Drive Test Data Path" on page 1272 "Displaying Drive Test Data" on page 1275 "Defining the Display of a Drive Test Data Path" on page 1275 "Network Verification" on page 1276 "Exporting a Drive Test Data Path" on page 1282 "Extracting CW Measurements from Drive Test Data" on page 1282 "Printing and Exporting the Drive Test Data Window" on page 1282.
12.6.1 Importing a Drive Test Data Path In Atoll, you can analyse networks by importing drive test data in the form of ASCII text files (with tabs, commas, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: • •
1272
The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells). In WiMAX networks, a cell can be identified by its BSID (6-byte MAC address) or its preamble index. Therefore, you must indicate during the import process which column contains the BSID or the preamble indexes of cells.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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. Select the Network explorer. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the file or files you want to open. You can import one or several files. If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing Shift and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import. 5. Click Open. The Import of Measurement Files dialogue appears. Files with the extension PLN, as well as some FMT files (created with old versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue. 6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Import configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Import configuration, select an import configuration from the Configuration list. b. Continue with step 10. •
•
When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. If several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters: • • •
Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement conditions, • •
Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button (
) and select the coordinate system used in the drive test data file. Atoll
will then convert the data imported to the coordinate system used in the Atoll document. 8. Click the Setup tab (see Figure 12.60).
1273
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.60: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st measurement row, select the data Separator, and select the Decimal symbol used in the file. b. Click the Setup button to link file columns and internal Atoll fields. The Drive Test Data Setup dialogue appears. c. Under Measurement point position, select the columns in the imported file that give the X-coordinates and the Y-coordinates of each point in the drive test data file. You can also identify the columns containing the XY coordinates of each point in the drive test data file by selecting them from the Field row of the table on the Setup tab
d. If you are importing data using preamble indexes as cell identifiers: i.
Select By preamble index under Transmitter identification.
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. e. If you are importing data using BSID as cell identifiers: i.
Select By cell ID under Transmitter identification.
ii. 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.
1274
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
•
If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Setup dialogue, Atoll should recognise all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "". Columns marked with "" 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 want to save the definition of the data structure so that you can use it again, you can save it as an import configuration: a. On the Setup tab, under Import configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll’s installation folder. In case you cannot write into that folder, you can click Browse to choose a different location. c. Enter a Configuration name and an Extension of the files that this import configuration will describe (for example, "*.txt"). d. Click OK. Atoll will now select this import configuration automatically every time you import a drive test data path file with the selected extension. If you import a file with the same structure but a different extension, you can select this import configuration from the Import configuration list. • •
•
You do not have to complete the import procedure to save the import configuration and have it available for future use. When importing a measurement file, you can expand the NumMeasINIfile.ini file by clicking the Expand button ( ) in front of the file under Import configuration to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration file under Import configuration and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import all, if you are importing more than one file. The drive test data are imported into the current Atoll document.
12.6.2 Displaying Drive Test Data When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see the information at that location. To display information about a single drive test data point: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Select the display check box of the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want more information. Atoll displays an arrow pointing towards the serving cell (see Figure 12.65 on page 1280) in the same colour as the transmitter.
12.6.3 Defining the Display of a Drive Test Data Path You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to define labels, tip text and the legend. To display the Display tab of a drive test data path’s Properties dialogue: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path whose display you want to set. The context menu appears. 4. Select Properties from the context menu. The drive test data path’s properties dialogue appears.
1275
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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 for each transmitter (a circle, triangle, cross, etc.) and a symbol size according to the altitude. • • •
•
Fast display forces Atoll to use the lightest symbol to display the points. This is particularly useful when you have a very large number of points. You can not use Advanced display if the Fast display check box has been selected. You can sort drive test data paths in alphabetical order in the Network explorer by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can save the display settings (such as colours and symbols) of a drive test data path in a user configuration file to make them available for use on another drive test data path. To save or load the user configuration file, click the Actions button on the Display tab of the path properties dialogue and select Save or Load from the Display Configuration submenu.
12.6.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 Measurement Points Along Drive Test Data Paths" on page 1276. "Creating Coverage Predictions on Drive Test Data Paths" on page 1279. "Displaying Statistics Over a Drive Test Data Path" on page 1279. "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 1280. "Analysing Measurement Variations Along the Path" on page 1280.
12.6.4.1 Filtering Measurement Points Along Drive Test Data Paths When using a drive test data path, some measured points may present values that are too far outside the median values to be useful. As well, test paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from a more lightly populated region between the two. You can filter out unreliable measurement points from the drive test data path either geographically, by filtering by clutter classes and the focus zone, or using an advanced filter. To filter out measurement points by clutter class: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to filter out measurement points. The context menu appears. 4. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 5. Under Clutter classes, clear the check boxes of the clutter classes you want to exclude. Measurement points located on the excluded clutter classes will be filtered out. 6. If you want to use the focus zone as part of the filter, select the Use focus zone to filter check box. Measurement points located outside the focus zone will be filtered out. 7. If you want to permanently delete the measurement points outside the filter, select the Delete points outside the filter check box.
1276
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
• •
You can apply a filter on all the drive test data paths in the Drive Test Data folder by selecting Filter from the context menu of the folder. If you want to use the measurement points that you permanently deleted, you will have to import the drive test data path again.
To filter out measurement points using an advanced filter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to filter out measurement points. The context menu appears. 4. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 5. Click More. The Filter dialogue appears. For more information on using the Filter dialogue, see "Advanced Data Filtering" on page 96. You can update heights (of the DTM, and clutter heights) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones by selecting Refresh Geo Data from the context menu of the Drive Test Data folder.
12.6.4.2 Predicting Signal Level on Drive Test Data Points To predict signal level on drive test data points: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to create the point prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Point predictions, select Point Signal Level and click OK. The Point Signal Level Properties dialogue appears (see Figure 12.61).
Figure 12.61: Point Signal Level Properties Dialogue At this stage, you must decide whether or not you want Atoll to calculate the errors between measured and predicted signal levels, and to add the corresponding columns in the drive test data table. If you do not want to calculate the errors between measured and predicted signal levels: a. Click OK. A new point prediction is created for the selected drive test data path. b. Right-click the drive test data path. The context menu appears. c. Select Calculations > Calculate All the Predictions from the context menu. A new column is added to the drive test data table for the predicted point signal level from the serving cell.
1277
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.62: Drive Test Data Table after Point Signal Level Prediction (without Error Calculations) A new column is also added for the predicted point signal level from each neighbour cell. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1280. The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main matrix. For more information on propagation models, see Chapter 5: Working with Calculations in Atoll. If you want to calculate errors between measured and predicted signal levels: a. Under Select signal levels for error calculations, select the names of the columns representing measured signal level values in the drive test data table for which you want to calculate the errors (see Figure 12.63).
Figure 12.63: Selecting Measured Signal Levels for which Errors will be Calculated b. Click OK. A new point prediction is created for the selected drive test data path. c. Right-click the drive test data path. The context menu appears. d. Select Calculations > Calculate All the Predictions from the context menu. New columns are added to the drive test data table for the predicted point signal level from the serving cell and the errors between the measured and predicted values.
Figure 12.64: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations) New columns are also added for the predicted point signal level from each neighbour cell and the errors between the predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1280. The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main matrix. For more information on propagation models, see Chapter 5: Working with Calculations in Atoll.
1278
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.6.4.3 Creating Coverage Predictions on Drive Test Data Paths You can create the following coverage predictions for all transmitters on each point of a drive test data path: • •
Coverage by Signal Level Preamble C/(I+N) (DL)
To create a coverage prediction along a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Standard predictions, select one of the following coverage predictions and click OK: •
Coverage by Signal Level: Click the Condition tab. • • • •
•
On 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.
Preamble C/(I+N) (DL): Click the Condition tab. • • • • • •
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 1200. You can also select a cell Layer, or carry out the prediction for the "Best" layer. If you want the preamble C/(I+N) prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. You can select the Indoor coverage check box to add indoor losses.
6. When you have finished setting the parameters for the coverage prediction, click OK. You can create a new coverage prediction by repeating the procedure from step 1. to step 6. for each new coverage prediction. 7. When you have finished creating new coverage predictions for these drive test data, right-click the drive test data. The context menu appears. 8. Select Calculations > Calculate All the Predictions from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Working with Calculations in Atoll). You can display the information in these new columns in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1280.
12.6.4.4 Displaying Statistics Over a Drive Test Data Path If predictions have been calculated along a drive test data path, you can display the statistics between the measured and the predicted values on that path. To display the statistics for a specific drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to display comparative statistics. The context menu appears. 4. Select Display Statistics from the context menu. The Measurement and Prediction Fields Selection dialogue appears. 5. Under For the following transmitters, select one or more transmitters to include in the statistics. 6. Under Select the predicted values, select the fields that contain the predicted values that you want to use in the statistics. 7. Under Select the measured values, select the fields that contain the measured values that you want to use in the statistics.
1279
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
8. Enter the Measured values range for the statistics. Only the measured values within this range will be included in the statistics. 9. Click OK. Atoll opens a window listing statistics of comparison between measured and predicted values.
12.6.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter You can extract information for a selected transmitter from a field of a drive test data path. The extracted information is available in a new column in the drive test data table. To extract a field from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to extract a field. The context menu appears. 4. Select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter dialogue appears. 5. Under On the transmitter, select the transmitter for which you want to extract a field. 6. Under For the fields, select the fields that you want to extract for the selected transmitter. 7. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitter and with the selected values.
12.6.4.6 Analysing Measurement Variations Along the Path In Atoll, you can analyse variations in measurements along any drive test data path using the Drive Test Data analysis tool. You can also use the Drive Test Data analysis tool to find serving cells of points. To analyse measurement variations using the Drive Test Data analysis tool. 1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears (see Figure 12.65).
Figure 12.65: The Drive Test Data window 2. In the Drive Test Data analysis tool, click the Display button. The Display Parameters dialogue appears (see Figure 12.66).
1280
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.66: The drive test data display parameters 3. In the Display Parameters dialogue: • • •
Select the check box next to each field you want to display in the Drive Test Data analysis tool. If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new colour from the palette that appears. Click OK to close the Display Parameters dialogue. You can change the display status or the colour of more than one field at the same time by selecting several fields. You can select contiguous fields by clicking the first field, pressing Shift and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking each field. You can then change the display status or the colour by right-clicking on the selected fields and selecting the choice from the context menu. The selected fields are displayed in the Drive Test Data analysis tool.
4. You can display the data in the drive test data path in the following ways: • •
Click the values in the Drive Test Data analysis tool. 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 12.65 on page 1280) in the same colour as the transmitter. 5. You can display a secondary Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters dialogue. You select the value to be displayed from the right-hand list at the top of the Drive Test Data analysis tool. The values are displayed in the colour defined in the Display Parameters dialogue. 6. You can zoom in on the graph displayed in the Drive Test Data analysis tool in the following ways: •
Zoom in or out: i.
Right-click the Drive Test Data analysis tool. The context menu appears.
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 analysis tool on one end of the range of data you want to zoom in on. The context menu appears.
ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data analysis tool on the other end of the range of data you want to zoom in on. The context menu appears. iv. Select Last Zoom Point from the context menu. The Drive Test Data analysis tool zooms in on the data between the first zoom point and the last zoom point. 7. Click the data in the Drive Test Data analysis tool to display the selected point in the map window. Atoll will centre the map window on the selected point if it is not presently visible.
1281
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
If you open the table for the drive test data you are displaying in the Drive Test Data analysis tool, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data analysis tool (see Figure 12.65 on page 1280).
12.6.5 Exporting a Drive Test Data Path You can export drive test data paths to files as vector data. To export a drive test data path to a vector file: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path 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.
12.6.6 Extracting CW Measurements from Drive Test Data You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path from which you want to export CW measurements. 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 Extraction parameters of CW measurement paths: a. Enter the Min. number of points to extract per measurement path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured signal levels. CW measurements are created with drive test data points where the signal levels are within this specified range. 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.
12.6.7 Printing and Exporting the Drive Test Data Window You can print and export the contents of the Drive Test Data analysis tool. To print or export the contents of the Drive Test Data analysis tool: 1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears (see Figure 12.65 on page 1280). 2. Define the display parameters and zoom level as explained in "Analysing Measurement Variations Along the Path" on page 1280. 3. Right-click the Drive Test Data analysis tool. The context menu appears. • •
1282
To print the Drive Test Data analysis tool, select Print from the context menu. To export the Drive Test Data window, select Copy from the context menu, then paste.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.7 Co-planning WiMAX Networks with Other Networks Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a WiMAX and a GSM network for the same area in Atoll, and then work with Atoll’s co-planning features to study the mutual impacts of the two networks. Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other network’s Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In addition, you can optimise the settings of the two networks using Atoll’s Automatic Cell Planning (ACP) module. In this section, the following are explained: • • • • • •
"Switching to Co-planning Mode" on page 1283. "Working with Coverage Predictions in a Co-planning Project" on page 1285. "Performing Inter-technology Neighbour Allocation" on page 1288. "Creating a WiMAX Sector From a Sector in the Other Network" on page 1298. "Using ACP in a Co-planning Project" on page 1299. "Ending Co-planning Mode" on page 1300.
12.7.1 Switching to Co-planning Mode Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a WiMAX Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, The WiMAX document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems.
To switch to co-planning mode: 1. Open the main document. •
Select File > Open or File > New > From an Existing Database.
2. Link the other document with the open main document. a. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document. b. Select Document > 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]. 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 Atoll’s co-planning features are now available.
1283
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll synchronises the display for the following: • • • •
Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.
Displaying Both Networks in the Same Atoll Document After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 1283, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the explorer window of the linked document to the explorer window of the main document (e.g., you can display GSM sites and measurement paths in a WiMAX document). To display sites from the linked document in the main document: 1. Click the linked document’s map window. The linked document’s map window becomes active and the explorer window shows the contents of the linked document. 2. Select the Network explorer. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In from the context menu, and select the name of the main document from the submenu that opens. The Sites folder of the linked document is now available in the main document. The Explorer window of the main document now contains a folder named Sites in [linked document], where [linked document] is the name of the linked document. If you want the Sites folder of the linked document to appear in the main document automatically, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual. The same process can be used to link other folders in one document, folders such as CW Measurements, Drive Test Data, Clutter Classes, Traffic, DTM, etc., in the other document. Once the folders are linked, you can access their properties and the properties of the items in the folders from either of the two documents. Any changes you make in the linked document are taken into account in the both the linked and main documents. However, because working document is the main document, any changes made in the main document are not automatically taken into account in the linked document. If you close the linked document, Atoll displays a warning icon (
) in the main document’s Explorer window, and the linked
items are no longer accessible from the main document. You can load the linked document in Atoll again by right-clicking the linked item in the explorer window of the main document, and selecting Open Linked Document. The administrator can create and set a configuration file for the display parameters of linked and main document transmitters in order to enable you to distinguish them on the map and to be able to select them on the map using the mouse. If such a configuration file has not been set up, you can choose different symbols, sizes and colours for the linked and the main document transmitters. For more information on folder configurations, see "Folder Configurations" on page 105. You can also set the tip text to enable you to distinguish the objects and data displayed on the map. For more information on tip text, see "Defining the Object Type Tip Text" on page 46. 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 Windows" on page 39. Figure 12.67 shows an example of WiMAX transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in a tip text.
1284
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.67: GSM and WiMAX Transmitters displayed on the map
12.7.2 Working with Coverage Predictions in a Co-planning Project Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: • •
"Updating Coverage Predictions" on page 1285 "Analysing Coverage Predictions" on page 1286.
12.7.2.1 Updating Coverage Predictions You can access the properties of the coverage predictions in the linked Predictions folder in the main document’s Explorer window. After modifying the linked coverage prediction properties, you can update them from the main document. To update a linked coverage prediction: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button (
) in the Radio Planning toolbar.
When you click the Calculate button, Atoll first calculates uncalculated and invalid path loss matrices and then unlocked coverage predictions in the main and linked Predictions folders. When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions" on page 218. 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 Radio Planning 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.
1285
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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.
12.7.2.2 Analysing Coverage Predictions In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tip text to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which coverage predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following are explained: • • • • •
12.7.2.2.1
"Co-Planning Coverage Analysis Process" on page 1286 "Displaying the Legend Window" on page 1286 "Comparing Coverage Prediction Results Using Tip Text" on page 1287 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 1287 "Studying Differences Between Coverage Areas" on page 1287.
Co-Planning Coverage Analysis Process The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes. The recommended process for analysing coverage areas, and the effect of parameter modifications in one 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 1187 and "Making a Coverage Prediction by Signal Level" on page 1185. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tip text contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage prediction’s 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 1284. 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 1287 and "Studying Differences Between Coverage Areas" on page 1287. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.
12.7.2.2.2
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to legend check box on the Display tab. To display the Legend window: •
1286
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.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.7.2.2.3
Comparing Coverage Prediction Results Using Tip Text You can compare coverage predictions by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. Atoll displays information for all displayed coverage predictions in both the working and the linked documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Co-Planning Coverage Analysis Process" on page 1286). To get coverage prediction results in the form of tip text: •
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 12.22). The tip text for the working document is on top and the tip text for the linked document, with the linked document identified by name is on the bottom.
Figure 12.68: Comparing coverage prediction results using tip text
12.7.2.2.4
Comparing Coverage Areas by Overlaying Coverage Predictions You can compare the coverage areas of the main and linked documents by overlaying coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is displayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 43. 9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The coverage prediction is displayed 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 Windows" on page 39.
12.7.2.2.5
Studying Differences Between Coverage Areas You can compare coverage predictions to find differences in coverage areas.
1287
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
To compare coverage predictions: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 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 document’s Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 1196.
12.7.3 Performing Inter-technology Neighbour Allocation The following sections describe the features available in Atoll that help the RF planner to carry out inter-technology neighbour planning. For example, handovers between a WiMAX and a GSM network can be studied in Atoll by allocating neighbour GSM sectors to WiMAX cells In this section, the following are explained: • • • • • • •
"Setting Inter-technology Exceptional Pairs" on page 1288 "Configuring Importance Factors for Inter-technology Neighbours" on page 1290 "Allocating Inter-technology Neighbours Automatically" on page 1291 "Displaying Inter-technology Neighbours on the Map" on page 1292 "Allocating and Deleting Inter-technology Neighbours per Cell" on page 1293 "Calculating the Importance of Existing Inter-technology Neighbours" on page 1296 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 1297.
In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Coplanning Mode" on page 1283.
12.7.3.1 Setting Inter-technology Exceptional Pairs You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Exceptional Pairs from the context menu. The Inter-technology Exceptional Pairs table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list. c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. 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 cell’s inter-technology neighbours and exceptional pairs by using its Properties dialogue.
1288
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
To open a cell’s Properties dialogue: 1. Select the Network explorer. 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 cell’s Properties dialogue appears. 5. Click the Inter-technology Neighbours tab. In GSM, the Inter-technology Neighbours tab is found on the transmitter’s Properties dialogue. Displaying Inter-technology Exceptional Pairs on the Map You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table. To display exceptional pairs defined between the main and the linked documents: 1. Click the main document’s map window. 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
3. Select Display Options from the menu. The Neighbour Display 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 links: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines.
6. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
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 Edit Relations on the Map button ( ) in the Radio Planning toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Edit Relations on the Map 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 41). The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the map. Adding and Removing Inter-technology Exceptional Pairs on the Map You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-technology Exceptional Pairs on the Map" on page 1289. 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.
1289
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
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. 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 41).
12.7.3.2 Configuring Importance Factors for Inter-technology Neighbours You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Neighbours > Inter-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. In a GSM project, you must select Neighbours > Inter-technology > Configure Importance from the Transmitters folder’s context menu.
4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: • • •
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. 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 1291.
5. Click OK.
1290
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
12.7.3.3 Allocating Inter-technology Neighbours Automatically Atoll can automatically determine handover relations between networks of different technologies, for example, WiMAX and GSM. In this case, inter-technology handovers from WiMAX to GSM may occur when the WiMAX coverage is not continuous. The network’s overall coverage is extended by a WiMAX-to-GSM handover. Atoll can automatically determine neighbours in the linked document for cells in the main document and vice versa. Inter-technology neighbours are stored in the database. To automatically allocate neighbours in the linked document for cells in the main document: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 5. Click the Inter-technology Neighbours tab. 6. Define the maximum distance between the reference cell and a possible neighbour in the Max inter-site distance box. 7. Define the maximum number of inter-technology neighbours that can be allocated to a cell in the Max Number of Neighbours box. This value can be either set here for all the cells, or specified for each cell in the Cells table. 8. Clear the Use overlapping coverage check box in order to base the neighbour allocation on distance criterion and continue with step 9. Otherwise, select the Use overlapping coverage check box if you want to base the neighbour allocation on coverage conditions. a. Click the Define button to change the coverage conditions for the cells in the main document. The WiMAX Coverage Conditions dialogue appears. In the WiMAX Coverage Conditions dialogue, you can change the following parameters: • • • •
Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic neighbour allocation. Margin: Enter the margin relative to the preamble signal level of the best server. The preamble signal level of the neighbour transmitter is either the highest one or within a margin of the highest one. Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell edge coverage probability. Indoor coverage: If desired, select the Indoor coverage check box. Atoll will then calculate additional losses for indoor coverage.
b. Click OK to save your modifications and close the Coverage Conditions dialogue. c. Click the Define button to change the coverage conditions for the transmitters/cells in the linked document. 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 cell’s coverage area that the neighbour’s 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.
1291
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
11. Once the calculations finish, Atoll displays the list of neighbours in the Results section. The results include the names of the neighbours, the number of neighbours of each cell, and the reason they are included in the neighbours list. The reasons include: Reason
Description
When
Exceptional pair
Neighbour relation is defined as an exceptional pair.
Force exceptional pairs is selected
Co-site
The neighbour is located at the same site as the reference cell.
Force co-site as neighbours is selected
Distance
The neighbour is within the maximum distance from the reference cell.
Use coverage overlapping is not selected
% of covered area and overlapping area
Neighbour relation that fulfils coverage conditions.
Use coverage overlapping is selected
Existing
The neighbour relation existed before running the automatic allocation.
Reset is not selected
12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this stage you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document. To compare the proposed and existing neighbour lists: •
Click Compare. The list of automatically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: • • • •
The document name and the neighbour allocation type, 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 Inter-technology Neighbours tab of each cell. 14. Click Close.
12.7.3.4 Displaying Inter-technology Neighbours on the Map You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios. To display neighbours in the linked document for cells in the main document: 1. Click the main document’s map window. 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
3. Select Display Options from the menu. The Neighbour Display dialogue appears. 4. Under Inter-technology Neighbours, select the Display links check box. 5. Under Advanced, select the neighbour links to display: •
•
•
Outwards non-symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards non-symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric links: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines.
6. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
1292
) in the Radio Planning toolbar. A menu
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
7. Select Neighbours as the type of neighbour links to display. 8. Click the Edit Relations on the Map button ( ) in the Radio Planning toolbar. Neighbours are now displayed on the map until you click the Edit Relations on the Map button again. 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, 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 41). If you select the Display links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intratechnology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.
12.7.3.5 Allocating and Deleting Inter-technology Neighbours per Cell Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Inter-technology Neighbours table. This section explains the following: • • •
"Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1293. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 1294. "Allocating and Removing Inter-technology Neighbours on the Map" on page 1295.
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 transmitter’s Properties dialogue: 1. On the main document’s map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitter’s 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 cell’s Properties dialogue appears. 5. Click the Inter-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. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Under List, select the cell from the list in the Neighbour column in the row marked with the New row icon (
).
c. Click elsewhere in the table to complete creating the new neighbour.
1293
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, and sets the Source to "manual." To create a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. Select Make Symmetrical 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Press DEL to delete the neighbour. 8. Click OK. In GSM, the Inter-technology Neighbours tab is available in each transmitter’s Properties dialogue. Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Neighbours from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour. 6. Allocate or delete a neighbour. To allocate an inter-technology neighbour: a. In the row marked with the New row icon (
), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Source to "manual." To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Make Symmetrical 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 Make Symmetrical from the context menu.
1294
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
To take all exceptional pairs into consideration: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. You can add or delete either forced neighbours or forbidden neighbours using the of Intertechnology Exceptional Pairs 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 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 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. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector). Allocating and Removing Inter-technology Neighbours on the Map You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-technology Neighbours on the Map" on page 1292. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press Shift and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press Shift and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter. To 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.
1295
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
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. 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 41).
12.7.3.6 Calculating the Importance of Existing Inter-technology Neighbours After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing inter-technology neighbours: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 5. Select the Inter-technology Neighbours tab. 6. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as potential neighbours. 7. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance. 8. Clear the Use overlapping coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 10. Otherwise, select the Use overlapping coverage check box if you want to base the neighbour importance calculation on coverage conditions. 9. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for cells in the main document. The 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: • • • •
1296
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.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
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. 10. If you cleared the Use overlapping coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max inter-site distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated. 11. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. • • • •
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.
12. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
12.7.3.7 Checking the Consistency of the Inter-technology Neighbour Plan You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appear. 3. Select Neighbours > Inter-technology > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Neighbours tab. 5. Define the parameters of the audit: • • •
•
• • • •
Average no. of neighbours: Select the Average no. of neighbours check box if you want to verify the average number of neighbours per cell. Empty lists: Select the Empty lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full lists: Select the Full lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all the cells, or specified for each cell in the Cells table. Lists > max number: Select the Full lists check box if you want to verify which cells have more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all the cells, or specified for each cell in the Cells table. Missing co-sites: Select the Missing co-sites check box if you want to verify which cells have no co-site neighbours. Missing symmetrics: Select the Missing symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional pairs: Select the Exceptional pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance between neighbours: Select the Distance between neighbours check box and enter the distance between neighbours that should not be exceeded.
6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file:
1297
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
•
Average number of neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax:
•
Full lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax:
•
|CELL|
|CELL| |NUMBER| |MAX NUMBER|
Lists > max number (default max number = Y): x/X; x number of cells out of a total of X having more than Y number of neighbours listed in their respective neighbours lists. Syntax:
|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:
•
Non symmetric links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
Existing forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Missing forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
|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|
12.7.4 Creating a WiMAX Sector From a Sector in the Other Network You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main document’s map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new WiMAX transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document. To update the display settings of the new sector: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the Transmitters folder of the main document. The context menu appears. 4. Select Apply Current Configuration from the context menu.
1298
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.69: New sector – Before and after applying the configuration The azimuths and mechanical tilts of secondary antennas or remote antennas are not included when you select Apply Configuration and have to be set up manually.
12.7.5 Using ACP in a Co-planning Project Atoll ACP enables you to automatically calculate the optimal network settings in terms of network coverage and capacity in co-planning projects where networks using different technologies, for example, WiMAX and GSM, must both be taken into consideration. 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 1283. 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 1299 "Importing the Other Network into the Setup" on page 1299.
12.7.5.1 Creating a New Co-planning Optimisation Setup Once you have displayed both networks in the main document as explained in "Switching to Co-planning Mode" on page 1283, you can create the new co-planning optimisation setup. To create a new co-planning optimisation setup: 1. Click the main document’s map window. 2. Select the Network explorer. 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 234. 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.
12.7.5.2 Importing the Other Network into the Setup Once you have created the co-planning optimisation setup, you must import the GSM network. To import the linked network: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 4. Right-click the setup you created in "Creating a New Co-planning Optimisation Setup" on page 1299. The context menu appears. 5. Select Import Project from the context menu and select the name of the document you want to import into the newly created setup.
1299
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
The setup has been modified to include the linked network. You can modify the parameters for the optimisation setup by right-clicking it in the Network explorer and selecting Properties from the context menu. For information on the parameters available, see "Defining Optimisation Parameters" on page 234. 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 267. For information on the optimisation results, see "Viewing Optimisation Results" on page 270. Click the Create Setup button to save the defined optimisation to be run later.
12.7.6 Ending Co-planning Mode once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents. To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select Document > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.
12.8 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 1300. "The Global Network Settings" on page 1301. "Defining Frame Configurations" on page 1304. "Defining WiMAX Radio Bearers" on page 1306. "Defining WiMAX Quality Indicators" on page 1306. "Defining WiMAX Reception Equipment" on page 1306. "Defining WiMAX Schedulers" on page 1309. "Defining Smart Antenna Equipment" on page 1313. "Multiple Input Multiple Output Systems" on page 1315. "Modelling Shadowing" on page 1316. "Modelling Inter-technology Interference" on page 1317.
12.8.1 Defining Frequency Bands To define frequency bands: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder.
1300
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
3. Click the Expand button ( ) to expand the Frequencies folder. 4. In the Frequencies folder, right-click Bands. The context menu appears. 5. Select Open Table. The Frequency Bands table appears. 6. In the Frequency Bands table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each frequency band, enter: •
• • •
Name: Enter a name for the frequency band, for example, "3.3 GHz - 10 MHz." Each WiMAX frequency band has a specific channel width. Mentioning the channel width in the frequency band name is a good approach. This name will appear in other dialogues when you select a frequency band. Channel width (MHz): Enter the channel width for each channel in the frequency band. First channel: Enter the number of the first channel in this frequency band. Last channel: Enter the number of the last channel in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First channel field. The relationship between the frequency band (spectrum), the channel width, and the channel numbers can be defined as: Frequency band width = Channel width x (Last channel + 1 - First channel) So, if you have a frequency band of 30 MHz, and you are deploying your network with 10 MHz allocated to each cell, you can find the first and last channel numbers by: Last channel - First channel = (Frequency band width/Channel width) - 1 If you plan to keep the First channel number = 0, for this example: Last channel = (30 MHz/10 MHz) - 1 = 2
•
• • • •
Excluded channels: Enter the channel numbers which do not belong to the frequency band. You can enter nonconsecutive channel numbers separated with a comma, or you can enter a range of channel numbers separating the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5"). 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 calculating the sampling frequency. Duplexing method: Select the duplexing method used in the frequency band from the list.
7. When you have finished adding frequency bands, click the Close button (
).
You can also access the properties dialogue of each individual frequency band by double-clicking the left margin of the table row containing the frequency band.
12.8.2 The Global Network Settings Atoll allows you to set network level parameters which are common to all the transmitters and cells in the network. These parameters are used in coverage predictions as well as during Monte Carlo simulations by the radio resource management and scheduling algorithms. This section explains the options available on the Global Parameters and Calculation Parameters tabs of the Network Settings folder properties, and explains how to access them: • • •
"The Options on the Global Parameters Tab" on page 1301. "The Options on the Calculation Parameters Tab" on page 1303. "Modifying Global Network Settings" on page 1303.
12.8.2.1 The Options on the Global Parameters Tab The global WiMAX parameters include: • •
•
Frame duration: The frame length in milliseconds. You can choose from a list of frame durations defined in the IEEE 802.16 specifications. Cyclic prefix ratio: The total symbol duration in WiMAX comprises the useful part of the symbol, carrying the data bits, and a CRC part, which is a portion of the useful data part repeated at the beginning of each symbol. The cyclic prefix is the method used in WiMAX to counter inter-symbol interference (ISI). The cyclic prefix and the orthogonality of subcarriers ensure that there is negligible intra-cell interference in WiMAX. Fixed and variable overheads: The fixed and variable overheads in the uplink and downlink subframes are used to model the preamble and other time-domain overheads such as broadcast messages including DL-MAP, UL-MAP, UCD, and DCD, and the FCH, in downlink, and Ranging and Bandwidth Request messages in the uplink. The preamble is always one symbol duration long and can be modelled using the fixed overhead, while other messages whose lengths vary according to either the frame duration or the channel bandwidth can be modelled using the variable overheads.
1301
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
Due to this reason, fixed overheads are available in terms of symbol durations (SD) and the variable overheads in terms of percentages of the uplink and downlink subframes. Variable overheads are percentages of the downlink and the uplink subframes excluding the fixed overheads. DL:UL ratio (TDD only): This ratio represents the fractions of the frame duration which correspond to downlink and uplink subframes. In FDD networks, the downlink and uplink subframes have the same durations as the frame itself. In TDD networks, the downlink and uplink subframes use the same frequency but are duplexed in time. You can define the DL:UL ratio as percentages: you can enter the percentage of the DL subframe with respect to the total frame duration and the percentage corresponding to the uplink subframe is assumed to be equal to the remaining part of the frame. You can choose to define the DL:UL ratio in terms of fractions of the total number of symbol durations available in one frame. For example, if the WiMAX frame contains 47 symbol durations, you can set the downlink fraction to 32 and uplink to 15 (instead of a percentage of 66.667%) so that Atoll uses the exact numbers of downlink and uplink symbol durations as entered in calculations. The exact number of symbol durations in one frame depends on various parameters (channel bandwidth, frame duration, cyclic prefix lengths, sampling factor, 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. Best server selection method: You can select whether the best server selection will be based on the preamble C or the preamble C/(I+N). Depending on the selected method, Atoll compares either the preamble C or the preamble C/ (I+N) from different transmitters at each pixel (or mobile) to determine the best server. Serving (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 highest 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 highest 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 highest cell layer, the second mobile to the second highest cell layer, and so on.
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. Permutation zone selection criterion: You can select whether the permutation zone selection will be based on the preamble C/N or the preamble C/(I+N). Depending on the selected criterion, Atoll compares either the preamble C/N or the preamble C/(I+N) with the quality threshold defined for the permutation zones in the Frame Configurations properties. For more information on the permutation zone quality threshold, see "Defining Frame Configurations" on page 1304.
Figure 12.70 depicts a WiMAX frame with the described parameters marked.
1302
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.70: WiMAX Frame
12.8.2.2 The Options on the Calculation Parameters Tab The WiMAX calculation parameters include: •
Min interferer C/N threshold: Minimum requirement for interferers to be considered in calculations. Interfering cells from which the received carrier-power-to-noise ratio is less than this threshold are discarded. For example, setting this value to -20 dB means that interfering cells from which the received signals are 100 times lower than the thermal noise level will be discarded in calculations. The calculation performance of interferencebased coverage predictions, interference matrices calculations, and Monte Carlo simulations can be improved by setting a high value of this threshold.
•
•
Height: The receiver height at which the path loss matrices and coverage predictions are calculated. Calculations made on mobile users (from traffic maps) in Monte Carlo simulations are also carried out at this receiver height. Calculations made on fixed subscribers (from subscriber lists) in Monte Carlo simulations are carried out at their respective heights. Max range: The maximum coverage range of transmitters in the network. You can use the Max range parameter to limit the coverage range of transmitters in order to avoid uplink-to-downlink interference in TDD networks. In TDD networks, the TTG and RTG parameters, available on the Global Parameters tab of the Network Settings folder 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 Here TTG and RTG are values in milliseconds, "Max range" is in metres, and the "Min()" function returns the lower of the two values given to it in the parentheses.
12.8.2.3 Modifying Global Network Settings You can change global network settings in the properties dialogue of the Network Settings folder. To set the network level parameters: 1. Select the Parameters explorer. 2. Right-click the Network Settings folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Global Parameters tab. In this tab you can set the frame structure parameters. Under Frame structure (see Figure 12.71), you can modify the following: the Frame duration of WiMAX frame, the Cyclic prefix ratio, the fixed and variable overheads for the uplink and the downlink subframes, and, for TDD networks,
1303
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
the downlink-to-uplink subframe ratio (DL:UL ratio) either as a percentage or as a fraction of the number of available symbol durations in one frame, and the transmission and reception time guards (TTG and RTG). The DL:UL ratio entered as a fraction must include the symbol duration(s) used by the preamble or any other fixedduration overheads. During calculations, Atoll first determines the total amount of resources available in one frame and then the resources effectively available for user data by removing any fixed and variable overheads that you have defined.
Figure 12.71: Common Global Parameters 5. Click the Advanced button. The Advanced Parameters dialogue appears. 6. In the Advanced Parameters dialogue, you can set: • • • • •
Best server selection method: In this section, you can choose the best server selection Method. Serving cell layer selection: In this section, you can choose the serving cell layer selection Method. Uplink power control: In this section, you can enter the uplink power control Margin. Adaptive MIMO switching: In this section, you can choose the adaptive MIMO switching Criterion. Permutation zone selection: In this section, you can choose the permutation zone selection Criterion.
7. Select the Calculation Parameters tab. On this tab you can set: • • •
Calculation limitation: In this section, you can enter the Min interferer C/N threshold. Receiver: In this section, you can enter the receiver Height. System: In this section, select the Max range check box if you want to apply a maximum system range limit, and enter the maximum system range in the text box to the right.
8. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
12.8.3 Defining Frame Configurations The SOFDMA frame configuration model uses different numbers of subcarriers for different channel bandwidths. As well, there can be up to 8 different permutation zones in the downlink subframe and 3 in the uplink subframe. Each permutation zone can use a different subchannel allocation mode, and may have different numbers of used and data subcarriers. The Frame Configurations table in Atoll models the channel and frame configuration of a cell. To create a new frame configuration: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. In the Network Settings folder, right-click Frame Configurations. The context menu appears. 4. Select Open Table. The Frame Configurations table appears. 5. In the Frame Configurations table, each row describes a frame configuration. For the new frame configuration, enter: • • •
1304
Name: The name of the frame configuration. Total number of subcarriers: The total number of subcarriers per channel. Number of preamble subcarriers: The number of subcarriers used for the transmitting the preamble. This is the number of subcarriers used when the preamble is not segmented. For a segmented frame configuration, the
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
• •
number of subcarriers used by the segmented preamble are determined automatically from this value during calculations. Segmentation support (DL): Select this check box if the first PUSC permutation zone in the downlink is segmented. Segmentation support (UL): Select this check box if the first PUSC permutation zone in the uplink is segmented.
6. Double-click the frame configuration row in the table once the new frame configuration has been added to the table. The frame configuration’s Properties dialogue opens. 7. Under the General tab, you can modify the parameters that you set previously. 8. 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. Subchannel allocation mode: The subchannel allocation mode used by the permutation zone: PUSC DL, PUSC, FUSC, OFUSC, AMC, TUSC1, and TUSC2 in downlink and PUSC UL, OPUSC, and AMC in uplink. Subframe: Whether the permutation zone belongs to the downlink or 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. Quality threshold: The minimum preamble C/N or C/(I+N) required for a user to be allocated the permutation zone. Make sure that the permutation zone quality threshold values respect the traffic power reduction defined for the cell. For example, if the required traffic channel quality is 2 dB and the traffic power reduction is 3 dB, the quality threshold, i.e., the required preamble quality, should be set to 5 dB.
• • • •
Max speed: The maximum vehicular speed supported by the permutation zone. Max distance: The maximum distance from the base station covered by the permutation zone. Priority: The priority of the permutation zone in terms of its allocation to a user. Diversity support: The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, AMS, or MU-MIMO) supported by the permutation zone. You cannot select more than one type of MIMO technique (STTD/MRC, SUMIMO, MU-MIMO, or AMS) at a time. Specific calculations are performed (and gains applied) for terminals supporting AAS and MIMO. A permutation zone that only supports None does not have any antenna diversity mechanism, and all the terminal types can connect to this zone. A permutation zone that supports None and one or more antenna diversity techniques can also support terminals capable of those diversity techniques. For example, None+AAS can support simple as well as AAS-capable terminals, and None+AMS can support simple and MIMO-capable terminals. Simple terminals cannot connect to a permutation zone that does not support None.
• • • • • •
Zone 0 subchannel groups (segment 0): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned to the segment 0 for the permutation zone 0. Zone 0 subchannel groups (segment 1): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned to the segment 1 of the permutation zone 0. Zone 0 subchannel groups (segment 2): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned to the segment 2 of the permutation zone 0. Zone 8 subchannels (segment 0): The subchannels assigned to the segment 0 for the permutation zone 8. Zone 8 subchannels (segment 1): The subchannels assigned to the segment 1 for the permutation zone 8. Zone 8 subchannels (segment 2): The subchannels assigned to the segment 2 for the permutation zone 8. You can enter non-consecutive subchannel numbers separated with a comma, or you can enter a range of subchannels separating the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
Permutation zones are allocated to users based on the Quality threshold (dB), Max speed (km/h), Max distance, and Priority parameters. The quality threshold, maximum speed, and maximum distance criteria are used to determine the possible permutation zones for each user. Then, the highest priority permutation zone among the possible permutation zones is allocated to the user. During Monte-Carlo simulations, two values of uplink noise rise are calculated per cell, one for the segmented permutation zone and one for the non-segmented permutation zones. For cells using smart antennas, one angular distribution of uplink noise rise is calculated per cell. This angular distribution of uplink noise rise is considered to include both segmented and nonsegmented permutation zones. To see examples of how to set up cells with and without downlink segmentation, and how to set up cells with PUSC, FUSC, and permutation zones of other subchannel allocation modes, see "Tips and Tricks" on page 1319.
1305
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
12.8.4 Defining WiMAX Radio Bearers WiMAX radio bearers carry the data in the uplink as well as in the downlink. In the Atoll WiMAX module, a "bearer" refers to a combination of MCS, i.e., modulation, and coding schemes. The Radio Bearers table lists the available radio bearers. You can add, remove, and modify bearer properties, if you want. To define WiMAX bearers: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. In the Network Settings folder, right-click Radio Bearers. The context menu appears. 4. Select Open Table. The Radio Bearers table appears. 5. In the table, enter one bearer per row. For information on working with data tables, see "Working with Data Tables" on page 69. 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 reception 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. Channel coding rate: Enter the coding rate used by the bearer. This column is for information and display purposes only. Bearer efficiency (bits/symbol): Enter the number of useful bits that the bearer can carry in a symbol. This information is used in throughput calculations. For information on the relation between bearer efficiency and spectral efficiency, see "Relation Between Bearer Efficiency And Spectral Efficiency" on page 1321.
6. Click the Close button (
) to close the Radio Bearers table.
12.8.5 Defining WiMAX Quality Indicators Quality indicators depict the coverage quality at different locations. The Quality Indicators table lists the available quality indicators. You can add, remove, and modify quality indicators, if you want. To define quality indicators: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. In the Network Settings folder, right-click Quality Indicators. The context menu appears. 4. Select Open Table. The Quality Indicators table appears. 5. In the table, enter one quality indicator per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each quality indicator, enter: • • •
Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear in other dialogues and results. Used for data services: Select this check box to indicate that this quality indicator can be used for data services. Used for voice services: Select this check box to indicate that this quality indicator can be used for voice services.
6. Click the Close button (
) to close the Quality Indicators table.
12.8.6 Defining WiMAX Reception Equipment WiMAX reception equipment model the reception characteristics of cells and user terminals. Bearer selection thresholds and channel quality indicator graphs are defined in WiMAX reception equipment. To create a new piece of reception equipment: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. In the Network Settings folder, right-click Reception Equipment. The context menu appears. 4. Select Open Table. The Reception Equipment table appears. 5. In the Reception Equipment table, each row describes a piece of equipment. For the new piece of equipment you are creating, enter its name.
1306
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
6. Double-click the equipment entry in the Reception Equipment table once your new equipment has been added to the table. The equipment’s Properties dialogue opens. The Properties dialogue has the following tabs: • •
General: On this tab, you can define the Name of the reception equipment. Bearer Selection Thresholds: On this tab (see Figure 12.72), you can modify the bearer selection thresholds for different mobility types. A bearer is selected for data transfer at a given pixel if the received carrier-to-interference-and-noise ratio is higher than its selection threshold. For more information on bearers and mobility types, see "Defining WiMAX Radio Bearers" on page 1306 and "Modelling Mobility Types" on page 1201, respectively.
Figure 12.72: WiMAX Reception Equipment - Bearer Selection Thresholds i.
Click the Best bearer thresholds button to open the C/(I+N) Thresholds (dB) dialogue (see Figure 12.73).
ii. Enter the graph values. iii. Click OK.
Figure 12.73: C/(I+N) Thresholds (dB) dialogue For more information on the default values of the bearer selection thresholds, see "Bearer Selection Thresholds" on page 1320. For converting receiver equipment sensitivity values (dBm) into bearer selection thresholds, see "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1320. •
Quality Graphs: On this tab (see Figure 12.74), you can modify the quality indicator graphs for different bearers and mobility types. These graphs depict the performance characteristics of the equipment under different radio conditions. For more information on bearers, quality indicators, and mobility types, see "Defining WiMAX Radio Bearers" on page 1306, "Defining WiMAX Quality Indicators" on page 1306, and "Modelling Mobility Types" on page 1201, respectively.
1307
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.74: WiMAX Reception Equipment - Quality Graphs i.
Click the Quality graph button to open the Quality Graph dialogue (see Figure 12.75).
ii. Enter the graph values. iii. Click OK.
Figure 12.75: Quality Graph dialogue •
MIMO: On this tab (see Figure 12.76), you can modify the SU-MIMO and STTD/MRC gains for different bearers, mobility types, subchannel allocation modes, BLER values, and numbers of transmission and reception antennas. The MIMO throughput gain is the increase in channel capacity compared to a SISO system. For more information on bearers and mobility types, see "Defining WiMAX Radio Bearers" on page 1306 and "Modelling Mobility Types" on page 1201, respectively. For more information on the different MIMO systems, see "Multiple Input Multiple Output Systems" on page 1315. No MIMO gain (STTD/MRC, SU-MIMO, and MU-MIMO) is applied if the numbers of transmission and reception antennas are both equal to 1.
1308
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.76: WiMAX Reception Equipment - MIMO gains i.
Enter the STTD/MRC gain for a combination of Subchannel allocation mode, 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, mobility, radio bearer index, Max BLER, Number of transmission antennas, and Number of reception antennas (see Figure 12.77). iii. Enter the graph values. iv. Click OK. You can define the STTD/MRC and SU-MIMO gains for any 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 12.77: Max SU-MIMO Gain dialogue 7. Click OK. The Properties dialogue closes. The settings are stored. 8. Click the Close button (
) to close the Reception Equipment table.
12.8.7 Defining WiMAX Schedulers In Atoll, schedulers perform the selection of users for resource allocation, the radio resource allocation and management according to the QoS classes of the services being accessed by the selected users.
1309
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
WiMAX has the following QoS classes: QoS Class
Priority
UGS
Highest
ErtPS
:
rtPS
:
nrtPS
:
Best Effort
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 cell’s 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 as long as there are remaining resources. 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 = N
ii. Users of a service with QoS class = UGS, Service priority = N-1 ... iii. Users of a service with QoS class = ErtPS, Service priority = N iv. Users of a service with QoS class = ErtPS, Service priority = N-1 ... v. Users of a service with QoS class = rtPS, Service priority = N vi. Users of a service with QoS class = rtPS, Service priority = N-1 ... vii. Users of a service with QoS class = nrtPS, Service priority = N viii. Users of a service with QoS class = nrtPS, Service priority = N-1 In order to be connected, users active in downlink and uplink must be able to get their minimum throughput in both directions. If a user active in downlink and uplink gets his minimum throughput in only one direction, he will be rejected. 3. Resource allocation for supporting the Max throughput demands: Once the resources have been allocated for supporting the minimum throughput demands in the previous step, the remaining resources can be allocated in different ways to support the maximum throughput demands of the users. The last four QoS classes can have maximum throughput demand requirements. For allocating resources to support the maximum throughput demands, the following types of scheduling methods are available:
1310
•
Proportional fair: The proportional fair scheduling method allocates the same amount of resources to all the users with a maximum throughput demand. Therefore, the resources allocated to each user are either the resources it requires to achieve its maximum throughput demand or the total amount of resources divided by the total number of users in the cell, which ever is smaller. The proportional fair scheduler can also model the effect of resource scheduling over time, i.e., how a proportional fair scheduler benefits from fast fading, by applying multiuser diversity gains (MUG) to user throughputs.
•
Proportional demand: The proportional demand scheduling method allocates resources proportional to the demands of users who have a maximum throughput demand. Therefore, users with higher maximum throughput demands will have higher resulting throughputs than the users with lower maximum throughput demands.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
•
Biased (QoS class): The biased scheduling method first determines the amount of resources available for the users of each QoS class, and then allocates these resources among the users of each QoS class like a proportional fair scheduler. The percentage of the remaining resources that are available for any QoS class is determined based on the QoS class bias factor and the priorities of the QoS classes: 1 i N i × --- β - × 100 % of resources available for QoS Class i = ---------------------------------i N × 1 --- i β
i
Where i represents the QoS classes that have a maximum throughput demand, i.e., ErtPS (i = 1), rtPS (i = 2), nrtPS (i = 3), and Best Effort (i = 4). N i is the number users of QoS class i, and β is the QoS class bias determined from QoS
f 100
QoS Bias -. the QoS class bias factor f Bias as follows: β = 1 + ----------
The QoS class bias factor should be set so as to achieve a valid value of β . For example, for equal numbers of users in each QoS class, •
QoS
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. •
QoS
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. •
Max aggregate throughput: This scheduling method allocates the resources required by the users to achieve their maximum throughput demands in the order of their traffic C/(I+N). This means that users who are under good radio conditions, high traffic C/(I+N), will get the resources they require. The end result of this scheduling method is that the aggregate cell throughputs are maximised.
•
Round robin: The round robin scheduling method allocates the same amount of resources to all the users with a maximum throughput demand. Therefore, the resources allocated to each user are either the resources it requires to achieve its maximum throughput demand or the total amount of resources divided by the total number of users in the cell, which ever is smaller.
For all the scheduling methods, resources are allocated to support the maximum throughput demand until either the maximum throughput demands of all the users are satisfied or the scheduler runs out of resources. The Schedulers table lists the available schedulers. You can add, remove, and modify scheduler properties, if you want. To define WiMAX schedulers: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. In the Network Settings folder, right-click Schedulers. The context menu appears. 4. Select Open Table. The Schedulers table appears. 5. In the table, enter one scheduler per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each scheduler, enter: • • • • • •
Name: Enter a name for the scheduler. This name will appear in the cell properties. Scheduling method: Select the scheduling method used by the scheduler for allocating resources to support the maximum throughput demands. QoS class bias factor: For the schedulers using Biased (QoS class) scheduling method, enter the bias factor to be used for distributing resources between different QoS classes. QoS class bias factor = 0 means no bias. Target throughput for voice services: Select the throughput that the scheduler will target to satisfy for all voicetype services. Target throughput for data services: Select the throughput that the scheduler will target to satisfy for all datatype services. Bearer selection criterion: Select the criterion for the selection of the best bearer. • Bearer index: The best bearer selected for throughput calculations is the one with the highest bearer index among the bearers available in the reception equipment. • Peak MAC throughput: The best bearer selected for throughput calculations is the one with the highest peak MAC throughput (including SU-MIMO gains) among the bearers available in the reception equipment.
1311
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
•
•
Effective MAC throughput: The best bearer selected for throughput calculations is the one with the highest effective MAC throughput (including SU-MIMO gains) among the bearers available in the reception equipment. Uplink bandwidth allocation target: Select the goal of the uplink subchannelisation (bandwidth allocation). • Full bandwidth: All the subchannels are used for the uplink C/(I+N) calculations, 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. • Best bearer: The number of subchannels is reduced in order to increase the uplink C/(I+N) so that the mobile is able to get the best bearer available. The definition of the highest bearer depends on the Bearer selection criterion, i.e., highest index, highest peak MAC throughput, or highest effective MAC throughput. When Bearer selection criterion is set to Effective MAC throughput, Atoll calculates the effective MAC throughput for all possible combinations of [number of subchannels, bearers], and keeps the number of subchannels and the bearer which provide the highest effective MAC throughput.
You can open a scheduler’s properties dialogue by double-clicking the corresponding row in the Schedulers table. In the properties dialogue, a MUG tab is available for the Proportional fair scheduling method. On the MUG tab, you can enter the throughput gains due to multi-user diversity for different mobility types and the maximum traffic C/(I+N) above which the gains are not applied. 6. Click the Close button (
) to close the Schedulers table.
12.8.8 Smart Antenna Systems Smart antenna systems use digital signal processing with more than one antenna element in order to locate and track various types of signals to dynamically minimise interference and maximise the useful signal reception. Different types of smart antenna modelling techniques exist, including beam switching, beam steering, beamforming, etc. Adaptive antenna systems are capable of using adaptive algorithms to cancel out interfering signals. Atoll includes two smart antenna models. The conventional beamformer performs beamforming in downlink and uplink. The optimum beamformer performs beamforming in downlink, and beamforming and interference cancellation in the uplink using an MMSE (Minimum Mean Square Error) algorithm. Smart antenna models dynamically calculate and apply weights on each antenna element in order to create beams in the direction of served users. In uplink, the Minimum Mean Square Error algorithm models the effect of null steering towards interfering mobiles. The antenna patterns created for downlink transmission have a main beam pointed in the direction of the useful signal. For the optimum beamformer, in the uplink, in addition to the main beam pointed in the direction of the useful signal, there can also be one or more nulls in the directions of the interfering signals. If the optimum beamformer uses L antenna elements, it is possible to create L–1 nulls and, thereby, cancel L–1 interfering signals. In a mobile environment where the sources of interference are not stationary, the antenna patterns are adjusted so that the nulls remain in the direction of the moving interference sources. Atoll’s smart antenna models support linear adaptive array systems. TDD WiMAX networks are more suitable for smart antennas than FDD because of the similar uplink and downlink channel characteristics in TDD. Information gathered from a mobile in the uplink can be assumed valid for downlink as well. Atoll’s WiMAX module includes the following smart antenna modelling types: • •
"Optimum Beamformer" on page 1312. "Conventional Beamformer" on page 1313.
The following section explains how to work with smart antenna equipment in Atoll: •
"Defining Smart Antenna Equipment" on page 1313.
12.8.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 C/(I+N) 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
1312
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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 interference-based coverage predictions for the base stations using smart antennas. •
Modelling in Coverage Predictions: The smart antenna results from Monte Carlo simulations are used in coverage predictions. In the 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 the 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.
12.8.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 mobile being served. Beamforming is performed in interfered as well as interfering cells and the downlink C/(I+N) 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 interference-based coverage predictions for the base stations using smart antennas.
•
Modelling in Coverage Predictions: The smart antenna results of Monte Carlo simulations are used in coverage predictions. In the 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 the 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.
12.8.8.3 Defining Smart Antenna Equipment Smart antenna equipment model adaptive antenna array systems, with more than one antenna element. Atoll WiMAX module includes two smart antenna models, a conventional beamformer and an MMSE-based (Minimum Mean Square Error) optimum beamformer. For more information on these smart antenna models in Atoll, see the Technical Reference Guide To create smart antenna equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Click the Expand button ( ) to expand the Smart Antennas folder. 4. In the Smart Antennas folder, right-click Smart Antenna Equipment. The context menu appears. 5. Select Open Table from the context menu. The Smart Antenna Equipment table appears. 6. In the Smart Antenna Equipment table, each row describes a piece of smart antenna equipment. For information on working with data tables, see "Working with Data Tables" on page 69. For the new smart antenna equipment, enter: • •
Name: Enter a name for the smart antenna equipment. Antenna model: Select Optimum Beamformer or Conventional Beamformer from the list.
1313
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
Main antenna model: Select the main antenna model to be used with the smart antenna equipment. The list contains the antennas available in the Antennas table. When you assign the smart antenna equipment to a transmitter, you can choose to replace the current main antenna model with this model.
7. Double-click the equipment entry in the Smart Antenna Equipment table once your new equipment has been added to the table. The equipment’s Properties dialogue opens. 8. Under the General tab, you can modify the parameters that you set previously. 9. To modify the properties of the smart antenna model assigned to the smart antenna equipment, click the Parameters button under Smart antenna models. The smart antenna model’s properties dialogue appears. a. Click the General tab. On the General tab, you can change the default Name of the smart antenna model. b. Click the Properties tab (see Figure 12.78). On the Properties tab, you can define: • • •
Number of elements: The number of antenna elements in the smart antenna system. Single element pattern: The antenna model to be used for each antenna element. You can select an antenna model from the list. The list contains the antennas available in the Antennas folder. Diversity gain (cross-polarisation): Select the Diversity gain (cross-polarisation) check box if you are using cross-polarised smart antennas and want to add diversity gains to the calculated downlink beamforming gains. You can define the diversity gains per clutter class on the Clutter tab of the smart antenna model’s properties dialogue.
Figure 12.78: Smart antenna model - Properties tab c. Click the Clutter tab (see Figure 12.78). On the Clutter tab, you can define the following parameters per clutter class: • •
•
Array gain offset (dB): Enter an offset to be added to the calculated beamforming array gains on pilot and traffic subcarriers. Positive offset values are considered as gains while negative values as losses. Power combining gain offset (dB): Enter an offset to be added to the calculated power combining gains on preamble, pilot, and traffic subcarriers. Positive offset values are considered as gains while negative values as losses. Diversity gain (cross-polarisation) (dB): Enter the diversity gains for cross-polarised smart antennas to be applied to preamble, pilot, and traffic subcarriers.
Figure 12.79: Smart antenna model - Clutter tab d. Click OK. The smart antenna model properties are saved. 10. Click OK. The smart antenna equipment properties are saved.
1314
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
11. Click the Close button (
) to close the Smart Antenna Equipment table.
12.8.9 Multiple Input Multiple Output Systems Multiple Input Multiple Output (MIMO) systems use different transmission and reception diversity techniques. MIMO diversity systems can roughly be divided into the following types, all of which are modelled in Atoll: Space-Time Transmit Diversity and Maximum Ratio Combining STTD uses more than one transmission antenna to send more than one copy of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining, MRC) at the receiver to extract the useful signal. As the receiver gets more than one copy of the useful signal, the signal level at the receiver after combination of all the copies is more resistant to interference than a single signal would be. Therefore, STTD improves the C/(I+N) at the receiver. It is often used for the regions of a cell that have insufficient C/(I+N). Different STTD coding techniques exist, such as STC (Space Time Coding), STBC (Space-Time Block Codes), and SFBC (Space-Frequency Block Codes). In Atoll, you can set whether a permutation zone supports STTD/MRC by selecting the corresponding diversity support mode frame configuration properties (see "Defining Frame Configurations" on page 1304). STTD/MRC gains on downlink and uplink can be defined in the reception equipment for different numbers of transmission and reception antennas, mobility types, bearers, subchannel allocation modes, and maximum BLER. For more information on uplink and downlink STTD/MRC gains, see "Defining WiMAX Reception Equipment" on page 1306. Additional gain values can be defined per clutter class. For information on setting the additional STTD/MRC uplink and downlink gains for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to an uplink or downlink permutation zone that supports STTD/MRC, will benefit from the downlink and uplink STTD/MRC gains. Single-User MIMO or Spatial Multiplexing SU-MIMO uses more than one transmission antenna to send different signals (data streams) on each antenna. The receiver can also have more than one antenna to receive different signals. Using spatial multiplexing with M transmission and N reception antennas, the throughput over the transmitter-receiver link can be theoretically increased M or N times, whichever is smaller. SU-MIMO improves the throughput (channel capacity) for a given C/(I+N), and is used for the regions of a cell that have sufficient C/(I+N). SU-MIMO (single-user MIMO) is also referred to as SM (spatial multiplexing) or simply MIMO. In Atoll, you can set whether a permutation zone supports SU-MIMO by selecting the corresponding diversity support mode frame configuration properties (see "Defining Frame Configurations" on page 1304). SU-MIMO capacity gains can be defined in the reception equipment for different numbers of transmission and reception antennas, mobility types, bearers, subchannel allocation modes, and maximum BLER. For more information on SU-MIMO gains, see "Defining WiMAX Reception Equipment" on page 1306. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to uplink and downlink permutation zones that support SU-MIMO, will benefit from the SU-MIMO gain in its throughput depending on its traffic C/(I+N). When SU-MIMO improves the channel capacity or throughputs, the traffic C/(I+N) of a user is first determined. Once the traffic C/(I+N) is known, Atoll calculates the user throughput based on the bearer available at the user location. The obtained user throughput is then increased according to the SU-MIMO capacity gain and the SU-MIMO gain factor of the user’s clutter class. The capacity gains defined in Max SU-MIMO gain graphs are the maximum theoretical capacity gains using SU-MIMO. SUMIMO requires rich multipath environment, without which the gain is reduced. In the worst case, there is no gain. Therefore, it is possible to define an SU-MIMO gain factor per clutter class whose value can vary from 0 to 1 (0 = no gain, 1 = 100% gain). For information on setting the SU-MIMO gain factor for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. The SU-MIMO capacity gain vs. C/(I+N) graphs available in Atoll by default have been generated based on the maximum theoretical SU-MIMO capacity gains obtained using the following equations: CC MIMO G MIMO = --------------------CC SISO
Min ( N Ant, N Ant )
TX RX C ⁄ (I + N) Where CC MIMO = Min ( N Ant, N Ant ) × Log 2 1 + ----------------------------------------- is the channel capacity at a given C/(I+N) for a MIMO system TX RX RX using N TX Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 ( 1 + C ⁄ ( I + N ) ) is the channel capacity for a
single antenna system at a given C/(I+N). C/(I+N) is used as a ratio (not dB) in these formulas. You can replace the default SUMIMO capacity gain graphs with graphs extracted from simulated or measured values.
1315
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Adaptive MIMO Switching Adaptive MIMO switching is a technique for switching from SU-MIMO to STTD/MRC as the preamble signal conditions get worse than a given threshold. AMS can be used in cells to provide SU-MIMO gains to users that have better preamble C/N or C/(I+N) conditions than a given AMS threshold, and STTD/MRC gains to users that have worse preamble C/N or C/(I+N) conditions than the threshold. AMS provides the optimum solution using STTD/MRC 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 uplink and downlink permutation zones that support AMS, will benefit from the gain to be applied, STTD/MRC or SU-MIMO, depending on the user’s preamble C/N or C/(I+N) and the AMS threshold defined in the cell properties. STTD/MRC gain is applied to the user’s traffic C/(I+N) if the user’s preamble C/N or C/(I+N) is less than the AMS threshold, and SU-MIMO is used if the preamble C/N or C/(I+N) is higher than the AMS threshold. Multi-User MIMO or Collaborative MIMO MU-MIMO (Multi-User MIMO) or Collaborative MIMO is a technique for spatially multiplexing two users who have sufficient radio conditions at their locations. This technique is used in uplink so that a cell with more than one reception antenna can receive uplink transmissions from two different users over the same frequency-time allocation. This technique provides considerable capacity gains in uplink, and can be used with single-antenna user equipment, i.e., it does not require more than one antenna at the user equipment as opposed to SU-MIMO, which only provides considerable gains with more than one antenna at the user equipment. In Atoll, you can set whether an uplink permutation zone supports MU-MIMO in uplink by selecting the corresponding diversity support mode in the frame configuration properties (see "Defining Frame Configurations" on page 1304). MU-MIMO capacity gains result from the scheduling and the RRM process. Using MU-MIMO, schedulers are able to allocate resources over two spatially multiplexed parallel frames in the same frequency-time resource allocation plane. MU-MIMO can only work under good radio conditions and if the cell has more than one reception antenna. Therefore, the preamble C/N must be higher than the MU-MIMO threshold defined by cell in order for the scheduler to be able to multiplex users in uplink. During the calculation of Monte Carlo simulations in Atoll, each new user connected to the first antenna creates virtual resources available on the second antenna. These virtual resources can then be allocated to a second user connected to the second antenna without increasing the overall load of the cell. This way, each new mobile consumes the virtual resources made available be the previous mobile, and might create new virtual resources available on the other antenna. The MU-MIMO capacity gain resulting from this uplink collaborative multiplexing is the ratio of the traffic loads of all the mobiles connected to both parallel frames in uplink to the uplink traffic load of the cell. MU-MIMO is only possible for mobiles that support MIMO and at which the preamble C/N is greater than the MU-MIMO threshold defined for their serving cell. The MU-MIMO capacity gain can be defined per cell by the user or it can be an output of Monte Carlo simulations. This gain is used during the calculation of uplink throughput coverage predictions. The channel throughput is multiplied by this gain for pixels where MU-MIMO is used as the diversity mode.
12.8.10 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 145. 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 1175) A coverage prediction (see "Studying Signal Level Coverage" on page 1176).
Atoll always takes shadowing into consideration when calculating a Monte Carlo simulations. Atoll uses the values defined for the model standard deviations per clutter class when calculating the signal level coverage predictions. Atoll uses the values defined for the C/I standard deviations per clutter class when calculating the interference-based coverage predictions.
1316
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per Clutter Class" on page 1317.
12.8.10.1 Displaying the Shadowing Margins per Clutter Class To display the shadowing margins per clutter class: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins dialogue appears. 4. You can set the following parameters: • •
Cell edge coverage probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard deviation: Select the type of standard deviation to be used to calculate the shadowing margin: • •
Model: The model standard deviation. Atoll will display the shadowing margin of the signal level. C/I: The C/I standard deviation. Atoll will display the C/I shadowing margin.
5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.
12.8.11 Modelling Inter-technology Interference Analyses of WiMAX networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in a WiMAX network. Atoll can take into account interference from coexisting networks in Monte Carlo simulations and coverage predictions. The following inter-technology interference scenarios are modelled in Atoll: •
Interference received by mobiles on the downlink: Interference can be received by mobiles in a WiMAX network on the downlink from external base stations and mobiles in the vicinity. Interference from external base stations (also called downlink-to-downlink interference) can be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (GSM, UMTS, CDMA2000, etc.). These graphs are then used for calculating the interference from the external base stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-technology IRFs" on page 1318. Interference from external mobiles (also called uplink-to-downlink interference) can be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your WiMAX network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled in Atoll using the Inter-technology DL noise rise definable for each cell in the WiMAX network. This noise rise is taken into account in all downlink interference-based calculations. For more information on the Inter-technology DL noise rise, see "Cell Description" on page 1155.
Figure 12.80: 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) can be created by insufficient separation between the downlink frequency used by the external network and the uplink frequency used by your WiMAX network. Such interference may also come from co-existing TDD networks. Interference from external mobiles (also called uplink-to-uplink interference) can be created by the use of same or nearby frequencies for uplink in both networks. Unless the exact locations of external mobiles is known, it is not possi-
1317
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
ble to separate interference received from external base stations and mobiles on the uplink. The effect of this interference is modelled in Atoll using the Inter-technology UL noise rise definable for each cell in the WiMAX network. This noise rise is taken into account in uplink interference calculations in Monte-Carlo simulations, but not in coverage predictions. For more information on the Inter-technology UL noise rise, see "Cell Description" on page 1155.
Figure 12.81: Interference received by cells on the uplink
12.8.11.1 Defining Inter-technology IRFs Interference received from external base stations on mobiles of your WiMAX network can be calculated by Atoll. Atoll uses the inter-technology interference reduction factor (IRF) graphs for calculating the interference levels. An IRF graph represents the variation of the Adjacent Channel Interference Ratio (ACIR) as a function of frequency separation. ACIR is determined from the Adjacent Channel Suppression (ACS) and the Adjacent Channel Leakage Ratio (ACLR) parameters as follows: 1 ACIR = ------------------------------------1 1 ------------- + ----------------ACS ACLR
An IRF depends on: • • • •
The interfering technology (GSM, UMTS, CDMA2000, etc.) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).
IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your WiMAX document, i.e., when Atoll is in co-planning mode. For more information on how to switch to co-planning mode, see "Switching to Co-planning Mode" on page 1283. To define the inter-technology IRFs in the victim network: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Inter-technology Interference Reduction Factors. The context menu appears. 4. Select Open Table. The Inter-technology Interference Reduction Factors table appears. 5. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter: • • • •
Technology: The technology used by the interfering network. Interferer bandwidth (kHz): 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): 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. i.
Enter the interference reduction factors in the Reduction (dB) column for different frequency separation, Freq. delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document. • •
Reduction values must be positive. If you leave reduction factors undefined, Atoll assumes there is no interference.
ii. When done, click OK. 6. Click the Close button (
1318
) to close the Inter-technology Interference Reduction Factors table.
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
You can link more than one Atoll document with your main document following the procedure described in "Switching to Coplanning Mode" on page 1283. 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.
12.9 Tips and Tricks The following tips and tricks are described below: • • • • • • • • • • •
"Obtaining User Throughputs for All the Subscribers of a Subscriber List" on page 1319. "Working With User Densities Instead of User Profiles" on page 1319. "Restricting Coverage Predictions to LOS Areas Only" on page 1320. "Bearer Selection Thresholds" on page 1320. "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1320. "Relation Between Bearer Efficiency And Spectral Efficiency" on page 1321. "Determining Approximate Required DL:UL Ratio for a TDD Network" on page 1321. "Working With Frame Configurations, Permutation Zones, and Downlink Segmentation: Examples" on page 1321. "Modelling VoIP Codecs" on page 1325. "Modelling Different Types of AMC Subchannels" on page 1326. "Modelling the Co-existence of Networks" on page 1327.
Obtaining User Throughputs for All the Subscribers of a Subscriber List This procedure is only recommended if you have a proper subscriber list and have complete knowledge of the services they use.
Atoll generates a realistic user distribution containing active and inactive users during Monte Carlo simulations. The activity status of these users is determined through the user’s service usage parameters defined in the user profile. In Atoll, subscribers in a subscriber list must have a user profile assigned to them in order to be taken into account in Monte Carlo simulations. In Monte Carlo simulations based on subscriber lists, Atoll determines active users from among the users listed in the subscriber list and carries out RRM and resource allocation for calculating user throughputs. If you want to determine user throughputs for all the subscribers in a subscriber list, you can run a Monte Carlo simulation with the subscriber list as input after modifying the user profiles assigned to the subscribers such that the probability of activity for all the subscribers is 100 %. 1. Create a subscriber list with subscribers having an activity probability of 100%: a. Create as many user profiles as there are services used by the subscribers in the list. b. Assign only one service to each user profile. c. Assign the following service usage parameters to the user profiles that you create: i.
For Voice services, set:
• •
Calls/hour = 1. Duration (sec.) = 3600.
ii. For Data services: • • •
Calls/hour = 1. UL volume (KBytes) = Service uplink average requested throughput x 3600/8. DL volume (KBytes) = Service downlink average requested throughput x 3600/8.
d. Assign these user profiles to subscribers in the subscriber list. 2. Create a Monte Carlo simulation based only on this subscriber list. The simulation results will contain all the subscribers in the subscriber list with their respective user throughputs determined by Atoll after the scheduling process. Working With User Densities Instead of User Profiles If you do not currently have reliable WiMAX multi-service traffic, you can provide Atoll with user density information per service, for example, traffic data from adapted GSM Erlang maps. In this case, you do not have to create user profiles. As well, Atoll does not have to determine the user activity probabilities to create traffic scenarios during simulations. The distribution of traffic during simulations will only depend on the user densities per service.
1319
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
If you know the user densities for each service, you can set user activity probabilities to 100 % in your WiMAX document, as shown below: 1. For Voice services, set: • •
Calls/hour = 1. Duration (sec.) = 3600.
2. For Data services: • • •
Calls/hour = 1. UL volume (KBytes) = Service uplink average requested throughput x 3600/8. DL volume (KBytes) = Service downlink average requested throughput x 3600/8.
The above settings will set the user activity probabilities to 100 %. If you create a traffic map based on environment classes, the user density values that you define in your environment classes will be the actual user densities. This means that, for X users/km² defined in the environment class for a given user profile, the Monte Carlo simulator will generate exactly X users/ km² for each service of the user profile. In this way, you can know beforehand the exact number of active users, and their services, generated during the simulations. This procedure should only be used when appropriate traffic data is not available. Restricting Coverage Predictions to LOS Areas Only You can restrict the coverage to LOS areas only if you are using the Standard Propagation Model. To restrict coverage to LOS areas, you have to enter a very high value for the K4 Standard Propagation Model parameter. Bearer Selection Thresholds The default values of the bearer selection thresholds, the BLER quality graphs, and the bearer efficiency values in Atoll have been extracted and estimated from the NS2 simulator results available with the WiMAX Forum (see Figure 12.82). These values correspond to an ideal (AWGN) radio channel, and are rather optimistic compared to actual radio channels. It is recommended to use more realistic values when available.
Figure 12.82: Link Adaptation in WiMAX The spectral efficiency is the number of useful data bits that can be transmitted using any modulation and coding scheme per Hz, the transition points between any two modulation and coding schemes give the default bearer selection thresholds in Atoll, and the normalised values from the slopes of the graphs, that represent the reduction in the spectral efficiency, give the block error rate. Calculating Bearer Selection Thresholds From Receiver Sensitivity Values You can convert the receiver sensitivity values, from your equipment data sheet, into bearer selection thresholds using the following conversion method: n × BW × N Used CNR = RS + 114 – NF – 10 × Log ------------------------------------------ + 10 × Log ( R ) – L Imp N Total
Where RS is the receiver sensitivity in dBm, NF is the noise figure of the receiver in dB, n is the sampling factor, BW is the channel bandwidth in MHz, N Used is the number of used subcarriers, N Total is the total number of subcarriers, R is the number of
1320
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
retransmissions, and L Imp is the implementation loss in dB. If you do not know the values for R and L Imp , you can ignore the corresponding terms and simplify the equation. Here the term receiver refers to the base station in uplink and to the mobile/user equipment in the downlink. Relation Between Bearer Efficiency And Spectral Efficiency Spectral efficiency of a modulation and coding scheme is defined as the number of useful bits that can be transmitted per second over 1 Hz wide channel. Spectral efficiency is hence given in terms of bps/Hz. In Atoll, the efficiency of bearers (modulation and coding schemes) are defined in the Radio Bearers table. The bearer efficiency is given in terms of bits/symbol. Remember that in Atoll symbol refers to modulation symbol, the data transmission unit which is 1 symbol duration long and 1 subcarrier width wide, as shown in Figure 12.83.
Figure 12.83: Symbol Bearer efficiency is similar to spectral efficiency. The only difference is in the units used. 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, let’s say that QPSK1/2 has a bearer efficiency of 1 bits/symbol. Here as well, the number of bits refers to useful data bits. The width of a subcarrier in WiMAX is 1 ΔF = 10.94 kHz , from which we can calculate the useful symbol duration as well: T U = ------- = 91.4 μ sec . In one second, ΔF
there can be 1 sec ⁄ 91.4 μ sec = 10940 symbol durations. If 10940 symbols are transmitted using QPSK1/2, this gives us a data rate of 10940 Symbols/sec × 1 bits/Symbol = 10940 bps , which is the data rate achievable using one subcarrier of 10.94 kHz. We can find the spectral efficiency by normalizing the data rate to unit bandwidth. This gives: 10940 bps/subcarrier ⁄ 10.94 kHz/subcarrier = 1 bps/Hz
In order to compare equivalent quantities, we have ignored the system parameters such as the cyclic prefix, TTG, RTG, and have considered that the entire frame is transmitted in one direction, uplink or downlink. Determining Approximate Required DL:UL Ratio for a TDD Network In TDD networks, the durations of the downlink and uplink subframes have to be properly set in order to optimally satisfy the traffic demands in both downlink and uplink. You can use the simulation results to calculate the approximate value of the DL:UL ratio required for your network under the given traffic scenario of the simulation. The DL:UL ratio can be calculated by taking the ratio of the sum of the downlink traffic loads of all the cells and the sums of all the downlink and uplink traffic loads of all the cells. The downlink and uplink traffic loads of all the cells are listed in the Cells tab of the simulations results dialogue.
TL
DL
All Cells DL:UL ratio = -----------------------------------------------------------------DL UL TL + TL
All Cells
All Cells
You can then set this value of DL:UL ratio in the Global Parameters tab of the Network Settings folder’s properties dialogue, for optimising your network’s resource usage. Working With Frame Configurations, Permutation Zones, and Downlink Segmentation: Examples In the following examples, we assume that: • •
You are working on a document with existing base stations. One 5 MHz channel, with channel number 0, defined in the frequency band, that can be allocated to sectors.
1321
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
•
© Forsk 2012
The frame configuration that can be used is FFT Size 512 with 512 total subcarriers.
There can be different scenarios for this implementation: 1. Without segmentation, i.e., a frequency reuse plan of N=1. a. Set up the frame configuration: i.
Open the Frame Configurations table as explained in "Defining Frame Configurations" on page 1304.
ii. Verify that the Segmentation support (DL) check box is not selected for FFT Size 512. iii. Double-click the frame configuration FFT Size 512. iv. Click the Permutation Zones tab. v. Activate the permutation zones 0 (PUSC DL) and 8 (PUSC UL). vi. Click OK. vii. Close the Frame Configurations tables. b. Set up the cells: i.
Right-click the Transmitters folder. 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 1205 and "Making a Coverage Prediction by Throughput" on page 1211, respectively. In this case, the same 5 MHz channel is allocated to the three sectors of each 3-sector site. The sectors receive cochannel 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 12.84 and Figure 12.85.
Figure 12.84: Downlink Traffic C/(I+N) Coverage Prediction - PUSC Without Segmentation
1322
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.85: Downlink Channel Throughput Coverage Prediction - PUSC Without Segmentation 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 1304.
ii. Select the Segmentation support (DL) check box for FFT Size 512. iii. Double-click the frame configuration FFT Size 512. iv. Click the Permutation Zones tab. v. Activate the permutation zones 0 (PUSC DL) and 8 (PUSC UL). vi. Click OK. vii. Close the Frame Configurations tables. b. Set up the cells: i.
Right-click the Transmitters folder. 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 1205 and "Making a Coverage Prediction by Throughput" on page 1211, 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 12.86 and Figure 12.87.
1323
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
Figure 12.86: Downlink Traffic C/(I+N) Coverage Prediction - PUSC With Segmentation
Figure 12.87: 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 1304.
ii. Select the Segmentation support (DL) check box for FFT Size 512. iii. Double-click the frame configuration FFT Size 512. The Permutation Zones table appears. iv. Activate the permutation zones 0 (PUSC DL), 2 (FUSC) and 8 (PUSC UL). v. Click OK. vi. Close the Frame Configurations tables. b. Set up the cells: i.
Right-click the Transmitters folder. 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. 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:
1324
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
i.
Create or import a traffic map, as explained in "Creating a Traffic Map" on page 1241, to be used as input to the Monte Carlo simulator.
ii. Create a new Monte Carlo simulation as explained in "Creating Simulations" on page 1257. iii. Open the simulation results, and commit the results to the Cells table as explained in "Updating Cell Load Values With Simulation Results" on page 1268. 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 1205 and "Making a Coverage Prediction by Throughput" on page 1211, 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 12.88 and Figure 12.89.
Figure 12.88: Downlink Traffic C/(I+N) Coverage Prediction - Segmented PUSC + FUSC
Figure 12.89: Downlink Channel Throughput Coverage Prediction - Segmented PUSC + FUSC If you compare the traffic C/(I+N) and throughput coverage predictions in the above cases, you will observe that the traffic C/ (I+N) improves with segmentation, but the throughput is reduced. Modelling VoIP Codecs VoIP codecs are application-layer elements in the OSI system model. Atoll models application throughputs using a throughput offset and a scaling factor with respect to the MAC layer throughputs. You can model different VoIP codecs by creating a new
1325
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
service for each VoIP codec, and setting the target throughput to application throughput for the scheduler used. Here are two examples of the most common VoIP codecs, and how they can be modelled in Atoll: •
G.711 VoIP Codec The actual voice data rate needed by the G.711 codec is 64 kbps, but with the lower layer headers and other added bits, the needed MAC data rate could be between 66.4 and 107.2 kbps. In this example, we show how to model the codec with header bits that lead to 85.6 kbps MAC data rate. a. Create a new service with the following parameters: • • • • • • •
Name: VoIP (G.711) Type: Voice QoS class: UGS Min throughput demand (DL) and Min throughput demand (UL): 64 kbps Average requested throughput (DL) and Average requested throughput (UL): 64 kbps Scaling factor: 74.77 % Offset: 0 kbps
b. Set the Target throughput for voice services to "2 - Application throughput" for the scheduler being used. In this way, Atoll will allocate resources to the users of this service such that they get 64 kbps application throughput, and around 85.6 kbps of effective MAC throughput. •
G.729 VoIP Codec The actual voice data rate needed by the G.729 codec is 8 kbps, but with the lower layer headers and other added bits, the needed MAC data rate could be between 9.6 and 29.6 kbps. In this example, we show how to model the codec with header bits that lead to 29.6 kbps required data rate. a. Create a new service with the following parameters: • • • • • • •
Name: VoIP (G.729) Type: Voice QoS class: UGS Min throughput demand (DL) and Min throughput demand (UL): 8 kbps Average requested throughput (DL) and Average requested throughput (UL): 8 kbps Scaling factor: 27.03 % Offset: 0 kbps
b. Set the Target throughput for voice services to "2 - Application throughput" for the scheduler being used. In this way, Atoll will allocate resources to the users of this service such that they get 8 kbps application throughput, and around 29.6 kbps of effective MAC throughput. Modelling Different Types of AMC Subchannels AMC subchannels are composed of bins, i.e., groups of 9 adjacent subcarriers. The following four types of AMC subchannels exist:
Type
Name
Number of Bins in 1 Subchannel
Number of Subcarriers in 1 Subchannel
Length (Number of Symbol Durations)
Total Number of Modulation Symbols in One Slot
1 2 3 4
6 x 1 (Default) 3x2 2x3 1x6
6 3 2 1
6 x 9 = 54 3 x 9 = 27 2 x 9 = 18 1x9=9
1 2 3 6
54 x 1 = 54 27 x 2 = 54 18 x 3 = 54 9 x 6 = 54
As the above table shows, each type of AMC subchannels has a different number of bins. However, the duration of an AMC slot varies corresponding to the number of bins in the subchannel in order to maintain the number of modulation symbols in one slot constant. In the first type (6 x 1; default in Atoll), a slot consists of a subchannel of 6 consecutive bins (54 subcarriers) over 1 symbol duration. A slot of the second type (3 x 2) consists of a subchannel of 3 consecutive bins (27 subcarriers) over 2 symbol durations. A slot of the third type (2 x 3) consists of a subchannel of 2 consecutive bins (18 subcarriers) over 3 symbol durations. And, a slot of the fourth type (1 x 6) consists of a subchannel of 1 bin (9 subcarriers) over 6 symbol durations. In all the cases, a slot comprises 54 modulation symbols.
1326
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
Figure 12.90: 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 type of AMC subchannels, you will have to increase the number of subchannels per channel accordingly, i.e., multiply the current value by 2, 3, or 6, for modelling the second, third, or fourth type, respectively. Modelling the Co-existence of Networks In Atoll, you can study the effect of interference received by your network from other WiMAX networks. The interfering WiMAX network can be a different part of your own network, or a network belonging to another operator. To study interference from co-existing networks: 1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a Group of Base Stations" on page 1165. 2. For the interfering network’s transmitters, set the Transmitter type to Inter-network (Interferer only) as explained in "Transmitter Description" on page 1152. During calculations, Atoll will consider the transmitters of type Inter-network (Interferer only) when calculating interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interference. Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network. If the interfering network is a part of your own network, this information would be readily available. However, if the interfering network belongs to another operator, the information available might not be accurate. Moreover, for other operators’ networks, and if the interfering networks use OFDM but are not WiMAX networks, you will have to create specific frame configurations to assign to the cells of the interfering network. The number of subcarriers used in these frame configurations would depend on the channel bandwidth on which transmitter is interfering. For more information on frame configuration parameters, see "Defining Frame Configurations" on page 1304.
12.10 Glossary of WiMAX Terms Understanding the following terms and there use in Atoll is very helpful in understanding the WiMAX module: •
User: A general term that can also designate a subscriber, mobile, and receiver.
•
Subscriber: Users with fixed geographical coordinates.
•
Mobile: Users generated and distributed during simulations. These users have, among other parameters, defined services, terminal types, and mobility types assigned for the duration of the simulations.
•
Receiver: A probe mobile, with the minimum required parameters needed for the calculation of path loss, used for propagation loss and raster coverage predictions.
•
Radio Bearer: A Modulation and Coding Scheme (MCS) used to carry data over the channel.
•
Peak MAC Throughput: The maximum MAC layer throughput (user or channel) that can be achieved at a given location using the highest WiMAX bearer available. This throughput is the raw data rate without considering the effects of retransmission due to errors and higher layer coding and encryption.
1327
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
© Forsk 2012
•
Effective MAC Throughput: The net MAC layer throughput (user or channel) that can be achieved at a given location using the highest WiMAX bearer available computed taking into account the reduction of throughput due to retransmission due to errors.
•
Application Throughput: The application layer throughput (user or channel) that can be achieved at a given location using the highest WiMAX bearer available computed taking into account the reduction of throughput due to PDU/SDU header information, padding, encryption, coding, and other types of overhead.
•
Channel Throughputs: Peak MAC, effective MAC or application throughputs achieved at a given location using the highest WiMAX bearer available with the entire cell resources (uplink or downlink).
•
Allocated Bandwidth Throughputs: Uplink peak MAC, effective MAC or application throughputs achieved at a given location using the best possible WiMAX bearer with the number of subchannels calculated after subchannelisation.
•
User Throughputs: Peak MAC, effective MAC or application throughputs achieved at a given location using the highest WiMAX bearer available with the amount of resources allocated to a user by the scheduler.
•
Traffic Loads: The uplink and downlink traffic loads are the percentages of the uplink and the downlink subframes in use (allocated) to the traffic (mobiles) in the uplink and in the downlink, respectively.
•
Resources: In Atoll, the term "resource" is used to refer to the average number of slots, expressed in percentage (as traffic loads, when the average is performed over a considerably long duration) of the total number of slots in a superframe of 1 sec.
•
Uplink Noise Rise: Uplink noise rise is a measure of uplink interference with respect to the uplink noise: I UL + N UL NR UL = ------------------------ , or NR UL = 10 × Log ( I UL + N UL ) – 10 × Log ( N UL ) in dB. This parameter is one of the two N UL
methods in which uplink interference can be expressed with respect to the noise. The other parameter often used I I UL + N UL
UL - . Usually, the uplink load factor is kept as a instead of the uplink noise rise is the uplink load factor: L UL = ------------------------
linear value (in percentage) while the uplink noise rise is expressed in dB. The two parameters express exactly the same information, and can be inter-converted as follows: I I+N–N I I+N N I N N I I+N 1 ------------ = ---------------------- => ------------ = ------------ – ------------ => ------------ = 1 – ------------ => ------------ = 1 – ------------ => ------------ = --------------------I I+N I+N I+N I+N I+N I+N I+N I+N I+N N 1 – -----------I+N 1 => NR = -----------
1–L
The following table shows the relation between interference, load factor, and noise rise. Interference (I) 0 =N =9xN = 99 x N
Load Factor (%) 0 50 90 99
Noise Rise 1 2 10 100
Noise Rise (dB) 0 3.01 10 20
The reason why uplink interference is expressed in terms of noise rise (in dB) in Atoll instead of load factor (in percentage) is that the load factor varies exponentially with the increase in interference. •
Symbol: A symbol is the modulation symbol, corresponding to one frequency unit (subcarrier) over one time unit (symbol duration or OFDM symbol).
•
Symbol Duration (SD): The symbol duration is the length of each symbol in the frame. The length of a frame, i.e., the frame duration, can be expressed in terms of the number of symbol durations in the frame. It is referred to as OFDM symbol in the IEEE 802.16 specifications.
•
Subchannels: A subchannel is a group of subcarriers. A channel can be divided into a number of subchannels. You can set the number of these subchannels at the network level in Atoll.
•
Subcarriers (or tone): A channel contains a number of subcarriers including the upper and lower guard bands, the pilot subcarriers, and the data subcarriers. The guards, pilots, and the DC subcarrier can not be used for data transfer. The total thermal noise over the entire channel bandwidth is calculated according to the number of used subcarriers out of the total number of subcarriers. The used subcarriers are the data and the pilot subcarriers. The data transfer capacity of a channel is calculated by considering the data subcarriers only.
•
Frame Configuration: A frame configuration is the description of a frame in the frequency as well as in the time dimension. In the frequency domain, it defines how many subcarriers exist in the channel width used, and how many of these subcarriers are used and for which purpose, i.e., pilot, data, DC, guard. In the time domain, it defines how long the frame is, and its composition. The frame configuration depends on the channel width because the system uses Scalable OFDMA. The IEEE specifications define different frame configurations for different channel widths. For example, a cell using a 10 MHz channel
1328
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
AT312_UM_E1
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 1304. •
Permutation Zone: A permutation zone is a subdivision of a WiMAX frame in the time domain. According to the IEEE specifications, there can be as many as 8 permutation zones in the downlink and 3 in the uplink. Each permutation zone can use a different subchannel allocation mode (or a permutation scheme), and can have different numbers of used, pilot, and data subcarriers. The different subchannel allocation modes are: PUSC, FUSC, OFUSC, AMC, TUSC1, and TUSC2 in downlink, and PUSC, OPUSC, and AMC in uplink.
•
Segmentation: The PUSC subchannel allocation mode allows the allocation of groups of subchannels to cells. According to the IEEE specifications, there are 6 subchannel groups in the downlink PUSC subchannel allocation mode. You can, for example, use 2 subchannel groups at each sector of a 3-sector site, and completely eliminate interference between these sectors by correctly planning the preamble indexes. On one hand, segmentation improves the CINR by allowing you to different segments of the same channel at different sectors, but on the other hand, it reduces the available cell capacity (throughput) because the channel width used at each sector is reduced. For examples on how to use segmentation in Atoll, see "Working With Frame Configurations, Permutation Zones, and Downlink Segmentation: Examples" on page 1321.
•
Primary and Secondary Subchannel Groups (PUSC DL): The primary subchannel groups (0, 2, and 4) and secondary subchannel groups (1, 3, and 5) are mapped to subchannel numbers as follows:
Total Number of Subcarriers
Subchannel Group Subchannel Range
Total Number of Subcarriers
Subchannel Group Subchannel Range
0
0
0
0-5
1
N/A
1
6-9
2
1
2
10-15
128
1024 3
N/A
3
16-19
4
2
4
20-25
5
N/A
5
26-29
0
0-4
0
0-11
1
N/A
1
12-19
2
5-9
2
20-31
512
2048 3
N/A
3
32-39
4
10-14
4
40-51
5
N/A
5
52-59
1329
Atoll 3.1.2 User Manual Chapter 12: WiMAX BWA Networks
1330
© Forsk 2012
Chapter 13 Wi-Fi Networks This chapter provides the information to use Atoll to design, analyse, and optimise a Wi-Fi network.
In this chapter, the following are explained: •
"Designing a Wi-Fi Network" on page 1333
•
"Planning and Optimising Wi-Fi Access Points" on page 1334
•
"Studying Network Capacity" on page 1383
•
"Verifying Network Capacity" on page 1410
•
"Co-planning Wi-Fi Networks with Other Networks" on page 1418
•
"Advanced Configuration" on page 1421
•
"Tips and Tricks" on page 1430
Atoll 3.1.2 User Manual Chapter 13: Starting a Project
1332
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
13 Wi-Fi Networks Wi-Fi refers to a group of WLAN (Wireless Local Area Network) standards from the IEEE. The WLAN air interface is described in the IEEE 802.11 standards family. IEEE 802.11 includes various technologies and operating frequencies for WLAN, including: 802.11a
802.11b
802.11g
802.11n
802.11ac
Released
1999
1999
2003 Rev. 2007
2009
2012
Technology
OFDM
DSSS
OFDM
OFDM
OFDM
Operating Frequencies (GHz)
5
2.4
2.4
2.4, 5
5
Channel Widths (MHz)
20
22
20
20, 40
20, 40, 80, 160
Modulations
BPSK, QPSK, 16QAM, 64QAM
+ 256QAM
MIMO Capabilities
—
—
—
4x4 (Maximum)
8x8 (Maximum)
Maximum Throughput per Access Point (Mbps)
54
11
54
540 (Long GIa) 600 (Short GI)
6240 (Long GI) 6933 (Short GI)
a.
Guard Interval
Atoll enables you to design OFDM-based IEEE 802.11 WLAN networks. Atoll can predict radio coverage, evaluate network capacity, and analyse the amount of mobile traffic that can be offloaded from a mobile nework to a Wi-Fi network. Atoll uses Monte Carlo simulations to generate and analyse realistic network scenarios (snapshots) by carrying out scheduling and resource allocation. Realistic user distributions can be generated using different types of traffic maps and subscriber data. You can create coverage predictions to analyse received signal levels, signal quality, service areas, and throughputs in downlink and in uplink. Mobile (LTE, CDMA2000, UMTS, LTE, etc.) and Wi-Fi networks can be planned in the same Atoll session. New mobile access technologies, such as HSPA, HSPA+, and LTE, have triggered a significant increase in data traffic. Mobile operators are looking for viable solutions for delivering high speed data access with satisfactory QoS. Among many available options, Wi-Fi provides operators with a feasible approach for mobile network traffic offloading due to the following factors: • • • •
Numerous active Wi-Fi hotspots already exist, Most mobile devices support Wi-Fi in addition to mobile access technologies, Wi-Fi uses licence-free frequency bands, Wi-Fi is based on OFDM and uses the same hardware as LTE and LTE-Advanced.
Atoll Wi-Fi provides comprehensive Wi-Fi modelling with advanced traffic offload analysis features that enable operators to assess different traffic offloading options and make the right decision for their network.
13.1 Designing a Wi-Fi Network The steps involved in planning a Wi-Fi network are described below. 1. Open an existing radio-planning document or create a new one. • •
You can open an existing Atoll document by selecting File > Open. Creating a new Atoll document is explained in Chapter 2: Starting an Atoll Project.
2. Configure the network by adding network elements and changing parameters. •
"Creating a Wi-Fi Access Point" on page 1334.
You can also add access points using an access point template (see "Placing a New Access Point Using a Station Template" on page 1339). 3. Carry out basic coverage predictions. • •
"Making a Point Analysis to Study the Profile" on page 1347. "Studying Signal Level Coverage" on page 1348 and "Signal Level Coverage Predictions" on page 1357.
4. 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 traffic maps and subscriber lists (see "Studying Network Capacity" on page 1383).
1333
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
•
You can define cell load conditions manually either on the Cells tab of each transmitter’s Properties dialogue or in the Cells table (see "Creating or Modifying a Cell" on page 1339).
5. Make Wi-Fi-specific signal quality coverage predictions using the defined cell load conditions. •
"Wi-Fi Coverage Predictions" on page 1370.
6. If necessary, modify network parameters to study the network.
13.2 Planning and Optimising Wi-Fi Access Points As described in Chapter 2: Starting an Atoll Project, you can create an Atoll document from a template, with no access points, or from a database with an existing set of access points. As you work on your Atoll document, you will still need to create access points and modify existing ones. In Atoll, a site is defined as a geographical point where transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and its parameters. In a Wi-Fi project, you must also add cells to each transmitter. A cell refers to the characteristics of an RF channel on a transmitter. Atoll lets you create one site, transmitter, or cell at a time, or create several at once using station templates. In Atoll, an access point refers to a site and a transmitter with its antennas, equipment, and cells. In Atoll, you can study a single access point or a group of access points using coverage predictions. Atoll allows you to make a variety of coverage predictions, such as signal level or signal quality coverage predictions. The results of calculated coverage predictions can be displayed on the map, compared, and studied. Atoll enables you to model network traffic by creating services, users, user profiles, traffic environments, and terminals. This data can be then used to make coverage predictions that depend on network load, such as C/(I+N), service area, radio bearer, and throughput coverage predictions. In this section, the following are explained: • • • • • • • •
"Creating a Wi-Fi Access Point" on page 1334. "Creating a Group of Access Points" on page 1345. "Modifying Sites and Transmitters Directly on the Map" on page 1345. "Display Tips for Access Points" on page 1346. "Creating a Multi-band Wi-Fi Network" on page 1346. "Setting the Working Area of an Atoll Document" on page 1346. "Studying a Single Access Point" on page 1347. "Studying Access Points" on page 1350.
13.2.1 Creating a Wi-Fi Access Point When you create a site, you create only the geographical point; you must add the transmitters and cells afterwards. The site with a transmitter and its antennas and cells is called an access point. In this section, each element of an access point is described. If you want to add a new access point, see "Placing a New Access Point Using a Station Template" on page 1339. If you want to create or modify one of the elements of an access point, see "Creating or Modifying an Access Point" on page 1337. If you need to create a large number of access points, Atoll allows you to import them from another Atoll document or from an external source. For information, see "Creating a Group of Access Points" on page 1345. This section explains the various parts of the access point creation process: • • • • •
"Definition of an Access Point" on page 1334. "Creating or Modifying an Access Point" on page 1337. "Placing a New Access Point Using a Station Template" on page 1339. "Managing Station Templates" on page 1340. "Duplicating an Existing Access Point" on page 1344.
13.2.1.1 Definition of an Access Point An access point consists of the site, transmitters, antennas, and cells. You will usually create a new access point using a station template, as described in "Placing a New Access Point Using a Station Template" on page 1339. This section describes the following elements of an access point and their parameters: • • •
1334
"Site Description" on page 1335 "Transmitter Description" on page 1335 "Cell Description" on page 1337.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
13.2.1.1.1
Site Description The parameters of a site can be found in the site’s Properties dialogue. The Properties dialogue has the following tab: •
The General tab (see Figure 13.1): • •
Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If you want to change the default name that Atoll gives to new sites, see the Administrator Manual. Position: By default, Atoll places the new site at the centre of the map window. You can modify the location of the site here. While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 41.
•
•
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.
Figure 13.1: New Site dialogue
13.2.1.1.2
Transmitter Description The parameters of a transmitter can be found in the transmitter’s 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 1337), the Propagation tab (see Chapter 5: Working with Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 43). •
The General tab: •
•
•
•
Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You can enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names transmitters, see the Administrator Manual. Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can click the Browse button ( ) to access the properties of the site. For information on the site Properties dialogue, see "Site Description" on page 1335. You can click the New button to create a new site for the transmitter. Shared antenna: This field is used to identify the transmitters located at the same site or on sites with the same position and that share the same antenna. The entry in the field must be the same for all transmitters sharing the same antenna. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters defined as having a shared antenna. Under Antenna position, you can modify the position of the antennas: • •
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 this option if you want to enter the coordinates of the antenna, and then enter the x-axis and y-axis coordinates of the antenna, X and Y, respectively.
1335
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
•
© Forsk 2012
The Transmitter tab (see Figure 13.2):
Figure 13.2: Transmitter dialogue - Transmitter tab •
Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are displayed with a specific icon in the Transmitters folder of the Network explorer. Only active transmitters are taken into consideration during calculations.
•
Transmitter type: If you want Atoll to consider the transmitter as a potential server as well as an interferer, set the transmitter type to Intra-network (Server and interferer). If you want Atoll to consider the transmitter only as an interferer, set the type to Inter-network (Interferer only). No coverage for an interferer-only transmitter will be calculated for coverage predictions and it will not serve any mobile in Monte Carlo simulations. This enables you to model the co-existence of different networks in the same geographic area. For more information on how to study interference between co-existing networks, see "Modelling the Co-existence of Networks" on page 1430.
• •
Transmission/Reception: Under Transmission/Reception, you can set the total losses and the noise figure of the transmitter. Antennas: •
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site given by the DTM. If the transmitter is situated on a building, the height entered must include the height of building. Main antenna: Under Main antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens a dialogue displaying all the possible antennas based on the same physical antenna as the currently selected one. Selecting the Electrical tilt of the antenna model displays the appropriate antennas under Available antennas. Selecting the antenna under Available antennas and clicking OK assigns the antenna to the transmitter. The other fields, Azimuth, Mechanical downtilt, and Additional electrical downtilt, display additional antenna parameters. • • •
1336
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. The mechanical and additional electrical downtilts defined for the main antenna are also used for the calculations of smart antennas.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
•
13.2.1.1.3
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 1426.
Cell Description In Atoll, a cell is defined as an RF channel on a transmitter. When you create a transmitter, Atoll automatically creates a cell for the transmitter using the properties of the currently selected station template. The following explains the parameters of a Wi-Fi cell. You can, if you want, modify these parameters. The properties of a Wi-Fi cell are found on Cells tab of the Properties dialogue of the transmitter to which it belongs. 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. 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, see "Serving (Reference) Cell Layer Selection Method" on page 1431. BSID: The access point ID. Frequency band: The cell’s frequency band from the frequency band list. Channel number: The number of the channel from the list of available channels. Power (dBm): The cell’s transmission power over the frame. Min C/N (dB): The minimum C/N required for a user to be connected to the cell. Calculated C/N is compared with this threshold to determine whether or not a user can be connected to a cell. AMS threshold (dB): The C/N threshold for switching from SU-MIMO to STTD/MRC as the radio conditions get worse than the given value. For more information on Adaptive MIMO switching, see "Multiple Input Multiple Output Systems" on page 1426. Reception equipment: You can select the cell’s reception equipment from the reception equipment list. For more information, see "Defining Wi-Fi Reception Equipment" on page 1424. Max number of users: The maximum number of simultaneous users supported by the cell. Frame Configuration: The cell’s frame configuration selected from the list. For more information on frame configurations, see "Wi-Fi Frame Configurations" on page 1422. Max traffic load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a downlink traffic load greater than this maximum. Traffic load (DL) (%): The downlink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations. Max traffic load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink traffic load greater than this maximum. Traffic load (UL) (%): The uplink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations. 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. Inter-technology UL noise rise: This noise rise represents the interference created by the mobiles and access points of an external network on this cell on the uplink. This noise rise will be taken into account in all uplink interferencebased calculations involving this cell in Monte Carlo simulations. It is not used in predictions where Atoll calculates the uplink total interference from the uplink noise rise which includes inter-technology uplink interference. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 1428. 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 1428.
13.2.1.2 Creating or Modifying an Access Point An access point consists of the site, transmitters, and cells. This section describes how to create or modify the following elements of an access point: • • •
"Creating or Modifying a Site" on page 1338 "Creating or Modifying a Transmitter" on page 1338 "Creating or Modifying a Cell" on page 1339
1337
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
13.2.1.2.1
© Forsk 2012
Creating or Modifying a Site You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 1335, through the site’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create a new site: 1. Select the Network explorer. 2. Right-click the Sites folder. The context menu appears. 3. Select New from the context menu. The Sites: New Element Properties dialogue appears (see Figure 13.1 on page 1335). 4. Modify the parameters described in "Site Description" on page 1335. 5. Click OK. To modify the properties of an existing site: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Sites folder. 3. Right-click the site you want to modify. The context menu appears. 4. Select Properties from the context menu. The site’s Properties dialogue appears. 5. Modify the parameters described in "Site Description" on page 1335. 6. Click OK. If you are creating several sites at the same time, or modifying several existing sites, you can do it quickly by editing or pasting the data directly in the Sites table. You can open the Sites table by right-clicking the Sites folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
13.2.1.2.2
Creating or Modifying a Transmitter You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio Planning toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 1335, through the transmitter’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create a new transmitter: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select New from the context menu. The Transmitters: New Element Properties dialogue appears (see Figure 13.2). 4. Modify the parameters described in "Transmitter Description" on page 1335. 5. Click OK. When you create a new transmitter, Atoll automatically creates a cell based on the default station template. For information on creating a cell, see "Creating or Modifying a Cell" on page 1339. To modify the properties of an existing transmitter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Modify the parameters described in "Transmitter Description" on page 1335. 6. Click OK.
1338
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
•
•
13.2.1.2.3
If you are creating several transmitters at the same time, or modifying several existing transmitters, you can do it more quickly by editing or pasting the data directly in the Transmitters table. You can open the Transmitters table by rightclicking the Transmitters folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77. If you want to add a transmitter to an existing site on the map, you can add the transmitter by right-clicking the site and selecting New Transmitter from the context menu.
Creating or Modifying a Cell You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Description" on page 1337, through the Properties dialogue of the transmitter where the cell is located. How you access the Properties dialogue depends on whether you are creating a new cell or modifying an existing cell. To create or modify a cell: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Description" on page 1337. 7. Click OK. •
•
If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the Transmitters folder in the Network explorer and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 77), or import data into the table (see "Importing Tables from Text Files" on page 82). If you want to add a cell to an existing transmitter on the map, you can add the cell by right-clicking the transmitter and selecting New Cell from the context menu.
13.2.1.3 Placing a New Access Point Using a Station Template In Atoll, an access point is defined as a site with transmitters sharing the same properties. With Atoll, you can create a network by placing access points based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template: 1. In the Radio Planning toolbar, select a template from the list.
2. Click the New Transmitter or Station button (
) in the Radio Planning 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 pointer’s current location are visible in the status bar.
4. Click to place the station.
1339
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
•
•
To place the access point more accurately, you can zoom in on the map before you click the New Station button. For information on using the zooming tools, see "Changing the Map Scale" on page 49. If you let the pointer rest over the access point you have placed, Atoll displays its tip text with its exact coordinates, allowing you to verify that the location is correct.
You can also place a series of access points using a station template. You do this by defining an area on the map where you want to place the access points. Atoll calculates the placement of each access point according to the defined hexagonal cell radius in the station template. For information on defining the cell radius, see "Modifying a Station Template" on page 1341. To place a series of access points within a defined area: 1. In the Radio Planning toolbar, select a template from the list. 2. Click the Hexagonal Design button ( ), to the right of the template list. A hexagonal design is a group of access points created from the same station template. 3. Draw a zone delimiting the area where you want to place the series of access points: 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 access points and their hexagonal shapes. Access point 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 access points as you work with any access point object, adding, for example, another antenna to a transmitter. Placing a Station on an Existing Site When you place a new station using a station template as explained in "Placing a New Access Point Using a Station Template" on page 1339, the site is created at the same time as the station. However, you can also place a new station on an existing site. To place an access point on an existing site: 1. In the Network explorer, clear the display check box beside the Hexagonal Design folder. 2. In the Radio Planning toolbar, select a template from the list. 3. Click the New Transmitter or Station button (
) in the Radio Planning 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.
13.2.1.4 Managing Station Templates Atoll comes with Wi-Fi station templates, but you can also create and modify station templates. The tools for working with station templates can be found on the Radio Planning toolbar (see Figure 13.3).
Figure 13.3: The Radio Planning toolbar In this section, the following are explained: • • • • •
13.2.1.4.1
"Creating a Station Template" on page 1340 "Modifying a Station Template" on page 1341 "Copying Properties from One Station Template to Another" on page 1343 "Modifying a Field in a Station Template" on page 1343 "Deleting a Station Template" on page 1344.
Creating a Station Template When you create a station template, you can do so by selecting an existing station template that most closely resembles the station template you want to create and making a copy. Then you can modify the parameters that differ. To create a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder.
1340
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the Station Templates table, right-click the station template that most closely resembles the station template you want to create. The context menu appears. 6. Select Copy from the context menu. 7. Right-click the row marked with the New row icon (
). The context menu appears.
8. Select Paste from the context menu. The station template you copied in step 5. is pasted in the new row, with the Name of the new station template given as the same as the template copied but preceded by "Copy of". 9. Edit the parameters of the new station template in the table or as explained in "Modifying a Station Template" on page 1341.
13.2.1.4.2
Modifying a Station Template You can modify a station template directly in the Station Templates table, or you can open the Properties dialogue for that station template and modify the parameters in the dialogue. To modify a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. Right-click the station template you want to modify. The context menu appears. 6. Select Record Properties from the context menu. The station template’s Properties dialogue appears. 7. Click the General tab of the Properties dialogue. In this tab (see Figure 13.4), 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: 1st sector azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Height/ground of the antennas from the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of the building), the Mechanical downtilt, and the Additional electrical downtilt for the antennas. • •
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide.
Under Main antenna, you can select the main antenna Model, and under Number of MIMO Antennas, you can enter the number of antennas used for Transmission and for Reception for MIMO. •
•
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information on propagation models, see Chapter 5: Working with Calculations in Atoll. Under Comments, you can add additional information. The information you enter will be the default information in the Comments field of any transmitter created using this station template.
1341
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
Figure 13.4: Station Template Properties dialogue – General tab 8. Click the Transmitter tab. On this tab (see Figure 13.5), if the Active check box is selected, you can modify the following under Transmission/Reception: Total losses, Noise figure.
Figure 13.5: Station Template Properties dialogue – Transmitter tab 9. Click the Wi-Fi tab. On this tab (see Figure 13.6), you can modify the following: • •
Power, Frequency band, Reception equipment, Max number of users, Frame configuration, C/N threshold, and AMS threshold. You can assign a channel 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 channel number.
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 grid, assign a channel number to each cell. iv. Carry out the steps above to assign a channel number to each sector. v. Click OK. •
1342
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.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
•
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 1428.
Figure 13.6: Station Template Properties dialogue – Wi-Fi tab 10. 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. 11. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.
13.2.1.4.3
Copying Properties from One Station Template to Another You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the 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.
13.2.1.4.4
Modifying a Field in a Station Template You can add, delete, and edit user-defined data table fields in the Station Templates table. If you want to add a user-defined field to the station templates, you must have already added it to the Sites table for it to appear as an option in the station template properties To access the station templates data table field definition dialogue: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Properties from the context menu. The Station Template Properties dialogue appears. 5. Select the Table tab. 6. For information on adding, deleting, and editing user-defined fields, see "Adding, Deleting, and Editing Data Table Fields" on page 70). 7. When you have finished, Click OK.
1343
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
13.2.1.4.5
© Forsk 2012
Deleting a Station Template To delete a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Station Templates folder. 4. In the Station Templates folder, right-click the station template you want to delete. The context menu appears. 5. Select Delete from the context menu. The template is deleted.
13.2.1.5 Duplicating an Existing Access Point You can create new access points by duplicating an existing access point. When you duplicate an existing access point, the access point you create will have the same transmitter, and cell parameter values as the original access point. If no site exists where you place the duplicated access point, Atoll will create a new site with the same parameters as the site of the original access point. Duplicating an access point allows you to: • •
Quickly create a new access point with the same settings as an original one in order to study the effect of a new station on the coverage and capacity of the network, and Quickly create a new homogeneous network with access points that have the same characteristics.
To duplicate an existing access point: 1. Select the Network explorer. 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 Duplicate. 5. Place the new access point on the map using the mouse: •
Creating a duplicate access point and site: In the map window, move the pointer over the map to where you would like to place the duplicate. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 13.7).
Figure 13.7: Creating a duplicate access point and site •
Placing the duplicate access point on an existing site: In the map window, move the pointer over the existing site where you would like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 13.8).
Figure 13.8: Placing a new access point •
•
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 49. 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 access point. A new access point is placed on the map. If the duplicate access point was placed on a new site, the site, transmitters, and cells of the new access point have the same names as the site, transmitters, and cells of the original access point
1344
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
with each name marked as "Copy of." The site, transmitters, and cells of the duplicate access point have the same settings as those of the original access point. If the duplicate access point was placed on an existing site, the transmitters, and cells of the new access point have the same names as the transmitters, and cells of the original access point with each name preceded by the name of the site on which the duplicate was placed. You can also place a series of duplicate access points 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 an Access Point" on page 1334.
13.2.2 Creating a Group of Access Points You can create access points individually as explained in "Creating a Wi-Fi Access Point" on page 1334, or you can create one or several access points by using station templates as explained in "Placing a New Access Point Using a Station Template" on page 1339. However, if you have a large project and you already have existing data, you can import this data into your current Atoll document and create a group of access points. 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 121. You can import access point 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 access points by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. The table you copy from must have the same column layout as the table you are pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77. •
Importing data: If you have access point data in text or comma-separated value (CSV) format, you can import it into the tables in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of access points by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80. For information on importing table data, see "Importing Tables from Text Files" on page 82.
13.2.3 Modifying Sites and Transmitters Directly on the Map In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu in the Network explorer. However, in a complex radio-planning project, it can be difficult to find the data object in the Network explorer, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. You can also select a site to display all of the transmitters located on it in the Site Configuration window. When selecting a transmitter, if there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: • • • • • •
"Working with the Site Configuration Window" on page 37 "Selecting One of Several Transmitters" on page 41 "Moving a Site Using the Mouse" on page 41 "Moving a Site to a Higher Location" on page 42 "Changing the Azimuth of the Antenna Using the Mouse" on page 42 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42.
1345
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
13.2.4 Display Tips for Access Points Atoll allows to you to display information about access points in a number of ways. This enables you not only to display selected information, but also to distinguish access points at a glance. The following tools can be used to display information about access points: •
•
•
•
Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object type’s data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information in the label will make it harder to distinguish the information you are looking for. For information on defining the label, see "Defining the Object Type Label" on page 46. Tip text: You can display information about each object, such as each site or transmitter, in the form of tip text that is only visible when you move the pointer over the object. You can choose to display more information than in the label, because the information is only displayed when you move the pointer over the object. You can display information from any field in that object type’s data table, including from fields that you add. For information on defining the tip text, see "Defining the Object Type Tip Text" on page 46. Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example, you can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active transmitters. You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns a colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding it. For information on defining the transmitter colour, see "Defining the Display Type" on page 44. Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can select a symbol that graphically represents the antenna half-power beamwidth (
). If you have two transmitters on the
same site with the same azimuth, you can differentiate them by selecting different symbols for each ( For information on defining the transmitter symbol, see "Defining the Display Type" on page 44.
and
).
13.2.5 Creating a Multi-band Wi-Fi Network In Atoll, you can model a multi-band Wi-Fi network, for example, a network consisting of 2.4 GHz and 5 GHz cells, in one document. Creating a multi-band Wi-Fi network consists of the following steps: 1. Defining the frequency bands in the document (see "Defining Frequency Bands" on page 1421). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Working with Calculations in Atoll). 3. Assigning a frequency band to each cell and a relevant propagation model to each transmitter (see "Creating or Modifying a Cell" on page 1339 and "Creating or Modifying a Transmitter" on page 1338).
13.2.6 Setting the Working Area of an Atoll Document You can restrict a coverage prediction to the access points that you are interested in and calculate only the results you need. In Atoll, there are two ways of restricting the number of access points covered by a coverage prediction, each with its own advantages: •
Filtering the desired access points You can simplify the selection of access points to be studied by using a filter. You can filter access points according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 107. This enables you to keep only the access points with the characteristics you want for your calculations. The filtering zone is taken into account whether or not it is visible. For information on filtering, see "Filtering Data" on page 95.
•
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 can not be significant. In a larger project, especially when you are making repeated predictions in order to see the effects of small changes in site configuration, the savings in time is considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus zone or hot spot is the area taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 1355.
You can combine a computation zone and a filter, in order to create a very precise selection of the access points to be studied.
1346
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
13.2.7 Studying a Single Access Point As you create an access point, you can study it to test the effectiveness of the set parameters. You can later expand your coverage prediction to a number of access points once you have optimised the settings for each individual access point. Before studying an access point, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates propagation losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Any coverage prediction you make on an access point uses the propagation model to calculate its results. In this section, the following are explained: • •
"Making a Point Analysis to Study the Profile" on page 1347. "Studying Signal Level Coverage" on page 1348.
13.2.7.1 Making a Point Analysis to Study the Profile In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a user. Before studying an access point, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on the selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 1353. You can make a point analysis to study the reception in real time along a profile between a reference transmitter and a Wi-Fi user, and the interference along a profile between a reference transmitter and a user. To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis button ( pointer changes (
) in the Radio Planning toolbar. The Point Analysis window appears and the
) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: • • •
Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: • Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. • Target Site: Select a site from the list to place the receiver directly on a site.
4. Select the Profile view. The profile analysis appears in the Profile view of the Point Analysis 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 can 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 view: • • • •
The received signal strength from the selected transmitter for the cell with the highest power The propagation model used The shadowing margin and the indoor loss (if selected) The distance between the transmitter and the receiver.
You can change the following options using the Profile view toolbar: •
Transmitter: Select the transmitter from the list. You can click the Properties button ( properties dialogue.
•
Options: Click the Options button ( • • • •
•
) to open the transmitter
) to display the Calculation Options dialogue. In this dialogue, you can:
Change the X and Y coordinates to change the current position of the receiver. Select the Shadowing taken into account check box and enter a Cell edge coverage probability. Select Signal level, Path loss, or Total losses from the Result type list. You can select the Indoor coverage check box to add indoor losses.
Geographic Profile: Click the Geographic Profile button ( ) if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter
1347
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate or display signal levels and losses. •
Link Budget: Click the Link Budget button (
•
Detailed Report: Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis. The detailed report is only available for the Standard Propagation Model.
) to display a dialogue with the link budget.
You can select a different transmitter.
Displays data, including received signal, shadowing margin, cell edge coverage probability, propagation model used, and transmitter-receiver distance.
Fresnel ellipsoid
Line of sight
Attenuation with diffraction
Figure 13.9: Point Analysis - Profile view 5. To end the point analysis, click the Point Analysis button (
) in the Radio Planning toolbar again.
13.2.7.2 Studying Signal Level Coverage As you are building your radio-planning project, you might want to check the coverage of a new access point without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single access point. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. For a transmitter with more than one cell, the signal level is calculated for the cell with the highest power. You can use the same procedure to study the signal level coverage of several access points by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 89. To study the signal level coverage of a single access point: 1. Select the Network explorer. 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. If you want to study only sites by their status, at this step you could group them by status.
3. Select the propagation parameters to be used in the coverage prediction: 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.
1348
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
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 Prediction from the context menu. The Prediction Types dialogue appears. The Prediction Types dialogue lists the coverage prediction types available. They are divided into Standard Predictions, supplied with Atoll, and Customised Predictions. Unless you have already created some customised predictions, the Customised Predictions list will be empty. 5. Select Coverage by Signal Level and click OK. A coverage prediction 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. If you create a new coverage prediction from the context menu of the Predictions folder, you can select the sites using the Group By, Sort, and Filter buttons under Display configuration. However, if you create a new coverage prediction from the context menu of the Transmitters folder, only the Filter button is available, because, by creating a coverage prediction directly from the Transmitters folder, you have effectively already selected the target sites.
•
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 13.10). • •
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 13.10: Condition settings for a coverage prediction by signal level •
Display tab: You can modify how the results of the coverage prediction will be displayed. •
Under Display type, select "Value intervals."
1349
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
• •
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 43.
•
You can create tip text with information about the coverage prediction by clicking the Browse button ( next to the Tip text box and selecting the fields you want to display in the tip text. You can select the Add to legend check box to add the displayed value intervals to the legend.
•
)
If you change the display properties of a coverage prediction after you have calculated it, you can make the coverage prediction invalid. You will then have to recalculate the coverage prediction to obtain valid results. 7. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the 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 in the Network explorer. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button (
) beside the coverage prediction in the Predictions
), Atoll only calculates unlocked coverage predictions (
).
13.2.8 Studying Access Points When you make a coverage prediction, Atoll calculates all access points that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects the rectangle containing the computation zone. Figure 13.11 gives an example of a computation zone. In Figure 13.11, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction. Site 130 is within the coverage zone but has no active transmitters. Therefore, it will not be taken into consideration either.
1350
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Figure 13.11: 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 13.11) 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 1351. "Assigning a Propagation Model" on page 1353. "The Calculation Process" on page 1355. "Creating a Computation Zone" on page 1355. "Setting Transmitters or Cells as Active" on page 1356. "Signal Level Coverage Predictions" on page 1357. "Analysing a Coverage Prediction" on page 1361. "Wi-Fi Coverage Predictions" on page 1370. "Printing and Exporting Coverage Prediction Results" on page 1382.
13.2.8.1 Path Loss Matrices In addition to the distance between the transmitter and the received, path loss is caused by objects in the transmitter-receiver path. In Atoll, the path loss matrices must be calculated before predictions and simulations can be made. Storing Path Loss Matrices Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radioplanning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning project. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: • • •
One file per transmitter with the extension LOS for its main path loss matrix. 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.
1351
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
To set the storage location of the path loss matrices: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions 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 Private directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally. Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private directory.
When you save the path loss files externally, the external files are updated as soon as calculations are performed. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it if you have updated the path loss matrices. •
Shared directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see the Administrator Manual.
5. Click OK. Checking the Validity of Path Loss Matrices Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available results table. You have the following display options: • •
Display all the matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available results table lists the following information for each displayed path loss matrix: • • • • • •
Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a Boolean field indicating whether or not the path loss matrix is valid. 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.
5. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 13.12) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.
1352
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Figure 13.12: Path loss matrices statistics
13.2.8.2 Assigning a Propagation Model In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used as for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 1354, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 1354, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 1353, this is the propagation model that will be used for all transmitters, except for those to which you will later assign a propagation model either individually or as part of a group. When you assign a propagation model globally, you override any selection you might have made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 201, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following are explained: • • •
"Assigning a Propagation Model to All Transmitters" on page 1353. "Assigning a Propagation Model to a Group of Transmitters" on page 1354. "Assigning a Propagation Model to One Transmitter" on page 1354.
For more information about the available propagation models, see Chapter 5: Working with Calculations in Atoll. Assigning a Propagation Model to All Transmitters In Atoll, you can choose a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 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.
1353
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
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. Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 1354 will override this entry.
Assigning a Propagation Model to a Group of Transmitters Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters and then assigning the propagation model. To define a main and extended propagation model for a defined group of transmitters: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. From the Group By submenu of the context menu, select the property by which you want to group the transmitters. The objects in the folder are grouped by that property. You can group transmitters by several properties by using the Group By button on the Properties dialogue. For more information, see "Advanced Grouping" on page 90.
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 Main resolution Extended propagation model Extended calculation radius Extended resolution
To enter the same values in one column for all transmitters in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button (
) in the Table toolbar. For more information on working with tables in Atoll,
see "Working with Data Tables" on page 69. Assigning a Propagation Model to One Transmitter If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previously made globally.
1354
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Transmitters folder. 3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main matrix: • •
Select a Propagation model. Enter a Radius and Resolution.
7. If desired, under Extended matrix: • •
Select a Propagation model. Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter. 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.
13.2.8.3 The Calculation Process When you create a coverage prediction and click the Calculate button (
), Atoll follows the following process:
1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button (
).
3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( Predictions folder. •
You can stop any calculations in progress by clicking the Stop Calculations button (
•
) beside the coverage prediction in the
) in the Radio Planning toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.
13.2.8.4 Creating a Computation Zone To create a computation zone: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Computation Zone. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the zone.
ii. Click once on the map to define each point on the map where the border of the zone changes direction. iii. Click twice to finish drawing and close the zone. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the zone.
1355
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
ii. Drag to the opposite corner of the rectangle that will define the zone. When you release the mouse, the zone will be created from the rectangle defined by the two corners. The computation zone is delimited by a red line. If you clear the computation zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a computation zone with one of the following methods: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor 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. You can also combine an existing computation zone with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Computation Zone from the context menu. 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 in the Geo explorer and selecting Import from the context menu. Fit Zone to Map Window: You can create a computation zone the size of the map window by right-clicking the Computation Zone in the Geo explorer and selecting Fit Zone to Map Window from the context menu. You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the computation zone in the user configuration: For information on saving the computation zone in the user configuration, see "Saving a User Configuration" on page 101. Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone in the Geo explorer and selecting Export from the context menu.
13.2.8.5 Setting Transmitters or Cells as Active When you make a coverage prediction, Atoll considers all access points that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Therefore, before you define a coverage prediction, you must ensure that all the transmitters on the access points you want to study have been activated. In the explorer window, active transmitters are indicated with an on icon (
) in the Transmitters
folder and with the defined colour on the map and inactive transmitters are indicated with an off icon ( ters folder and empty symbol on the map.
) in the Transmit-
In Atoll, you can also set the cell on a transmitter as active or inactive. You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by activating them from the Transmitters context menu, by activating the transmitters’ cells from the Cells table, or by selecting the transmitters with a zone and activating them from the zone’s context menu. To set an individual transmitter as active: 1. Select the Network explorer. 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. Select the Network explorer. 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 rightclick the group of transmitters you want to set as active. The context menu appears.
3. Select Activate Transmitters from the context menu. The selected transmitters are set as active. To set more than one transmitter as active using the Transmitters table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Open Table. The Transmitters table appears with each transmitter’s parameters in a row. 4. For each transmitter that you want to set as active, select the check box in the Active column.
1356
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
To set more than one cell as active using the Cells table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cell’s 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. Select the Geo explorer. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder. 3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 54.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Working with Calculations in Atoll. Calculating path loss matrices can be 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.
13.2.8.6 Signal Level Coverage Predictions Atoll offers a series of standard coverage predictions based on the measured signal level at each pixel; other factors, such as interference, are not taken into consideration. Coverage predictions specific to Wi-Fi are covered in "Wi-Fi Coverage Predictions" on page 1370. Once you have created and calculated a coverage prediction, you can use the coverage prediction’s context menu to make the coverage prediction into a customised prediction which will appear in the Prediction Types dialogue. You can also select Duplicate from the coverage prediction’s context menu to create a copy. By duplicating an existing prediction that has the parameters you want to study, you can create a new coverage prediction more quickly than by creating a new coverage prediction. If you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the coverage prediction with the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the calculated coverage prediction. You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to load it into a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predictions are saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations, see "Saving a User Configuration" on page 101. The following standard coverage predictions are explained in this section: • • •
13.2.8.6.1
"Making a Coverage Prediction by Signal Level" on page 1357 "Making a Coverage Prediction by Transmitter" on page 1358 "Making a Coverage Prediction on Overlapping Zones" on page 1359.
Making a Coverage Prediction by Signal Level A coverage prediction by signal level allows you to predict coverage zones by the transmitter signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest power. To make a coverage prediction by signal level: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage
1357
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 13.13). On the Condition tab, you can define the signals that will be considered for each pixel. • •
At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration.
• •
If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 13.13: 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 43. 8. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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.
13.2.8.6.2
Making a Coverage Prediction by Transmitter A coverage prediction by transmitter allows the user to predict coverage zones by transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest power. To make a coverage prediction by transmitter: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears.
1358
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group by button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Condition tab (see Figure 13.14). On the Condition tab, you can define the signals that will be considered for each pixel. • •
At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration.
• •
If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 13.14: 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 43. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
13.2.8.6.3
Making a Coverage Prediction on Overlapping Zones Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction on overlapping zones on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest power.
1359
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
To make a coverage prediction on overlapping zones: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 13.15). On the Condition tab, you can define the signals that will be considered for each pixel. • •
At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration.
• •
If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 13.15: 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 43. When creating a coverage prediction displaying the number of servers, you can not export the values per pixel.
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
1360
) on the Radio Planning toolbar.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
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.
13.2.8.7 Analysing a Coverage Prediction Once you have completed a prediction, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 1348). If several coverage predictions are visible on the map, it can be difficult to clearly see the results of the coverage prediction you want to analyse. You can select which predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following tools are explained: • • • • • • •
13.2.8.7.1
"Displaying the Legend Window" on page 1361. "Displaying Coverage Prediction Results Using the Tip Text" on page 1361. "Using the Point Analysis Reception View" on page 1361. "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1363. "Displaying a Coverage Prediction Report" on page 1363. "Viewing Coverage Prediction Statistics" on page 1365. "Comparing Coverage Predictions: Examples" on page 1366.
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to legend check box on the Display tab. To display the Legend window: •
13.2.8.7.2
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction identified by the name of the coverage prediction.
Displaying Coverage Prediction Results Using the Tip Text You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 1348). To get coverage prediction results in the form of tip text: •
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined in the Display tab of the coverage prediction properties (see Figure 13.16).
Figure 13.16: Displaying coverage prediction results using tip text
13.2.8.7.3
Using the Point Analysis Reception View Once you have calculated the coverage prediction, you can use the Point Analysis tool. At any point on the map, the Reception view gives you information on the signal levels, C/(I+N), bearers, and throughputs, etc. The analysis is provided for a userdefinable probe receiver which has a terminal, a mobility, and a service. The analysis is based on: •
• • •
The signal levels, used to determine the best server for the pixel. The best serving transmitter is determined according to the received signal level from the cell with the highest power. If more than one cell covers the pixel, the one with the highest layer is selected as the serving (reference) cell. The C/N, used to determine whether SU-MIMO or STTD/MRC is used for AMS. The downlink traffic loads, used to determine the downlink C/(I+N), bearer, and throughputs. The uplink noise rise values, used to determine the uplink C/(I+N), bearer, and throughputs.
1361
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
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. If so, before you make the reception 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 (
) on the Radio Planning toolbar. The Point Analysis window appears (see
Figure 13.17) and the pointer changes (
) to represent the receiver.
2. Select the Reception view. 3. At the top of the Reception view, select "Cells table" from Load. 4. Select the signal to be displayed from the Display list. 5. 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. Click the Options button ( ) in the Reception view toolbar to display the Calculation Options dialogue. The Calculation Options 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.
c. Click OK to close the Calculation Options dialogue. 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. The line from the pointer to its best server is slightly thicker than the other lines. The best server of the pointer is the transmitter from which the pointer receives the highest 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. Select the load conditions to use in this analysis from simulations or from the Cells table.
The signal level from the best server (top-most bar) and all interfering cells. Solid bars indicate signal levels above the C/N threshold.
The connection status for the current point. : Successful : Failed
Select the parameters of the probe user to be studied. Figure 13.17: Point analysis tool: Reception view The bar graph displays the following information: • • •
The signal levels or C/N (depending on the selection made from the Display list) from different transmitters (the colour of the bar corresponds to the colour of the transmitter on the map). The C/N thresholds: The empty portion of the bar indicates signal levels below the C/N thresholds. The availability of coverage and service in downlink and uplink.
If there is at least one successful connection, double-clicking the icons in the right-hand frame opens a dialogue with additional information about the best server: • • •
General: Azimuth and tilt of the receiver, and path losses. Downlink: Diversity mode, received power, total noise, C/(I+N), bearer, channel throughputs, and cell capacities. Uplink: Diversity mode, received power, transmission power, total noise, C/(I+N), bearer, channel throughputs, and cell capacities.
To get all this information in a single report: •
1362
Click the Report button in the Reception view toolbar. The Analysis Report dialogue appears.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
8. Click the Point Analysis button (
13.2.8.7.4
) on the Radio Planning toolbar again to end the point analysis.
Creating a Focus Zone or Hot Spot for a Coverage Prediction Report The focus and hot spots define the area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spots in addition to the focus zone. It is important not to confuse the computation zone and the focus and hot spots. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus and hot spots are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spots. To define a focus zone or hot spot: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Focus Zone or Hot Spots folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the focus zone or hot spot.
ii. Click once on the map to define each point on the map where the border of the focus zone or hot spot changes direction. iii. Click twice to finish drawing and close the focus zone or hot spot. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the focus zone or hot spot.
ii. Drag to the opposite corner of the rectangle that will define the focus zone or hot spot. When you release the mouse, the focus zone or hot spot will be created from the rectangle defined by the two corners. A focus zone is delimited by a green line; a hot spot is delimited by a heavy black line. If you clear the zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot by right-clicking it and selecting Use As > Focus Zone or Use As > Hot Spot from the context menu. You can also combine an existing focus zone or hot spot with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Focus Zone or Add To > 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. You can import it by right-clicking the Focus Zone or Hot Spots folder in the Geo explorer and selecting Import from the context menu. When you import hot spots, you can import the name given to each zone as well. Fit Zone to Map Window: You can create a focus or hot spot the size of the map window by selecting Fit Zone to Map Window from the context menu. •
You can save the focus zone or hot spots, so that you can use it in a different Atoll document, in the following ways: •
•
13.2.8.7.5
Saving the focus zone in the user configuration: For information on saving the focus zone in the user configuration, see "Saving a User Configuration" on page 101. • Exporting the focus zone or hot spots: You can export the focus zone or hot spots by right-clicking the Focus Zone or the Hot Spots folder in the Geo explorer and selecting Export from the context menu. You can include population statistics in the focus or hot spot by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137.
Displaying a Coverage Prediction Report Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage prediction’s Properties dialogue.
1363
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
The coverage prediction report is displayed in a table. For information on working with tables, see "Working with Data Tables" on page 69. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 74. Atoll bases the report on the area covered by the focus zone and hot spots; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot must be defined before you display a report; it is not necessary to define it before calculating coverage. The focus zone or hot spot does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1363. Once you have generated a report, you can export it to a text file or to an Excel spreadsheet. For more information on exporting a coverage prediction report, see "Exporting a Coverage Prediction Report" on page 1365. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Select the Network explorer. 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 up or
to move it down. You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spots and on the focus zone if available or on the hot spots and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Select the Network explorer. 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 up or
to move it down. You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied.
1364
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spots by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137. Normally, Atoll takes all geographic data into consideration, whether it is displayed or not. However, for the population statistics to be used in a report, the population map has to be displayed. To include population statistics in the focus zone or hot spots: 1. Ensure that the population geographic data is visible. For information on displaying geographic data, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. 2. Select the Network explorer. 3. Right-click the Predictions folder. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Select the following columns, where "Population" is the name of the folder in the Geo explorer 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.
6. Click OK. Atoll saves the names of the columns you select and will automatically select them the next time you create a coverage prediction report. 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 154.
13.2.8.7.6
Exporting a Coverage Prediction Report Once you have generated a coverage prediction report as explained in "Displaying a Coverage Prediction Report" on page 1363, you can export it to a text file or to a spreadsheet. To export a coverage prediction report: 1. Right-click the report and select Export from the context menu or click the Export button ( The Save As dialogue appears.
) in the Table toolbar.
2. In the Save As dialogue, enter the File name and select the format from the Save as type list: • • • •
TXT: To save the report as a text file. CSV: To save the report as a comma-separated values file. XLS: To save the report as an Excel spreadsheet. XML spreadsheet 2003: To save the report as an XML spreadsheet.
3. Click Save to export the coverage prediction report.
13.2.8.7.7
Viewing Coverage Prediction Statistics Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage prediction colours, interval steps, and shading as defined on the Display tab of the coverage prediction’s Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spots are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before calculating coverage. For information on defining a focus zone, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1363.
1365
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
To display the statistics on a coverage prediction: 1. Select the Network explorer. 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 13.18). • •
• • •
Under Histogram based on covered areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Zoom on selected values section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics based on prediction conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.
Figure 13.18: Histogram of a coverage prediction by signal level
13.2.8.7.8
Comparing Coverage Predictions: Examples Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison in one of the following ways: • •
•
Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both predictions are displayed in red). Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and pixels covered by only one prediction are blue). Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for example, pixels covered by both predictions are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).
To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction.
1366
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
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 Access Point" on page 1367 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 1368.
Example 1: Studying the Effect of a New Access Point If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can verify if a newly added access point improves coverage. A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 1357. The results are displayed in Figure 13.19. An area with poor coverage is visible on the right side of the figure.
Figure 13.19: Signal level coverage prediction of existing network A new access point is added, either by creating the access point and adding the transmitters, as explained in "Creating a WiFi Access Point" on page 1334, or by placing a station template, as explained in "Placing a New Access Point Using a Station Template" on page 1339. 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 access point (see Figure 13.20).
Figure 13.20: Signal level coverage prediction of network with new access point Now you can compare the two predictions.
1367
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
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 access point made, you should choose Difference. 5. Click OK to create the comparison. The comparison in Figure 13.21, shows clearly the area covered only by the new access point.
Figure 13.21: Comparison of both signal level coverage predictions Example 2: Studying the Effect of a Change in Transmitter Tilt If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can see how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 1358. The results are displayed in Figure 13.22. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated by a red oval in Figure 13.22.
1368
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Figure 13.22: 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 13.23).
Figure 13.23: 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.
1369
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
5. Click OK to create the comparison. The comparison in Figure 13.24, shows clearly the increase in coverage due at the change in antenna tilt.
Figure 13.24: Comparison of both transmitter coverage predictions
13.2.8.8 Wi-Fi Coverage Predictions Two types of Wi-Fi coverage predictions are available in Atoll: coverage predictions used to analyse the effective signal levels, and coverage predictions used to analyse the signal quality. Effective signal analysis coverage predictions can be used to analyse signal levels in downlink and uplink with the user-end gains and losses considered. These coverage predictions do not depend on the network load conditions. The cell coverage areas for these predictions are only limited by the cell C/N thresholds. 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. The cell coverage areas for signal quality, service area, throughput, and quality indicator predictions are limited by both the cell C/N thresholds and the bearer selection thresholds of the lowest available bearer. For the purposes of these coverage predictions, each pixel is considered a non-interfering user with a defined service, mobility type, and terminal. These are explained in the following section: •
"Service and User Modelling" on page 1370.
This section explains the coverage predictions available for analysing the effective signal level and signal quality: • •
"Analysing the Effective Signal Levels" on page 1372. "Analysing the Signal Quality" on page 1373.
You can also use the Point Analysis tool 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: •
13.2.8.8.1
"Analysing Interference Areas Using a Point Analysis" on page 1381.
Service and User Modelling Atoll can base its signal quality coverage predictions on the DL traffic loads and the UL noise rise entered in the Cells table (for more information, see "Setting the Traffic Loads and the UL Noise Rise" on page 1374). Before you can model services, you must define Wi-Fi radio bearers. For more information on Wi-Fi radio bearers, see "Defining Wi-Fi Radio Bearers" on page 1423. In this section, the following are explained: • • •
"Modelling Services" on page 1370. "Modelling Mobility Types" on page 1371. "Modelling Terminals" on page 1372.
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: • • • •
1370
Highest bearer Lowest bearer Throughput scaling factor Throughput offset
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
•
Body loss
To create or modify a service: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services: New Element Properties dialogue appears. You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.
5. 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 the service during Monte Carlo simulations. For Voice services, this parameter is used when working with sector traffic maps and user density traffic maps. For Data services, Atoll distributes the users according to the activity factors when importing user density traffic maps for all activity statuses. Highest bearer: Select the highest bearer that the service can use in the uplink and downlink. This is considered as an upper limit during bearer determination. Lowest bearer: Select the lowest bearer that the service can use in the uplink and downlink. This is considered as a lower limit during bearer determination. Max throughput demand: Enter the highest throughput that the service can demand in the uplink and downlink. 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 MAC (Medium Access Control) throughput and a throughput Offset. These parameters model the header information and other supplementary data that does not appear at the application level. The application throughput parameters are used in throughput coverage predictions and for application throughput calculation.
•
Body loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For example, in a voice connection the body loss, due to the proximity of the user’s head, is estimated to be 3 dB.
6. Click OK. Modelling Mobility Types In Wi-Fi, information about the receiver mobility is required for determining which bearer selection threshold and quality graph to use from the reception equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking speeds do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely dependent on mobile speed. To create or modify a mobility type: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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.
1371
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
•
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 Wi-Fi, a terminal is the user equipment that is used in the network. To create or modify a terminal: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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. Reception equipment: Select a reception equipment from the list of available equipment. For more information on reception equipment, see "Defining Wi-Fi Reception Equipment" on page 1424. 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. 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. Diversity support: Select whether terminal supports MIMO or not. Under MIMO, enter the Number of transmission antennas and the Number of reception antennas available in the terminal.
6. Click OK.
13.2.8.8.2
Analysing the Effective Signal Levels Atoll offers a couple of Wi-Fi coverage predictions which can be based on the predicted signal level from the best server and the thermal background noise at each pixel, i.e., received carrier power (C) and the carrier-to-noise ratio (C/N). This section explains the coverage predictions available for analysing the effective signal levels. Atoll calculates the serving transmitter for each pixel depending on the downlink signal level. The serving transmitter is determined according to the received signal level from the cell with the highest power. In a prediction for the "Best" layer, if more than one cell covers the pixel, the one with the highest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the effective signal level or C/N. Pixels are coloured if the display threshold condition is fulfilled. To make an effective signal analysis coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Effective Signal Analysis (DL) or Effective Signal Analysis (UL) and click OK. The coverage prediction’s Properties dialogue appears. 5. Click the General tab.
1372
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 13.25). On the Condition tab, you can select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The effective signal analysis coverage prediction is always a best server coverage prediction. The Noise figure defined in the terminal type’s 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 reception equipment, see "Modelling Services" on page 1370, "Modelling Terminals" on page 1372, "Modelling Mobility Types" on page 1371, and "Defining Wi-Fi Reception Equipment" on page 1424, respectively. If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. The shadowing margin for the effective signal analysis calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor coverage into consideration.
Figure 13.25: Condition settings for an effective signal analysis coverage prediction 7. Click the Display tab. 8. From the Display type list, select "Value intervals" to display the coverage prediction by signal levels or C/N levels. For information on adjusting the display, see "Display Properties of Objects" on page 43. 9. Click the Result Export tab. If, on the Display tab, you have selected to display the results by value intervals and, if you are not displaying the results by the number of servers, you can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
13.2.8.8.3
Analysing the Signal Quality In Wi-Fi, the capacity and the effective service coverage areas of cells are influenced by network loads. As the network load increases, the area where a cell provides service decreases. For this reason, network loads must be defined in order to calculate these coverage predictions. Atoll offers a series of coverage predictions which are based on the predicted signal level from the best server and the predicted signal levels from other cells (interference) at each pixel, i.e., carrier-to-interference-and-noise ratio, or C/(I+N). The downlink interference received from different cells of the network is weighted by their respective downlink traffic loads. The measure of uplink interference for each cell is provided by the uplink noise rise.
1373
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
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 1374.
Several signal quality coverage predictions are explained in this section. The following coverage predictions are explained: • • • • • • •
"Making a Coverage Prediction by C/(I+N) Level" on page 1374. "Making a Downlink or Uplink Service Area Analysis" on page 1376. "Studying the Effective Service Area" on page 1377. "Making a Coverage Prediction by Throughput" on page 1378. "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1380. "Making a Coverage Prediction by Quality Indicator" on page 1380. "Analysing Interference Areas Using a Point Analysis" on page 1381.
Setting the Traffic Loads and the UL Noise Rise If you are setting the traffic loads and the uplink noise rise for a single transmitter, you can set these parameters on the Cells tab of the transmitter’s Properties dialogue. However, you can set the traffic loads and the uplink noise rise for all the cells using the Cells table. To set the traffic loads and the uplink noise rise using the Cells table: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Enter a value in the following columns: • •
Traffic load (DL) (%) UL noise rise (dB)
Although, you can also set a value for the Traffic load (UL) (%) column as an indication of cells’ uplink loads, this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink is given by the uplink noise rise values. For a definition of the values, see "Cell Description" on page 1337. To enter the same values in one column for all cells in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69. Making a Coverage Prediction by C/(I+N) Level Downlink and uplink coverage predictions by C/(I+N) level predict the interference levels and signal-to-interference levels in the part of the network being studied. Atoll calculates the best server for each pixel depending on the downlink signal level. The serving transmitter is determined according to the received signal level from the cell with the highest power. In a prediction for the "Best" layer, if more than one cell covers the pixel, the one with the highest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the interference from other cells, and finally calculates the C/(I+N). The pixel is coloured if the display threshold condition is fulfilled. Coverage prediction by C/(I+N) level calculates the co-channel interference as well as the adjacent channel interference, which is reduced by the adjacent channel suppression factor defined in the Frequency Bands table. For more information on frequency bands, see "Defining Frequency Bands" on page 1421.
1374
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
To make a coverage prediction by C/(I+N) level: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 13.26). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the cell loads stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The C/(I+N) coverage prediction is a best server coverage prediction. The Noise figure defined in the terminal type’s 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 reception equipment, see "Modelling Services" on page 1370, "Modelling Terminals" on page 1372, "Modelling Mobility Types" on page 1371, and "Defining Wi-Fi Reception Equipment" on page 1424, 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 13.26: Condition settings for a coverage prediction by C/(I+N) level 7. Click the Display tab. 8. From the Display type list, select "Value intervals" to display the coverage prediction by C/(I+N) levels or total noise (I+N) levels. For information on adjusting the display, see "Display Properties of Objects" on page 43.
1375
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
9. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Making a Downlink or Uplink Service Area Analysis Downlink and uplink service area analysis coverage predictions calculate and display the Wi-Fi radio bearers based on C⁄(I+N) for each pixel. In the coverage predictions, the downlink or uplink service areas are limited by the bearer selection thresholds of the highest and lowest bearers of the selected service. To make a coverage prediction on service area: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Service Area Analysis (DL) or Service Area Analysis (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 13.27). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the downlink traffic load, uplink noise rise values, and any angular distributions of interference stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The best bearer coverage prediction is always based on the best server. The Noise figure defined in the terminal type’s 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 reception equipment. This reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection threshold graph to use. You can make Atoll use only the bearers for which selection thresholds are defined in both the terminal’s and the cell’s reception equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1370, "Modelling Terminals" on page 1372, "Modelling Mobility Types" on page 1371, and "Defining Wi-Fi Reception Equipment" on page 1424, 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.
1376
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Figure 13.27: Condition settings for a coverage prediction on Wi-Fi bearers 7. Click the Display tab. 8. From the Display type list, select display by bearer or modulation. For information on adjusting the display, see "Display Properties of Objects" on page 43. 9. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Studying the Effective Service Area The effective service area is the intersection zone between the uplink and downlink service areas. In other words, the effective service area prediction calculates where a service is actually available in both downlink and uplink. The service availability depends upon the bearer selection thresholds of the highest and lowest bearers as defined in the properties of the service selected for the prediction. To make an effective service area coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Effective Service Area Analysis (DL+UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the 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 cell loads defined in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The best bearer coverage prediction is always based on the best server. For more information on
1377
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1370, "Modelling Terminals" on page 1372, "Modelling Mobility Types" on page 1371, and "Defining Wi-Fi Reception Equipment" on page 1424, 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. 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 is available in both downlink and uplink. For information on defining display properties, see "Display Properties of Objects" on page 43. When creating a coverage prediction by unique values, you can not export the values per pixel.
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Making a Coverage Prediction by Throughput Downlink and uplink throughput coverage predictions calculate and display the channel throughputs and cell capacities based on C⁄(I+N) and bearer calculations for each pixel. These coverage predictions can also display aggregate cell throughputs if Monte Carlo simulation results are available. For more information on making aggregate cell throughput coverage predictions using simulation results, see "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1380. To make a coverage prediction by throughput: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 13.28). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the downlink traffic load, uplink noise rise values, and any angular distribution of interference stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The throughput coverage prediction is always based on the best server. The Noise figure defined in the terminal type’s 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
1378
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
reception equipment. This reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the serving transmitter for the uplink coverage predictions. 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. You can make Atoll use only the bearers for which selection thresholds are defined in both the terminal’s and the cell’s reception equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1370, "Modelling Terminals" on page 1372, "Modelling Mobility Types" on page 1371, and "Defining Wi-Fi Reception Equipment" on page 1424, 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 13.28: Condition settings for a throughput coverage prediction 7. Click the Display tab. 8. From the Display type list, select "Value intervals" to display the coverage prediction by peak MAC, effective MAC, or application throughputs. For information on adjusting the display, see "Display Properties of Objects" on page 43. 9. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Atoll calculates the peak MAC channel throughputs from the information provided in the frame configurations and in the terminal and mobility properties for the terminal and mobility selected in the coverage prediction. Atoll determines the bearer at each pixel and multiplies the bearer efficiency by the number of symbols in the frame to determine the peak MAC channel throughputs. The effective MAC throughputs are the peak MAC throughputs reduced by retransmission due to errors, or the Block Error Rate (BLER). Atoll uses the block error rate graphs of the reception equipment defined in the selected terminal for downlink or the reception equipment of the cell of the serving transmitter for uplink. The application throughput is the effective MAC throughput reduced by the overheads of the different layers between the MAC and the Application layers.
1379
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
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. For more information on throughput calculation, see the Technical Reference Guide. For more information on the Global Parameters, see "The Global Network Settings" on page 1422. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Making an Aggregate Throughput Coverage Prediction Using Simulation Results Atoll calculates the aggregate peak MAC, effective MAC, and application cell throughputs during Monte Carlo simulations. The aggregate cell throughputs are the sums of the cell’s user throughputs. You can create a coverage prediction that calculates and displays the surface area covered by each cell, and colours the coverage area of each cell according to its aggregate throughput. To create an aggregate throughput coverage prediction: 1. Create and run a Monte Carlo simulation. For more information on creating Monte Carlo simulations, see "Calculating and Displaying Traffic Simulations" on page 1397. 2. Create a coverage prediction by throughput as explained in "Making a Coverage Prediction by Throughput" on page 1378, with the following exceptions: a. On the Condition tab, select a simulation or group of simulations from the Load conditions list. The coverage prediction will display the results based on the selected simulation or on the average results of the selected group of simulations. b. On the Display tab, you can display results by Peak MAC aggregate throughput, Effective MAC aggregate throughput, or Aggregate application throughput. The coverage prediction results will be in the form of thresholds. For information on defining the display, see "Display Properties of Objects" on page 43. 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 1409. Making a Coverage Prediction by Quality Indicator Downlink and uplink quality indicator coverage predictions calculate and display the values of different quality indicators (BLER, BER, etc.) based on the best Wi-Fi radio bearers and on C⁄(I+N) for each pixel. To make a coverage prediction by quality indicator: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Quality Indicator (DL) or Coverage by Quality Indicator (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 13.27). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the downlink traffic load, uplink noise rise values, and any angular distribution of interference stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The quality indicator coverage prediction is always based on the best server. The Noise figure defined in the terminal type’s 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
1380
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
bearer selection for each pixel according to the traffic C⁄(I+N) level is performed using the bearer selection thresholds defined in the reception equipment, and the quality indicator graphs from the reception equipment are used to determine the values of the selected quality indicator on each pixel. The reception 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. You can make Atoll use only the bearers for which selection thresholds are defined in both the terminal’s and the cell’s reception equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1370, "Modelling Terminals" on page 1372, "Modelling Mobility Types" on page 1371, and "Defining Wi-Fi Reception Equipment" on page 1424, 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 13.29: Condition settings for a coverage prediction by quality indicators 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 Wi-Fi Quality Indicators" on page 1423. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 43. 8. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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.
13.2.8.8.4
Analysing Interference Areas Using a Point Analysis In Atoll, you can study the interferers of a transmitter using the Point Analysis tool. At any point on the map, the Interference view gives you information on interference received on any downlink channel. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility, and a service. The downlink and uplink load conditions can be taken from the Cells table or from Monte Carlo simulations. You can make an interference analysis to verify a coverage prediction. If you do, before you make the point analysis, ensure the coverage prediction you want to verify is displayed on the map.
1381
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
To make an interference analysis: 1. Click the Point Analysis button (
) in the Radio Planning toolbar. The Point Analysis window appears (see
Figure 13.30) and the pointer changes (
) to represent the receiver.
2. Select the Interference view. 3. At the top of the Interference view, select "Cells table" from Load. 4. If you are making an interference 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. Click the Options button ( • • •
) in the Interference view toolbar. The Calculation Options 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.
c. Click OK to close the Calculation Options dialogue. 5. Move the pointer over the map to make an interference analysis for the current location of the pointer. In the map window, an thick arrow from the pointer to its best server is displayed. Thinner arrows are also displayed from the interfering cells towards the pointer. 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 tip text. 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. Select the load conditions to use in this analysis from simulations or from the Cells table.
The best server signal level (top-most bar), total noise (black bar), and interference from other cells.
Select the parameters of the probe user to be studied. Figure 13.30: Point analysis tool: Interference view The Interference view displays, in the form of a bar graph, the signal level from the best server, a black bar indicating the total noise (I+N) received by the receiver, and bars representing the interference received from each interferer. You can change the following options in the Interference view: •
AtollIntra-technology: You can select the Intra-technology check box if you want Atoll to display the intra-technology interference.
To get the details about the best server and all the interferers in the form of a report: •
Click the Report button (
7. Click the Point Analysis button (
) in the Interference view toolbar. The Analysis Report dialogue appears. ) on the Radio Planning toolbar again to end the point analysis.
13.2.8.9 Printing and Exporting Coverage Prediction Results Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. •
•
1382
Printing coverage prediction results: Atoll offers several options allowing you to customise and optimise the printed coverage prediction results. Atoll supports printing to a variety of paper sizes, including A4 and A0. For more information on printing coverage prediction results, see "Printing a Map" on page 84. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
•
as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 59. Exporting coverage prediction results: In Atoll, you can export the coverage areas of a coverage prediction in raster or vector formats. In raster formats, you can export in BMP, TIF, JPEG 2000, ArcView© grid, or Vertical Mapper (GRD and GRC) formats. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 GB. In vector formats, you can export in ArcView©, MapInfo©, or AGD formats. For more information on exporting coverage prediction results, see "Exporting Coverage Prediction Results" on page 67.
13.3 Studying Network Capacity In Atoll, a simulation is based on a realistic distribution of users at a given point in time. The distribution of users at a given moment is referred to as a snapshot. Based on this snapshot, Atoll calculates various network parameters such as the downlink and uplink traffic loads, the uplink noise rise values, the user throughputs, etc. Simulations are calculated in an iterative fashion. When several simulations are performed at the same time using the same traffic information, the distribution of users will be different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snapshot to another. To create snapshots, services and users must be modelled. As well, certain traffic information in the form of traffic maps or subscriber lists must be provided. Once services and users have been modelled and traffic maps and subscriber lists have been created, you can make simulations of the network traffic. In this section, the following are explained: • • • • • •
"Defining Multi-service Traffic Data" on page 1383. "Creating a Traffic Map" on page 1383. "Exporting a Traffic Map" on page 1393. "Working with a Subscriber Database" on page 1393. "Calculating and Displaying Traffic Simulations" on page 1397. "Making Coverage Predictions Using Simulation Results" on page 1409.
13.3.1 Defining Multi-service Traffic Data The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: •
•
• •
Wi-Fi radio bearers: Radio bearers are used by the network for carrying information. The Wi-Fi Radio Bearer table lists all the available radio bearers. You can create new radio bearers and modify existing ones by using the Wi-Fi Radio Bearer table. For information on defining radio bearers, see "Defining Wi-Fi Radio Bearers" on page 1423. 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 1370. Mobility types: Information about receiver mobility is important to determine the user’s radio conditions and throughputs. For information on modelling mobility types, see "Modelling Mobility Types" on page 1371. Terminals: A terminal is the user equipment that is used in the network. For information on modelling terminals, see "Modelling Terminals" on page 1372.
13.3.2 Creating a Traffic Map The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atollprovides three types of traffic maps for Wi-Fi projects. • • •
Sector traffic map User profile traffic map User density traffic map (number of users per km2)
These maps can be used for different types of traffic data sources as follows: •
Sector traffic maps can be used if you have live traffic data from the network. In these maps, 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 (all activity statuses). For more information, see "Creating a Sector Traffic Map" on page 1384.
•
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
1383
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
pixel has an assigned environment class, are both supported. For more information, see "Importing a User Profile Traffic Map" on page 1387, "Importing a User Profile Environment Based Traffic Map" on page 1389 and "Creating a User Profile Environment Based Traffic Map" on page 1389. •
User density traffic maps (number of users per km2) can be used if you have population-based traffic data. 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 "Creating User Density Traffic Maps (No. Users/km2)" on page 1390, "Importing a User Density Traffic Map" on page 1390, "Exporting Cumulated Traffic" on page 1392 and "Exporting Cumulated Traffic" on page 1392.
13.3.2.1 Creating a Sector Traffic Map This section explains how to create a sector traffic map in Atoll to model traffic. You can input either the throughput demands in the uplink and in the downlink or the number of users per activity status or the total number of users (all activity statuses). A coverage prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by Transmitter" on page 1358. To create a sector traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector traffic map. 5. Select the type of traffic information you want to input. You can choose between 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. You can also import a traffic map from a file by clicking the Import button. You can import AGD (Atoll Geographic Data) format files that you have exported from another Atoll document. 7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter. 8. Enter the data required in the Sector Traffic 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 Total number of users (all activity statuses), enter the number of connected users for each sector and for each listed service. If you have selected Number of users per activity status, enter the number of inactive users, the number of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each service. You can also import a text file containing the data by clicking the Actions button and selecting Import Table from the menu. For more information on importing table data, see "Importing Tables from Text Files" on page 82.
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 Maps folder. You can modify the sector traffic map after it has been created.
1384
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
To modify the sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 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 modified values. You can update the information, throughput demands and the number of users, on the map afterwards. You must first recalculate the coverage prediction by transmitter. For more information, see "Making a Coverage Prediction by Transmitter" on page 1358. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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 1392.
13.3.2.2 Creating a User Profile Traffic Map You can have information describing the behaviour of different types of users, i.e., which type of user accesses which services and for how long. In Atoll, this type of data can be used to create traffic maps based on user profiles and environments. A user profile models the behaviour of different user categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for calls of the type "voice") or uplink and downlink volume (for calls of the type "data"). Environment classes are used to describe the distribution of users on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of users with the same profile per km²). The sections "Importing a User Profile Traffic Map" on page 1387, "Importing a User Profile Environment Based Traffic Map" on page 1389 and "Creating a User Profile Environment Based Traffic Map" on page 1389 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 1385. "Modelling Environments" on page 1386.
Modelling User Profiles You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user might be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multimedia services and web browsing. To create or modify a user profile: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder.
1385
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles: New Element Properties dialogue appears. You can modify the properties of an existing user profile by right-clicking the user profile in the User Profiles folder and selecting Properties from the context menu.
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 1370. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 1372. 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 can not use the service continually. For example, with a webbrowsing service, a session starts when the user opens his browsing application and ends when he quits the browsing application. Between these two events, the user might be downloading web pages and other times he can not be using the application, or he might be browsing local files, but the session is still considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and not by the time. In order for all the services defined for a user profile to be taken into account during traffic scenario elaboration, the sum of activity probabilities must be lower than 1.
• • •
Duration (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 environment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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 environment. 7. In the row marked with the New row icon ( tion that this 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.
1386
), set the following parameters for each user profile/mobility combina-
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
For example: An area of 10 km² with a 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 want you can specify a percentage of indoor users for each clutter class. During a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss. 11. Click OK.
13.3.2.2.1
Importing a User Profile Traffic Map User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscribers⁄km, or polygons with a number of subscribers⁄km²) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile densities from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1389. 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 map’s properties dialogue appears. 11. Select the Traffic tab (see Figure 13.31). 12. Under Traffic fields, you can specify the user profiles to be considered, their mobility type (km⁄h), and their density. If the file you are 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.
1387
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
Figure 13.31: Traffic map properties dialogue - Traffic tab Define each of the following: •
•
•
User profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the Traffic Parameters folder of the Parameter tab, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers when the map consists of points. When you import user profile or mobility information from the file, the values in the file must be exactly the same as the corresponding names in the Traffic Parameters folder in the Parameters explorer. If the imported user profile or mobility does not match, Atoll will display a warning.
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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
14. If you want, you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss. 15. Click OK to finish importing the traffic map.
1388
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
13.3.2.2.2
Importing a User Profile Environment Based Traffic Map Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1389. 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 map’s 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 Traffic Parameters in the Parameters explorer. For more information, see "Modelling Environments" on page 1386. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 43. 14. Click OK.
13.3.2.2.3
Creating a User Profile Environment Based Traffic Map Atollenables you to create a user profile environment traffic map based on by drawing it in the map window. To draw a traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list. 6. Click Create. The Environment Map Editor toolbar appears (see Figure 13.32).
Draw Polygon
Delete Polygon
Figure 13.32: 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.
1389
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
13.3.2.2.4
© Forsk 2012
Displaying Statistics on a User Profile Environment Traffic Map You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears. The Statistics window lists the surface (Si in km²) and the percentage of surface (% of i) for each environment class "i" S
i - × 100 within the focus zone. The percentage of surface is given by: % of i = -------------
Sk k
You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.
13.3.2.3 Creating User Density Traffic Maps (No. Users/km2) User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants). User density traffic maps provide the number of connected users per unit surface, i.e., the density of users, as input. This can be either the density of users per activity status or the total density of users (all activity statuses). In this section, the following ways of creating a user density traffic map are explained: • •
"Importing a User Density Traffic Map" on page 1390 "Creating a User Density Traffic Map" on page 1391.
User density traffic maps can be created from sector traffic maps in order to extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. For more information, see "Creating User Density Traffic Maps from Sector Traffic Maps" on page 1392.
13.3.2.3.1
Importing a User Density Traffic Map The user density traffic map defines the density of users per pixel. For a traffic density of X users per km², Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined in the Traffic tab of the traffic map’s properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select 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.
1390
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
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 1389. 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 map’s 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 percentage must equal 100. 13. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 14. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 15. Under Clutter distribution, enter for each clutter class the percentage of indoor users. 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. 16. Click OK. Atoll creates the traffic map in the Traffic Maps folder.
13.3.2.3.2
Creating a User Density Traffic Map Atollenables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User density traffic map (Number of users per km2). 5. Select the type of traffic information you input. You can choose from: • • • • •
All activity statuses: Select All activity statuses if the map you are importing provides a density of users with any activity status. Active in uplink: Select Active in uplink if the map you are importing provides a density of users active in the uplink only. Active in downlink: Select Active in downlink if the map you are importing provides a density of users active in the downlink only. Active in uplink and downlink: Select Active in uplink and downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.
6. Click the Create button. The traffic map’s 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 Maps folder. 13. Right-click the traffic map. The context menu appears. 14. Select Edit from the context menu.
1391
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
15. Use the tools available in the Vector Editor toolbar in order to draw contours. For more information on how to edit contours, see "Editing Polygons, Lines, and Points" on page 61. 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.
13.3.2.3.3
Creating User Density Traffic Maps from Sector Traffic Maps You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. To create user density traffic maps from a sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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.
13.3.2.4 Exporting Cumulated Traffic Atoll allows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user densities. The cumulated traffic is exported in 32-bit BIL, ArcView© Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears. 4. Enter a file name and select the file format. 5. Click Save. The Export dialogue appears. 6. Under Region, select the area to export: • •
The entire project area: This option allows you to export the cumulated traffic over the entire project. The computation zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone.
7. Define a Resolution in metres. The resolution must be an integer and the minimum resolution allowed is 1. 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: • • • •
1392
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.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
•
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.
13.3.3 Exporting a Traffic Map To export a traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save. If you are exporting a raster traffic map, you have to define: •
The Export region: • • •
•
Entire project area: Saves the entire traffic map. Only pending changes: Saves only the modifications made to the map. Computation zone: Saves only the part of the traffic map inside the computation zone.
An export Resolution.
13.3.4 Working with a Subscriber Database Atoll Wi-Fi includes a subscriber database for modelling fixed user distributions in a network. The subscriber database consists of subscriber lists. You can create subscriber lists in Atoll by adding subscribers to the list using the mouse, or by copying data from any other source such as a spreadsheet. You can also directly import subscriber lists in Atoll from text (TXT) and comma separated value (CSV) files. Atoll can allocate reference or serving access points (cells) to subscribers. You can also have the subscriber antenna oriented towards its serving cell to decrease interference. The automatic server allocation performs a number of calculations on the subscriber locations. In this section, the following are explained: • •
"Creating a Subscriber List" on page 1393. "Performing Calculations on Subscriber Lists" on page 1397.
13.3.4.1 Creating a Subscriber List You create subscribers in Atoll in two steps. First, you create a subscriber list, and then you add subscribers to the list. You can add subscribers to the list directly on the map using the mouse. For more information, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 1395. If you need to create a large number of subscribers, Atoll allows you to import them from another Atoll document or from an external source. For more information, see "Importing a Subscriber List" on page 1396. To create a subscriber list: 1. Select the Network explorer. 2. Right-click the Subscribers folder. The context menu appears. 3. Select New List from the context menu. The Subscriber List N Properties dialogue appears (see Figure 13.33), where N is an incremental digit.
1393
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
Figure 13.33: 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 93. Filter: Click the Filter button to filter the data in the subscriber list. For information on filtering, see "Filtering Data" on page 95.
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 43. 6. Click OK. Atoll creates a new subscriber list. The following parameters are available by default in a new subscriber list: • • • • •
•
• • • • •
•
• •
1394
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 subscriber’s location is always fixed. Height: The altitude of the subscriber antenna with respect to the ground (DTM). 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 1385. Terminal: The default terminal (CPE) is the user equipment with an antenna, reception 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. Clutter: The name of the clutter class where the subscriber is located. This is a non-editable field whose contents are automatically updated. Indoor: This field indicates whether the subscriber is indoor or outdoor. Best server: The serving transmitter of the subscriber. You can either define this value manually or let Atoll calculate it for the subscriber. The serving access point is determined according to the received signal level from the cell with the highest 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 access point covers the subscriber, the one with the highest layer is selected as the reference cell. Distance: The distance of the subscriber from its serving access point. This is a non-editable field whose contents are automatically updated. 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 access point.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
•
• • • • • •
• •
•
• • • • •
• • •
•
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 access point. 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. Received power (DL) (dBm): The signal level received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. C/(I+N) (DL) (dB): The C/(I+N) at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. 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. Bearer (DL): The highest Wi-Fi bearer available for the 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 subscriber’s terminal type’s reception equipment for the 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 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. 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. 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. Bearer (UL): The highest Wi-Fi 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. BLER (UL): The Block Error Rate read from the reference cell’s reception 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 in uplink. Transmission power (UL) (dBm): The transmission power of the subscriber’s terminal after power control in the uplink. 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 1396. For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations on Subscriber Lists" on page 1397. 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 1395. You can open the subscriber list table containing all the subscribers and their parameters. To open the subscriber list table: 1. Select the Network explorer. 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 69.
13.3.4.1.1
Adding Subscribers to a Subscriber List Using the Mouse You can use the mouse to add subscribers to an existing subscriber list. Atoll applies the default parameters defined in the Table tab of the subscriber list Properties dialogue to all the subscribers you add to the list. For more information on the Table
1395
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
tab, see "Creating a Subscriber List" on page 1393. To add subscribers to a subscriber list using the mouse: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Subscribers folder. 3. Right-click the subscriber list to which you want to add subscribers. The context menu appears. 4. Select Add Subscribers from the context menu. The pointer changes to subscriber addition mode (
).
5. Move the mouse over the map window, and click once to add each subscriber. 6. Press ESC or click the normal pointer button (
) to finish adding subscribers.
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 49.
13.3.4.1.2
Importing a Subscriber List You can also import subscriber lists from text files (TXT) or comma separated value files (CSV), including Microsoft Excel files exported in CSV format. To import a subscriber list: 1. Select the Network explorer. 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 more information on importing table data, see "Importing Tables from Text Files" on page 82. You can also export subscriber lists. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80.
13.3.4.1.3
Selecting the Columns to Display in the Subscriber Lists You can select the columns to display in the Properties dialogue of the Subscribers folder from those in "Creating a Subscriber List" on page 1393. To select the columns to display in subscriber lists: 1. Select the Network explorer. 2. Right-click the Subscribers folder. The context menu appears. 3. Select Properties from the context menu. The Subscribers Properties dialogue appears. 4. Click the Column Selection tab. 5. Under Configuration, you can Load an existing configuration of the columns to display, Save the current settings in an existing configuration file, or Save as a new configuration file. 6. Select the columns you want to display: a. Select the column in the Available columns list and click b. Select a column in the Columns to display list and click
to move it to the Columns to display list. to move it to the Available columns list.
c. Change the order of the columns by selecting a column and clicking 7. Click OK to close the Subscribers Properties dialogue.
1396
or
to move it up or down in the list.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
13.3.4.2 Performing Calculations on Subscriber Lists You can perform calculations on subscriber lists without having to carry out simulations first. Atoll does not base calculations performed on subscriber lists on the path loss matrices calculated for transmitters. This is because the path loss matrices are calculated for a given receiver height (1.5 m by default) defined on the Calculation Parameters tab of the Properties dialogue of the Network Settings folder, but each subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates the path loss, received power, and other output for each subscriber when you perform calculations based on subscribers. Atoll can perform an automatic server allocation for all the subscribers in a list. To perform calculations on a subscriber list: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Subscribers folder. 3. Right-click the subscriber list on which you want to perform calculations. The context menu appears. 4. Select Calculations > Automatic Server Allocation from the context menu. The Automatic Server Allocation dialogue appears. If you want the calculations to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. The shadowing margin for signal level calculations is based on the model standard deviation, and the shadowing margin for C/(I+N) calculations is based on the C/I standard deviation. 5. Click Calculate. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. 6. Once the calculations are finished, click Close to close the Event Viewer. 7. Click Commit to store the results in the subscriber list. For the list of results that are available after the calculations, see "Creating a Subscriber List" on page 1393.
13.3.5 Calculating and Displaying Traffic Simulations To plan and optimise Wi-Fi networks, you will need to study the network capacity and to study the network coverage taking into account realistic user distribution and traffic demand scenarios. You can also carry out traffic offload analysis in co-planning mode, i.e., study the amount of mobile traffic from a mobile network (LTE, UMTS, etc.) that can be carried by a Wi-Fi network layer deployed on top of the mobile network. To perform this analysis, you must link the Wi-Fi document with the mobile network document and run Monte Carlo simulations as explained in "Performing a Traffic Offload Analysis" on page 1420. In Atoll, a simulation corresponds to a given distribution of Wi-Fi users. It is a snapshot of a Wi-Fi network. The principal outputs of a simulation are a geographic user distribution with a certain traffic demand, resources allocated to each user of this distribution, and cell loads. You can create groups for one or more simulations and carry out as many simulations as required. A new simulation for each different traffic scenario can help visualise the network’s response to different traffic demands. Each user distribution (each simulation generates a new user distribution) is a Poisson distribution of the number of active users. Therefore, each simulation can have a varying number of users accessing the network. Wi-Fi 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. Wi-Fi 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: • • • • • •
"Wi-Fi Traffic Simulation Algorithm" on page 1397. "Creating Simulations" on page 1399. "Displaying the Traffic Distribution on the Map" on page 1400. "Displaying the Results of a Single Simulation" on page 1403. "Updating Cell Load Values With Simulation Results" on page 1408. "Estimating a Traffic Increase" on page 1409.
13.3.5.1 Wi-Fi Traffic Simulation Algorithm Figure 13.34 shows the Wi-Fi simulation algorithm. The simulation process in Wi-Fi consists of the following steps: 1. Mobile Generation and Distribution Simulations require traffic data, such as traffic maps (raster, vector, or live traffic data) and subscriber lists. Atoll generates a user distribution for each simulation using a Monte Carlo algorithm. This user distribution is based on the traffic data input and is weighted by a Poisson distribution.
1397
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
Each mobile generated during the simulations is assigned a service, a mobility type, and a terminal according to the user profile assigned to it. A transmission status is determined according to the activity probabilities. The transmission status is an important output of the simulation as it has a direct impact on the next step of the simulation process, i.e., the radio resource management (RRM), and has an impact on the interference level in the network. The geographical location of each mobile is determined randomly for the mobiles generated based on the traffic data from traffic maps. The mobiles generated based on the traffic data from subscriber lists are located on the subscriber locations.
Figure 13.34: Wi-Fi simulation algorithm 2. Best Server Determination Atoll determines the best server for each mobile based on the signal level in the downlink. For multi-cell transmitters, the best serving transmitter is determined according to the received signal level from the cell with the highest power. If more than one cell covers the mobile, the one with the highest layer is selected as the serving (reference) cell. 3. Downlink and Uplink Calculations The downlink and uplink calculations include the calculation of C/(I+N), determination of the best available bearer for the C/(I+N), allocation of resources (RRM), and calculation of user throughputs. 4. 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 using a round robin approach.
1398
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
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.), he is among the users selected by the scheduler for resource allocation (step 4.), and he is not rejected due to resource saturation (step 4.).
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 4., 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 cell’s 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.
13.3.5.2 Creating Simulations In Atoll, simulations enable you to study the capacity of your Wi-Fi network and model the radio resource management, 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. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name 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 in the Network explorer. 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 use the maximum uplink traffic load as defined in the properties for each cell, click the button ( Defined per cell.
) beside the box and select
7. You can enter some Comments if you want. 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 1383. 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: •
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.
1399
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
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. •
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.
10. Once you have defined the simulation, you can calculate it immediately or you can save it to calculate it later: • •
Calculate: Click Calculate to save the defined simulation and calculate it immediately. OK: Click OK to save the defined simulation without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
All simulations created at the same time are grouped together in a folder in the Network explorer. You can now use the results from completed simulations for Wi-Fi coverage predictions. For more information on using simulation results in coverage predictions, see "Making Coverage Predictions Using Simulation Results" on page 1409.
13.3.5.3 Displaying the Traffic Distribution on the Map Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to activity status, service, reference cell, or throughputs. You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 43. In this section are the following examples of traffic distribution: • • • • •
"Displaying the Traffic Distribution by Activity Status" on page 1400. "Displaying the Traffic Distribution by Connection Status" on page 1401. "Displaying the Traffic Distribution by Service" on page 1401. "Displaying the Traffic Distribution by Throughput" on page 1402. "Displaying Traffic Simulation Results Using Tip Text" on page 1402. 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 Windows" on page 38.
13.3.5.3.1
Displaying the Traffic Distribution by Activity Status In this example, the traffic distribution is displayed by the activity status. To display the traffic distribution by the activity status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Activity status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 13.35).
1400
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Figure 13.35: Displaying the traffic distribution by activity status
13.3.5.3.2
Displaying the Traffic Distribution by Connection Status In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Connection status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 13.36).
Figure 13.36: Displaying the traffic distribution by connection status
13.3.5.3.3
Displaying the Traffic Distribution by Service In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 13.37).
1401
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
Figure 13.37: Displaying the traffic distribution by service
13.3.5.3.4
Displaying the Traffic Distribution by Throughput In this example, the traffic distribution is displayed by throughput. To display the traffic distribution by throughput: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value intervals" as the Display type and one of the following throughput types as the Field: • • •
Peak MAC, effective MAC, or application channel throughput Peak MAC, effective MAC, or application cell capacity Peak MAC, effective MAC, or application user throughput
5. Click OK. The traffic distribution is now displayed by throughput (see Figure 13.38).
Figure 13.38: Displaying the traffic distribution by throughput
13.3.5.3.5
Displaying Traffic Simulation Results Using Tip Text You can display information by placing the pointer over a mobile generated during a simulation to read the information displayed in the tip text. The information displayed is defined by the settings you made on the Display tab. For information on defining the tip text, see "Defining the Object Type Tip Text" on page 46. To display simulation results in the form of tip text: •
1402
In the map window, place the pointer over the user that you want more information on. After a brief pause, the tip text appears with the information defined in the Display tab of the Simulations folder properties (see Figure 13.39).
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Figure 13.39: Displaying the traffic simulation results using tip text
13.3.5.4 Displaying the Results of a Single Simulation After you have created a simulation, as explained in "Creating Simulations" on page 1399, you can display the results. To access the results of a single simulation: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. 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.
Results: Under Results, is data on the connection results: • • •
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. Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site. Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink, or downlink and uplink both.
1403
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
• • • • • • • • • • • • • • • •
Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink both. Number of connected users (DL): The number of users connected to any cell of the site in downlink. Number of connected users (UL): The number of users connected to any cell of the site in uplink. No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the downlink in all the cells of the site. Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the downlink in all the cells of the site. Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site. Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the uplink in all the cells of the site. Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the uplink in all the cells of the site. Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site. Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site.
The Cells tab: The Cells tab contains the following information, per site and transmitter: • • • • • • • • • • • • • • • • • • • • •
1404
Traffic load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation. Traffic load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation. UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation. Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected in the downlink. Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink. Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in the downlink. Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected in the uplink. Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink. Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in the uplink. Connection success rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both. Number of connected users (DL): The number of users connected to the cell in downlink. Number of connected users (UL): The number of users connected to the cell in uplink. No service: The number of users unable to connect to the cell for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to the cell for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to the cell for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to the cell for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was "Resource saturation." 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.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
• • • • • •
Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the downlink. Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink. Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the uplink. Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the uplink. Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink. Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with respect to the number of users covered by the cell.
The Mobiles tab: The Mobiles tab contains the following information: • • • • • • • • • •
• • • • • • • • • • • • • • • • • • •
•
• • •
X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the second random trial). Height: The height of the user terminal (antenna). User profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal and the user profile. Subscriber ID: The ID of the user if the user is generated from a subscriber list and not from a traffic map. Subscriber list: The subscriber list of the user if the user is generated from a subscriber list and not from a traffic map. Service: The service assigned during the first random trial during the generation of the user distribution. Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal and the user profile. Mobility: The mobility type assigned during the first random trial during the generation of the user distribution. Activity status: The assigned activity status. It can be Active DL, Active UL, Active DL+UL, or Inactive. Connection status: The connection status indicates whether the user is connected or rejected at the end of the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection cause is given. Clutter class: The code of the clutter class where the user is located. Indoor: This field indicates whether indoor losses have been added or not. Best server: The best server of the user. Reference cell: The reference cell of the serving transmitter of the subscriber. Azimuth: The orientation of the user’s terminal antenna in the horizontal plane. Azimuth is always considered with respect to the North. Atoll points the user antenna towards its best server. Downtilt: The orientation of the user’s terminal antenna in the vertical plane. Mechanical downtilt is positive when it is downwards and negative when upwards. Atoll points the user antenna towards its best server. Path loss (dB): The path loss from the best server calculated for the user. 2nd best server: The second best server of the user. 2nd best server path loss (dB): The path loss from the second best server calculated for the user. 3rd best server: The third best server of the user. 3rd best server path loss (dB): The path loss from the third best server calculated for the user. Received power (DL) (dBm): The signal level received at the user location in the downlink. C/(I+N) (DL) (dB): The C/(I+N) at the user location in the downlink. Total noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced at the user location in the downlink. Bearer (DL): The highest Wi-Fi bearer available for the traffic C/(I+N) level at the user location in the downlink. BLER (DL): The Block Error Rate read from the user terminal’s reception equipment for the traffic C/(I+N) level at the user location in the downlink. Diversity mode (DL): The diversity mode supported by the cell 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.
1405
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
• • • • • • • • •
•
• • •
Received power (UL) (dBm): The signal level received at the serving transmitter from the user terminal in the uplink. C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the user in the uplink. Total noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter of the user in the uplink. Bearer (UL): The highest Wi-Fi bearer available for the C/(I+N) level at the serving transmitter of the user in the uplink. BLER (UL): The Block Error Rate read from the reference cell’s reception equipment for the C/(I+N) level at the serving transmitter of the user in the uplink. Diversity mode (UL): The diversity mode supported by the cell in uplink. Transmission power (UL) (dBm): The transmission power of the user terminal after power control in the uplink. Peak MAC channel throughput (UL) (kbps): The maximum MAC channel throughput attainable using the highest bearer available at user location in the uplink. Effective MAC channel throughput (UL) (kbps): The effective MAC channel throughput attainable using the highest bearer available at the user location in the uplink. It is calculated from the peak MAC throughput and the BLER. Application channel throughput (UL) (kbps): The application throughput is the net throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput scaling factor of the service and the throughput offset. Peak MAC user throughput (UL) (kbps): The maximum MAC user throughput attainable using the highest bearer available at the user location in the uplink. Effective MAC user throughput (UL) (kbps): The effective MAC user throughput attainable using the highest bearer available at the user location in the uplink. It is calculated from the peak MAC throughput and the BLER. Application user throughput (UL) (kbps): The application throughput is the net throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput scaling factor of the service and the throughput offset. •
•
In Atoll, channel throughputs are peak MAC, effective MAC, or application throughputs achieved at a given location using the highest Wi-Fi 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 input parameters specified when creating the simulation: • • • • • •
•
Maximum number of iterations Global scaling factor Generator initialisation value Uplink and downlink traffic load convergence thresholds Uplink noise rise convergence threshold Names of the traffic maps and subscriber lists used.
The parameters related to the clutter classes, including the default values.
13.3.5.5 Displaying the Average Results of a Group of Simulations After you have created a group of simulations, as explained in "Creating Simulations" on page 1399, you can display the average results of the group. If you want to display the results of a single simulation in a group, see "Displaying the Results of a Single Simulation" on page 1403. To display the averaged results of a group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Right-click the group of simulations whose results you want to display. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the simulation results. Other tabs in the simulation properties dialogue contain the averaged results for all simulations of the group. The Statistics tab: The Statistics tab contains the following sections: •
Request: Under Request is data on the connection requests: •
1406
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.
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
• • •
During the first random trial, each user is assigned a service and an activity status. The number of users per activity status and the UL and DL throughput demands that all users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and UL and DL throughput demands) is given.
Results: Under Results is data on the connection results: • • •
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 average information per site: • • • • • • • • • • • • • • • • • • • • • • • •
Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected in the downlink in all the cells of the site. Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink in all the cells of the site. Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in the downlink in all the cells of the site. Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected in the uplink in all the cells of the site. Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink in all the cells of the site. Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in the uplink in all the cells of the site. Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site. Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink, or downlink and uplink both. Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink both. Number of connected users (DL): The number of users connected to any cell of the site in downlink. Number of connected users (UL): The number of users connected to any cell of the site in uplink. No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the downlink in all the cells of the site. Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the downlink in all the cells of the site. Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink in all the cells of the site. Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the uplink in all the cells of the site. Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the uplink in all the cells of the site. Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink in all the cells of the site. Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site.
The Cells (Average) tab: The Cells (Average) tab contains the following average information per cell: • • • •
Traffic load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation. Traffic load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation. UL noise rise (dB): The noise rise of the cells calculated on the uplink during the simulation. Peak MAC aggregate throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected in the downlink.
1407
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
• • • • • • • • • • • • • • • • • • • • • • •
Effective MAC aggregate throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users connected in the downlink. Aggregate application throughput (DL) (kbps): The sum of application throughputs of all the users connected in the downlink. Peak MAC aggregate throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected in the uplink. Effective MAC aggregate throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users connected in the uplink. Aggregate application throughput (UL) (kbps): The sum of application throughputs of all the users connected in the uplink. Connection success rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both. Number of connected users (DL): The number of users connected to the cell in downlink. Number of connected users (UL): The number of users connected to the cell in uplink. No service: The number of users unable to connect to the cell for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to the cell for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to the cell for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to the cell for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was "Resource saturation." Peak MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the downlink. Effective MAC aggregate throughput (DL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the downlink. Aggregate application throughput (DL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the downlink. Peak MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of peak MAC user throughputs of the users connected in the uplink. Effective MAC aggregate throughput (UL) (kbps) for each service: For each service, the sum of effective MAC user throughputs of the users connected in the uplink. Aggregate application throughput (UL) (kbps) for each service: For each service, the sum of application throughputs of the users connected in the uplink. Connection success rate (%) for each service: For each service, the percentage of users connected to the cell with respect to the number of users covered by the cell.
The Initial Conditions tab: The Initial Conditions tab contains the following information: •
The input parameters specified when creating the simulation: • • • • • •
•
Maximum number of iterations Global scaling factor Generator initialisation value Uplink and downlink traffic load convergence thresholds Uplink noise rise convergence threshold Names of the traffic maps and subscriber lists used.
The parameters related to the clutter classes, including the default values.
13.3.5.6 Updating Cell Load Values With Simulation Results After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 1399, you can update cell load values for each cell with the results calculated during the simulation. To update cell values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Select the Network explorer. b. Click the Expand button ( ) to expand the Simulations folder. c. Right-click the group of simulations whose results you want to access.
1408
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
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. Select the Network explorer. b. Click the Expand button ( ) to expand the Simulations folder. c. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. 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 (dB)
13.3.5.7 Estimating a Traffic Increase When you create simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increase of traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a simulation or group of simulations as described in "Creating Simulations" on page 1399. 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).
13.3.6 Making Coverage Predictions Using Simulation Results In Atoll, you can analyse simulation results by making coverage predictions using simulation results. In a coverage prediction each pixel is considered as a non-interfering probe user with a defined terminal, mobility, and service. The analyses can be based on a single simulation or on an averaged group of simulations. When no simulations are available, Atoll uses the downlink traffic load, uplink noise rise, and any angular distribution of interference stored for each cell to make coverage predictions. For information on cell properties, see "Cell Description" on page 1337; for information on modifying cell properties, see "Creating or Modifying a Cell" on page 1339. Once you have made simulations, Atoll can use the information from the simulations instead of the defined parameters in the cell properties to make coverage predictions. For each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a group of simulations, which uses the average of all simulations in the group. The coverage predictions that can use simulation results are: • • • • •
Coverage by C/(I+N) Level: For information on making a downlink or uplink coverage by C/(I+N) level, see "Making a Coverage Prediction by C/(I+N) Level" on page 1374. Service Area Analysis: For information on making a downlink or uplink service area analysis, see "Making a Downlink or Uplink Service Area Analysis" on page 1376. Effective Service Area Analysis: For information on making an effective service area analysis, see "Making a Downlink or Uplink Service Area Analysis" on page 1376. Coverage by Throughput: For information on making a downlink or uplink coverage by throughput, see "Making a Coverage Prediction by Throughput" on page 1378. Coverage by Quality Indicator: For information on making a downlink or uplink coverage by quality indicator, see "Making a Coverage Prediction by Quality Indicator" on page 1380.
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.
1409
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
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.
13.4 Verifying Network Capacity You can verify the capacity of the network using measurements of the strength of the signals and C/(I+N) in different locations within the area covered by the network. This collection of measurements is called drive test data. The data contained in a drive test data path can be used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: • • • • • • •
"Importing a Drive Test Data Path" on page 1410 "Displaying Drive Test Data" on page 1412 "Defining the Display of a Drive Test Data Path" on page 1412 "Network Verification" on page 1413 "Exporting a Drive Test Data Path" on page 1417 "Extracting CW Measurements from Drive Test Data" on page 1417 "Printing and Exporting the Drive Test Data Window" on page 1418.
13.4.1 Importing a Drive Test Data Path In Atoll, you can analyse networks by importing drive test data in the form of ASCII text files (with tabs, commas, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: • •
The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells. In Wi-Fi networks, a cell is identified by its BSID (6-byte MAC address). Therefore, you must indicate during the import process which column contains the BSID of cells.
You can import a single drive test data file or several drive test data files at the same time. If you regularly import drive test data files with the same format, you can create an import configuration. The import configuration contains information that defines the structure of the data in the drive test data file. By using the import configuration, you will not need to define the data structure each time you import a new drive test data file. To import one or several drive test data files: 1. Select the Network explorer. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the file or files you want to open. You can import one or several files. If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing Shift and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import. 5. Click Open. The Import of Measurement Files dialogue appears. Files with the extension PLN, as well as some FMT files (created with old versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue. 6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Import configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Import configuration, select an import configuration from the Configuration list. b. Continue with step 10.
1410
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
•
•
When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. If several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters: • • •
Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement conditions, • •
Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button (
) and select the coordinate system used in the drive test data file. Atoll
will then convert the data imported to the coordinate system used in the Atoll document. 8. Click the Setup tab. a. Under File, enter the number of the 1st measurement row, select the data Separator, and select the Decimal symbol used in the file. b. Click the Setup button to link file columns and internal Atoll fields. The Drive Test Data Setup dialogue appears. c. Under Measurement point position, select the columns in the imported file that give the X-coordinates and the Y-coordinates of each point in the drive test data file. You can also identify the columns containing the XY coordinates of each point in the drive test data file by selecting them from the Field row of the table on the Setup tab
d. Under Transmitter identification, enter a string found in the column name identifying the BSID of scanned cells in the BSID identifier box. 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. Click OK. •
•
If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Setup dialogue, Atoll should recognise all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "". Columns marked with "" will not be imported. The data in the file must be structured so that the column identifying the BSID is placed before the data columns for each cell. Otherwise Atoll will not be able to properly import the file.
9. If you want to save the definition of the data structure so that you can use it again, you can save it as an import configuration: a. On the Setup tab, under Import configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll’s installation folder. In case you cannot write into that folder, you can click Browse to choose a different location. c. Enter a Configuration name and an Extension of the files that this import configuration will describe (for example, "*.txt"). d. Click OK. Atoll will now select this import configuration automatically every time you import a drive test data path file with the selected extension. If you import a file with the same structure but a different extension, you can select this import configuration from the Import configuration list.
1411
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
• •
•
You do not have to complete the import procedure to save the import configuration and have it available for future use. When importing a measurement file, you can expand the NumMeasINIfile.ini file by clicking the Expand button ( ) in front of the file under Import configuration to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration file under Import configuration and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import all, if you are importing more than one file. The drive test data are imported into the current Atoll document.
13.4.2 Displaying Drive Test Data When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see the information at that location. To display information about a single drive test data point: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Select the display check box of the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want more information. Atoll displays an arrow pointing towards the serving cell in the same colour as the transmitter.
13.4.3 Defining the Display of a Drive Test Data Path You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to define labels, tip text and the legend. To display the Display tab of a drive test data path’s Properties dialogue: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path whose display you want to set. The context menu appears. 4. Select Properties from the context menu. The drive test data path’s 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 for each transmitter (a circle, triangle, cross, etc.) and a symbol size according to the altitude.
1412
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
• • •
•
Fast display forces Atoll to use the lightest symbol to display the points. This is particularly useful when you have a very large number of points. You can not use Advanced display if the Fast display check box has been selected. You can sort drive test data paths in alphabetical order in the Network explorer by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can save the display settings (such as colours and symbols) of a drive test data path in a user configuration file to make them available for use on another drive test data path. To save or load the user configuration file, click the Actions button on the Display tab of the path properties dialogue and select Save or Load from the Display Configuration submenu.
13.4.4 Network Verification The imported drive test data is used to verify the Wi-Fi 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 Measurement Points Along Drive Test Data Paths" on page 1413 "Predicting Signal Level on Drive Test Data Points" on page 1414 "Creating Coverage Predictions on Drive Test Data Paths" on page 1415 "Displaying Statistics Over a Drive Test Data Path" on page 1415 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 1416 "Analysing Measurement Variations Along the Path" on page 1416.
13.4.4.1 Filtering Measurement Points Along Drive Test Data Paths When using a drive test data path, some measured points can present values that are too far outside the median values to be useful. As well, test paths might include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from a more lightly populated region between the two. You can filter out unreliable measurement points from the drive test data path either geographically, by filtering by clutter classes and the focus zone, or using an advanced filter. To filter out measurement points by clutter class: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to filter out measurement points. The context menu appears. 4. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 5. Under Clutter classes, clear the check boxes of the clutter classes you want to exclude. Measurement points located on the excluded clutter classes will be filtered out. 6. If you want to use the focus zone as part of the filter, select the Use focus zone to filter check box. Measurement points located outside the focus zone will be filtered out. 7. If you want to permanently delete the measurement points outside the filter, select the Delete points outside the filter check box. • •
You can apply a filter on all the drive test data paths in the Drive Test Data folder by selecting Filter from the context menu of the folder. If you want to use the measurement points that you permanently deleted, you will have to import the drive test data path again.
To filter out measurement points using an advanced filter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to filter out measurement points. The context menu appears. 4. Select Filter from the context menu. The Drive Test Data Filter dialogue appears.
1413
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
5. Click More. The Filter dialogue appears. For more information on using the Filter dialogue, see "Advanced Data Filtering" on page 96. You can update heights (of the DTM, and clutter heights) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones by selecting Refresh Geo Data from the context menu of the Drive Test Data folder.
13.4.4.2 Predicting Signal Level on Drive Test Data Points To predict the signal level on drive test data points: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to create the point prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Point predictions, select Point Signal Level and click OK. The Point Signal Level Properties dialogue appears (see Figure 13.40).
Figure 13.40: Point Signal Level Properties dialogue The errors between measured and predicted signal levels can be calculated and added to the drive test data table. 6. If you want to calculate errors between measured and predicted signal levels, under Select signal levels for error calculations, select the names of the columns representing measured signal level values in the drive test data table for which you want to calculate the errors (see Figure 13.41). If you do not want to add this information to the drive test data table, continue with step 7.
Figure 13.41: Selecting measured signal levels for which errors will be calculated 7. Click OK. A new point prediction is created for the selected drive test data path. 8. Right-click the drive test data path. The context menu appears. 9. Select Calculations > Calculate All the Predictions from the context menu. If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the drive test data table for the predicted point signal level from the serving cell and the errors between the measured and predicted values.
1414
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Figure 13.42: Drive Test Data Table after Point Signal Level Prediction (with Error Calculations) New columns are also added for the predicted point signal level from each neighbour cell and the errors between the predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1416. The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main matrix. For more information on propagation models, see Chapter 5: Working with Calculations in Atoll.
13.4.4.3 Creating Coverage Predictions on Drive Test Data Paths You can create the following coverage prediction for all transmitters on each point of a drive test data path: •
Coverage by Signal Level
To create a coverage prediction along a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data to which you want to add a coverage prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Standard predictions, select one of the following coverage predictions and click OK: •
Coverage by Signal Level: Click the Condition tab. • • • •
On 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.
6. When you have finished setting the parameters for the coverage prediction, click OK. You can create a new coverage prediction by repeating the procedure from step 1. to step 6. for each new coverage prediction. 7. When you have finished creating new coverage predictions for these drive test data, right-click the drive test data. The context menu appears. 8. Select Calculations > Calculate All the Predictions from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Working with Calculations in Atoll). You can display the information in these new columns in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1416.
13.4.4.4 Displaying Statistics Over a Drive Test Data Path If predictions have been calculated along a drive test data path, you can display the statistics between the measured and the predicted values on that path. To display the statistics for a specific drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to display comparative statistics. The context menu appears. 4. Select Display Statistics from the context menu. The Measurement and Prediction Fields Selection dialogue appears.
1415
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
5. Under For the following transmitters, select one or more transmitters to include in the statistics. 6. Under Select the predicted values, select the fields that contain the predicted values that you want to use in the statistics. 7. Under Select the measured values, select the fields that contain the measured values that you want to use in the statistics. 8. Enter the Measured values range for the statistics. Only the measured values within this range will be included in the statistics. 9. Click OK. Atoll opens a window listing statistics of comparison between measured and predicted values.
13.4.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter You can extract information for a selected transmitter from a field of a drive test data path. The extracted information is available in a new column in the drive test data table. To extract a field from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to extract a field. The context menu appears. 4. Select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter dialogue appears. 5. Under On the transmitter, select the transmitter for which you want to extract a field. 6. Under For the fields, select the fields that you want to extract for the selected transmitter. 7. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitter and with the selected values.
13.4.4.6 Analysing Measurement Variations Along the Path In Atoll, you can analyse variations in measurements along any drive test data path using the Drive Test Data analysis tool. You can also use the Drive Test Data analysis tool to find serving cells of points. To analyse measurement variations using the Drive Test Data analysis tool. 1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears. 2. In the Drive Test Data analysis tool, click the Display button. The Display Parameters dialogue appears. 3. In the Display Parameters dialogue: • • •
Select the check box next to each field you want to display in the Drive Test Data analysis tool. If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new colour from the palette that appears. Click OK to close the Display Parameters dialogue. You can change the display status or the colour of more than one field at the same time by selecting several fields. You can select contiguous fields by clicking the first field, pressing Shift and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking each field. You can then change the display status or the colour by right-clicking on the selected fields and selecting the choice from the context menu. The selected fields are displayed in the Drive Test Data analysis tool.
4. You can display the data in the drive test data path in the following ways: • •
Click the values in the Drive Test Data analysis tool. 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 in the same colour as the transmitter. 5. You can display a secondary Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters dialogue. You select the value to be displayed from the right-hand list at the top of the Drive Test Data analysis tool. The values are displayed in the colour defined in the Display Parameters dialogue. 6. You can zoom in on the graph displayed in the Drive Test Data analysis tool in the following ways: •
1416
Zoom in or out:
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
i.
Right-click the Drive Test Data analysis tool. The context menu appears.
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 analysis tool on one end of the range of data you want to zoom in on. The context menu appears.
ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data analysis tool on the other end of the range of data you want to zoom in on. The context menu appears. iv. Select Last Zoom Point from the context menu. The Drive Test Data analysis tool zooms in on the data between the first zoom point and the last zoom point. 7. Click the data in the Drive Test Data analysis tool to display the selected point in the map window. Atoll will centre the map window on the selected point if it is not presently visible. If you open the table for the drive test data you are displaying in the Drive Test Data analysis tool, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data analysis tool.
13.4.5 Exporting a Drive Test Data Path You can export drive test data paths to files as vector data. To export a drive test data path to a vector file: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path 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.
13.4.6 Extracting CW Measurements from Drive Test Data You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path from which you want to export CW measurements. 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 Extraction parameters of CW measurement paths: a. Enter the Min. number of points to extract per measurement path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured signal levels. CW measurements are created with drive test data points where the signal levels are within this specified range. 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.
1417
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
13.4.7 Printing and Exporting the Drive Test Data Window You can print and export the contents of the Drive Test Data analysis tool. To print or export the contents of the Drive Test Data analysis tool: 1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears. 2. Define the display parameters and zoom level as explained in "Analysing Measurement Variations Along the Path" on page 1416. 3. Right-click the Drive Test Data analysis tool. The context menu appears. • •
To print the Drive Test Data analysis tool, select Print from the context menu. To export the Drive Test Data window, select Copy from the context menu, then paste.
13.5 Co-planning Wi-Fi Networks with Other Networks Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design a Wi-Fi and an LTE network for the same area in Atoll, and then work with Atoll’s co-planning features to study the mutual impacts of the two networks. You can also carry out analyses of mobile traffic offloading to Wi-Fi. In other words, Atoll allows you to perform network capacity analyses of your mobile network alone and in the case where you can have a Wi-Fi network available to carry a part of your mobile network’s traffic. Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. You can display network elements, geographic data, and coverage predictions, etc., of one network in the other network’s Atoll document. In this section, the following are explained: • • •
"Switching to Co-planning Mode" on page 1418. "Performing a Traffic Offload Analysis" on page 1420. "Ending Co-planning Mode" on page 1421.
13.5.1 Switching to Co-planning Mode Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have a Wi-Fi Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, The Wi-Fi document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems.
To switch to co-planning mode: 1. Open the main document. •
Select File > Open or File > New > From an Existing Database.
2. Link the other document with the open main document. a. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document. b. Select Document > Link With. The Link With dialogue appears. c. Select the document to be linked. d. Click Open.
1418
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
The selected document is opened in the same Atoll session as the main document and the two documents are linked. The Explorer window of the main document now contains a folder named Transmitters in [linked document], where [linked document] is the name of the linked document and another folder named Predictions in [linked document]. By default, only the Transmitters and Predictions folders of the linked document appear in the main document. If you want the Sites folder of the linked document to appear in the main document as well, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual. As soon as a link is created between the two documents, Atoll switches to co-planning mode and Atoll’s co-planning features are now available. When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll synchronises the display for the following: • • • •
Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.
Displaying Both Networks in the Same Atoll Document After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 1418, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the explorer window of the linked document to the explorer window of the main document (e.g., you can display LTE sites and measurement paths in a Wi-Fi document). To display sites from the linked document in the main document: 1. Click the linked document’s map window. The linked document’s map window becomes active and the explorer window shows the contents of the linked document. 2. Select the Network explorer. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In from the context menu, and select the name of the main document from the submenu that opens. The Sites folder of the linked document is now available in the main document. The Explorer window of the main document now contains a folder named Sites in [linked document], where [linked document] is the name of the linked document. If you want the Sites folder of the linked document to appear in the main document automatically, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual. The same process can be used to link other folders in one document, folders such as CW Measurements, Drive Test Data, Clutter Classes, Traffic, DTM, etc., in the other document. Once the folders are linked, you can access their properties and the properties of the items in the folders from either of the two documents. Any changes you make in the linked document are taken into account in the both the linked and main documents. However, because working document is the main document, any changes made in the main document are not automatically taken into account in the linked document. If you close the linked document, Atoll displays a warning icon (
) in the main document’s Explorer window, and the linked
items are no longer accessible from the main document. You can load the linked document in Atoll again by right-clicking the linked item in the explorer window of the main document, and selecting Open Linked Document. The administrator can create and set a configuration file for the display parameters of linked and main document transmitters in order to enable you to distinguish them on the map and to be able to select them on the map using the mouse. If such a configuration file has not been set up, you can choose different symbols, sizes and colours for the linked and the main document transmitters. For more information on folder configurations, see "Folder Configurations" on page 105. You can also set the tip text to enable you to distinguish the objects and data displayed on the map. For more information on tip text, see "Defining the Object Type Tip Text" on page 46. 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 Windows" on page 39.
1419
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
13.5.2 Performing a Traffic Offload Analysis You can also carry out traffic offload analysis in co-planning mode, i.e., study the amount of mobile traffic from a mobile network (LTE, UMTS, etc.) that can be carried by a Wi-Fi network layer deployed on top of the mobile network. To perform traffic offload analysis: 1. Switch to the mobile network document (linked document). 2. Select the Network explorer. 3. Right-click the Simulations folder. The context menu appears. 4. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 5. On the General tab of the dialogue, enter a Name for this simulation or group of simulations. 6. 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 in the Network explorer. 7. You can enter some Comments if you want. 8. On the Traffic tab, enter the following: •
Global scaling factor: If desired, enter a scaling factor to increase user density. The global scaling factor enables you to increase user density without changing traffic parameters or traffic maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps).
•
Select traffic maps to be used: Select the traffic maps in the mobile network technology (linked) document that you want to use for the simulation.
9. On the technology-specific tab, named after the technology of the linked mobile network document, define the load constraints and convergence criteria specific to the mobile network. 10. On the Wi-Fi tab, select the Take the Wi-Fi network into account check box and enter the following: •
Under Load constraints, enter the Max DL traffic load and Max UL traffic load. If you want to enter a global value for a maximum traffic load, click the button ( ) beside the box and select Global threshold. Then, enter a maximum traffic load. If you want to use the maximum traffic load as defined in the properties for each cell, click the
•
button ( ) beside the box and select Defined per cell. Under Convergence, enter the following parameters: • • •
DL traffic load convergence threshold: Enter the relative difference in terms of downlink traffic load that must be reached between two iterations. UL traffic load convergence threshold: Enter the relative difference in terms of uplink traffic load that must be reached between two iterations. UL noise rise convergence threshold: Enter the relative difference in terms of uplink noise rise that must be reached between two iterations.
11. On the Advanced tab, enter the following: • •
Max number of iterations: Enter the maximum number of iterations that Atoll should run to make convergence. Generator initialisation: Enter an integer as the generator initialisation value. If you enter "0," the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value. Using the same generated user and shadowing error distribution for several simulations can be useful when you want to compare the results of several simulations where only one parameter changes.
12. Once you have defined the simulation, click Calculate to save the defined simulation and calculate it immediately. When you calculate a Monte Carlo simulation in co-planning mode with Wi-Fi network taken into account, Atoll carries out the following steps: 1. Creates a mobile user distribution on the map based on the selected traffic maps from the mobile network document. 2. Sends this mobile distribution to the main Wi-Fi document. 3. Creates and runs a Wi-Fi Monte Carlo simulation in the Wi-Fi document, with the same parameters as those set in the mobile network document when creating the co-planning simulation, using the mobile distribution received from the mobile network document. In other words, traffic maps in the mobile network document are used to generate the traffic scenario. Any traffic maps available in the Wi-Fi document are not used.
1420
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
4. In order for a mobile generated by Atoll in step 1. to be taken into account in the Wi-Fi Monte Carlo simulation, the mobile’s service, terminal, and mobility type must exist in the traffic parameter definition in the Wi-Fi document. 5. Once the Wi-Fi Monte Carlo simulation is complete, the list of mobiles unable to connect to Wi-Fi is sent back to the mobile network document as potential users attempting to connect to the mobile network, and the list of mobiles connected to Wi-Fi is sent back to the mobile network document with their connection status set to "Connected WiFi." 6. Runs the mobile network Monte Carlo simulation using the list of mobiles unable to connect to Wi-Fi. The Monte Carlo simulation results in the mobile network document contain the number of mobiles connected to Wi-Fi, in addition to the usual results of the mobile network Monte Carlo simulations. The Wi-Fi Monte Carlo simulation results, in the Wi-Fi document, contain detailed results for the mobiles connected to Wi-Fi. For more information on the Monte Carlo simulation results available in Wi-Fi, see "Displaying the Results of a Single Simulation" on page 1403. In order to study the impact of a Wi-Fi network on your mobile network, you can perform Monte Carlo simulations in your mobile network document with and without taking the Wi-Fi network into account, and compare the statistics on the numbers of connected and rejected users, throughputs, and cell loads, in the two cases.
13.5.3 Ending Co-planning Mode Once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents. To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select Document > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.
13.6 Advanced Configuration The following sections describe different advanced parameters and options available in the Atoll Wi-Fi 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 1421 "The Global Network Settings" on page 1422 "Wi-Fi Frame Configurations" on page 1422 "Defining Wi-Fi Radio Bearers" on page 1423 "Defining Wi-Fi Quality Indicators" on page 1423 "Defining Wi-Fi Reception Equipment" on page 1424 "Multiple Input Multiple Output Systems" on page 1426 "Modelling Shadowing" on page 1427 "Modelling Inter-technology Interference" on page 1428.
13.6.1 Defining Frequency Bands To define frequency bands: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. Click the Expand button ( ) to expand the Frequencies folder. 4. In the Frequencies folder, right-click Bands. The context menu appears. 5. Select Open Table. The Frequency Bands table appears. 6. In the Frequency Bands table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each frequency band, enter: •
Name: Enter a name for the frequency band, for example, "2.4 GHz - 20 MHz." Each Wi-Fi frequency band has a specific channel width. Mentioning the channel width in the frequency band name is a good approach. This name will appear in other dialogues when you select a frequency band.
1421
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
• • • •
• •
Channel width (MHz): Enter the channel width for each channel in the frequency band. First channel: Enter the number of the first channel in this frequency band. Last channel: Enter the number of the last channel in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First channel field. Excluded channels: Enter the channel numbers which do not belong to the frequency band. You can enter nonconsecutive channel numbers separated with a comma, or you can enter a range of channel numbers separating the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5"). Start frequencies (MHz): Enter the downlink and uplink start frequencies. 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.
7. When you have finished adding frequency bands, click the Close button (
).
You can also access the properties dialogue of each individual frequency band by double-clicking the left margin of the table row containing the frequency band.
13.6.2 The Global Network Settings Atoll allows you to set network level parameters which are common to all the transmitters and cells in the network. These parameters are used in coverage predictions as well as during Monte Carlo simulations by the radio resource management and scheduling algorithms. This section explains the options available on the Calculation Parameters tab of the Network Settings folder properties, and explains how to access them: • •
"The Options on the Calculation Parameters Tab" on page 1422. "Modifying Global Network Settings" on page 1422.
13.6.2.1 The Options on the Calculation Parameters Tab The Wi-Fi calculation parameters include: •
Min interferer C/N threshold: Minimum requirement for interferers to be considered in calculations. Interfering cells from which the received carrier-power-to-noise ratio is less than this threshold are discarded. For example, setting this value to -20 dB means that interfering cells from which the received signals are 100 times lower than the thermal noise level will be discarded in calculations. The calculation performance of interferencebased coverage predictions, interference matrices calculations, and Monte Carlo simulations can be improved by setting a high value of this threshold.
•
•
Height: The receiver height at which the path loss matrices and coverage predictions are calculated. Calculations made on mobile users (from traffic maps) in Monte Carlo simulations are also carried out at this receiver height. Calculations made on fixed subscribers (from subscriber lists) in Monte Carlo simulations are carried out at their respective heights. Max range: The maximum coverage range of transmitters in the network.
13.6.2.2 Modifying Global Network Settings You can change global network settings in the properties dialogue of the Network Settings folder. To set the network level parameters: 1. Select the Parameters explorer. 2. Right-click the Network Settings folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Calculation Parameters tab. On this tab you can set: • • •
Calculation limitation: In this section, you can enter the Min interferer C/N threshold. Receiver: In this section, you can enter the receiver Height. System: In this section, select the Max range check box if you want to apply a maximum system range limit, and enter the maximum system range in the text box to the right.
5. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
13.6.3 Wi-Fi Frame Configurations The following Wi-Fi frame configurations are available in Atoll:
1422
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Total Number of Number of Used Number of Data Subcarriers Subcarriers Subcarriers
Diversity Support
802.11a — 20 MHz
64
52
48
None
802.11g — 20 MHz
64
52
48
None
802.11n — 20 MHz
64
52
48
AMSa
802.11n — 20 MHz (HTb)
64
56
52
AMS
802.11n — 40 MHz
128
104
96
AMS
802.11n — 40 MHz (HT)
128
114
108
AMS
802.11ac — 20 MHz (VHTc)
64
56
52
AMS
802.11ac — 40 MHz (VHT)
128
114
108
AMS
802.11ac — 80 MHz (VHT)
256
242
234
AMS
802.11ac — 160 MHz (VHT)
512
484
468
AMS
a. b. c.
Adaptive MIMO Switching High Throughput Very High Throughput Atoll currently supports Long Guard Interval.
13.6.4 Defining Wi-Fi Radio Bearers Wi-Fi radio bearers carry the data in the uplink as well as in the downlink. In Atoll Wi-Fi, a "bearer" refers to a combination of MCS, i.e., modulation, and coding schemes. The Radio Bearers table lists the available radio bearers. You can add, remove, and modify bearer properties, if you want. To define Wi-Fi bearers: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. In the Network Settings folder, right-click Radio Bearers. The context menu appears. 4. Select Open Table. The Radio Bearers table appears. 5. In the table, enter one bearer per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each Wi-Fi 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 reception 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. Channel coding rate: Enter the coding rate used by the bearer. This column is for information and display purposes only. Bearer efficiency (bits/symbol): Enter the number of useful bits that the bearer can carry in a symbol. This information is used in throughput calculations.
6. Click the Close button (
) to close the Radio Bearers table.
13.6.5 Defining Wi-Fi Quality Indicators Quality indicators depict the coverage quality at different locations. The Quality Indicators table lists the available quality indicators. You can add, remove, and modify quality indicators, if you want. To define quality indicators: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Network Settings folder.
1423
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
3. In the Network Settings folder, right-click Quality Indicators. The context menu appears. 4. Select Open Table. The Quality Indicators table appears. 5. In the table, enter one quality indicator per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each quality indicator, enter: • • •
Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear in other dialogues and results. Used for data services: Select this check box to indicate that this quality indicator can be used for data services. Used for voice services: Select this check box to indicate that this quality indicator can be used for voice services.
6. Click the Close button (
) to close the Quality Indicators table.
13.6.6 Defining Wi-Fi Reception Equipment Wi-Fi reception equipment model the reception characteristics of cells and user terminals. Bearer selection thresholds and channel quality indicator graphs are defined in Wi-Fi reception equipment. To create a new piece of reception equipment: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Network Settings folder. 3. In the Network Settings folder, right-click Reception Equipment. The context menu appears. 4. Select Open Table. The Reception Equipment table appears. 5. In the Reception Equipment table, each row describes a piece of equipment. For the new piece of equipment you are creating, enter its name. 6. Double-click the equipment entry in the Reception Equipment table once your new equipment has been added to the table. The equipment’s Properties dialogue opens. The Properties dialogue has the following tabs: • •
General: On this tab, you can define the Name of the reception equipment. Bearer Selection Thresholds: On this tab (see Figure 13.43), you can modify the bearer selection thresholds for different mobility types. A bearer is selected for data transfer at a given pixel if the received carrier-to-interference-and-noise ratio is higher than its selection threshold. For more information on bearers and mobility types, see "Defining Wi-Fi Radio Bearers" on page 1423 and "Modelling Mobility Types" on page 1371, respectively.
Figure 13.43: Wi-Fi Reception Equipment - Bearer Selection Thresholds i.
Click the Best bearer thresholds button to open the C/(I+N) Thresholds (dB) dialogue (see Figure 13.44).
ii. Enter the graph values. iii. Click OK.
1424
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Figure 13.44: C/(I+N) Thresholds (dB) dialogue For more information on the default values of the bearer selection thresholds, see "Bearer Selection Thresholds" on page 1430. For converting receiver equipment sensitivity values (dBm) into bearer selection thresholds, see "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1430. •
Quality Graphs: On this tab, you can modify the quality indicator graphs for different bearers and mobility types. These graphs depict the performance characteristics of the equipment under different radio conditions. For more information on bearers, quality indicators, and mobility types, see "Defining Wi-Fi Radio Bearers" on page 1423, "Defining Wi-Fi Quality Indicators" on page 1423, and "Modelling Mobility Types" on page 1371, respectively. i.
Click the Quality graph button to open the Quality Graph dialogue.
ii. Enter the graph values. iii. Click OK. •
MIMO: On this tab (see Figure 13.45), you can modify the SU-MIMO and STTD/MRC gains for different bearers, mobility types, BLER values, and numbers of transmission and reception antennas. The MIMO throughput gain is the increase in channel capacity compared to a SISO system. For more information on bearers and mobility types, see "Defining Wi-Fi Radio Bearers" on page 1423 and "Modelling Mobility Types" on page 1371, respectively. For more information on the different MIMO systems, see "Multiple Input Multiple Output Systems" on page 1426. No MIMO gain (STTD/MRC, SU-MIMO, and MU-MIMO) is applied if the numbers of transmission and reception antennas are both equal to 1.
1425
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
Figure 13.45: Wi-Fi Reception Equipment - MIMO gains i.
Enter the STTD/MRC gain for a combination of 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 (see Figure 13.46). iii. Enter the graph values. iv. Click OK. You can define the STTD/MRC and SU-MIMO gains for any combination of mobility type, bearer, and BLER, as well as the default gains for "All" mobility types, "All" bearers, and a max BLER of 1. During calculations, Atoll uses the gains defined for a specific combination if available, otherwise it uses the default gains.
Figure 13.46: Max SU-MIMO Gain dialogue 7. Click OK. The Properties dialogue closes. The settings are stored. 8. Click the Close button (
) to close the Reception Equipment table.
13.6.7 Multiple Input Multiple Output Systems Multiple Input Multiple Output (MIMO) systems use different transmission and reception diversity techniques. MIMO diversity systems can roughly be divided into the following types, all of which are modelled in Atoll:
1426
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Space-Time Transmit Diversity and Maximum Ratio Combining STTD uses more than one transmission antenna to send more than one copy of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining, MRC) at the receiver to extract the useful signal. As the receiver gets more than one copy of the useful signal, the signal level at the receiver after combination of all the copies is more resistant to interference than a single signal would be. Therefore, STTD improves the C/(I+N) at the receiver. It is often used for the regions of a cell that have insufficient C/(I+N). Different STTD coding techniques exist, such as STC (Space Time Coding), STBC (Space-Time Block Codes), and SFBC (Space-Frequency Block Codes). In Atoll, STTD/MRC gains on downlink and uplink can be defined in the reception equipment for different numbers of transmission and reception antennas, mobility types, bearers, and maximum BLER. For more information on uplink and downlink STTD/MRC gains, see "Defining Wi-Fi Reception Equipment" on page 1424. Additional gain values can be defined per clutter class. For information on setting the additional STTD/MRC uplink and downlink gains for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal will benefit from the downlink and uplink STTD/MRC gains. Single-User MIMO or Spatial Multiplexing SU-MIMO uses more than one transmission antenna to send different signals (data streams) on each antenna. The receiver can also have more than one antenna to receive different signals. Using spatial multiplexing with M transmission and N reception antennas, the throughput over the transmitter-receiver link can be theoretically increased M or N times, whichever is smaller. SU-MIMO improves the throughput (channel capacity) for a given C/(I+N), and is used for the regions of a cell that have sufficient C/(I+N). SU-MIMO (single-user MIMO) is also referred to as SM (spatial multiplexing) or simply MIMO. In Atoll, SU-MIMO capacity gains can be defined in the reception equipment for different numbers of transmission and reception antennas, mobility types, bearers, and maximum BLER. For more information on SU-MIMO gains, see "Defining Wi-Fi Reception Equipment" on page 1424. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal will benefit from the SU-MIMO gain in its throughput depending on its C/(I+N). When SU-MIMO improves the channel capacity or throughputs, the C/(I+N) of a user is first determined. Once the C/(I+N) is known, Atoll calculates the user throughput based on the bearer available at the user location. The obtained user throughput is then increased according to the SU-MIMO capacity gain and the SU-MIMO gain factor of the user’s clutter class. The capacity gains defined in Max SU-MIMO gain graphs are the maximum theoretical capacity gains using SU-MIMO. SU-MIMO requires rich multipath environment, without which the gain is reduced. In the worst case, there is no gain. Therefore, it is possible to define an SU-MIMO gain factor per clutter class whose value can vary from 0 to 1 (0 = no gain, 1 = 100% gain). For information on setting the SU-MIMO gain factor for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. Adaptive MIMO Switching Adaptive MIMO switching is a technique for switching from SU-MIMO to STTD/MRC as the radio conditions get worse than a given threshold. AMS can be used in cells to provide SU-MIMO gains to users under good radio conditions and STTD/MRC gains to users under bad radio conditions. AMS provides the optimum solution using STTD/MRC and SU-MIMO features to their best. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal will benefit from the gain to be applied, STTD/MRC or SU-MIMO, depending on the user’s C/N and the AMS threshold defined in the cell properties.
13.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 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.
1427
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
In Wi-Fi 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 145. 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 1347) A coverage prediction (see "Studying Signal Level Coverage" on page 1348).
Atoll always takes shadowing into consideration when calculating a Monte Carlo simulations. Atoll uses the values defined for the model standard deviations per clutter class when calculating the signal level coverage predictions. Atoll uses the values defined for the C/I standard deviations per clutter class when calculating the interference-based coverage predictions. You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per Clutter Class" on page 1428.
13.6.8.1 Displaying the Shadowing Margins per Clutter Class To display the shadowing margins per clutter class: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins dialogue appears. 4. You can set the following parameters: • •
Cell edge coverage probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard deviation: Select the type of standard deviation to be used to calculate the shadowing margin: • •
Model: The model standard deviation. Atoll will display the shadowing margin of the signal level. C/I: The C/I standard deviation. Atoll will display the C/I shadowing margin.
5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.
13.6.9 Modelling Inter-technology Interference Analyses of Wi-Fi networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference can create considerable capacity reduction in a Wi-Fi network. Atoll can take into account interference from co-existing networks in Monte Carlo simulations and coverage predictions. The following inter-technology interference scenarios are modelled in Atoll: •
Interference received by mobiles on the downlink: Interference can be received by mobiles in a Wi-Fi network on the downlink from other-network interferers in the vicinity. Downlink-to-downlink interference can be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (LTE, UMTS, CDMA2000, etc.). These graphs are then used for calculating the interference from the external sources. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-technology IRFs" on page 1429. Uplink-to-downlink interference can be created by insufficient separation between the uplink frequency used by the other network and the downlink frequency used by your Wi-Fi network. The effect of this interference is modelled in Atoll using the Inter-technology DL noise rise definable for each cell in the Wi-Fi network. This noise rise is taken into account in all downlink interference-based calculations. For more information on the Inter-technology DL noise rise, see "Cell Description" on page 1337.
1428
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
Figure 13.47: Interference received by mobiles on the downlink •
Interference received by cells on the uplink: Interference can be received by cells of a Wi-Fi network on the uplink from other-network interferers in the vicinity. Downlink-to-uplink interference can be created by insufficient separation between the downlink frequency used by the other network and the uplink frequency used by your Wi-Fi network. Uplink-to-uplink interference can be created by the use of same or nearby frequencies for uplink in both networks. . The effect of this interference is modelled in Atoll using the Inter-technology UL noise rise definable for each cell in the Wi-Fi network. This noise rise is taken into account in uplink interference calculations in Monte-Carlo simulations, but not in coverage predictions. For more information on the Inter-technology UL noise rise, see "Cell Description" on page 1337.
Figure 13.48: Interference received by cells on the uplink
13.6.9.1 Defining Inter-technology IRFs Interference received from external sources on mobiles of your Wi-Fi network can be calculated by Atoll. Atoll uses the intertechnology interference reduction factor (IRF) graphs for calculating the interference levels. An IRF graph represents the variation of the Adjacent Channel Interference Ratio (ACIR) as a function of frequency separation. ACIR is determined from the Adjacent Channel Suppression (ACS) and the Adjacent Channel Leakage Ratio (ACLR) parameters as follows: 1 ACIR = ------------------------------------1 1 ------------- + ----------------ACS ACLR
An IRF depends on: • • • •
The interfering technology (LTE, UMTS, CDMA2000, etc.) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).
IRFs are used by Atoll to calculate the interference from external sources only if the Atoll document containing the other network is linked to your Wi-Fi 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 1418. To define the inter-technology IRFs in the victim network: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Inter-technology Interference Reduction Factors. The context menu appears. 4. Select Open Table. The Inter-technology Interference Reduction Factors table appears.
1429
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
© Forsk 2012
5. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter: • • • •
Technology: The technology used by the interfering network. Interferer bandwidth (kHz): 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): 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. i.
Enter the interference reduction factors in the Reduction (dB) column for different frequency separation, Freq. delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document. • •
Reduction values must be positive. If you leave reduction factors undefined, Atoll assumes there is no interference.
ii. When done, click OK. 6. Click the Close button (
) to close the Inter-technology Interference Reduction Factors table.
You can link more than one Atoll document with your main document following the procedure described in "Switching to Coplanning Mode" on page 1418. 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 access points in all the linked documents.
13.7 Tips and Tricks The following tips and tricks are described below: • • • •
"Bearer Selection Thresholds" on page 1430. "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1430. "Modelling the Co-existence of Networks" on page 1430. "Serving (Reference) Cell Layer Selection Method" on page 1431.
Bearer Selection Thresholds The default values of the bearer selection thresholds, the BLER quality graphs, and the bearer efficiency values in Atoll have been extracted from the IEEE 802.11 specifications. These C/(I+N) values correspond to the receiver sensitivity values listed in the IEEE specifications. Calculating Bearer Selection Thresholds From Receiver Sensitivity Values You can convert the receiver sensitivity values, from your equipment data sheet, into bearer selection thresholds using the following conversion method: BW × N Used CNR = RS + 114 – NF – 10 × Log -------------------------------- – L Imp N Total
Where RS is the receiver sensitivity in dBm, NF is the noise figure of the receiver in dB, BW is the channel bandwidth in MHz, N Used is the number of used subcarriers, N Total is the total number of subcarriers, and L Imp is the implementation loss in dB. If you do not know the value for L Imp , you can ignore the corresponding term and simplify the equation. According to IEEE, typical values for NF and L Imp are 10 and 5 dB, respectively. Here the term receiver refers to the access point in uplink and to the mobile/user equipment in the downlink. Modelling the Co-existence of Networks In Atoll, you can study the effect of interference received by your network from other Wi-Fi networks. The interfering Wi-Fi network can be a different part of your own network, or a network belonging to another operator. To study interference from co-existing networks: 1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a Group of Access Points" on page 1345. 2. For the interfering network’s transmitters, set the Transmitter type to Inter-network (Interferer only) as explained in "Transmitter Description" on page 1335.
1430
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
AT312_UM_E1
During calculations, Atoll will consider the transmitters of type Inter-network (Interferer only) when calculating interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interference. Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network. If the interfering network is a part of your own network, this information would be readily available. However, if the interfering network belongs to another operator, the information available might not be accurate. Serving (Reference) Cell Layer Selection Method The reference cell layer selection method is used to determine the reference cell for transmitters with more than one cell. The best serving transmitter for a pixel, subscriber, or mobile is determined according to the received signal level from the cell with the highest power. If more than one cell of the same transmitter covers the pixel, subscriber, or mobile, the reference cell is determined as follows: • •
In coverage predictions, point analysis, and calculations on subscriber lists, the cell of the highest layer is selected as the serving (reference) cell. In Monte Carlo simulations, a random cell is selected as the serving (reference) cell. The reference cell once assigned to a mobile does not change during Monte Carlo simulations.
1431
Atoll 3.1.2 User Manual Chapter 13: Wi-Fi Networks
1432
© Forsk 2012
Chapter 14 LTE Networks This chapter provides the information to use Atoll to design, analyse, and optimise an LTE network.
In this chapter, the following are explained: •
"Designing an LTE Network" on page 1435
•
"Planning and Optimising LTE Base Stations" on page 1436
•
"Configuring Network Parameters Using the AFP" on page 1517
•
"Studying Network Capacity" on page 1526
•
"Optimising Network Parameters Using the ACP" on page 1555
•
"Verifying Network Capacity" on page 1558
•
"Co-planning LTE Networks with Other Networks" on page 1568
•
"Advanced Configuration" on page 1587
•
"Tips and Tricks" on page 1603
•
"Glossary of LTE Terms" on page 1608
Atoll 3.1.2 User Manual Chapter 14: Starting a Project
1434
© Forsk 2012
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
14 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 E-UTRA (Evolved UTRA) networks. LTE uses SOFDMA (Scalable Orthogonal Frequency Division Multiple Access) and SC-FDMA (Single-Carrier Frequency Division Multiple Access) technologies in the downlink and the uplink, respectively. The aim of LTE is to provide mobile broadband wireless access that supports handovers between LTE cells as well as between LTE and UMTS/GSM cells at high user speeds. 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 smart antennas and 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 analyse the following and other parameters for LTE channels in downlink and in uplink: • • • •
Signal levels The carrier-to-interference-and-noise ratio Service areas and radio bearer coverage Cell capacity and aggregate throughput per cell
Coverage predictions that depend on the network’s traffic loads can be created from either Monte Carlo simulation results or from a user-defined network load configuration (uplink and downlink traffic loads, and uplink noise rise). GSM GPRS EDGE, UMTS HSPA, CDMA2000, TD-SCDMA, and WiMAX networks can be planned in the same Atoll session. Before working with the Atoll LTE module for the first time, it is highly recommended to go through the "Glossary of LTE Terms" on page 1608. This will help you get accustomed to the terminology used by the 3GPP and in Atoll.
14.1 Designing an LTE Network Figure 14.1 depicts the process of creating and planning an LTE network. The steps involved in planning an LTE network are described below. The numbers refer to Figure 14.1. 1. Open an existing radio-planning document or create a new one ( 1 ). • •
You can open an existing Atoll document by selecting File > Open. You can create a new Atoll document as explained in Chapter 2: Starting an Atoll Project.
2. Configure the network by adding network elements and changing parameters ( 2 ). You can add and modify the following elements of base stations: • • •
"Creating or Modifying a Site" on page 1445. "Creating or Modifying a Transmitter" on page 1445. "Creating or Modifying a Cell" on page 1446.
You can also add base stations using a base station template (see "Placing a New Base Station Using a Station Template" on page 1446). 3. Carry out basic coverage predictions ( 3 ). • •
"Making a Point Analysis to Study the Profile" on page 1462. "Studying Signal Level Coverage" on page 1463 and "Signal Level Coverage Predictions" on page 1472.
4. Allocate neighbours ( 4 ). •
"Planning Neighbours" on page 1505.
5. Allocate frequencies ( 5 ). •
"Planning Frequencies" on page 1520.
1435
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
6. Allocate physical cell IDs ( 6 ). •
"Planning Physical Cell IDs" on page 1521.
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 1526). You can define cell load conditions manually either on the Cells tab of each transmitter’s Properties dialogue or in the Cells table (see "Creating or Modifying a Cell" on page 1446) ( 7d ).
8. Make LTE-specific signal quality coverage predictions using the defined cell load conditions ( 8 ). •
"LTE Coverage Predictions" on page 1486.
9. If necessary, modify network parameters to study the network with a different frequency plan ( 10 ). After modifying the network’s frequency plan, you must perform steps 7 and 8 again. 1
2
3
4
5
6 7a
7d
7c
7b 7
8
9
10
Figure 14.1: Planning an LTE network - workflow
14.2 Planning and Optimising LTE Base Stations As described in Chapter 2: Starting an Atoll Project, you can create an Atoll document from a template, with no base stations, or from a database with an existing set of base stations. As you work on your Atoll document, you will still need to create base stations and modify existing ones. In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any additional equipment, such as the TMA, feeder cables, etc. In an LTE project, you must also add cells to each transmitter. A cell refers to the characteristics of an RF channel on a transmitter.
1436
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Atoll lets you create one site, transmitter, or cell at a time, or create several at once using station templates. In Atoll, a base station refers to a site and a transmitter with its antennas, equipment, and cells. In Atoll, you can study a single base station or a group of base stations using coverage predictions. Atoll allows you to make a variety of coverage predictions, such as signal level or signal quality coverage predictions. The results of calculated coverage predictions can be displayed on the map, compared, and studied. Atoll enables you to model network traffic by creating services, users, user profiles, traffic environments, and terminals. This data can be then used to make coverage predictions that depend on network load, such as C/(I+N), service area, radio bearer, and throughput coverage predictions. In this section, the following are explained: • • • • • • • • • • • • •
"Creating an LTE Base Station" on page 1437 "Creating a Group of Base Stations" on page 1453 "Modifying Sites and Transmitters Directly on the Map" on page 1453 "Display Tips for Base Stations" on page 1453 "Creating a Multi-band LTE Network" on page 1454 "Creating a Repeater" on page 1454 "Creating a Remote Antenna" on page 1458 "Setting the Working Area of an Atoll Document" on page 1461 "Studying a Single Base Station" on page 1462 "Studying Base Stations" on page 1465 "Planning Neighbours" on page 1505 "Planning Frequencies" on page 1520 "Planning Physical Cell IDs" on page 1521.
14.2.1 Creating an LTE Base Station When you create a site, you create only the geographical point; you must add the transmitters and cells afterwards. The site, with the transmitters, antennas, equipment, and cells is called a base station. In this section, each element of a base station is described. If you want to add a new base station, see "Placing a New Base Station Using a Station Template" on page 1446. If you want to create or modify one of the elements of a base station, see "Creating or Modifying a Base Station Element" on page 1444. If you need to create a large number of base stations, Atoll allows you to import them from another Atoll document or from an external source. For information, see "Creating a Group of Base Stations" on page 1453. This section explains the various parts of the base station creation process: • • • • •
"Definition of a Base Station" on page 1437. "Creating or Modifying a Base Station Element" on page 1444. "Placing a New Base Station Using a Station Template" on page 1446. "Managing Station Templates" on page 1447. "Duplicating an Existing Base Station" on page 1451.
14.2.1.1 Definition of a Base Station A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. You will usually create a new base station using a station template, as described in "Placing a New Base Station Using a Station Template" on page 1446. This section describes the following elements of a base station and their parameters: • • •
14.2.1.1.1
"Site Description" on page 1437 "Transmitter Description" on page 1438 "Cell Description" on page 1441.
Site Description The parameters of a site can be found in the site’s Properties dialogue. The Properties dialogue has the following tab: •
The General tab (see Figure 14.2): • •
Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If you want to change the default name that Atoll gives to new sites, see the Administrator Manual. Position: By default, Atoll places the new site at the centre of the map window. You can modify the location of the site here. While this method allows you to place a site with precision, you can also place sites using the mouse and then position them precisely with this dialogue afterwards. For information on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 41.
1437
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
•
•
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.
Figure 14.2: New Site dialogue
14.2.1.1.2
Transmitter Description The parameters of a transmitter can be found in the transmitter’s 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 1441), the Propagation tab (see Chapter 5: Working with Calculations in Atoll), and the Display tab (see "Display Properties of Objects" on page 43). •
The General tab: •
•
•
•
Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You can enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names transmitters, see the Administrator Manual. Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you can click the Browse button ( ) to access the properties of the site. For information on the site Properties dialogue, see "Site Description" on page 1437. You can click the New button to create a new site for the transmitter. Shared antenna: This field is used to identify the transmitters, repeaters, and remote antennas located at the same site or on sites with the same position and that share the same antenna. The entry in the field must be the same for all transmitters, repeaters, and remote antennas sharing the same antenna. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna position, you can modify the position of the antennas (main and secondary): • •
•
1438
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 this option if you want to enter the coordinates of the antenna, and then enter the x-axis and y-axis coordinates of the antenna, X and Y, respectively.
The Transmitter tab (see Figure 14.3):
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.3: 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 LTE Transmitters folder of the Network explorer. Only active transmitters are taken into consideration during calculations.
•
Transmitter type: If you want Atoll to consider the transmitter as a potential server as well as an interferer, set the transmitter type to Intra-network (Server and interferer). If you want Atoll to consider the transmitter only as an interferer, set the type to Inter-network (Interferer only). No coverage for an interferer only transmitter will be calculated for coverage predictions and it will not serve any mobile in Monte Carlo simulations. This enables you to model the co-existence of different networks in the same geographic area. For more information on how to study interference between co-existing networks, see "Modelling the Co-existence of Networks" on page 1606.
•
•
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 14.4), 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 176.
•
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 176. Transmitter equipment: You can select transmitter equipment from the Transmitter list. You can click the
•
• •
Browse button ( ) to access the properties of the transmitter equipment. For information on creating transmitter equipment, see "Defining Transmitter Equipment" on page 176. 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.
1439
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.4: The Equipment Specifications dialogue Any loss related to the noise due to a transmitter’s repeater is included in the calculated losses. Atoll always considers the values in the Real boxes in coverage predictions even if they are different from the values in the Computed boxes. The information in the real Noise figure box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Total losses at transmission and reception and the real Noise figure at reception. Any value you enter must be positive. •
Antennas: •
•
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered must include the height of building. AAS power combining gain: The AAS power combining gain is calculated automatically depending on the number of antenna elements on the smart antenna equipment, if any, assigned to the transmitter. This gain is applied to the downlink transmission power for reference signals and other control channels 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. Clicking the Select button opens a dialogue displaying all the possible antennas based on the same physical antenna as the currently selected one. Selecting the Electrical tilt of the antenna model displays the appropriate antennas under Available antennas. Selecting the antenna under Available antennas and clicking OK assigns the antenna to the transmitter. The other fields, Azimuth, Mechanical downtilt, and Additional electrical downtilt, display additional antenna parameters. • • •
•
•
•
1440
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. The mechanical and additional electrical downtilts defined for the main antenna are also used for the calculations of smart antennas.
Smart antenna: Under Smart antenna, the smart antenna equipment is available in the Equipment list. You can click the Browse button ( ) to access the properties of the smart antenna equipment. When you select smart antenna equipment, you can choose whether to keep the current main antenna model or to replace it with the main antenna model defined for the selected smart antenna equipment, if any. For more information on smart antenna equipment, see "Defining Smart Antenna Equipment" on page 1597. 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 1599. Under Secondary antennas, you can select one or more secondary antennas in the Antenna column and enter their Azimuth, Mechanical downtilt, and % Power, which is the percentage of power reserved for this particular antenna. For example, for a transmitter with one secondary antenna, if you reserve 40% of the total power for the secondary antenna, 60% is available for the main antenna.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• • •
•
•
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
The transmission power is divided among the main and secondary antennas. This is not compatible with smart antennas. You must not assign smart antennas to transmitters with secondary antennas, and vice versa. In calculations, repeaters and remote antennas are transparent to the donor transmitters and the served users. For example, beamforming smart antennas at donor transmitters create beams directly towards the served users, and not towards the repeater or remote antenna that covers the users. This results in a combined signal level received from the transmitter using the smart antenna and from the repeater or remote antenna. If this approach does not match how your equipment works, you must not assign smart antennas to transmitters with repeaters and remote antennas, and vice versa. This is also true for MIMO.
The main antenna is used to transmit the control channels. Coverage predictions based on the reference signals are performed using the main antenna. The main antenna is also used for traffic if there is no smart antenna equipment selected for the transmitter, or if the cells do not support AAS. If smart antenna equipment is assigned to the transmitter and the cells support AAS, traffic data are transmitted and received using the smart antenna, whereas the control channels are transmitted using the main antenna.
14.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 automatically creates a cell for the transmitter using the properties of the currently selected station template. The following explains the parameters of an LTE cell. 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 belongs. 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. 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 Network Settings" on page 1588. Frequency band: The cell’s 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 without cost. • Allocated: The current channel has been allocated automatically or manually. The AFP considers that an Allocated channel is modifiable but only if absolutely necessary. • Locked: The current channel has been allocated automatically or manually. The AFP considers that a Locked channel is not modifiable. For more information on the AFP, see "Configuring Network Parameters Using the AFP" on page 1517.
•
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 cell’s reference signals transmit a pseudo-random sequence corresponding to the physical cell ID of the cell. Physical cell IDs also indicate the subcarriers being used for reference signal transmission in the downlink. Reference signal hopping, or v-shifting, is the calculation of the index of the subcarrier being used for reference signal resource elements. The v-shifting index is calculated as (PCI)Mod 6 for single-antenna transmitters and as (PCI)Mod 3 for multiantenna transmitters.
•
PSS ID: The PSS ID corresponding to the current physical cell ID. This value is determined automatically from the physical cell ID.
1441
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• •
• •
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 AFP considers that a Not allocated physical cell ID is modifiable without cost. • Allocated: The current physical cell ID has been allocated automatically or manually. The AFP considers that an Allocated physical cell ID is modifiable but only if absolutely necessary. • Locked: The current physical cell ID has been allocated automatically or manually. The AFP considers that a Locked physical cell ID is not modifiable. Physical cell ID domain: The physical cell ID domain to which the allocated physical cell ID belongs. This and the reuse distance are used by the AFP for physical cell ID allocation. Reuse distance: The minimum reuse distance after which the channel or physical cell ID assigned to this cell can be assigned to another cell by the AFP. For more information on the AFP, see "Configuring Network Parameters Using the AFP" on page 1517.
•
Max power (dBm): The cell’s maximum transmission power. You can enter or modify this value if the RS EPRE option under the Advanced options on the Global Parameters tab of the LTE Network Settings folder’s Properties dialogue is set to any of the following: • • • •
Calculated (equal distribution of unused EPRE) Calculated (with boost): This option corresponds to a 3 dB boost in the RS EPRE with 2 transmission antenna ports and 6 dB boost with 4 ports. Calculated (without boost) Independent of max power
The transmission powers corresponding to different channels are calculated using Max power, the energy per resource element offsets defined for the SS, PBCH, PDSCH, and PDCCH, and the number of resource elements corresponding to each channel, all of which are also calculated by Atoll. Max power is calculated by Atoll from the user-defined RS EPRE value if the RS EPRE option in the Global Parameters of the LTE Network Settings folder is set to User-defined. •
RS EPRE (dBm): The reference signal energy per resource element. You can enter or modify this value if the RS EPRE option under the Advanced options on the Global Parameters tab of the LTE Network Settings folder’s Properties dialogue is set to User-defined or Independent of max power. This value is calculated by Atoll from the user-defined max power value if the RS EPRE option under the Advanced options on the Global Parameters tab of the LTE Network Settings folder’s Properties dialogue is set to any of the following: • • •
Calculated (equal distribution of unused EPRE) Calculated (with boost): This option corresponds to a 3 dB boost in the RS EPRE with 2 transmission antenna ports and 6 dB boost with 4 ports. Calculated (without boost)
For more information, see "The Global Network Settings" on page 1588. •
•
•
•
SS EPRE Offset/RS (dB): The difference in the energy of a resource element belonging to the synchronisation signals with respect to the energy of a reference signal resource element. This value is used to calculate the transmission power corresponding to the primary and secondary synchronisation signals (PSS, SSS). PBCH EPRE Offset/RS (dB): The difference in the energy of a resource element belonging to the PBCH with respect to the energy of a reference signal resource element. This value is used to calculate the transmission power corresponding to the physical broadcast channel (PBCH). PDCCH EPRE Offset/RS (dB): The difference in the energy of a resource element belonging to the PDCCH with respect to the energy of a reference signal resource element. This value is used to calculate the transmission power corresponding to the physical downlink control channel (PDCCH). PDSCH EPRE Offset/RS (dB): The difference in the energy of a resource element belonging to the PDSCH with respect to the energy of a reference signal resource element. This value is used to calculate the transmission power corresponding to the physical downlink shared channel (PDSCH). Atoll first calculates the energy per resource element corresponding to the reference signal resource elements, the SS, PBCH, PDSCH, and PDCCH. Once the energies available for each of these resource element types are known, they are converted into transmission powers for further calculations. In the offset fields above, you 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.
• •
1442
Instantaneous RS power (dBm): The instantaneous reference signal transmission power calculated from the maximum power or RS EPRE and the EPRE offsets. Instantaneous SS power (dBm): The instantaneous SS transmission power calculated from the maximum power or RS EPRE and the EPRE offsets.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• • •
Instantaneous PBCH power (dBm): The instantaneous PBCH transmission power calculated from the maximum power or RS EPRE and the EPRE offsets. Average PDCCH power (dBm): The average PDCCH transmission power calculated from the maximum power or RS EPRE and the EPRE offsets. Average PDSCH power (dBm): The average PDSCH transmission power calculated from the maximum power or RS EPRE and the EPRE offsets. If the cell’s transmitter has smart antenna equipment assigned to it, the transmission powers of the cell increase by 10 × Log ( n ) (in dB), where n is the number of antenna elements of the smart antenna. This gain in transmission powers is referred to as the AAS power combining gain.
• • •
• • • •
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 cell’s coverage or not. Reception equipment: You can select the cell’s reception equipment from the reception equipment list. For more information, see "Defining LTE Reception Equipment" on page 1592. 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 1595. 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 cell’s frequency band is TDD. If the network’s 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 network’s 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 Network Settings" on page 1588. TDD frame configuration is hidden when there is no TDD frequency band defined in the Frequency Bands table (see "Defining Frequency Bands" on page 1587.
•
•
Diversity support (DL): The type of antenna diversity technique (transmit diversity, SU-MIMO, AMS, or AAS) supported by the cell in downlink. You cannot select more than one type of MIMO technique (transmit diversity, SUMIMO, or AMS) at a time. 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 are performed (and gains applied) for terminals supporting AAS and MIMO.
•
•
•
•
•
•
AMS & MU-MIMO threshold (dB): For AMS, it is the reference signal C/N or C/(I+N) threshold, according to the option set in the Advanced parameters ("The Global Network Settings" on page 1588), for switching from SU-MIMO to Transmit or receive diversity. 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 1599. 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 power control on the uplink. The difference between the Max PUSCH C/(I+N) and the uplink noise rise of the cell corresponds to the nominal PUSCH power for the cell. The nominal PUSCH power is a cell-specific parameter from which a limit on the uplink transmission powers of mobiles in the cell can be extracted. This factor is represented by P O_PUSCH in 3GPP specifications. Max PUSCH C/(I+N) is updated during uplink noise rise control in Monte Carlo simulations based on the maximum noise rise constraints of the neighbouring cells. 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 the AFP by allocating physical cell IDs. For more information, see "Planning Physical Cell IDs" on page 1521. ICIC configuration: The inter-cell interference coordination (ICIC) configuration used by the cell in downlink and uplink. ICIC configuration defines the numbers of frequency blocks available in the ICIC parts of the frames when the cell supports Static DL or Static UL inter-cell interference coordination. For more information, see "Defining ICIC Con-
1443
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
•
•
• •
•
• • •
•
• •
•
•
• • •
figurations" on page 1600. 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. Max traffic load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a downlink traffic load greater than this maximum. Traffic load (DL) (%): The downlink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations. 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 userdefined or an output of Monte Carlo simulations. Max traffic load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink traffic load greater than this maximum. Traffic load (UL) (%): The uplink traffic load percentage. This can be user-defined or an output of Monte Carlo simulations. 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 user-defined or an output of Monte Carlo simulations. Max UL noise rise (dB): The upper limit on both uplink noise rise values, i.e., the UL noise rise and the ICIC UL noise rise. It is used for uplink noise rise control during Monte Carlo simulations. This parameter represents the maximum interference that a cell can tolerate on the uplink. Angular distributions of interference (AAS): The Monte Carlo simulation results generated for transmitters using a smart antenna. These results are the angular distributions of the downlink traffic power spectral density. AAS usage (DL) (%): The total downlink traffic load that corresponds to the traffic loads of the users supported by the smart antenna. For example, if the downlink traffic load is 80%, and you set the AAS usage to 50%, it means that 40% downlink traffic load is supported by the smart antenna equipment while the other 40% is supported by the main antenna. AAS usage is calculated during Monte Carlo simulations, and cannot be modified manually because the AAS usage values correspond to the angular distributions of interference. 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 Monte Carlo simulations. It is not used in predictions where Atoll calculates the uplink total interference from the uplink noise rise which includes inter-technology uplink interference. For more information on inter-technology interference, see "Modelling Inter-technology Interference" on page 1601. 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 1601. Max number of intra-technology neighbours: The maximum number of LTE neighbours that the cell can have. Max number of inter-technology neighbours: The maximum number of other technology neighbours that the cell can have. Neighbours: You can access a dialogue in which you can set both intra-technology and inter-technology neighbours by clicking the Browse button ( page 1505.
). For information on defining neighbours, see "Planning Neighbours" on
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.
14.2.1.2 Creating or Modifying a Base Station Element A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for example, cells. This section describes how to create or modify the following elements of a base station: • • •
1444
"Creating or Modifying a Site" on page 1445 "Creating or Modifying a Transmitter" on page 1445 "Creating or Modifying a Cell" on page 1446
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
14.2.1.2.1
Creating or Modifying a Site You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site Description" on page 1437, through the site’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new site or modifying an existing site. To create a new site: 1. Select the Network explorer. 2. Right-click the Sites folder. The context menu appears. 3. Select New from the context menu. The Sites: New Element Properties dialogue appears (see Figure 14.2 on page 1438). 4. Modify the parameters described in "Site Description" on page 1437. 5. Click OK. To modify the properties of an existing site: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Sites folder. 3. Right-click the site you want to modify. The context menu appears. 4. Select Properties from the context menu. The site’s Properties dialogue appears. 5. Modify the parameters described in "Site Description" on page 1437. 6. Click OK. If you are creating several sites at the same time, or modifying several existing sites, you can do it quickly by editing or pasting the data directly in the Sites table. You can open the Sites table by right-clicking the Sites folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
14.2.1.2.2
Creating or Modifying a Transmitter You can modify an existing transmitter or you can create a new transmitter. When you create a new transmitter, its initial settings are based on the default station template displayed in the Radio Planning toolbar. You can access the properties of a transmitter, described in "Transmitter Description" on page 1438, through the transmitter’s Properties dialogue. How you access the Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter. To create a new transmitter: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select New from the context menu. The Transmitters: New Element Properties dialogue appears (see Figure 14.3). 4. Modify the parameters described in "Transmitter Description" on page 1438. 5. Click OK. When you create a new transmitter, Atoll automatically creates a cell based on the default station template. For information on creating a cell, see "Creating or Modifying a Cell" on page 1446. To modify the properties of an existing transmitter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the LTE Transmitters folder. 3. Right-click the transmitter you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Modify the parameters described in "Transmitter Description" on page 1438. 6. Click OK.
1445
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
•
•
14.2.1.2.3
If you are creating several transmitters at the same time, or modifying several existing transmitters, you can do it more quickly by editing or pasting the data directly in the Transmitters table. You can open the Transmitters table by rightclicking the LTE Transmitters folder in the Network explorer and selecting Open Table from the context menu. For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77. If you want to add a transmitter to an existing site on the map, you can add the transmitter by right-clicking the site and selecting New Transmitter from the context menu.
Creating or Modifying a Cell You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell Description" on page 1441, through the Properties dialogue of the transmitter where the cell is located. How you access the Properties dialogue depends on whether you are creating a new cell or modifying an existing cell. To create or modify a cell: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the LTE Transmitters folder. 3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu appears. 4. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 5. Select the Cells tab. 6. Modify the parameters described in "Cell Description" on page 1441. 7. Click OK. •
•
If you are creating or modifying several cells at the same time, you can do it more quickly by editing the data directly in the Cells table. You can open the Cells table by right-clicking the LTE Transmitters folder in the Network explorer and selecting Cells > Open Table from the context menu. You can either edit the data in the table, paste data into the table (see "Copying and Pasting in Tables" on page 77), or import data into the table (see "Importing Tables from Text Files" on page 82). If you want to add a cell to an existing transmitter on the map, you can add the cell by right-clicking the transmitter and selecting New Cell from the context menu.
14.2.1.3 Placing a New Base Station Using a Station Template In Atoll, a base station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can create a network by placing base stations based on station templates. This allows you to build your network quickly with consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding the cells. To place a new station using a station template: 1. In the Radio Planning toolbar, select a template from the list.
2. Click the New Transmitter or Station button (
) in the Radio Planning 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 pointer’s current location are visible in the Status bar.
4. Click to place the station.
1446
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
•
•
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 49. 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 "Modifying a Station Template" on page 1448. To place a series of base stations within a defined area: 1. In the Radio Planning toolbar, select a template from the list (see Figure 14.5). 2. Click the Hexagonal Design button ( ) to the right of the station template list. A hexagonal design is a group of base stations created from the same station template. 3. Draw a zone delimiting the area where you want to place the series of base stations: a. Click once on the map to start drawing the zone. b. Click once on the map to define each point on the map where the border of the zone changes direction. c. Click twice to finish drawing and close the zone. Atoll fills the delimited zone with new base stations and their hexagonal shapes. Base station objects such as sites and transmitters are also created and placed into their respective folders. You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for example, another antenna to a transmitter. Placing a Station on an Existing Site When you place a new station using a station template as explained in "Placing a New Base Station Using a Station Template" on page 1446, the site is created at the same time as the station. However, you can also place a new station on an existing site. To place a base station on an existing site: 1. In the Network explorer, clear the display check box beside the Hexagonal Design folder. 2. In the Radio Planning toolbar, select a template from the list. 3. Click the New Transmitter or Station button (
) in the Radio Planning 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.
14.2.1.4 Managing Station Templates Atoll comes with LTE station templates, but you can also create and modify station templates. The tools for working with station templates are on the Radio Planning toolbar (see Figure 14.5).
Figure 14.5: The Radio Planning toolbar In this section, the following are explained: • • • • •
14.2.1.4.1
"Creating a Station Template" on page 1447 "Modifying a Station Template" on page 1448 "Copying Properties from One Station Template to Another" on page 1451 "Modifying a Field in a Station Template" on page 1451 "Deleting a Station Template" on page 1451.
Creating a Station Template When you create a station template, you can do so by selecting an existing station template that most closely resembles the station template you want to create and making a copy. Then you can modify the parameters that differ.To create a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears.
1447
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
4. Select Open Table from the context menu. The Station Templates table appears. 5. In the Station Templates table, right-click the station template that most closely resembles the station template you want to create. The context menu appears. 6. Select Copy from the context menu. 7. Right-click the row marked with the New row icon (
). The context menu appears.
8. Select Paste from the context menu. The station template you copied in step 5. is pasted in the new row, with the Name of the new station template given as the same as the template copied but preceded by "Copy of". 9. Edit the parameters of the new station template in the table or as explained in "Modifying a Station Template" on page 1448.
14.2.1.4.2
Modifying a Station Template You can modify a station template directly in the Station Templates table, or you can open the Properties dialogue for that station template and modify the parameters in the dialogue. To modify a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. Right-click the station template you want to modify. The context menu appears. 6. Select Record Properties from the context menu. The station template’s Properties dialogue appears. 7. Click the General tab of the Properties dialogue. On this tab (see Figure 14.6), 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: 1st sector azimuth, from which the azimuth of the other sectors are offset to offer complete coverage of the area, the Height/ground of the antennas from the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must include the height of the building), the Mechanical downtilt, and the Additional electrical downtilt for the antennas. • •
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide.
Under Main antenna, you can select the main antenna Model, under Smart antenna, you can select the smart antenna Equipment used by the transmitter, and under Number of antenna ports, you can enter the number of antennas used for Transmission and for Reception for MIMO. •
•
1448
Under Path loss matrices, you can modify the following: the Main propagation model, the Main radius, and the Main resolution, and the Extended propagation model, the Extended radius, and the Extended resolution. For information on propagation models, see Chapter 5: Working with Calculations in Atoll. Under Comments, you can add additional information. The information you enter will be the default information in the Comments field of any transmitter created using this station template.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.6: Station Template Properties dialogue – General tab 8. Click the Transmitter tab. On this tab (see Figure 14.7), if the Active check box is selected, you can modify the following under Transmission/Reception: you can click the Equipment button to open the Equipment Specifications dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or transmitter equipment. For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 1438. 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 14.4 on page 1440). Any loss related to the noise due to a transmitter’s 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 computed Noise figure box is calculated from the information you entered in the Equipment Specifications dialogue. You can modify the real Noise figure at reception if you want. Any value you enter must be positive.
Figure 14.7: Station Template Properties dialogue – Transmitter tab 9. Click the LTE tab. On this tab (see Figure 14.8), you can modify the following: •
Under Power and EPRE offsets relative to the reference signals EPRE, you can modify the Max power, RS EPRE, and the EPRE offsets for the SS, PBCH, PDSCH, and PDCCH in SS offset, PBCH offset, PDCCH offset, and PDSCH offset.
1449
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
•
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.
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, Reuse distance, Reception 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 1601.
Figure 14.8: Station Template Properties dialogue – LTE tab 10. Click the Neighbours tab. On this tab (see Figure 14.9), you can modify the following: •
1450
Under Max number of neighbours, you can set the maximum numbers of Intra-technology and Inter-technology neighbours.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.9: Station Template Properties dialogue – Neighbours tab 11. 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. 12. When you have finished setting the parameters for the station template, click OK to close the dialogue and save your changes.
14.2.1.4.3
Copying Properties from One Station Template to Another You can copy properties from one template to another template by using the Station Templates table. To copy properties from one template to another template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Open Table from the context menu. The Station Templates table appears. 5. In the 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.
14.2.1.4.4
Modifying a Field in a Station Template You can add, delete, and edit user-defined data table fields in the Station Templates table. If you want to add a user-defined field to the station templates, you must have already added it to the Sites table for it to appear as an option in the station template properties To access the station templates data table field definition dialogue: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. Right-click the Station Templates folder. The context menu appears. 4. Select Properties from the context menu. The Station Template Properties dialogue appears. 5. Select the Table tab. 6. For information on adding, deleting, and editing user-defined fields, see "Adding, Deleting, and Editing Data Table Fields" on page 70). 7. When you have finished, Click OK.
14.2.1.4.5
Deleting a Station Template To delete a station template: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. Click the Expand button ( ) to expand the Station Templates folder. 4. In the Station Templates folder, right-click the station template you want to delete. The context menu appears. 5. Select Delete from the context menu. The template is deleted.
14.2.1.5 Duplicating an Existing Base Station You can create new base stations by duplicating an existing base station. When you duplicate an existing base station, the base station you create will have the same transmitter, and cell parameter values as the original base station. If no site exists where
1451
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
you place the duplicated base station, Atoll will create a new site with the same parameters as the site of the original base station. Duplicating a base station allows you to: • •
Quickly create a new base station with the same settings as an original one in order to study the effect of a new station on the coverage and capacity of the network, and Quickly create a new homogeneous network with base stations that have the same characteristics.
To duplicate an existing base station: 1. Select the Network explorer. 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 > Without Neighbours from the context menu, if you want to duplicate the base station without the intra- and inter-technology neighbours of its transmitters. Select Duplicate > With Outward Neighbours from the context menu, if you want to duplicate the base station along with the lists of intra- and inter-technology neighbours of its transmitters.
5. Place the new base station on the map using the mouse: •
Creating a duplicate base station and site: In the map window, move the pointer over the map to where you would like to place the duplicate. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 14.10).
Figure 14.10: Creating a duplicate base station and site •
Placing the duplicate base station on an existing site: In the map window, move the pointer over the existing site where you would like to place the duplicate. When the pointer is over the site, the site is automatically selected. The exact coordinates of the pointer’s current location are visible in the Status bar (see Figure 14.11).
Figure 14.11: Placing the duplicate base station on an existing site •
•
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 49. 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. If the duplicate base station was placed on a new site, the site, transmitters, and cells of the new base station have the same names as the site, transmitters, and cells of the original base station with each name marked as "Copy of." The site, transmitters, and cells of the duplicate base station have the same settings as those of the original base station. If the duplicate base station was placed on an existing site, the transmitters, and cells of the new base station have the same names as the transmitters, and cells of the original base station with each name preceded by the name of the site on which the duplicate was placed. All the remote antennas and repeaters of any transmitter on the original site are also duplicated. Any duplicated remote antennas and repeaters will retain the same donor transmitter as the original. If you want the duplicated remote antenna or repeater to use a transmitter on the duplicated base station, you must change the donor transmitter manually.
1452
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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 1437.
14.2.2 Creating a Group of Base Stations You can create base stations individually as explained in "Creating an LTE Base Station" on page 1437, or you can create one or several base stations by using station templates as explained in "Placing a New Base Station Using a Station Template" on page 1446. However, if you have a large project and you already have existing data, you can import this data into your current Atoll document and create a group of base stations. 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 121. You can import base station data in the following ways: •
Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the tables in your current Atoll document. When you create a group of base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. The table you copy 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 77. •
Importing data: If you have base station data in text or comma-separated value (CSV) format, you can import it into the tables in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select what values you import into which columns of the table. When you create a group of base stations by importing data, you must import site data in the Sites table, transmitter data in the Transmitters table, and cell data in the Cells table, in that order. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80. For information on importing table data, see "Importing Tables from Text Files" on page 82.
14.2.3 Modifying Sites and Transmitters Directly on the Map In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu in the Network explorer. However, in a complex radio-planning project, it can be difficult to find the data object in the Network explorer, although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters directly from the map. You can also select a site to display all of the transmitters located on it in the Site Configuration window. When selecting a transmitter, if there is more than one transmitter with the same azimuth, clicking the transmitters in the map window opens a context menu allowing you to select the transmitter. You can also change the position of the station by dragging it, or by letting Atoll find a higher location for it. Modifying sites and transmitters directly on the map is explained in detail in Chapter 1: The Working Environment: • • • • • •
"Working with the Site Configuration Window" on page 37 "Selecting One of Several Transmitters" on page 41 "Moving a Site Using the Mouse" on page 41 "Moving a Site to a Higher Location" on page 42 "Changing the Azimuth of the Antenna Using the Mouse" on page 42 "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42.
14.2.4 Display Tips for Base Stations Atoll allows to you to display information about base stations in a number of ways. This enables you not only to display selected information, but also to distinguish base stations at a glance. The following tools can be used to display information about base stations:
1453
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
•
•
•
•
Label: You can display information about each object, such as each site or transmitter, in the form of a label that is displayed with the object. You can display information from every field in that object type’s data table, including from fields that you add. The label is always displayed, so you should choose information that you would want to always be visible; too much information in the label will make it harder to distinguish the information you are looking for. For information on defining the label, see "Defining the Object Type Label" on page 46. Tip text: You can display information about each object, such as each site or transmitter, in the form of tip text that is only visible when you move the pointer over the object. You can choose to display more information than in the label, because the information is only displayed when you move the pointer over the object. You can display information from any field in that object type’s data table, including from fields that you add. For information on defining the tip text, see "Defining the Object Type Tip Text" on page 46. Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example, you can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active transmitters. You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns a colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding it. For information on defining the transmitter colour, see "Defining the Display Type" on page 44. Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can select a symbol that graphically represents the antenna half-power beamwidth (
). If you have two transmitters on the
same site with the same azimuth, you can differentiate them by selecting different symbols for each ( For information on defining the transmitter symbol, see "Defining the Display Type" on page 44.
and
).
14.2.5 Creating a Multi-band LTE Network In Atoll, you can model a multi-band LTE network, for example, a network consisting of 900 MHz and 2.1 GHz, in one document. Creating a multi-band LTE network consists of the following steps: 1. Defining the frequency bands in the document (see "Defining Frequency Bands" on page 1587). 2. Selecting and calibrating a propagation model for each frequency band (see Chapter 5: Working with Calculations in Atoll). 3. Assigning a frequency band to each cell and a relevant propagation model to each transmitter (see "Creating or Modifying a Cell" on page 1446 and "Creating or Modifying a Transmitter" on page 1445).
14.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 value and the noise rise generated at the donor transmitter by the repeater. In calculations, repeaters are transparent to the donor transmitters and the served users. For example, beamforming smart antennas at donor transmitters create beams directly towards the served users, and not towards the repeater that covers the users. This results in a combined signal level received from the transmitter using the smart antenna and from the repeater. If this approach does not match how your equipment works, you must not assign smart antennas to transmitters with repeaters and vice versa. This is also true for MIMO.
In this section, the following are explained: • • • • • •
"Opening the Repeaters Table" on page 1455 "Creating and Modifying Repeater Equipment" on page 1455 "Placing a Repeater on the Map Using the Mouse" on page 1455 "Creating Several Repeaters" on page 1456 "Defining the Properties of a Repeater" on page 1456 "Tips for Updating Repeater Parameters" on page 1458. Atoll assumes that all carriers from the LTE donor transmitter are amplified.
1454
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
14.2.6.1 Opening the Repeaters Table Repeaters and their defining parameters are stored in the Repeaters table. To open the Repeaters table: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Repeaters > Open Table from the context menu. The Repeaters table appears.
14.2.6.2 Creating and Modifying Repeater Equipment You can define repeater equipment to be assigned to each repeater in the network. To create or modify repeater equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Repeater Equipment. The context menu appears. 4. Select Open Table from the context menu. The Repeater Equipment table appears. 5. Define the following in an existing record or in the row marked with the New row icon (
):
a. Enter a Name and Manufacturer for the new equipment. b. Enter a Noise figure (dB). The repeater causes a rise in noise at the donor transmitter, so the noise figure is used to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive value. c. Enter minimum and maximum repeater amplification gains in the Min. gain and Max gain columns. These parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equipment if there are any. d. Enter a Gain increment. Atoll uses the increment value when you increase or decrease the repeater amplifier gain using the buttons to the right of the Amplifier gain box ( logue.
) on the General tab of the repeater Properties dia-
e. Enter the maximum power that the equipment can transmit on the downlink in the Max downlink power column. This parameter enables Atoll to ensure that the downlink power after amplification does not exceed the limit of the equipment. f.
If desired, enter a Max uplink power, an Internal delay and Comments. These fields are for information only and are not used in calculations.
14.2.6.3 Placing a Repeater on the Map Using the Mouse In Atoll, you can create a repeater and place it using the mouse. When you create a repeater, you can add it to an existing site, or have Atoll automatically create a new site. Atoll supports cascading repeaters, in other words, repeaters that extend the coverage of another repeater or of a remote antenna. To create a repeater and place it using the mouse: 1. Select the donor transmitter, repeater, or remote antenna. You can select it from the LTE Transmitters folder in the Network explorer, or directly on the map. 2. Click the arrow next to New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
3. Select Repeater from the menu. 4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the same colour as the donor transmitter, repeater, or remote antenna. If the repeater is inactive, it is displayed by an empty icon. By default, the repeater has the same azimuth as the donor. Its tip text and label display the same information as displayed for the donor. As well, its tip text identifies the repeater and the donor. In the explorer window, the repeater is found in the LTE Transmitters folder of the Network explorer under its donor transmitter, repeater, or remote antenna. For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on page 1456. You can see to which base station the repeater is connected by clicking it; Atoll displays a link to the donor transmitter, repeater, or remote antenna.
1455
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
14.2.6.4 Creating Several Repeaters In Atoll, the characteristics of each repeater are stored in the Repeaters table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Repeaters table in your current Atoll document. To paste the information into the Repeaters table: 1. Open the Repeaters table as explained in "Opening the Repeaters Table" on page 1455. 2. Copy the data from the source document and paste it into the Repeaters table. 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 77.
14.2.6.5 Defining the Properties of a Repeater To define the properties of a repeater: 1. Right-click the repeater either directly on the map, or in the Repeaters table (for information on opening the Repeaters table, see "Opening the Repeaters Table" on page 1455). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
Name: You can change the Name of the repeater. By default, repeaters are named "SiteX_Y_RepZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the repeater when it was created. •
•
•
If the donor is a remote antenna or another repeater, then "RepZ" is preceded by "RemA_" or "RepB_" where "A" and "B" identify the donor remote antenna and the donor repeater. In Multi-RAT documents, a repeater’s name is "SiteX_T_Y_RepZ" where "T" stands for the technology (either GSM, UMTS, or LTE)..
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, a remote antenna, or another repeater. Clicking the Browse button (
• •
•
You can change the Site on which the repeater is located. Clicking the Browse button ( ) opens the Properties dialogue of the selected site. You can enter a value in the Shared antenna (coverage side) field for the repeater. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna position, you can define the position of the repeater, if it is not located on the site itself: • •
• •
) opens the Properties dialogue of the selected donor.
Relative to site: Select Relative to site, if you want to define the position of the repeater relative to the site itself and then enter the XY offsets. Coordinates: Select Coordinates, if you want to define the position of the repeater by its XY coordinates.
You can select equipment from the Equipment list. Clicking the Browse button ( ) opens the Properties dialogue of the equipment. You can change the Amplifier Gain. The amplifier gain is used in the link budget to evaluate the repeater total gain.
4. Click the Donor Side tab. You can modify the following parameters: •
Under Donor-repeater link, select a Link type. • •
If you select Microwave link, enter the Link losses and proceed to step 5. If you select Air, select a Propagation model and enter the Propagation losses or click Calculate to determine the actual propagation losses between the donor and the repeater. If you do not select a propagation model, the propagation losses between the donor transmitter and the repeater are calculated using the ITU 526-5 propagation model. When you create an off-air repeater, it is assumed that the link between the donor transmitter and the repeater has the same frequency as the network.
1456
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
If you want to create a remote antenna, you must select Optical Fibre Link.
•
If you selected Air under Donor-repeater link, enter the following information under Antenna: •
Model: The type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the repeater. Based on the selected physical antenna and on the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the repeater.
•
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of the building. Mechanical Azimuth and Mechanical Downtilt display additional antenna parameters. You can click the Calculate button to update the mechanical azimuth and mechanical downtilt values after changing the repeater donor side antenna height or the repeater location. If you choose another site or change site coordinates in the General tab, click Apply before clicking the Calculate button.
•
If you selected Air under Donor-repeater link, enter the following information under Feeders: • •
Type: The type of feeder is visible in the Type list. You can click the Browse button ( erties of the feeder. Length: Enter the Length of the feeder cable at Transmission and at Reception.
) to access the prop-
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 LTE Transmitters folder in the Network explorer) 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 total gain values to calculate the signal level received from and at the repeater. The DL total gain is applied to RS, SS, PBCH, PDCCH, and PDSCH powers and EPREs. The UL total gain is applied to the PUCCH and PUSCH powers. The total gains take into account losses between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses), amplifier gain, and coverage characteristics (coverage antenna gain and transmission feeder losses).
•
Under Antennas, you can modify the following parameters: •
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the repeater is situated on a building, the height entered must include the height of building. Main antenna: Under Main antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna. To find a suitable antenna, select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the repeater. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. Select the antenna model to use from the Available Antennas and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the repeater. The remaining fields, Mechanical 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.
1457
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• • •
•
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. •
Under Losses, Atoll displays the Loss related to repeater noise rise.
6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propagation parameters. On the Propagation tab, you can modify the following: the Propagation model, Radius, and Resolution for both the Main matrix and the Extended matrix. By default, the propagation characteristics of the repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
14.2.6.6 Tips for Updating Repeater Parameters Atoll provides you with a few shortcuts that you can use to change certain repeater parameters: • •
You can update the calculated azimuth and downtilt of the donor-side antennas of all repeaters by selecting Repeaters > Calculate Donor Side Azimuths and Tilts from the Transmitters context menu. You can update the UL and DL total gains of all repeaters by selecting Repeaters > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected repeaters by creating a custom Boolean field named "FreezeTotalGain" in the Repeaters table and setting the value of the field to "True." Afterwards, when you select Repeaters > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for repeaters with the custom field "FreezeTotalGain" set to "False."
• •
You can update the propagation losses of all off-air repeaters by selecting Repeaters > Calculate Donor Side Propagation Losses from the Transmitters context menu. You can select a repeater on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
14.2.7 Creating a Remote Antenna Atoll allows you to create remote antennas to position antennas at locations that would normally require long runs of feeder cable. A remote antenna is connected to the base station with an optical fibre. Remote antennas allow you to ensure radio coverage in an area without a new base station. In Atoll, the remote antenna should be connected to a base station that does not have any antennas. It is assumed that a remote antenna, as opposed to a repeater, does not have any equipment and generates no amplification gain nor noise. In certain cases, you may want to model a remote antenna with equipment or a remote antenna connected to a base station that has antennas. This can be done by modelling a repeater. For information on creating a repeater, see "Creating a Repeater" on page 1454. In calculations, remote antennas are transparent to the donor transmitters and the served users. For example, beamforming smart antennas at donor transmitters create beams directly towards the served users, and not towards the remote antenna that covers the users. This results in a combined signal level received from the transmitter using the smart antenna and from the remote antenna. If this approach does not match how your equipment works, you must not assign smart antennas to transmitters with remote antennas and vice versa. This is also true for MIMO. In this section, the following are explained: •
1458
"Opening the Remote Antennas Table" on page 1459
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• • • •
"Placing a Remote Antenna on the Map Using the Mouse" on page 1459 "Creating Several Remote Antennas" on page 1459 "Defining the Properties of a Remote Antenna" on page 1460 "Tips for Updating Remote Antenna Parameters" on page 1461.
14.2.7.1 Opening the Remote Antennas Table The remote antennas and their defining parameters are stored in the Remote Antennas table. To open the Remote Antennas table: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Remote Antennas > Open Table from the context menu. The Remote Antennas table appears.
14.2.7.2 Placing a Remote Antenna on the Map Using the Mouse In Atoll, you can create a remote antenna and place it using the mouse. When you create a remote antenna, you can add it to an existing base station without antennas, or have Atoll automatically create a new site. To create a remote antenna and place it using the mouse: 1. Select the donor transmitter. You can select it from the LTE Transmitters folder in the Network explorer, or directly on the map. Ensure that the remote antenna’s donor transmitter does not have any antennas.
2. Click the arrow next to New Repeater or Remote Antenna button (
) on the Radio Planning toolbar.
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 the same symbol and colour as the donor transmitter. If the remote antenna is inactive, it is displayed by an empty icon. By default, the remote antenna has the same azimuth as the donor transmitter. Its tip text and label display the same information as displayed for the donor transmitter. As well, its tip text identifies the remote antenna and the donor transmitter. For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote Antenna" on page 1460. You can see to which base station the remote antenna is connected by clicking it; Atoll displays a link to the donor transmitter.
14.2.7.3 Creating Several Remote Antennas In Atoll, the characteristics of each remote antenna are stored in the Remote Antennas table. If you have data in table form, either in another Atoll document or in a spreadsheet, you can copy this data and paste it into the Remote Antennas table in your current Atoll document. To paste the information into the Remote Antennas table: 1. Open the Remote Antennas table as explained in "Opening the Remote Antennas Table" on page 1459. 2. Copy the data from the source document and paste it into the Remote Antennas table. The table you copy data from must have the same column layout as the table you are pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 77.
1459
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
14.2.7.4 Defining the Properties of a Remote Antenna To define the properties of a remote antenna: 1. Right-click the remote antenna either directly on the map, or in the Remote Antennas table (for information on opening the Remote Antennas table, see "Opening the Remote Antennas Table" on page 1459). The context menu appears. 2. Select Properties from the context menu. The Properties dialogue appears. 3. Click the General tab. You can modify the following parameters: •
Name: You can change the Name of the remote antenna. By default, remote antennas are named "SiteX_Y_RemZ" where "X" is the donor site number, "Y" the donor transmitter number, and "Z" a number assigned to the remote antenna when it was created. •
•
•
If the donor is a repeater or another remote antenna, then "RemZ" is preceded by "RepA_" or "RemB_" where "A" and "B" identify the donor repeater and the donor remote antenna. In Multi-RAT documents, a remote antenna’s name is "SiteX_T_Y_RemZ" where "T" stands for the technology (either GSM, UMTS, or LTE).
You can change the Donor by selecting it from the Donor list. The Donor can be a transmitter, another remote antenna or a repeater. Clicking the Browse button (
• •
•
) opens the Properties dialogue of the selected donor.
You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens the Properties dialogue of the selected site. You can enter a value in the Shared antenna (coverage side) field for the remote antenna. This field is used to identify the transmitters, repeaters, and remote antennas that are located at the same site or on sites with the same position and that share an antenna. The entry in the field must be the same for all such transmitters, repeaters, and remote antennas. When changes are made to the position offset (Dx, Dy), azimuth, antenna height, or mechanical tilt of one antenna, Atoll automatically synchronises the same changes to all other transmitters, repeaters, and remote antennas defined as having a shared antenna. Under Antenna position, you can define the position of the remote antenna, if it is not located on the site itself: • •
Relative to site: Select Relative to site, if you want to define the position of the remote antenna relative to the site itself and then enter the XY offsets. Coordinates: Select Coordinates, if you want to define the position of the remote antenna by its XY coordinates. A remote antenna does not have equipment.
4. Click the Donor Side tab. You can modify the following parameters: •
Under Donor-repeater link, select Optical fibre link and enter the Fibre losses.
5. Click the Coverage Side tab. You can modify the following parameters: • •
Select the Active check box. Only active remote antennas (displayed in red in the LTE Transmitters folder in the Network explorer) 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 total gain values to calculate the signal level received from and at the remote antenna. The DL total gain is applied to RS, SS, PBCH, PDCCH, and PDSCH powers and EPREs. The UL total gain is applied to the PUCCH and PUSCH powers. The total gains take into account losses between the donor transmitter and the remote antenna.
•
Under Antennas, you can modify the following parameters: •
•
Height/ground: The Height/ground box gives the height of the antenna above the ground. This is added to the altitude of the site as given by the DTM. If the remote antenna is situated on a building, the height entered must include the height of the building. Main antenna: Under Main antenna, the type of antenna is visible in the Model list. You can click the Browse button ( ) to access the properties of the antenna. Clicking the Select button opens the Antenna Selection Assistant dialogue with a list of available antennas based on the currently selected physical antenna.
1460
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
To find a suitable antenna, you select a Physical Antenna (which can have one or more possible antenna patterns, corresponding to different electrical downtilts), the Beamwidth (3dB aperture), and the Electrical tilt of the antenna model to be used at the remote antenna. Based on the selected physical antenna and the electrical downtilt, suitable antenna models are listed. You select the antenna model to use from the Available Antennas. and click OK. The Antenna Selection Assistant closes and the selected antenna model is assigned to the remote antenna. • •
Mechanical 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. • • •
•
The Additional electrical downtilt can be made accessible through an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on the effect of additional electrical downtilt on antenna patterns, see the Technical Reference Guide. For information on working with data tables, see "Working with Data Tables" on page 69.
Under Feeders, you can modify the following information: i.
Select a Type of feeder from the list. You can click the Browse button ( feeder.
) to access the properties of the
ii. Enter the Length of the feeder cable at Transmission and at Reception. 6. Click the Propagation tab. Since remote antennas are taken into account during calculations, you must set propagation parameters, as with transmitters. On the Propagation tab, you can modify the following: the Propagation model, Radius, and Resolution for both the Main matrix and the Extended matrix. By default, the propagation characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propagation models, see Chapter 5: Working with Calculations in Atoll.
14.2.7.5 Tips for Updating Remote Antenna Parameters Atoll provides you with a few shortcuts that you can use to change certain remote antenna parameters: •
You can update the UL and DL total gains of all remote antennas by selecting Remote Antennas > Calculate Gains from the Transmitters context menu. You can prevent Atoll from updating the UL and DL total gains of selected remote antennas by creating a custom Boolean field named "FreezeTotalGain" in the Remote Antennas table and setting the value of the field to "True." Afterwards, when you select Remote Antennas > Calculate Gains from the Transmitters context menu, Atoll will only update the UL and DL total gains for remote antennas with the custom field "FreezeTotalGain" set to "False."
•
You can select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using the Mouse" on page 42) or its position relative to the site (see "Changing the Antenna Position Relative to the Site Using the Mouse" on page 42).
14.2.8 Setting the Working Area of an Atoll Document When you load project data from a database, you will probably only modify the data in the region for which you are responsible. For example, a complex radio-planning project might cover an entire region or even an entire country. You, however, might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction to the base stations that you are interested in and generate only the results you need. In Atoll, there are two ways of restricting the number of base stations covered by a coverage prediction, each with its own advantages: •
Filtering the desired base stations You can simplify the selection of base stations to be studied by using a filter. You can filter base stations according to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information on graphic filters, see "Filtering Data Using a Filtering Zone" on page 107. This enables you to keep only the base stations with the characteristics you want for your calculations. The filtering zone is taken into account whether or not it is visible.
1461
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
For information on filtering, see "Filtering Data" on page 95. •
Setting a computation zone Drawing a computation zone to encompass the sites to be studied limits the number of sites to be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may not be significant. In a larger project, especially when you are making repeated predictions in order to see the effects of small changes in site configuration, the savings in time is considerable. Limiting the number of sites by drawing a computation zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is visible. It is important not to confuse the computation zone and the focus zone or hot spot. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus zone or hot spot is the area taken into consideration when generating reports and results. For information on the computation zone, see "Creating a Computation Zone" on page 1470.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be studied.
14.2.9 Studying a Single Base Station As you create a base station, you can study it to test the effectiveness of the set parameters. Coverage predictions on groups of base stations can take a large amount of time and consume a lot of computer resources. Restricting your coverage prediction to the base station you are currently working on allows you get the results quickly. You can expand your coverage prediction to a number of base stations once you have optimised the settings for each individual base station. Before studying a base station, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates propagation losses along the transmitter-receiver path. This allows you to predict the received signal level at any given point. Any coverage prediction you make on a base station uses the propagation model to calculate its results. In this section, the following are explained: • •
"Making a Point Analysis to Study the Profile" on page 1462. "Studying Signal Level Coverage" on page 1463.
14.2.9.1 Making a Point Analysis to Study the Profile In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a user. Before studying a base station, you must assign a propagation model. The propagation model takes the radio and geographic data into account and calculates losses along the transmitter-receiver path. The profile is calculated in real time, using the propagation model, allowing you to study the profile and get a prediction on the selected point. For information on assigning a propagation model, see "Assigning a Propagation Model" on page 1468. You can make a point analysis to: • • •
study the reception in real time along a profile between a reference transmitter and an LTE user, study the interference along a profile between a reference transmitter and a user, and evaluate the signal levels from the surrounding transmitters at a given point (using existing path loss matrices).
To make a point analysis: 1. In the map window, select the transmitter from which you want to make a point analysis. 2. Click the Point Analysis button ( pointer changes (
) in the Radio Planning toolbar. The Point Analysis window appears and the
) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the following: • • •
Move the receiver to change the current position. Click to place the receiver at the current position. You can move the receiver again by clicking it a second time. Right-click the receiver to choose one of the following commands from the context menu: • Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates. • Target Site: Select a site from the list to place the receiver directly on a site.
4. Select the Profile view. The profile analysis appears in the Profile view of the Point Analysis 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, the obstacle 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 attenuation peaks. The total attenuation is displayed above the main peak.
1462
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
The results of the analysis are displayed at the top of the Profile view: • • • •
The received signal strength from the selected transmitter for the cell with the highest reference signal power The propagation model used The shadowing margin and the indoor loss (if selected) The distance between the transmitter and the receiver.
You can change the following options from the Profile view toolbar: •
Transmitter: Select the transmitter from the list. You can click the Properties button ( properties dialogue.
•
Options: Click the Options button ( • • • •
) to open the transmitter
) to display the Calculation Options dialogue. In this dialogue, you can:
Change the X and Y coordinates to change the current position of the receiver. Select the Shadowing taken into account check box and enter a Cell edge coverage probability. Select Signal level, Path loss, or Total losses from the Result type list. You can select the Indoor coverage check box to add indoor losses.
•
Geographic Profile: Click the Geographic Profile button ( ) if you want to view the geographic profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate or display signal levels and losses.
•
Link Budget: Click the Link Budget button (
•
Detailed Report: Click the Detailed Report button ( ) to display a text document with details on the displayed profile analysis. The detailed report is only available for the Standard Propagation Model.
) to display a dialogue with the link budget.
You can select a different transmitter.
Displays data, including received signal, shadowing margin, cell edge coverage probability, propagation model used, and transmitter-receiver distance.
Fresnel ellipsoid
Line of sight
Attenuation with diffraction
Figure 14.12: Point Analysis - Profile view 5. To end the point analysis, click the Point Analysis button (
) in the Radio Planning toolbar again.
14.2.9.2 Studying Signal Level Coverage While you are building your radio-planning project, you might want to check the coverage of a new base station without having to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage prediction. This section explains how to calculate the signal level coverage of a single base station. A signal level coverage prediction displays the signal of the best server for each pixel of the area studied. For a transmitter with more than one cell, the signal level is calculated for the cell with the highest reference signal power. You can use the same procedure to study the signal level coverage of several base stations by grouping the transmitters. For information on grouping transmitters, see "Grouping Data Objects by a Selected Property" on page 89. To study the signal level coverage of a single base station: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder and select Group By > Sites from the context menu. The transmitters are now displayed in the LTE Transmitters folder by the site on which they are situated.
1463
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 LTE 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: • •
Select a Propagation model. Enter a Radius and Resolution.
f. If desired, in the Extended matrix column: • •
Select a Propagation model. Enter a Radius and Resolution.
g. Close the table. 4. In the LTE Transmitters folder, right-click the group of transmitters you want to study and select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. The Prediction Types dialogue lists the coverage prediction types available. They are divided into Standard Predictions, supplied with Atoll, and Customised Prediction. Unless you have already created some customised predictions, the Customised Prediction list will be empty. 5. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 6. You can configure the following parameters in the Properties dialogue: •
General tab: You can change the assigned Name of the coverage prediction, the Resolution, and the storage Folder for the coverage prediction, and add some Comments. The resolution you set is the display resolution, not the calculation resolution. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient:
•
Size of the Coverage Prediction
Display Resolution
City Centre
5m
City
20 m
County
50 m
State
100 m
Country
According to the size of the country
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 14.13). • •
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.
• •
1464
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.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.13: Condition settings for a coverage prediction by signal level •
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." You can change the value intervals and their displayed colour. For information on changing display properties, see "Display Properties of Objects" on page 43.
•
You can create tip text with information about the coverage prediction by clicking the Browse button ( next to the Tip text box and selecting the fields you want to display in the tip text. You can select the Add to legend check box to add the displayed value intervals to the legend.
•
)
If you change the display properties of a coverage prediction after you have calculated it, you may make the coverage prediction invalid. You will then have to recalculate the coverage prediction to obtain valid results. 7. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the 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 in the Network explorer. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( folder. When you click the Calculate button (
) beside the coverage prediction in the Predictions
), Atoll only calculates unlocked coverage predictions (
).
14.2.10 Studying Base Stations When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects the rectangle containing the computation zone. Figure 14.14 gives an example of a computation zone. In Figure 14.14, the computation zone is displayed in red, as it is in the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consideration when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone. However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not intersect the green rectangle. Therefore, they will not be taken into account in the coverage prediction. Site 130 is within the coverage zone but has no active transmitters. Therefore, it will not be taken into consideration either.
1465
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.14: 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 14.14) 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 1466. "Assigning a Propagation Model" on page 1468. "The Calculation Process" on page 1470. "Creating a Computation Zone" on page 1470. "Setting Transmitters or Cells as Active" on page 1471. "Signal Level Coverage Predictions" on page 1472. "Analysing a Coverage Prediction" on page 1477. "LTE Coverage Predictions" on page 1486. "Printing and Exporting Coverage Prediction Results" on page 1504.
14.2.10.1 Path Loss Matrices In addition to the distance between the transmitter and the receiver, path loss is caused by objects in the transmitter-receiver path. In Atoll, the path loss matrices must be calculated before predictions and simulations can be made. Storing Path Loss Matrices Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matrices in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case of large radioplanning projects, saving your path loss matrices externally will help reduce the size of the file and the use of computer resources. The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same radio-planning project. In this case, the radio data is stored in a database and the path loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual. When you save the path loss matrices to an external directory, Atoll creates: • • •
1466
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.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
To set the storage location of the path loss matrices: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Properties from the context menu. The Predictions 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 Private directory ( ) and select Embedded to save the path loss matrices in the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally. Path loss matrices you calculate locally are not stored in the same directory as shared path loss matrices. Shared path loss matrices are stored in a read-only directory. In other words, you can read the information from the shared path loss matrices but any changes you make will be stored locally, either embedded in the ATL file or in a private external folder, depending on what you have selected in Private directory.
When you save the path loss files externally, the external files are updated as soon as calculations are performed. In order to keep consistency between the Atoll document and the stored calculations, you should save the Atoll document before closing it if you have updated the path loss matrices. •
Shared directory: When you are working in a multi-user Atoll environment, the project data is stored in a database and the path loss matrices are stored in a directory that is accessible to all users. Any changes you make will not be saved to this directory; they will be saved in the location indicated in Private directory. The path loss matrices in the shared directory are updated by a user with administrator rights based on the updated information in the database. For more information on shared directories, see the Administrator Manual.
5. Click OK. Checking the Validity of Path Loss Matrices Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want, you can check whether the path loss matrices are valid without creating a coverage prediction. To check whether the path loss matrices are valid: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Propagation tab. The path loss matrix information is listed in the Available results table. You have the following display options: • •
Display all matrices: All path loss matrices are displayed. Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available results table lists the following information for each displayed path loss matrix: • • • • • •
Transmitter: The name of the transmitter. Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices are recalculated. Valid: This is a Boolean field indicating whether or not the path loss matrix is valid. 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.
5. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue appears (see Figure 14.15) with the total number of invalid path loss matrices and the reasons for invalidity, as well as a summary of the reasons for invalidity.
1467
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.15: Path loss matrices statistics
14.2.10.2 Assigning a Propagation Model In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used for all transmitters where the main propagation model selected is "(Default model)." Because you can assign a propagation model in several different ways, it is important to understand which propagation model Atoll will use: 1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model to One Transmitter" on page 1469, or to a group of transmitters, as explained in "Assigning a Propagation Model to a Group of Transmitters" on page 1469, this is the propagation model that will be used. The propagation model assigned to an individual transmitter or to a group of transmitters will always have precedence over any other assigned propagation model. 2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation Model to All Transmitters" on page 1468, this is the propagation model that will be used for all transmitters, except for those to which you will later assign a propagation model either individually or as part of a group. When you assign a propagation model globally, you override any selection you might have made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default Propagation Model" on page 201, this is the propagation model that will be used for all transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main propagation model, that is the propagation model that will be used. In this section, the following are explained: • • •
"Assigning a Propagation Model to All Transmitters" on page 1468. "Assigning a Propagation Model to a Group of Transmitters" on page 1469. "Assigning a Propagation Model to One Transmitter" on page 1469.
For more information about the available propagation models, see Chapter 5: Working with Calculations in Atoll. Assigning a Propagation Model to All Transmitters In Atoll, you can assign a propagation model per transmitter or globally. To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Right-click the LTE 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: • •
1468
Select a Propagation model Enter a Radius and Resolution.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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. Setting a different main or extended matrix on an individual transmitter as explained in "Assigning a Propagation Model to One Transmitter" on page 1469 will override this entry.
Assigning a Propagation Model to a Group of Transmitters Transmitters that share the same parameters and environment will usually use the same propagation model and settings. In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common parameters and then assigning the propagation model. To define a main and extended propagation model for a defined group of transmitters: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. From the Group By submenu of the context menu, select the property by which you want to group the transmitters. The objects in the folder are grouped by that property. You can group transmitters by several properties by using the Group By button on the Properties dialogue. For more information, see "Advanced Grouping" on page 90.
4. Click the Expand button ( ) to expand the LTE 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 Main resolution Extended propagation model Extended calculation radius Extended resolution
To enter the same values in one column for all transmitters in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69. Assigning a Propagation Model to One Transmitter If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmitters. When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previously made globally.
1469
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
To define a main and extended propagation model for all transmitters: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the LTE Transmitters folder. 3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu appears. 4. Select Properties from the context menu. The Properties dialogue appears. 5. Click the Propagation tab. 6. Under Main matrix: • •
Select a Propagation model. Enter a Radius and Resolution.
7. If desired, under Extended matrix: • •
Select a Propagation model. Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter. 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.
14.2.10.3 The Calculation Process When you create a coverage prediction and click the Calculate button (
), Atoll follows the following process:
1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle containing the computation zone. 2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click the Calculate button (
).
3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results of a coverage prediction as soon as it is calculated, as indicated by the icon ( Predictions folder.
) beside the coverage prediction in the
•
You can stop any calculations in progress by clicking the Stop Calculations button
•
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll calculates all path loss matrices, unlocked coverages, and pending simulations.
(
) in the toolbar.
14.2.10.4 Creating a Computation Zone To create a computation zone: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Computation Zone. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the zone.
ii. Click once on the map to define each point on the map where the border of the zone changes direction. iii. Click twice to finish drawing and close the zone. •
Draw Rectangle i.
1470
Click the point on the map that will be one corner of the rectangle that will define the zone.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
ii. Drag to the opposite corner of the rectangle that will define the zone. When you release the mouse, the zone will be created from the rectangle defined by the two corners. The computation zone is delimited by a red line. If you clear the computation zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a computation zone with one of the following methods: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor 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. You can also combine an existing computation zone with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Computation Zone from the context menu. 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 in the Geo explorer and selecting Import from the context menu. Fit Zone to Map Window: You can create a computation zone the size of the map window by right-clicking the Computation Zone in the Geo explorer and selecting Fit Zone to Map Window from the context menu. You can save the computation zone, so that you can use it in a different Atoll document, in the following ways: •
•
Saving the computation zone in the user configuration: For information on saving the computation zone in the user configuration, see "Saving a User Configuration" on page 101. Exporting the computation zone: You can export the computation zone by rightclicking the Computation Zone folder in the Geo explorer and selecting Export from the context menu.
14.2.10.5 Setting Transmitters or Cells as Active When you make a coverage prediction, Atoll considers all base stations that are active, filtered (i.e., that are selected by the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. Therefore, before you define a coverage prediction, you must ensure that all the transmitters on the base stations you wish to study have been activated. In the explorer window, active transmitters are indicated with an on icon (
) in the LTE Transmitters folder
and with the defined colour on the map and inactive transmitters are indicated with an off icon ( folder and empty symbol on the map.
) in the LTE Transmitters
In Atoll, you can also set the cell on a transmitter as active or inactive. You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active by activating them from the Transmitters context menu, by activating the transmitters’ cells from the Cells table, or by selecting the transmitters with a zone and activating them from the zone’s context menu. To set an individual transmitter as active: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the LTE 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. Select the Network explorer. 2. Select the transmitters you want to set as active: • •
To set all transmitters as active, right-click the LTE Transmitters folder. The context menu appears. To set a group of transmitters as active, click the Expand button ( ) to expand the LTE 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. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Open Table. The Transmitters table appears with each transmitter’s parameters in a row. 4. For each transmitter that you want to set as active, select the check box in the Active column.
1471
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
To set more than one cell as active using the Cells table: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Cells > Open Table. The Cells table appears with each cell’s 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. Select the Geo explorer. 2. Click the Expand button ( ) to the left of Zones folder to expand the folder. 3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears. If you do not yet have a zone containing the transmitters you want to set as active, you can draw a zone as explained in "Using Zones in the Map Window" on page 54.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active. Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on choosing and configuring a propagation model, see Chapter 5: Working with Calculations in Atoll. Calculating path loss matrices can be 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.
14.2.10.6 Signal Level Coverage Predictions Atoll offers a series of standard coverage predictions based on the measured signal level at each pixel; other factors, such as interference, are not taken into consideration. Coverage predictions specific to LTE are covered in "LTE Coverage Predictions" on page 1486. Once you have created and calculated a coverage prediction, you can use the coverage prediction’s context menu to make the coverage prediction into a customised prediction which will appear in the Prediction Types dialogue. You can also select Duplicate from the coverage prediction’s context menu to create a copy. By duplicating an existing prediction that has the parameters you want to study, you can create a new coverage prediction more quickly than by creating a new coverage prediction. If you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the coverage prediction with the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the calculated coverage prediction. You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to load it into a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predictions are saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations, see "Saving a User Configuration" on page 101. The following standard coverage predictions are explained in this section: • • •
14.2.10.6.1
"Making a Coverage Prediction by Signal Level" on page 1472 "Making a Coverage Prediction by Transmitter" on page 1474 "Making a Coverage Prediction on Overlapping Zones" on page 1476.
Making a Coverage Prediction by Signal Level A coverage prediction by signal level allows you to predict coverage zones by the transmitter signal strength at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest reference signal power. To make a coverage prediction by signal level: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Signal Level and click OK. The Coverage by Signal Level Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage
1472
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 14.16). On the Condition tab, you can define the signals that will be considered for each pixel. • •
At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, a longer time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration.
• •
If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 14.16: 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 43. 8. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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 14.17).
1473
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.17: Coverage prediction by signal level
14.2.10.6.2
Making a Coverage Prediction by Transmitter A coverage prediction by transmitter allows the user to predict coverage zones by transmitter at each pixel. You can base the coverage on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest reference signal power. To make a coverage prediction by transmitter: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Transmitter and click OK. The Coverage by Transmitter Properties dialogue appears. 5. Click the General tab. On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining the Storage Location of Coverage Prediction Results" on page 216. Under Display configuration, you can create a Filter to select which sites to display in the results. You can also display the results grouped in the Network explorer by one or more characteristics by clicking the Group by button, or you can display the results sorted by clicking the Sort button. For information on filtering, see "Filtering Data" on page 95; for information on grouping, see "Advanced Grouping" on page 90; for information on sorting, see "Advanced Sorting" on page 94. 6. Click the Condition tab (see Figure 14.18). On the Condition tab, you can define the signals that will be considered for each pixel. • •
At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration.
• •
1474
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.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.18: 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 43. When creating a coverage prediction by discrete values, you can not export the values per pixel.
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.19).
Figure 14.19: Coverage prediction by transmitter
1475
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
14.2.10.6.3
© Forsk 2012
Making a Coverage Prediction on Overlapping Zones Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmitters. You can base a coverage prediction on overlapping zones on the signal level, path loss, or total losses within a defined range. For a transmitter with more than one cell, the coverage is calculated for the cell with the highest reference signal power. To make a coverage prediction on overlapping zones: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 14.20). On the Condition tab, you can define the signals that will be considered for each pixel. • •
At the top of the Condition tab, you can set the range of signal level to be considered. Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level" necessitates, however, the longest time for calculation. When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll will take into consideration.
• •
If you select the Shadowing taken into account check box, you can change the Cell edge coverage probability. You can select the Indoor coverage check box to add indoor losses.
Figure 14.20: 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 43. 8. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: •
1476
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
•
OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.21).
Figure 14.21: Coverage prediction on overlapping zones
14.2.10.7 Analysing a Coverage Prediction Once you have completed a prediction, you can analyse the results with the tools that Atoll provides. The results are displayed graphically in the map window according to the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 1463). If several coverage predictions are visible on the map, it can be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following tools are explained: • • • • • • •
14.2.10.7.1
"Displaying the Legend Window" on page 1477. "Displaying Coverage Prediction Results Using the Tip Text" on page 1477. "Using the Point Analysis Reception View" on page 1478. "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1479. "Displaying a Coverage Prediction Report" on page 1480. "Viewing Coverage Prediction Statistics" on page 1482. "Comparing Coverage Predictions: Examples" on page 1483.
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by selecting the Add to legend check box on the Display tab. To display the Legend window: •
14.2.10.7.2
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction identified by the name of the coverage prediction.
Displaying Coverage Prediction Results Using the Tip Text You can get information by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 1463). To get coverage prediction results in the form of tip text: •
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined in the Display tab of the coverage prediction properties (see Figure 14.22).
1477
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.22: Displaying coverage prediction results using tip text
14.2.10.7.3
Using the Point Analysis Reception View Once you have calculated the coverage prediction, you can use the Point Analysis tool. The Reception view gives you information on the reference signal, SS, PBCH, PDSCH, PDCCH, and PUSCH and PUCCH signal levels, C/(I+N), bearers, and throughputs, etc., for any point on the map. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility, and a service. The analysis is based on: •
• • •
The reference signal levels, used to determine the best server for the pixel. The best serving transmitter is determined according to the received reference signal level from the cell with the highest reference signal power. If more than one cell covers the pixel, the one with the highest layer is selected as the serving (reference) cell. The reference signal C/N or C/(I+N), used to determine whether SU-MIMO or transmit or receive diversity is used in case of AMS, and whether MU-MIMO can be used in uplink or not. The PDSCH signal levels, downlink traffic loads, ICIC ratios, angular distributions of interference, and AAS usage, for determining the PDSCH C/(I+N), bearer, and throughputs. The PUSCH & PUCCH signal levels and uplink noise rise for determining the PUSCH & PUCCH C/(I+N), bearer, and throughputs.
The downlink and uplink load conditions can be taken from the Cells table or from Monte Carlo simulations. You can make a reception analysis to verify a coverage prediction. If you do, 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 (
) on the Radio Planning toolbar. The Point Analysis window appears (see
Figure 14.23) and the pointer changes (
) to represent the receiver.
2. Select the Reception view. 3. At the top of the Reception view, select "Cells table" from Load. 4. Select the signal to be displayed from the Display list. 5. 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. Click the Options button ( • • •
) in the Reception view toolbar. The Calculation Options dialogue appears.
Edit the X and Y coordinates to change the current position of the receiver. Select the Shadowing taken into account check box and enter a Cell edge coverage probability. Select the Indoor coverage check box to add indoor losses. Indoor losses are defined per clutter class.
c. Click OK to close the Calculation Options dialogue. 6. Move the pointer over the map to display 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. The line from the pointer to its best server is slightly thicker than the other lines. The best server of the pointer is the transmitter from which the pointer receives the highest 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.
1478
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Select the load conditions to use in this analysis from simulations or from the Cells table.
The RSRP from the best server (top-most bar) and all interfering cells. Solid bars indicate RSRP above the minimum RSRP.
The connection status for the current point. : Successful : Failed
Select the parameters of the probe user to be studied. Figure 14.23: Point analysis tool: Reception view 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 empty portion of the bar indicates signal levels below the minimum RSRP. The availability of reference signal coverage, and service in downlink and uplink.
If there is at least one successful connection (for reference signals, downlink, or uplink), double-clicking the icons in the right-hand frame opens a 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, received powers of the downlink channels, received total noise on the downlink channels, C/(I+N) of the downlink channels, bearer, channel throughputs, cell capacities, and average user throughputs. Uplink: Diversity mode, received powers of the uplink channels, transmission power, allocated bandwidth, total noise on the uplink channels, C/(I+N) of the uplink channels, bearer, channel throughputs, cell capacities, allocated bandwidth throughputs, and average user throughputs.
To get all the above information in a single report: •
Click the Report button (
8. Click the Point Analysis button (
14.2.10.7.4
) in the Reception view toolbar. The Analysis Report dialogue appears. ) on the Radio Planning toolbar again to end the point analysis.
Creating a Focus Zone or Hot Spot for a Coverage Prediction Report The focus and hot spots define the area on which statistics can be drawn and on which reports are made. While you can only have one focus zone, you can define several hot spots in addition to the focus zone. It is important not to confuse the computation zone and the focus and hot spots. The computation zone defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus and hot spots are the areas taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spots. To define a focus zone or hot spot: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Zones folder. 3. Right-click the Focus Zone or Hot Spots folder, depending on whether you want to create a focus zone or a hot spot. The context menu appears. 4. From the context menu, select one of the following: •
Draw Polygon i.
Click once on the map to start drawing the focus zone or hot spot.
ii. Click once on the map to define each point on the map where the border of the focus zone or hot spot changes direction. iii. Click twice to finish drawing and close the focus zone or hot spot. •
Draw Rectangle i.
Click the point on the map that will be one corner of the rectangle that will define the focus zone or hot spot.
1479
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
ii. Drag to the opposite corner of the rectangle that will define the focus zone or hot spot. When you release the mouse, the focus zone or hot spot will be created from the rectangle defined by the two corners. A focus zone is delimited by a green line; a hot spot is delimited by a heavy black line. If you clear the zone’s visibility check box in the Zones folder of the Geo explorer, it will no longer be displayed but will still be taken into account. You can also create a focus or hot spot as follows: • •
•
•
Vector Editor toolbar: You can use the New Polygon ( ) and New Rectangle ( ) buttons available in the Vector Editor toolbar to draw the computation zone. Existing polygon: You can use any existing polygon on the map as a focus or hot spot by right-clicking it and selecting Use As > Focus Zone or Use As > Hot Spot from the context menu. You can also combine an existing focus zone or hot spot with any existing polygon by right-clicking it on the map or in the explorer window and selecting Add To > Focus Zone or Add To > 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. You can import it by right-clicking the Focus Zone or Hot Spots folder in the Geo explorer and selecting Import from the context menu. When you import hot spots, you can import the name given to each zone as well. Fit Zone to Map Window: You can create a focus or hot spot the size of the map window by selecting Fit Zone to Map Window from the context menu. •
You can save the focus zone or hot spots, so that you can use it in a different Atoll document, in the following ways: •
•
14.2.10.7.5
Saving the focus zone in the user configuration: For information on saving the focus zone in the user configuration, see "Saving a User Configuration" on page 101. • Exporting the focus zone or hot spots: You can export the focus zone or hot spots by right-clicking the Focus Zone or the Hot Spots folder in the Geo explorer and selecting Export from the context menu. You can include population statistics in the focus or hot spot by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137.
Displaying a Coverage Prediction Report Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the covered surface and percentage for each threshold value defined in the Display tab of the coverage prediction’s Properties dialogue. The coverage prediction report is displayed in a table. For information on working with tables, see "Working with Data Tables" on page 69. By default, the report table only displays the name and coverage area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding columns, see "Displaying or Hiding a Column" on page 74. Atoll bases the report on the area covered by the focus zone and hot spots; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can create a report for a specific number of sites, instead of creating a report for every site that has been calculated. The focus zone or hot spot must be defined before you display a report; it is not necessary to define it before calculating coverage. The focus zone or hot spot does not, however, need to be visible; even if it is not displayed, Atoll will take it into account when generating the report. For information on defining a focus zone or hot spot, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1479. Once you have generated a report, you can export it to a text file or to an Excel spreadsheet. For more information on exporting a coverage prediction report, see "Exporting a Coverage Prediction Report" on page 1482. Atoll can generate a report for a single prediction, or for all displayed predictions. To display a report on a single coverage prediction: 1. Select the Network explorer. 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:
1480
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
You can select the columns that will be displayed in the report and define the order they are in: a. Select the check box for each column you want to have displayed. b. Define the order of the columns by selecting each column you want to move and clicking to move it down.
to move it up or
You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. 6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report is based on the hot spots and on the focus zone if available or on the hot spots and computation zone if there is no focus zone. To display a report on all coverage predictions: 1. Select the Network explorer. 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.
to move it up or
You can save the current report format in a configuration: a. Under Configuration, click the Save button. The Save As dialogue appears. b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name. You can load a configuration that you have saved previously and apply it to the current report: a. Under Configuration, click the Load button. The Open dialogue appears. b. Select the configuration you want to load and click Open. The loaded report configuration is applied. 5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation zone if there is no focus zone. You can include population statistics in the focus zone or hot spots by importing a population map. For information on importing maps, see "Importing a Raster-format Geo Data File" on page 137. Normally, Atoll takes all geo data into consideration, whether it is displayed or not. However, for the population statistics to be used in a report, the population map has to be displayed. To include population statistics in the focus zone or hot spots: 1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. 2. Select the Network explorer. 3. Right-click the Predictions folder. The context menu appears. 4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears. 5. Select the following columns, where "Population" is the name of the folder in the Geo explorer 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.
6. Click OK.
1481
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Atoll saves the names of the columns you select and will automatically select them the next time you create a coverage prediction report. 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 154.
14.2.10.7.6
Exporting a Coverage Prediction Report Once you have generated a coverage prediction report as explained in "Displaying a Coverage Prediction Report" on page 1480, you can export it to a text file or to a spreadsheet. To export a coverage prediction report: 1. Right-click the report and select Export from the context menu or click the Export button ( The Save As dialogue appears.
) in the Table toolbar.
2. In the Save As dialogue, enter the File name and select the format from the Save as type list: • • • •
TXT: To save the report as a text file. CSV: To save the report as a comma-separated values file. XLS: To save the report as an Excel spreadsheet. XML Spreadsheet 2003: To save the report as an XML spreadsheet.
3. Click Save to export the coverage prediction report.
14.2.10.7.7
Viewing Coverage Prediction Statistics Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays a histogram using the coverage prediction colours, interval steps, and shading as defined on the Display tab of the coverage prediction’s Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1 - CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display the histogram or the CDFs as percentages of the covered area. Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation zone. However, by using a focus zone for the report, you can display the statistics for a specific number of sites, instead of displaying statistics for every site that has been calculated. Hot spots are not taken into consideration when displaying statistics. The focus zone must be defined before you display statistics; it is not necessary to define it before calculating coverage. For information on defining a focus zone, see "Creating a Focus Zone or Hot Spot for a Coverage Prediction Report" on page 1479. To display the statistics on a coverage prediction: 1. Select the Network explorer. 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 14.24). • •
• • •
1482
Under Histogram based on covered areas, you can select to view a histogram, CDF, or inverse CDF based on area or percentage. The Zoom on selected values section displays the covered area values, or the percentage of the covered area, along the y-axis against the coverage criterion along the x-axis. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values. You can copy the graph by clicking the Copy button. You can print the graph by clicking the Print button. Under Statistics based on prediction conditions, you can view the mean and standard deviation of the coverage criterion calculated during the coverage calculations, if available.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.24: Histogram of a coverage prediction by signal level
14.2.10.7.8
Comparing Coverage Predictions: Examples Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see how changes you make affect the network. In this section, there are two examples to explain how you can compare two similar predictions. You can display the results of the comparison in one of the following ways: • •
•
Intersection: This display shows the area where both prediction coverages overlap (for example, pixels covered by both predictions are displayed in red). Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and pixels covered by only one prediction are blue). Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for example, pixels covered by both predictions are red, pixels covered only by the first prediction are green, and pixels covered only by the second prediction are blue).
To compare two similar coverage predictions: 1. Create and calculate a coverage prediction of the existing network. 2. Examine the coverage prediction to see where coverage can be improved. 3. Make the changes to the network to improve coverage. 4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged). 5. Calculate the duplicated coverage prediction. 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 1483 "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 1485.
Example 1: Studying the Effect of a New Base Station If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can verify if a newly added base station improves coverage. A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal Level" on page 1472. The results are displayed in Figure 14.25. An area with poor coverage is visible on the right side of the figure.
1483
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.25: 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 1437, or by placing a station template, as explained in "Placing a New Base Station Using a Station Template" on page 1446. 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 14.26).
Figure 14.26: 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: • •
1484
Intersection Union
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
•
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 14.27, shows clearly the area covered only by the new base station.
Figure 14.27: Comparison of both signal level coverage predictions Example 2: Studying the Effect of a Change in Transmitter Tilt If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing coverage. In this example, you can see how modifying transmitter tilt can improve coverage. A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by Transmitter" on page 1474. The results are displayed in Figure 14.28. The coverage prediction shows that one transmitter is covering its area poorly. The area is indicated by a red oval in Figure 14.28.
Figure 14.28: 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 14.29).
1485
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.29: 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 14.30, shows clearly the increase in coverage due at the change in antenna tilt.
Figure 14.30: Comparison of both transmitter coverage predictions
14.2.10.8 LTE Coverage Predictions Two types of LTE coverage predictions are available in Atoll: coverage predictions used to analyse the effective signal levels, and coverage predictions used to analyse the signal quality.
1486
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Effective signal analysis coverage predictions can be used to analyse different signals (reference signals, SS, PBCH, PDSCH, and PDCCH) in the downlink as well as in the uplink once the user-end gains and losses have been considered. These coverage predictions do not depend on the network load conditions. The cell coverage areas for these predictions are only limited by the cell minimum RSRP. 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. The cell coverage areas for RS, SS, PBCH, and PDCCH signal quality predictions are only limited by the cell minimum RSRP. However, the cell coverage areas for PDSCH signal quality predictions, service area, throughput, and quality indicator predictions are limited by the cell minimum RSRP and the bearer selection thresholds of the lowest available bearer. 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 1487.
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 1489. "Analysing the Signal Quality" on page 1491.
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: •
14.2.10.8.1
"Analysing Interference Areas Using a Point Analysis" on page 1503.
Service and User Modelling Atoll can base its signal quality predictions on the DL traffic loads and the UL noise rise entered in the Cells table (for more information, see "Setting the Traffic Loads and the UL Noise Rise" on page 1492). Before you can model services, you must define LTE radio bearers. For more information on LTE radio bearers, see "Defining LTE Radio Bearers" on page 1591. In this section, the following are explained: • • •
"Modelling Services" on page 1487. "Modelling Mobility Types" on page 1488. "Modelling Terminals" on page 1488.
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: • • • • •
Highest bearer Lowest bearer Throughput scaling factor Throughput offset Body loss
To create or modify a service: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the Services folder. The context menu appears. 4. Select New from the context menu. The Services: New Element Properties dialogue appears. You can modify the properties of an existing service by right-clicking the service in the Services folder and selecting Properties from the context menu.
5. Click the General tab. On the General tab, you can change the following parameters: • •
•
Name: Atoll proposes a name for the new service, but you can set a more descriptive name. Activity factor: The uplink and downlink activity factors are used to determine the probability of activity for users accessing the service during Monte Carlo simulations. For Voice services, this parameter is used when working with sector traffic maps and user density traffic maps. For Data services, Atoll distributes the users according to the activity factors when importing user density traffic maps for all activity statuses. Average requested rate: 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.
1487
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
6. Click the LTE tab. On the LTE tab, you can change the following parameters: • • • • • • •
Type: You can select either Voice or Data as the service type. Priority: Enter a priority for this service. "0" is the lowest priority. Highest bearer: Select the highest bearer that the service can use in the uplink and downlink. This is considered as an upper limit during bearer determination. Lowest bearer: Select the lowest bearer that the service can use in the uplink and downlink. This is considered as a lower limit during bearer determination. Max throughput demand: Enter the highest throughput that the service can demand in the uplink and downlink. Min throughput demand: Enter the minimum required throughput 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 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 user’s head, is estimated to be 3 dB.
7. Click OK. Modelling Mobility Types In LTE, information about the receiver mobility is required for determining which bearer selection threshold and quality graph to use from the reception equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking speeds do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely dependent on mobile speed. To create or modify a mobility type: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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 car’s on-board navigation device. To create or modify a terminal: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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. Click the General tab. On the General tab, you can change the following parameters: •
1488
Name: Enter a descriptive name for the terminal.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
6. Click the LTE tab. On the LTE tab, you can change the following parameters: •
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. Reception equipment: Select an equipment from the list of available reception equipment. For more information on reception equipment, see "Defining LTE Reception Equipment" on page 1592. • UE category: Select a UE category from the list of available UE categories. For more information on UE categories, see "Defining LTE UE Categories" on page 1596. 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 omni-directional antenna, in calculations. An isotropic antenna has spherical radiation patterns in the horizontal as well as vertical planes.
• •
•
Gain: Enter the terminal antenna gain if you have not selected an antenna model in the Model field. If you have selected an antenna, the Gain field is disabled and shows the gain of the selected antenna. Diversity support: Select the type of antenna diversity techniques supported by the terminal. Antenna diversity gains will be applied to the users using any terminal type depending on the supported antenna diversity techniques, i.e., AAS, MIMO, or AAS+MIMO. If a terminal that supports AAS+MIMO is connected to a cell that supports both antenna diversity techniques, both AAS and MIMO gains will be applied. Under MIMO, enter the Number of transmission antenna ports and the Number of reception antenna ports available in the terminal.
7. Click OK.
14.2.10.8.2
Analysing the Effective Signal Levels Atoll offers a couple of LTE coverage predictions which can be based on the predicted signal level from the best server and the thermal background noise at each pixel, i.e., received carrier power (C) and the carrier-to-noise ratio (C/N). This section explains the coverage predictions available for analysing the effective signal levels. Downlink and uplink effective signal analysis coverage predictions predict the effective signal levels of different types of LTE signals, such as reference signals, SS, PBCH, PDSCH including the PDCCH and the downlink traffic channel, and PUSCH, in the part of the network being studied. Atoll calculates the serving transmitter for each pixel depending on the downlink reference signal level. The serving transmitter is determined according to the received reference signal level from the cell with the highest reference signal power. In a prediction for the "Best" layer, if more than one cell cover the pixel, the one with the highest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the effective signal (C or C/N for reference signals, SS, etc.). Pixels are coloured if the display threshold condition is fulfilled (in other words, if the C or C/N is higher than the C or C/N threshold). To make an effective signal analysis coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Effective Signal Analysis (DL) or Effective Signal Analysis (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group By and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 14.31). On the Condition tab, you can select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The effective signal analysis coverage prediction is always a best server coverage prediction. The Noise figure defined in the terminal type’s properties dialogue is used in the coverage
1489
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
prediction to determine the total noise in the downlink, and the Noise figure of the transmitter is used to determine the total noise in the uplink. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1487, "Modelling Terminals" on page 1488, "Modelling Mobility Types" on page 1488, and "Defining LTE Reception Equipment" on page 1592, respectively. If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a percentage in the Cell edge coverage probability text box. The shadowing margin for the effective signal analysis calculations is based on the C/I standard deviation. You can also have the coverage prediction take Indoor coverage into consideration.
Figure 14.31: Condition settings for an effective signal analysis coverage prediction 7. Click the Display tab. 8. From the Display type list, select "Value intervals" to display the coverage prediction by RSRP, signal levels, or C/N levels. For information on adjusting the display, see "Display Properties of Objects" on page 43. 9. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.32 and Figure 14.33).
1490
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.32: PDSCH C/N coverage prediction
Figure 14.33: PUSCH & PUCCH C/N coverage prediction
14.2.10.8.3
Analysing the Signal Quality In LTE, the capacity and the effective service coverage areas of cells are influenced by network loads. As the network load increases, the area where a cell provides service decreases. For this reason, network loads must be defined in order to calculate these coverage predictions. 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 depends on the cells’ physical cell IDs and 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.
1491
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 1492.
Several signal quality coverage predictions are explained in this section. The following predictions are explained: • • • • • • •
"Making a Coverage by C/(I+N) Level" on page 1492. "Making a Downlink or Uplink Service Area Analysis" on page 1495. "Studying the Effective Service Area" on page 1497. "Making a Coverage Prediction by Throughput" on page 1498. "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1500. "Making a Coverage Prediction by Quality Indicator" on page 1501. "Analysing Interference Areas Using a Point Analysis" on page 1503.
Setting the Traffic Loads and the UL Noise Rise If you are setting the traffic loads and the uplink noise rise for a single transmitter, you can set these parameters on the Cells tab of the transmitter’s Properties dialogue. However, you can set the traffic loads and the uplink noise rise for all the cells using the Cells table. To set the traffic loads and the uplink noise rise using the Cells table: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Cells > Open Table from the context menu. The Cells table appears. 4. Enter a value in the following columns: • • • •
Traffic load (DL) (%) ICIC ratio (DL) (%) UL noise rise (dB) ICIC UL noise rise (dB)
Although, you can also set a value for the Traffic load (UL) (%) column as an indication of cells’ uplink loads, this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink is given by the uplink noise rise values. For a definition of the values, see "Cell Description" on page 1441. To enter the same values in one column for all cells in the table: 1. Enter the value in the first row in the column. 2. Select the entire column. 3. Right-click the selection and select Edit > Fill Down from the context menu or click the Fill Down button ( Table toolbar to copy the contents of the top cell of the selection into the other cells.
) in the
If you want to copy the contents of the last cell in the selection into all other cells, you can right-click the selection and select Edit > Fill Up from the context menu or click the Fill Up button ( ) in the Table toolbar. For more information on working with tables in Atoll, see "Working with Data Tables" on page 69. Making a Coverage by C/(I+N) Level Downlink and uplink coverage predictions by C/(I+N) level predict the interference levels and signal-to-interference levels in the part of the network being studied. Atoll calculates the serving transmitter for each pixel depending on the downlink reference signal level. The serving transmitter is determined according to the received reference signal level from the cell with the highest reference signal power. In a prediction for the "Best" layer, if more than one cell cover the pixel, the one with the highest layer is selected as the serving (reference) cell. Then, depending on the prediction definition, it calculates the interference from other cells, and finally calculates the C/(I+N). The pixel is coloured if the display threshold condition is fulfilled (in other words, if the C/(I+N) is higher than C/(I+N) threshold). Coverage prediction by C/(I+N) level calculates the co-channel interference as well as the adjacent channel interference, which is reduced by the adjacent channel suppression factor defined in the Frequency Bands table. For more information on frequency bands, see "Defining Frequency Bands" on page 1587. C/(I+N) in the downlink is calculated for different channels using their respective transmission powers and by calculating the interference received by the resource elements corresponding to these channels from interfering cells. Downlink C/(I+N) calculations are made using the main antenna except for PDSCH C/(I+N) which can be calculated using the smart antenna
1492
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
equipment. C/(I+N) in the uplink 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. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 14.34). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the cell loads stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The C/(I+N) coverage prediction is a best server coverage prediction. The Noise figure defined in the terminal type’s 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 reception equipment, see "Modelling Services" on page 1487, "Modelling Terminals" on page 1488, "Modelling Mobility Types" on page 1488, and "Defining LTE Reception Equipment" on page 1592, 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 14.34: Condition settings for a coverage prediction by C/(I+N) level 7. Click the Display tab. 8. From the Display type list, select "Value intervals" to display the coverage prediction by RSRQ, RSSI, C/(I+N) levels, or total noise (I+N) levels. For information on adjusting the display, see "Display Properties of Objects" on page 43.
1493
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 1595. 9. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.35 and Figure 14.36).
Figure 14.35: Coverage prediction by PDSCH C/(I+N)
Figure 14.36: Coverage prediction by PUSCH & PUCCH C/(I+N)
1494
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Making a Downlink or Uplink Service Area Analysis Downlink and uplink service area analysis coverage predictions calculate and display the LTE radio bearers based on C⁄(I+N) for each pixel. In coverage predictions, the downlink or uplink service areas are limited by the bearer selection thresholds of the highest and lowest bearers of the selected service. To make a coverage prediction on service area: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Service Area Analysis (DL) or Service Area Analysis (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 14.37). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the cell loads stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The best bearer coverage prediction is always based on the best server. The Noise figure defined in the terminal type’s 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 reception equipment. This reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection threshold graph to use. You can make Atoll use only the bearers for which selection thresholds are defined in both the terminal’s and the cell’s reception equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1487, "Modelling Terminals" on page 1488, "Modelling Mobility Types" on page 1488, and "Defining LTE Reception Equipment" on page 1592, 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.
1495
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.37: Condition settings for a coverage prediction on LTE bearers 7. Click the Display tab. 8. From the Display type list, select display by bearer or modulation. For information on adjusting the display, see "Display Properties of Objects" on page 43. 9. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.38 and Figure 14.39).
Figure 14.38: Downlink service area analysis display by bearer
1496
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.39: Uplink service area analysis display by bearer Studying the Effective Service Area The effective service area is the intersection zone between the uplink and downlink service areas. In other words, the effective service area prediction calculates where a service actually is available in both downlink and uplink. The service availability depends upon the bearer selection thresholds of the highest and lowest bearers defined in the properties of the service selected for the prediction. To make an effective service area coverage prediction: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Effective Service Area Analysis (DL+UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the 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 cell loads stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The bearer coverage prediction is always based on the best server. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1487, "Modelling Terminals" on page 1488, "Modelling Mobility Types" on page 1488, and "Defining LTE Reception Equipment" on page 1592, 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.
1497
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 is available in both downlink and uplink. For information on defining display properties, see "Display Properties of Objects" on page 43. When creating a coverage prediction by unique values, you can not export the values per pixel.
8. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. Making a Coverage Prediction by Throughput Downlink and uplink throughput coverage predictions calculate and display the channel throughputs and cell capacities based on C⁄(I+N) and bearer calculations for each pixel. These coverage predictions can also display aggregate cell throughputs if Monte Carlo simulation results are available. For more information on making aggregate cell throughput coverage predictions using simulation results, see "Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 1500. To make a coverage prediction by throughput: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 14.40). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the cell loads stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The throughput coverage prediction is always based on the best server. The Noise figure defined in the terminal type’s 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 reception equipment. This reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the serving transmitter for the uplink coverage predictions. 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. You can make Atoll use only the bearers for which selection thresholds are defined in both the terminal’s and the cell’s reception equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual.
1498
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1487, "Modelling Terminals" on page 1488, "Modelling Mobility Types" on page 1488, and "Defining LTE Reception Equipment" on page 1592, 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 14.40: Condition settings for a throughput coverage prediction 7. Click the Display tab. 8. From the Display type list, select "Value intervals" to display the coverage prediction by peak RLC, effective RLC, or application throughputs. For information on adjusting the display, see "Display Properties of Objects" on page 43. 9. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 10. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer. Atoll determines the total number of symbols in the downlink and the uplink frames from the information in the global transmitter parameters and the frequency bands 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 reception equipment defined in the selected terminal for downlink or the reception equipment of the cell of the serving transmitter for uplink. The application throughput is the effective RLC throughput reduced by the overheads of the different layers between the RLC and the Application layers. 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 either the allocated bandwidth throughput or the uplink cell capacity divided by the number of uplink users of the serving cell, whichever it smaller. The allocated bandwidth throughputs are the throughputs corresponding to the number of frequency blocks allocated to the terminal at different locations. Users located far from the base stations use less numbers of frequency blocks than users
1499
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 Network Settings" on page 1588. Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Figure 14.41: Coverage prediction by downlink channel throughput
Figure 14.42: Coverage prediction by uplink channel throughput Making an Aggregate Throughput Coverage Prediction Using Simulation Results Atoll calculates the aggregate peak RLC, effective RLC, and application cell throughputs during Monte Carlo simulations. The aggregate cell throughputs are the sums of the cell’s user throughputs. You can create a coverage prediction that calculates and displays the surface area covered by each cell, and colours the coverage area of each cell according to its aggregate throughput.
1500
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
To create an aggregate throughput coverage prediction: 1. Create and calculate a Monte Carlo simulation. For more information on creating Monte Carlo simulations, see "Calculating and Displaying Traffic Simulations" on page 1541. 2. Create a coverage prediction by throughput as explained in "Making a Coverage Prediction by Throughput" on page 1498, with the following exceptions: a. On the Condition tab, select a simulation or group of simulations from the Load conditions list. The coverage prediction will display the results based on the selected simulation or on the average results of the selected group of simulations. b. On the Display tab, you can display results by Peak RLC aggregate throughput, Effective RLC aggregate throughput, or Aggregate application throughput. The coverage prediction results will be in the form of thresholds. For information on defining the display, see "Display Properties of Objects" on page 43. 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 1555. Making a Coverage Prediction by Quality Indicator Downlink and uplink quality indicator coverage predictions calculate and display the values of different quality indicators (BLER, BER, etc.) based on the best LTE radio bearers and on C⁄(I+N) for each pixel. To make a coverage prediction by quality indicator: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select New Prediction from the context menu. The Prediction Types dialogue appears. 4. Select Coverage by Quality Indicator (DL) or Coverage by Quality Indicator (UL) and click OK. The coverage prediction’s 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 216. Under Display configuration, you can create a Filter to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 95. The Group by and Sort buttons are not available when making a so-called "global" coverage prediction (e.g., signal level coverage prediction). 6. Click the Condition tab (see Figure 14.37). Select "(Cells table)" from Load conditions. In this case, the coverage prediction is not going to be based on load conditions taken from a simulation. Atoll will calculate the coverage prediction using the cell loads stored in the cell properties. When you base a coverage prediction on simulations, you would select the simulations on which you would be basing the coverage prediction from the Load conditions list.
You must select a Terminal, a Mobility type, and a Service. You can also select a cell Layer, or carry out the prediction for the "Best" layer. The quality indicator coverage prediction is always based on the best server. The Noise figure defined in the terminal type’s 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 reception equipment, and the quality indicator graphs from the reception equipment are used to determine the values of the selected quality indicator on each pixel. This reception equipment is the one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection threshold graph to use. You can make Atoll use only the bearers for which selection thresholds are defined in both the terminal’s and the cell’s reception equipment by adding an option in the atoll.ini file. For more information, see the Administrator Manual. For more information on services, terminals, mobility types, and reception equipment, see "Modelling Services" on page 1487, "Modelling Terminals" on page 1488, "Modelling Mobility Types" on page 1488, and "Defining LTE Reception Equipment" on page 1592, respectively.
1501
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 14.43: 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 1592. The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of Objects" on page 43. 8. Click the Result Export tab. You can export the results per pixel of the coverage prediction. For information, see "Exporting the Values per Pixel of a Coverage Prediction" on page 219. 9. Once you have created the coverage prediction, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined coverage prediction and calculate it immediately. OK: Click OK to save the defined coverage prediction without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning 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 14.44 and Figure 14.45).
1502
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.44: Coverage prediction by downlink BLER
Figure 14.45: Coverage prediction by uplink BLER
14.2.10.8.4
Analysing Interference Areas Using a Point Analysis In Atoll, you can study the interferers of a transmitter using the Point Analysis tool. The Interference view gives you information on interference received on any downlink channel on any point on the map. The analysis is provided for a user-definable probe receiver which has a terminal, a mobility, and a service. The downlink and uplink load conditions can be taken from the Cells table or from Monte Carlo simulations. You can make a interferences analysis to verify a coverage prediction. If you do, before you make the point analysis, ensure the coverage prediction you want to verify is displayed on the map. To make an interference analysis: 1. Click the Point Analysis button (
) on the Radio Planning toolbar. The Point Analysis window appears (see
Figure 14.46) and the pointer changes (
) to represent the receiver.
2. Select the Interference view. 3. At the top of the Interference view, select "Cells table" from Load. 4. Select the channel on which you wish to study the interference from the Display list.
1503
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
5. If you are making an interference 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. Click the Options button ( • • •
) in the Interference view toolbar. The Calculation Options 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.
c. Click OK to close the Calculation Options dialogue. 6. Move the pointer over the map to make an interference analysis for the current location of the pointer. In the map window, a thick arrow from the pointer to its best server is displayed. The best server of the pointer is the transmitter from which the pointer receives the highest reference signal level. Thinner arrows are also displayed from the interfering cells towards the pointer, indicating the interferers. If you let the pointer rest on an arrow, the interference level received from the corresponding transmitter at the receiver location will be displayed in the tip text. 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. Select the load conditions to use in this analysis from simulations or from the Cells table.
The best server signal level (top-most bar), total noise (black bar), and interference from other cells.
Select the parameters of the probe user to be studied. Figure 14.46: Point Analysis tool: Interference view The Interference view displays, in the form of a bar graph, the signal level from the best server, a black bar indicating the total noise (I+N) received by the receiver, and bars representing the interference received from each interferer. You can change the following options in the Interference view: •
Intra-technology: You can select the Intra-technology check box if you want Atoll to display the intra-technology interference.
To get the details about the best server and all the interferers in the form of a report: •
Click the Report button (
) in the Interference view toolbar. The Analysis Report dialogue appears.
8. Click the Details view. The Details view displays, for each cell received, the cell’s name, its distance from the receiver, its physical cell ID, 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. 9. Click the Point Analysis button (
) on the Radio Planning toolbar again to end the point analysis.
14.2.10.9 Printing and Exporting Coverage Prediction Results Once you have made a coverage prediction, you can print the results displayed on the map or save them in an external format. You can also export a selected area of the coverage as a bitmap. •
•
1504
Printing coverage prediction results: Atoll offers several options allowing you to customise and optimise the printed coverage prediction results. Atoll supports printing to a variety of paper sizes, including A4 and A0. For more information on printing coverage prediction results, see "Printing a Map" on page 84. Defining a geographic export zone: If you want to export part of the coverage prediction as a bitmap, you can define a geographic export zone. After you have defined a geographic export zone, when you export a coverage prediction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more information on defining a geographic export zone, see "Using a Geographic Export Zone" on page 59.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
•
Exporting coverage prediction results: In Atoll, you can export the coverage areas of a coverage prediction in raster or vector formats. In raster formats, you can export in BMP, TIF, JPEG 2000, ArcView© grid, or Vertical Mapper (GRD and GRC) formats. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 GB. In vector formats, you can export in ArcView©, MapInfo©, or AGD formats. For more information on exporting coverage prediction results, see "Exporting Coverage Prediction Results" on page 67.
14.2.11 Planning Neighbours You can set neighbours for each cell manually, or you can let Atoll automatically allocate neighbours, based on the parameters that you define. When allocating neighbours, the cell to which you are allocating neighbours is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as potential neighbours. When allocating neighbours to all active and filtered transmitters, Atoll allocates neighbours only to the cells within the focus zone and considers as potential neighbours all the active and filtered cells whose propagation zone intersects the rectangle containing the computation zone. If there is no focus zone, Atoll allocates 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 explorer 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 "The Focus Zone and Hot Spots" on page 56. For information on grouping transmitters in the explorer window, see "Grouping Data Objects" on page 89. 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 1505 "Defining Exceptional Pairs" on page 1505 "Configuring Importance Factors for Neighbours" on page 1506 "Allocating Neighbours Automatically" on page 1506 "Checking Automatic Allocation Results" on page 1509 "Allocating and Deleting Neighbours per Cell" on page 1512 "Calculating the Importance of Existing Neighbours" on page 1514 "Checking the Consistency of the Neighbour Plan" on page 1515 "Exporting Neighbours" on page 1516.
14.2.11.1 Importing Neighbours You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document using the Neighbours table. To import neighbours using the Neighbours table: 1. Open the Neighbours table: a. Select the Network explorer. b. Right-click the LTE Transmitters folder. The context menu appears. c. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears. 2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 82.
14.2.11.2 Defining Exceptional Pairs In Atoll, you can define neighbour constraints that will be taken into consideration during the automatic allocation of neighbours. Exceptional pairs can be taken into consideration when you manually allocate neighbours. To define exceptional pairs of neighbours: 1. Select the Network explorer. 2. Right-click the LTE 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 cell’s Properties dialogue appears.
1505
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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. Click the Edit button on the bottom-right of the dialogue. The exceptional pair list becomes editable. b. Select the cell from the list in the Neighbours column. c. In the Status column, select one of the following: • •
Forced: The selected cell will always be a neighbour of the reference cell. Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair. 9. Click OK. You can also create exceptional pairs using the Intra-technology Exceptional Pairs table. You can open this table by right-clicking the LTE Transmitters folder and selecting Neighbours > Intra-technology > Exceptional Pairs from the context menu.
14.2.11.3 Configuring Importance Factors for Neighbours You can define the relative importance of the factors that Atoll uses to evaluate possible intra-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for neighbours: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. On the Intra-technology Neighbours tab, you can set the following importance factors: • • •
•
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. Adjacency factor: Set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference transmitter. The Adjacency factor will be used if you select the Force adjacent transmitters as neighbours check box when defining an automatic neighbour allocation. For information on automatically allocating neighbours, see "Allocating Neighbours Automatically" on page 1506. 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 1506.
5. Click OK. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual.
14.2.11.4 Allocating Neighbours Automatically Atoll can automatically allocate neighbours in an LTE network. Atoll allocates neighbours based on the parameters you set in the Automatic Neighbour Allocation dialogue. To allocate LTE neighbours automatically: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > 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: •
1506
Max inter-site distance: Set the maximum distance between the reference cell and a possible neighbour.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• •
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. • Global min RSRP: Select the Global min RSRP check box if you want to set a global value for the minimum RSRP. If you set a global value here, Atoll will use either 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 14.47). The higher the value entered for the RSRP margin, the longer the list of potential 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 defined per clutter class in the calculations. % min covered area: Enter the minimum surface area, in percentage, that a possible neighbour cell’s coverage area must overlap the reference cell’s 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 cell’s 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 1505. 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 14.47: The handover area between the reference cell and the possible neighbour 7. 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.
1507
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• • • • • •
• • •
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 1506 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 Relation type: The type of the neighbour relation: intra-carrier or inter-carrier. Cells whose channels have the same centre frequency are intra-carrier neighbours. Other cells are inter-carrier neighbours. Coverage: The amount of reference cell’s 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 Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. 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 automatically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: • • • •
The document name and the neighbour allocation type 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 cell’s Properties dialogue. •
•
•
•
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already exists and the Delete existing neighbours check box is cleared when you start the new allocation. 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. However, if the neighbour relation is forced in one direction and forbidden in the other, the symmetry cannot be respected. By adding an option in the atoll.ini file, the neighbour allocation and importance calculation can be based on the distance criterion only. For more information, see the Administrator Manual. You can save automatic neighbour allocation parameters in a user configuration. For information on saving automatic neighbour allocation parameters in a user configuration, see "Saving a User Configuration" on page 101.
Atoll also enables you to automatically allocate neighbours to a single base station or transmitter: • •
14.2.11.4.1
"Allocating Neighbours to a New Base Station" on page 1508 "Allocating Neighbours to a New Transmitter" on page 1509.
Allocating Neighbours to a New Base Station When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new base station and other cells whose coverage area intersects the coverage area of the cells of the new base station.
1508
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
To allocate neighbours to a new base station: 1. In the Network explorer, group the transmitters by site, as explained in "Grouping Data Objects" on page 89. 2. In the LTE Transmitters folder, right-click the new base station. The context menu appears. 3. Select Neighbours > Intra-technology Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 1506.
14.2.11.4.2
Allocating Neighbours to a New Transmitter When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the new transmitters and other cells whose coverage area intersects the coverage area of the cells of the new transmitter. To allocate neighbours to a new transmitter: 1. Select the Network explorer. 2. In the LTE Transmitters folder, right-click the new transmitter. The context menu appears. 3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears. 4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on page 1506.
14.2.11.5 Checking Automatic Allocation Results You can verify the results of automatic neighbour allocation in the following ways: • •
14.2.11.5.1
"Displaying Neighbour Relations on the Map" on page 1509. "Displaying the Coverage of Each Neighbour of a Cell" on page 1511.
Displaying Neighbour Relations on the Map You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour relation is symmetric. To display the neighbour relations of a cell on the map: 1. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
2. Select Display Options from the context menu. The Neighbour Display dialogue appears. 3. Under Intra-technology Neighbours, select the Display links check box. 4. Click the Browse button ( appears.
) beside the Display links check box. The Intra-technology Neighbour Display dialogue
5. From the Display type list, choose one of the following: • •
•
Unique: Select "Unique" if you want Atoll to colour all neighbour links of a cell with a unique colour. Discrete values: Select "Discrete values", and then a value from the Field list, if you want Atoll to colour the cell’s 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 cell’s neighbour links according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s neighbours according to the importance, as determined by the weighting factors. 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 Type’s Data Table" on page 71.
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 43. 6. Select the Add to legend check box to add the displayed neighbour links to the legend.
1509
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
7. Click the Browse button ( ) next to Tip text and select the neighbour characteristics to be displayed in the tip text. This information will be displayed on each neighbour link. 8. Click OK to save your settings. 9. 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 links: Select the Symmetric links check box to display neighbour relations that are symmetric between the selected cell and the neighbour.
10. Click OK to save your settings. 11. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
12. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 13. Click the Edit Relations on the Map button (
) in the Radio Planning toolbar.
14. Select a transmitter to show its neighbour links: •
•
•
In the Transmitters folder of the Network explorer: Select the transmitter in the Transmitters folder. The selected transmitter is centred in the map and all its neighbours are indicated. Atoll displays the selected transmitter in the Neighbours table if it is open. On the map: Select the transmitter on the map. The neighbours of the selected transmitter are displayed on the map. 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 41). Atoll displays the selected transmitter in the Neighbours table if it is open. In the Neighbours table: Select the transmitter-neighbour relation you want to display by clicking in the left margin of the table row to select the entire row. The selected transmitter is centred in the map with the selected transmitter-neighbour relation (see Figure 14.48). The selected transmitter is also displayed in the Transmitters folder of the Network explorer.
Figure 14.48: Selecting a transmitters in the Neighbours table Atoll displays the following information (see Figure 14.49) 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 14.49.). 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 14.49.).
In Figure 14.49, 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.
1510
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.49: Neighbours of Site 22_3(0) - Display according to the neighbour You can display either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
14.2.11.5.2
Displaying the Coverage of Each Neighbour of a Cell By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the coverage area of a cell’s neighbours and colour them according to any neighbour characteristic in the Neighbours table. To display the coverage of each neighbour of a cell: 1. Create, calculate, and display a "Coverage by Transmitter" prediction, with the Display type set to "Discrete values" and the Field set to "Transmitter" (for information on creating a coverage by transmitter prediction, see "Making a Coverage Prediction by Transmitter" on page 1474). 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
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 ( dialogue appears.
) beside the Display coverage areas check box. The Intra-technology Neighbour Display
6. From the Display type list, choose one of the following: • • •
Unique: Select "Unique" if you want Atoll to colour the coverage area of a cell’s neighbours with a unique colour. Discrete values: Select "Discrete values", and then a value from the Field list, if you want Atoll to colour the coverage area of a cell’s neighbours according to a value from the Intra-technology Neighbours table. Value intervals: Select "Value intervals" to colour the coverage area of a cell’s neighbours according the value interval of the value selected from the Field list. For example, you can choose to display a cell’s neighbours according to the importance, as determined by the weighting factors.
7. Click the Browse button ( ) next to Tip text and select the neighbour characteristics to be displayed in the tip text. This information will be displayed on each coverage area. 8. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. The menu
9. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter. 10. Click the Edit Relations on the Map button (
) in the Radio Planning toolbar.
11. 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 41). 12. In order to restore colours and cancel the neighbour display, click the Edit Relations on the Map button ( Radio Planning toolbar.
) in the
1511
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
14.2.11.6 Allocating and Deleting Neighbours per Cell Although you can let Atoll allocate neighbours automatically, you can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete neighbours directly on the map or using the Cells tab of a transmitter’s Properties dialogue. This section explains the following: • • •
"Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1512. "Allocating or Deleting Neighbours Using the Neighbours Table" on page 1512. "Allocating or Deleting Neighbours on the Map" on page 1513.
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 transmitter’s 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 transmitter’s Properties dialogue appears. 3. Click the Cells tab. 4. On the Cells tab, click the Browse button (
) beside Neighbours. The cell’s Properties dialogue appears.
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. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Under List, select the cell from the list in the Neighbour column in the row marked with the New row icon (
).
c. 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 Source to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. Select Make Symmetrical 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Press DEL to delete the neighbour. 8. Click OK. Allocating or Deleting Neighbours Using the Neighbours Table To allocate or delete LTE neighbours using the Neighbours table: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Open Table from the context menu. The Neighbours table appears.
1512
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
For information on working with data tables, see "Working with Data Tables" on page 69.
4. Allocate or delete a neighbour. To allocate a new neighbour: a. In the row marked with the New row icon (
), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column, sets the Source to "manual," and sets the Importance to "1." To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Make Symmetrical 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 Make Symmetrical from the context menu. To take into consideration all exceptional pairs: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. You can add or delete either some forced neighbours or some forbidden neighbours using the Intra-technology Exceptional Pairs 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 the entire row. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation between the cell in the Neighbour column and the cell in the Cell column is deleted. To delete several symmetric neighbour relations: a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select contiguous rows by clicking the first row, pressing Shift and clicking the last row. You can select non-contiguous rows by pressing CTRL and clicking each rows separately. b. Right-click the Neighbours table. The context menu appears. c. Select Delete Link and Symmetric Relation from the context menu. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. Allocating or Deleting Neighbours on the Map You can allocate or delete intra-technology neighbours directly on the map using the mouse. To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neighbours on the map as explained in "Displaying Neighbour Relations on the Map" on page 1509.
1513
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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. •
•
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 41). You can add or delete either forced neighbours or forbidden neighbours by clicking the arrow ( ) next to the Edit Relations on the Map button ( ) in the Radio Planning toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
14.2.11.7 Calculating the Importance of Existing Neighbours After you have imported neighbours into the current Atoll document or manually defined neighbours, Atoll can calculate the importance of each neighbour, i.e., the weight of each neighbour. This value is used to define a rank for different neighbours in the AFP process. Atoll calculates the importance for neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing neighbours: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Neighbours > Intra-technology > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 4. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as potential neighbours. 5. Under Importance, select the factors to be taken into consideration when calculating the importance (for information on defining importance factors, see "Configuring Importance Factors for Neighbours" on page 1506): •
1514
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.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
•
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.
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. Global min RSRP: Select the Global min RSRP check box if you want to set a global value for the minimum RSRP. If you set a global value here, Atoll will use either 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, 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.
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. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. 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 4. Cause: The reason Atoll has allocated value in the Importance column. • Co-site • Adjacency • Symmetry • Coverage Relation type: The type of the neighbour relation: intra-carrier or inter-carrier. Cells whose channels have the same centre frequency are intra-carrier neighbours. Other cells are inter-carrier neighbours. Coverage: The amount of reference transmitter’s 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.
9. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
14.2.11.8 Checking the Consistency of the Neighbour Plan You can perform an audit of the current neighbour allocation plan. When you perform an audit of the current neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the neighbour allocation plan: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appear. 3. Select Neighbours > Intra-technology > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Intra-technology Neighbours tab. 5. Define the parameters of the audit: •
Average no. of neighbours: Select the Average no. of neighbours check box if you want to verify the average number of neighbours per cell.
1515
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• •
•
• • • •
Empty lists: Select the Empty lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full lists: Select the Full lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all the cells, or specified for each cell in the Cells table. Lists > max number: Select the Full lists check box if you want to verify which cells have more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all the cells, or specified for each cell in the Cells table. Missing co-sites: Select the Missing co-sites check box if you want to verify which cells have no co-site neighbours. Missing symmetrics: Select the Missing symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional pairs: Select the Exceptional pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance between neighbours: Select the Distance between neighbours check box and enter the distance between neighbours that should not be exceeded.
6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: •
Average number of neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax:
•
Full lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax:
•
|CELL|
|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| 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:
•
Non symmetric links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
Existing forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Missing forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
|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|
14.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. Select the Network explorer. 2. Right-click the LTE 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: • •
1516
Intra-technology > Open Table: This table contains the data for the intra-technology neighbours in the current Atoll document. Inter-technology > Open Table: This table contains the data for the inter-technology neighbours in the current Atoll document.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• •
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 and Spreadsheets" on page 80.
14.3 Configuring Network Parameters Using the AFP Atoll Automatic Frequency Planning (AFP) enables radio engineers designing LTE networks to automatically configure network parameters such as the frequency channels and physical cell IDs. The AFP can also perform fractional frequency planning through automatic configuration of the PSS ID in physical cell ID planning. In this section, the following are explained: • • • •
"AFP Prerequisites" on page 1517 "Planning Frequencies" on page 1520 "Planning Physical Cell IDs" on page 1521 "Displaying and Analysing the AFP Results" on page 1523.
14.3.1 AFP Prerequisites In Atoll, you can use an Automatic Frequency Planning (AFP) module to allocate frequencies and physical cell IDs. The Automatic Frequency Planning (AFP) module attempts to allocate resources in a way that minimises interference and complies with a set of user-defined constraints. The AFP assigns a cost to each constraint and then uses a cost-based algorithm to evaluate possible allocation plans and propose the allocation plan with the lowest costs. In this section, the AFP input elements are explained. The quality of the results given by the AFP depend on the accuracy of the input, therefore it is important to prepare the input before running the AFP. In this section, the following are explained: • • • •
"Interference Matrices" on page 1517 "Neighbour Importance" on page 1519 "Resources Available for Allocation" on page 1519 "Constraint Weights" on page 1519.
14.3.1.1 Interference Matrices In Atoll, the probability of interference between pairs of cells is stored in an interference matrix. An interference matrix can be thought of as the probability that a user in a cell will receive interference higher than a defined threshold. You can calculate, import, edit, and store more than one interference matrix in the Interference Matrices folder in the Network explorer. In this section, the following are explained: • • •
14.3.1.1.1
"Calculating Interference Matrices" on page 1517 "Importing and Exporting Interference Matrices" on page 1518 "Viewing and Editing Interference Matrices" on page 1518.
Calculating Interference Matrices Atollcalculates interference matrices in the form of co- and adjacent channel interference probabilities for each interfered and interfering cell pair. The probabilities of interference are stated in terms of percentages of the interfered area. In other words, it is the ratio of the interfered surface area to the best server coverage area of an interfered cell. When Atoll calculates interference matrices, it calculates the ratio of the reference signal level to the total interference and noise (I+N) for each pixel of the interfered service area between two cells (the interfered cell and the interfering cell). For cochannel interference, a pixel is considered interfered if this ratio is lower than the per-channel reference signal C/N corresponding to the minimum RSRP defined for the interfered cell. For adjacent channel interference, a pixel is considered interfered if this ratio is lower than the reference signal C/N corresponding to the minimum RSRP defined for the interfered cell less the adjacent channel suppression factor defined for the frequency band of the interfered cell. You can amplify the degradation of the C/(I+N) by using a high quality margin when calculating the interference matrices. For example, a 3 dB quality margin would imply that each interferer is considered to be twice as strong compared to a calculation without any quality margin (i.e., 0 dB). To calculate interference matrices: 1. Select the Network explorer. 2. Right-click the LTE Interference Matrices folder. The context menu appears. 3. Select New. The Interference Matrices Properties dialogue appears.
1517
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
4. On the General tab, you can set the following parameters: • • • • •
Name: Enter a name for the new interference matrix. Resolution: Enter the resolution used to calculate the coverage areas of cells for the interference matrix calculation. Type: The type is set to Calculated for calculated interference matrices. Quality margin: Enter a quality margin. Shadowing taken into account: If desired, select the Shadowing taken into account check box and enter a Cell edge coverage probability.
5. Once you have created the new interference matrix, you can calculate it immediately or you can save it and calculate it later: • •
Calculate: Click Calculate to save the defined interference matrix and calculate it immediately. OK: Click OK to save the defined interference matrix without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
Once calculated, the new interference matrix is available in the Interference Matrices folder and will be available for use the next time you run the AFP. You can modify the properties of an existing interference matrix by selecting Properties from the interference matrix context menu. You can recalculate an existing interference matrix by selecting Calculate from the interference matrix context menu.
14.3.1.1.2
Importing and Exporting Interference Matrices You can import interference matrices from external sources, such as the OAM, in Atoll from from TXT (text), CSV (comma separated value), and IM2 files. In the interference matrix file you want to import, the interference matrix entries must have the following syntax: The separator can be a tab, a comma, a semicolon, or space. If the interference matrix file being imported contains the same interfered-interferer pair more than once, Atoll keeps the last description of the pair. Atoll does not perform a validity check on the imported interference file; you must therefore ensure that the imported information is consistent with the current configuration. Furthermore, Atoll only imports interference matrices for active transmitters. To import an interference matrix: 1. Select the Network explorer. 2. Right-click the LTE Interference Matrices folder. The context menu appears. 3. Select Import. The Open dialogue appears. 4. Select the file containing the interference matrix and click Open. The table Import dialogue appears. For more information on importing table data, see "Importing Tables from Text Files" on page 82. To export an interference matrix: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the LTE Interference Matrices folder. 3. Right-click the interference matrix you want to export. The context menu appears. 4. Select Export. The Export dialogue appears. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80.
14.3.1.1.3
Viewing and Editing Interference Matrices Interference matrices store co- and adjacent channel interference probabilities for each interfered and interfering cell pair. To view or edit the contents of an interference matrix: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the LTE Interference Matrices folder. 3. Right-click the interference matrix whose contents you wish to view. The context menu appears. 4. Select Properties. The Interference Matrices Properties dialogue appears. 5. Click the Interference Matrices tab. The co- and adjacent channel interference probabilities are available in the form of a table for each interfered and interfering cell pair.
1518
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
You can edit the interference probabilities, add new interfered and interfering cell pairs and their probabilities, and copy interference probabilities from another source, such as the OAM, directly into this table. 6. Click OK, once you have viewed or edited the probabilities.
14.3.1.2 Neighbour Importance In Atoll, neighbour importance values are calculated by the automatic neighbour allocation process and can be used by the AFP for frequency and physical cell ID allocation. For information on configuring neighbour importance weighting, see "Configuring Importance Factors for Neighbours" on page 1506. For more information on calculating neighbour importance values, see "Calculating the Importance of Existing Neighbours" on page 1514. For more details on the calculation of neighbour importance values, see the Technical Reference Guide.
14.3.1.3 Resources Available for Allocation The AFP allocates resources from a pool of available resources. For automatic frequency planning, the available resources are defined by the channel numbers available in the frequency band assigned to any cell. In the frequency band properties, the first and last channel numbers define the range of available channel numbers in the band. Channel numbers within this range can be set as unavailable if they are listed in the excluded channels list. For more information, see "Defining Frequency Bands" on page 1587. For automatic physical cell ID planning, Atoll facilitates the management of physical cell IDs by letting you create domains, each containing groups of physical cell IDs. The procedure for managing physical cell IDs in an LTE document consists of the following steps: 1. Creating a physical cell ID domain, as explained in this section. 2. Creating groups, each containing a range of physical cell IDs, and assigning them to a domain, as explained in this section. 3. Assigning a physical cell ID domain to a cell or cells. If there is no physical cell ID domain, Atoll will consider all 504 possible physical cell IDs when assigning them automatically. To create a physical cell ID domain: 1. Select the Parameters explorer. 2. Click the Expand button (
) to expand the LTE Network Settings folder.
3. Click the Expand button (
) to expand the Physical Cell IDs folder.
4. Right-click Domains in the Physical Cell IDs folder. The context menu appears. 5. Select Open Table from the context menu. The Domains table appears. 6. In the row marked with the New Row icon (
), enter a Name for the new domain.
7. Click in another cell of the table to create the new domain and add a new blank row to the table. 8. Double-click the domain to which you want to add a group. The domain’s Properties dialogue appears. 9. Under Groups, enter the following information for each group you want to create. • • • • • •
Name: Enter a name for the new physical cell ID group. Min.: Enter the lowest available physical cell ID in this group’s range. Max: Enter the highest available physical cell ID in this group’s range. Step: Enter the separation interval between each physical cell ID. Excluded: Enter the physical cell ID in this range that you do not want to use. Extra: Enter any additional physical cell ID (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 physical cell IDs separated by either a comma, semi-colon, or a space. You can also enter a range of physical cell IDs separated by a hyphen. For example, entering, "1, 2, 3-5" means that the extra physical cell IDs are "1, 2, 3, 4, 5."
10. Click in another cell of the table to create the new group and add a new blank row to the table. The available resources can also be defined for all the cells globally in the AFP dialogue by selecting Custom for the Allocation domain, and entering the list of Excluded resources. For more information, see "Planning Physical Cell IDs" on page 1521.
14.3.1.4 Constraint Weights You can define the constraint weights for the AFP cost components that Atoll uses to evaluate possible frequency and physical cell ID plans.
1519
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
To configure the AFP constraint weights: 1. Select the Network explorer. 2. Right-click the Transmitters folder. The context menu appears. 3. Select AFP > Configure Constraint Weights from the context menu. The Constraint Weights dialogue appears. This dialogue enables you to define the relative weights of the cost components. The absolute values of the constraint weights are calculated by the AFP using these relative weights. For more information, see the Technical Reference Guide. 4. Click the Frequency Allocation tab. 5. On the Frequency Allocation tab, you can set the constraint weights for the Neighbours, Interference matrices, and Distance cost components. 6. Click the Physical Cell ID Allocation tab. 7. On the Physical Cell ID Allocation tab, you can set the constraint weights for the 1st order neighbours, 2nd order neighbours, Neighbours of a common cell, Interference matrices, and Distance cost components, as well as for the Physical cell ID constraint, PSS ID constraint, Same SSS ID per site constraint, and UL DMRS sequence group collision. •
• •
•
In 3GPP Multi-RAT documents, the constraint weight Neighbours of a common cell applies to LTE neighbours of a common LTE cell as well as to LTE neighbours of a common GSM transmitter or UMTS cell. You can move the slider all the way to the left to set the relative weight to 0 %. The constraint will no longer have any effect in the evaluation of the AFP cost. You can move the slider all the way to the right to set the relative weight to 100 %. The constraint will have the highest weight compared to the other constraints involved in the evaluation of the AFP cost. You can click the Reset button to set the weights to their default values.
8. Click OK.
14.3.2 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 in such a way 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. When allocating frequencies, the AFP can take into account interference matrices, reuse distance, and any constraints imposed by neighbours. To automatically allocate frequencies: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select AFP > Automatic Frequency Allocation. The Resource Allocation dialogue appears. 4. Under Allocate, select Frequencies to perform automatic frequency planning. 5. Under Relations, you can set the relations to take into account in automatic allocation. •
•
•
Interference matrices: Select this check box if you want the AFP to take interference matrices into account for the allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account, they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, imported, and edited in the Interference Matrices folder. For more information on interference matrices, see "Interference Matrices" on page 1517. Existing neighbours: Select this check box if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different frequencies to a cell and its neighbours. Atoll can only take neighbour relations into account if neighbours have already been allocated. For information on allocating neighbours, see "Planning Neighbours" on page 1505. Reuse distance: Select this check box if you want the AFP to take relations based on distance into account for the allocation. You can enter a Default reuse distance within which two cells must not have the same channel assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the size of the cell’s coverage area and the network density around the cell. If defined, a cell-specific reuse distance is used instead of default the value entered here.
6. Under Results, Atoll displays the Total cost of the current frequency allocation taking into account the parameters set in step 5. You can modify the parameters and click Update cost to see the change in the total cost.
1520
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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 allocation plan of the cell. Physical cell ID status: The value of the Physical cell ID status of the cell.
8. Click Commit. The proposed frequency plan is assigned to the cells of the network. When you allocate frequencies to a large number of cells, it is easiest to let Atoll allocate them automatically. However, if you want to assign a frequency to one cell or to modify it, you can do it by accessing the properties of the cell. To allocate the frequency to a cell manually: 1. On the map or in the LTE Transmitters folder in the Network explorer, right-click the transmitter to whose cell you want to allocate the frequency. The context menu appears. 2. Select Properties from the context menu. The transmitter’s Properties dialogue appears. 3. Select the Cells tab. 4. Select a Frequency band and Channel number for the cell. 5. Set the Channel allocation status to Locked if you want to lock the frequency that you assigned. 6. Click OK.
14.3.3 Planning Physical Cell IDs In LTE, 504 physical cell IDs are available, numbered from 0 to 503. There are as many pseudo-random sequences defined in the 3GPP specifications. Physical cell IDs are grouped into 168 unique cell ID groups (called SSS IDs in Atoll), with each group containing 3 unique identities (called PSS IDs in Atoll). An SSS ID is thus uniquely defined by a number in the range of 0 to 167, and a PSS ID is defined by a number in the range of 0 to 2. Each cell’s reference signals carry a pseudo-random sequence corresponding to the physical cell ID of the cell. The SSS and PSS are transmitted over the centre six frequency blocks independently of the channel bandwidths used by cells. Mobiles synchronise their transmission and reception frequency and time by first registering the PSS. Once the PSS ID of the cell is known, mobiles register the SSS of the cell in order to obtain the SSS ID. The combination of these two IDs gives the physical cell ID and the associated pseudo-random sequence that is transmitted over the downlink reference signals. Once the mobile has the physical cell ID and the associated pseudo-random sequence, the cell is recognised by the mobile based on the received reference signals. Channel quality measurements are also made on the reference signals. Because the cell search and selection depend on the physical cell IDs of the cells, these must be correctly allocated to cells in order to avoid unnecessary problems in cell recognition and selection. Atoll facilitates the management of physical cell IDs by letting you create groups of physical cell IDs and domains, where each domain is a defined set of groups. For more information, see "Resources Available for Allocation" on page 1519. You can assign physical cell IDs manually or automatically to any cell in the network. Once allocation is completed, you can audit the physical cell IDs, view physical cell ID reuse on the map, and make an analysis of physical cell ID distribution. Atoll can automatically assign physical cell IDs to the cells taking into account the selected SSS ID allocation strategy (free or same per site), allowed allocation domain, interference matrices, reuse distance, and any constraints imposed by neighbours. To automatically allocate physical cell IDs: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select AFP > Automatic Physical Cell ID Allocation. The Resource Allocation dialogue appears. 4. Under Allocate, select Physical Cell IDs to allocate physical cell IDs to cells automatically.
1521
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
5. Select the Allocation domain. You can choose Per cell to allocate physical cell IDs from the physical cell ID domains defined per cell, you can choose to allocate from the Entire (0-503) domain, or you can choose Custom and enter the Excluded resources to exclude some physical cell IDs from the allocation. You can enter non-consecutive physical cell IDs separated with a comma, or you can enter a range of physical cell IDs separating the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5"). 6. Under Allocation strategies, you can select: •
•
SSS ID allocation: Select Same per site if you want the AFP to allocate the same SSS ID to all the cells of a site. If allocating the same SSS ID to cells of a site causes collisions between physical cell IDs, the constraint of allocating the same SSS ID per site can be broken. Select Free if you want the AFP to ignore the SSS ID collisions. With free allocation, the SSS ID will not necessarily be the same for all the cells of a site. Uniform distribution: Select Strict if you want the AFP to distribute the physical cell ID uniformly. Select Inactive if a non-uniform distribution is acceptable.
7. Under Relations, you can set the relations to take into account in automatic allocation. •
•
Interference matrices: Select this check box if you want the AFP to take interference matrices into account for the allocation, and select an interference matrix from the list. For Atoll to take interference matrices into account, they must be available in the Interference Matrices folder in the Network explorer. Interference matrices can be calculated, imported, and edited in the Interference Matrices folder. For more information on interference matrices, see "Interference Matrices" on page 1517. Existing neighbours: Select this check box if you want the AFP to take neighbour relations into account for the allocation. The AFP will try to allocate different physical cell IDs to a cell and its neighbours, and to the neighbours of a common cell. In 3GPP Multi-RAT documents, the AFP will also try to allocate different physical cell IDs to LTE cells that are neighbours of a common GSM transmitter or UMTS cell. The AFP can take neighbours into account only if neighbours have already been allocated. If you want the AFP to take both first and second order neighbours into account, you must set an option in the atoll.ini file (see the Administrator Manual).
•
Reuse distance: Select this check box if you want the AFP to take relations based on distance into account for the allocation. You can enter a Default reuse distance within which two cells must not have the same physical cell ID assigned. However, it is highly recommended to define a reuse distance for each individual cell depending on the size of the cell’s coverage area and the network density around the cell. If defined, a cell-specific reuse distance is used instead of default the value entered here. A macro that automatically calculates a reuse distance for each cell can be provided upon request.
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 Update 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 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. Physical cell ID status: The value of the Physical cell ID status of the cell. Physical cell ID domain: The physical cell ID domain of the cell.
10. Click Commit. The proposed physical cell ID plan is assigned to the cells of the network. When you allocate physical cell IDs to a large number of cells, it is easiest to let Atoll allocate them automatically. However, if you want to assign a physical cell ID to one cell or to modify it, you can do it by accessing the properties of the cell. To allocate a physical cell ID to an LTE cell manually: 1. On the map or in the LTE Transmitters folder in the Network explorer, right-click the transmitter to whose cell you want to allocate a physical cell ID. The context menu appears. 2. Select Properties from the context menu. The transmitter’s Properties dialogue appears.
1522
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
3. Select the Cells tab. 4. Enter a Physical cell ID in the cell’s 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.
14.3.4 Displaying and Analysing the AFP Results You can display and analyse AFP results in several ways: • • • • • •
"Using the Find on Map Tool to Display AFP Results" on page 1523. "Displaying AFP Results Using Transmitter Display Settings" on page 1524. "Grouping Transmitters by Channels or Physical Cell IDs" on page 1524. "Analysing the Frequency Allocation Using Coverage Predictions" on page 1525. "Checking the Consistency of the Physical Cell ID Plan" on page 1525. "Displaying the Physical Cell ID Allocation Histogram" on page 1525.
14.3.4.1 Using the Find on Map Tool to Display AFP Results In Atoll, you can search for frequency bands, channel numbers, physical cell IDs, PSS IDs, and SSS IDs, using Find on Map. If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results displayed by transmitter, the search results will be displayed by transmitter coverage. The current allocation plan and any potential problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction by Transmitter" on page 1474. To find a frequency band using Find on Map: 1. Select Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "LTE Channel." 3. From the Band list, select a frequency band. 4. From the Channel list, select "All." 5. Click Search. Transmitters whose cells use the selected frequency band are displayed in red in the map window and are listed under Results in the Find on Map window. Transmitters with cells using other frequency bands are displayed in grey in the map window. To restore the initial transmitter colours, click the Reset display button in the Find on Map window. To find a channel number using Find on Map: 1. Select Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "LTE Channel." 3. From the Band list, select a frequency band. 4. From the Channel list, select the channel number. By default, Find on Map displays only co-channel transmitter cells. If you want adjacent channels to be displayed as well, select the Adjacent channels check box. 5. Click Search. Transmitters whose cells use the selected frequency band and channel number are displayed in red. Transmitters with cells using two adjacent channel numbers in the same frequency band (i.e., a channel higher and a channel lower) are displayed in yellow. Transmitters with cells using a lower adjacent channel number in the same frequency band are displayed in green. Transmitters with cells using a higher adjacent channel number in the same frequency band are displayed in blue. All other transmitters are displayed as grey lines. If you cleared the Adjacent channels check box, transmitters with cells using the same channel number are displayed in red, and all others, including transmitters with adjacent channels, are displayed as grey lines. To restore the initial transmitter colours, click the Reset display button in the Find on Map window. By including the frequency band and channel number of each cell in the transmitter label, the search results will be easier to understand. For information on defining the label, see "Defining the Object Type Label" on page 46.
1523
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
To find a physical cell ID, PSS ID, or SSS ID using Find on Map: 1. Click Tools > Find on Map. The Find on Map window appears. 2. From the Find list, select "Physical Cell ID." 3. Select what you what you want to search for: • • •
Physical cell ID: If you want to find a physical cell ID, select Physical cell ID and select the physical cell ID from the list. PSS ID: If you want to find a PSS ID, select PSS ID and select the PSS ID from the list: "All," "0," "1," or "2." SSS ID: If you want to find an SSS ID, select SSS ID and select the SSS ID from the list.
4. Click Search. When you select a physical cell ID or an SSS ID, transmitters with cells matching the search criteria are displayed in red. Transmitters that do not match the search criteria are displayed as grey lines. When you select a specific PSS ID, transmitters whose cells use the selected ID are displayed in red. Transmitters with cells that use other IDs are displayed as grey lines. When you choose to search for all PSS IDs, transmitters whose first cells use ID 0 are displayed in red, transmitters whose first cells use ID 1 are displayed in yellow, and transmitters whose first cells use ID 2 are displayed in green. To restore the initial transmitter colours, click the Reset display button in the Search Tool window. •
•
By including the physical cell ID of each cell in the transmitter label, the search results will be easier to understand. For information on defining the label, see "Defining the Object Type Label" on page 46. Transmitters with more than one cell might use different PSS IDs in different cells. Therefore, the search for all PSS IDs is only valid for single-cell transmitters.
14.3.4.2 Displaying AFP Results Using Transmitter Display Settings You can display the frequency and physical cell ID allocation on transmitters by using the transmitters’ display settings. To display the frequency allocation on the map: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. 5. Select "Discrete values" as the Display type and "Cells: Channel number" as the Field. 6. Click OK. Transmitters will be displayed by channel number. You can also display the frequency band and channel number in the transmitter label or tip text by selecting "Cells: Frequency band" and "Cells: Channel number" from the Label or Tip Text Field Definition dialogue. To display physical cell ID allocation on the map: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Click the Display tab. 5. Select "Discrete values" as the Display type and "Cells: Physical cell ID" as the Field. 6. Click OK. Transmitters will be displayed by physical cell ID. You can also display the physical cell ID in the transmitter label or tip text by selecting "Cells: Physical cell ID" from the Label or Tip Text Field Definition dialogue. For information on display options, see "Display Properties of Objects" on page 43.
14.3.4.3 Grouping Transmitters by Channels or Physical Cell IDs You can group transmitters in the Network explorer by their frequency bands, channel numbers, or physical cell IDs. To group transmitters by frequency bands, channel numbers, or physical cell IDs: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears.
1524
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
3. Select Properties from the context menu. The Properties dialogue appears. 4. On the General tab, click Group by. The Group dialogue appears. 5. Under Available fields, scroll down to the Cell section. 6. Select the parameter you want to group transmitters by: • • •
Frequency band Channel number Physical cell ID
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 ters will be grouped.
. The selected parameter is removed from the list of parameters on which the transmit-
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
to move it up to the desired position.
b. Select a parameter and click
to move it down to the desired position.
10. Click OK to save your changes and close the Group dialogue.
14.3.4.4 Analysing the Frequency Allocation Using Coverage Predictions You can create and compare reference signal C/(I+N) coverage predictions before and after the automatic frequency allocation in order to analyse and compare the improvements brought about by the AFP. For more information on creating reference signal C/(I+N) coverage predictions, see "Making a Coverage by C/(I+N) Level" on page 1492. For more information on comparing two coverage predictions, see "Comparing Coverage Predictions: Examples" on page 1483.
14.3.4.5 Checking the Consistency of the Physical Cell ID Plan Once you have completed allocating physical cell IDs, you can verify whether the allocated physical cell IDs respect the specified constraints and relations by performing an audit of the plan. The physical cell ID audit also enables you to check for inconsistencies if you have made some manual changes to the allocation plan. To perform an audit of the allocation plan: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select AFP > Physical Cell ID Audit. The Physical Cell ID Audit dialogue appears. 4. In the Physical Cell ID Audit dialogue, select the allocation criteria that you want to verify: •
•
•
•
Distance: If you select the Distance check box, Atoll will check for and list cells that do not respect the reuse distance defined in their properties. For cells that do not have a reuse distance defined in their properties, the value entered in this dialogue will be used for the audit. Neighbours: If you select the Neighbours check box, Atoll will check that no cell has the same physical cell ID as any of its neighbours, and that no two neighbours of a cell have the same physical cell ID. The report will list any cell that has the same physical cell ID as one of its neighbours. Same SSS ID at a site: If you select the Same SSS ID at a site check box, Atoll will check for and list base stations that do not match the criterion, i.e., base stations whose cells have physical cell IDs that correspond to different SSS IDs. Per-cell domain compliance: If you select the Per-cell domain compliance check box, Atoll will check if allocated physical cell IDs belong to domains assigned to the cells. The report will list any cells with physical cell IDs that do not belong to domains assigned to the cell.
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.
14.3.4.6 Displaying the Physical Cell ID Allocation Histogram You can use a histogram to analyse the use of allocated physical cell IDs in a network. The histogram represents the physical cell IDs as a function of the frequency of their use.
1525
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
To display the physical cell ID histogram: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select AFP > Physical Cell ID Distribution. The Distribution Histograms dialogue appears. Each bar represents a physical cell ID, its height depending on the frequency of its use. 4. Move the pointer over the histogram to display the frequency of use of each physical cell ID. The results are highlighted simultaneously in the Zoom on selected values list. You can zoom in on values by clicking and dragging in the Zoom on selected values list. Atoll will zoom in on the selected values.
14.4 Studying Network Capacity Interference is the major limiting factor in the performance of LTE networks. It has been recognised as the major bottleneck in network capacity and is often responsible for poor performance. Frequency reuse means that in a given coverage area there are several cells that use a given set of frequencies. The cells that use the same frequency are called co-channel cells, and the interference from users with the same channel in the other co-channel cells is called co-channel interference. Unlike thermal noise which can be overcome by increasing the signal-to-noise ratio (SNR), co-channel interference cannot be countered by simply increasing the carrier power of a transmitter. This is because an increase in carrier transmission power will increase the interference to neighbouring co-channel cells. To reduce co-channel interference, co-channel cells must be physically separated sufficiently by a distance, called the reuse distance. For a network with a limited number of frequency channels, a large reuse distance can guarantee a high QoS for the system, but the capacity will be decreased. Another type of interference in LTE networks is adjacent channel interference. Adjacent channel interference results from imperfect receiver filters which allow nearby frequencies to interfere with the used frequency channel. Adjacent channel interference can be minimised through careful filtering and channel assignment. In Atoll, a simulation is based on a realistic distribution of users at a given point in time. The distribution of users at a given moment is referred to as a snapshot. Based on this snapshot, Atoll calculates various network parameters such as the downlink and uplink traffic loads, the uplink noise rise, the user throughputs, etc. Simulations are calculated in an iterative fashion. When several simulations are performed at the same time using the same traffic information, the distribution of users will be different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snapshot to another. To create snapshots, services and users must be modelled. As well, certain traffic information in the form of traffic maps or subscriber lists must be provided. Once services and users have been modelled and traffic maps and subscriber lists have been created, you can make simulations of the network traffic. In this section, the following are explained: • • • • • •
"Defining Multi-service Traffic Data" on page 1526. "Creating a Traffic Map" on page 1527. "Exporting a Traffic Map" on page 1536. "Working with a Subscriber Database" on page 1536. "Calculating and Displaying Traffic Simulations" on page 1541. "Making Coverage Predictions Using Simulation Results" on page 1555.
14.4.1 Defining Multi-service Traffic Data The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of the parameters of network use, in terms of services, users, and equipment used. The following services and users are modelled in Atoll in order to create simulations: •
•
• •
1526
LTE radio bearers: Radio bearers are used by the network for carrying information. The LTE Radio Bearer table lists all the available radio bearers. You can create new radio bearers and modify existing ones by using the LTE Radio Bearer table. For information on defining radio bearers, see "Defining LTE Radio Bearers" on page 1591. 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 1487. Mobility types: In LTE, information about receiver mobility is important to determine the user’s radio conditions and throughputs. For information on modelling mobility types, see "Modelling Mobility Types" on page 1488. Terminals: In LTE, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a car’s on-board navigation device. For information on modelling terminals, see "Modelling Terminals" on page 1488.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
14.4.2 Creating a Traffic Map The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use them. Atollprovides three types of traffic maps for LTE projects. • • •
Sector traffic map User profile traffic map User density traffic map (number of users per km2)
These maps can be used for different types of traffic data sources as follows: •
Sector traffic maps can be used if you have live traffic data from the OMC (Operation and Maintenance Centre). The OMC (Operations and Maintenance Centre) collects data from all cells in a network. This includes, for example, the number of users or the throughput in each cell and the traffic characteristics related to different services. Traffic is spread over the best server coverage area of each transmitter and each coverage area is assigned either the throughputs in the uplink and in the downlink or the number of users per activity status or the total number of users (all activity statuses). For more information, see "Creating a Sector Traffic Map" on page 1527.
•
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 1530, "Importing a User Profile Environment Based Traffic Map" on page 1532 and "Creating a User Profile Environment Based Traffic Map" on page 1532.
•
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 "Creating User Density Traffic Maps (No. Users/km2)" on page 1533, "Importing a User Density Traffic Map" on page 1533, "Converting 2G Network Traffic" on page 1535 and "Exporting Cumulated Traffic" on page 1535
14.4.2.1 Creating a Sector Traffic Map This section explains how to create a sector traffic map in Atoll to model traffic. You can enter either the throughput demands in the uplink and in the downlink or the number of users per activity status or the total number of users (all activity statuses). You must have a coverage prediction by transmitter to create this traffic map. If you do not already have a coverage prediction by transmitter in your document, you must create and calculate it first. For more information, see "Making a Coverage Prediction by Transmitter" on page 1474. To create a sector traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select Sector traffic map. 5. Select the type of traffic information you want to input. You can choose either 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. You can also import a traffic map from a file by clicking the Import button. You can import AGD (Atoll Geographic Data) format files that you have exported from another Atoll document. 7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter. 8. Enter the data required in the Sector Traffic 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 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.
1527
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 82. 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 Maps folder. You can modify the sector traffic map after it has been created. To modify the sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map based on live data that you want to update. The context menu appears. 4. Select Properties from the context menu. The Sector Traffic Map dialogue appears. 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 modified values. You can update the information, throughput demands and the number of users, on the map afterwards. You must first recalculate the coverage prediction by transmitter. For more information, see "Making a Coverage Prediction by Transmitter" on page 1474. Once you have recalculated the coverage prediction, you can update the traffic map. To update the traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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 1535.
14.4.2.2 Creating a User Profile Traffic Map The marketing department can provide information which can be used to create traffic maps. This information describes the behaviour of different types of users. In other words, it describes which type of user accesses which services and for how long. There may also be information about the type of terminal devices they use to access different services. In Atoll, this type of data can be used to create traffic maps based on user profiles and environments.
1528
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
A user profile models the behaviour of different user categories. Each user profile is defined by a list of services which are in turn defined by the terminal used, the calls per hour, and duration (for calls of the type "voice") or uplink and downlink volume (for calls of the type "data"). Environment classes are used to describe the distribution of users on a map. An environment class describes its environment using a list of user profiles, each with an associated mobility type and a given density (i.e., the number of users with the same profile per km²). The sections "Importing a User Profile Traffic Map" on page 1530, "Importing a User Profile Environment Based Traffic Map" on page 1532 and "Creating a User Profile Environment Based Traffic Map" on page 1532 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 1529. "Modelling Environments" on page 1529.
Modelling User Profiles You can model variations in user behaviour by creating different profiles for different times of the day or for different circumstances. For example, a user might be considered a business user during the day, with video conferencing and voice, but no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and web browsing. To create or modify a user profile: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic Parameters folder. 3. Right-click the User Profiles folder. The context menu appears. 4. Select New from the context menu. The User Profiles: New Element Properties dialogue appears. 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 1487. Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 1488. 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 webbrowsing service, a session starts when the user opens his browsing application and ends when he quits the browsing application. Between these two events, the user might be downloading web pages and other times he may not be using the application, or he might be browsing local files, but the session is still considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and not by the time. In order for all the services defined for a user profile to be taken into account during traffic scenario elaboration, the sum of activity probabilities must be lower than 1.
• • •
Duration (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
1529
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 environment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Traffic 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. 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 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
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
For example: An area of 10 km² with a 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 (as defined in the clutter class properties) will be added to the indoor users path loss. 11. Click OK.
14.4.2.2.1
Importing a User Profile Traffic Map User profile traffic maps are composed of vectors (either points with a number of subscribers, lines with a number of subscribers⁄km, or polygons with a number of subscribers⁄km²) with a user profile, mobility type, and traffic density assigned to each vector. To create a user profile traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile densities from the list. 6. Click the Import button. The Open dialogue appears.
1530
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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 1532. 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 map’s properties dialogue appears. 11. Select the Traffic tab (see Figure 14.50). 12. Under Traffic fields, you can specify the user profiles to be considered, their mobility type (km⁄h), and their density. If the file you are 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 14.50: Traffic map properties dialogue - Traffic tab Define each of the following: •
•
•
User profile: If you want to import user profile information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a user profile from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the user profile in the Choice column. Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a mobility type from the Traffic Parameters folder in the Parameters explorer, under Defined, select "By value" and select the mobility type in the Choice column. Density: If you want to import density information from the file, under Defined, select "By field" and select the source field from the Choice column. If you want to assign a density, under Defined, select "By value" and enter a density in the Choice column for the combination of user profile and mobility type. In this context, the term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kilometre for polygons, the number of subscribers per kilometre in case of lines, and the number of subscribers when the map consists of points. When you import user profile or mobility information from the file, the values in the file must be exactly the same as the corresponding names in the Traffic Parameters folder in the Parameters explorer. If the imported user profile or mobility does not match, Atoll will display a warning.
13. Under Clutter distribution, enter a weight for each class that will be used to calculate a user distribution.
1531
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
The user distribution is calculated using the following equation: Wk × Sk N k = N Area × -------------------------Wi × Si
i
where: Nk
=
N Area =
Number of users in the clutter k Number of users in the zone Area
Wk
=
Weight of clutter k
Sk
=
Surface area of clutter k (in square km)
14. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss. 15. Click OK to finish importing the traffic map.
14.4.2.2.2
Importing a User Profile Environment Based Traffic Map Environment classes describe the distribution of user profiles. To create a user profile environment based traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list. 6. Click the Import button. The Open dialogue appears. You can also create a traffic map manually in Atoll by clicking the Create button in the New Traffic Map dialogue. For information, see "Creating a User Profile Environment Based Traffic Map" on page 1532. 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 map’s 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 Traffic Parameters in the Parameters explorer. For more information, see "Modelling Environments" on page 1529. 13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects" on page 43. 14. Click OK.
14.4.2.2.3
Creating a User Profile Environment Based Traffic Map Atoll enables you to create a user profile environment traffic map based on by drawing it in the map window. To draw a traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User profile traffic map. 5. Select User profile environments from the list.
1532
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
6. Click Create. The Environment Map Editor toolbar appears (see Figure 14.51).
Draw Map
Delete Map
Figure 14.51: 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.
14.4.2.2.4
Displaying Statistics on a User Profile Environment Traffic Map You can display the statistics of a user profile environment traffic map. Atoll provides absolute (surface) and relative (percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone defined, statistics are determined for the computation zone. To display traffic statistics of a user profile environment traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the user profile environment traffic map whose statistics you want to display. The context menu appears. 4. Select Statistics from the context menu. The Statistics window appears. The Statistics window lists the surface (Si in km²) and the percentage of surface (% of i) for each environment class "i" S
i - × 100 within the focus zone. The percentage of surface is given by: % of i = -------------
Sk k
You can print the statistics by clicking the Print button. 5. Click Close. If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per clutter class.
14.4.2.3 Creating User Density Traffic Maps (No. Users/km2) User density traffic maps can be based on population statistics (user densities can be calculated from the density of inhabitants) or on 2G traffic statistics. User density traffic maps provide the number of connected users per unit surface, i.e., the density of users, as input. This can be either the density of users per activity status or the total density of users (all activity statuses). In this section, the following ways of creating a user density traffic map are explained: • •
"Importing a User Density Traffic Map" on page 1533 "Creating a User Density Traffic Map" on page 1534.
User density traffic maps can be created from sector traffic maps 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 1535.
14.4.2.3.1
Importing a User Density Traffic Map The user density traffic map defines the density of users per pixel. For a traffic density of X users per km², Atoll will distribute x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a mobility type, a service, and percentage of indoor users as defined in the Traffic tab of the traffic map’s properties dialogue. You can create a number of user density traffic maps for different combinations of terminals, mobility types, and services. You can add vector layers to the map and draw regions with different traffic densities. To create a user density traffic map: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears.
1533
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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. 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 1532. 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 map’s 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 percentage must equal 100. 13. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must equal 100. 14. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal 100. 15. 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. 16. Click OK. Atoll creates the traffic map in the Traffic Maps folder.
14.4.2.3.2
Creating a User Density Traffic Map Atollenables you to create a user density traffic map by drawing it in the map window. To draw a traffic map per user density: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select New Map from the context menu. The New Traffic Map dialogue appears. 4. Select User density traffic map (Number of users per km2). 5. Select the type of traffic information you want to enter. You can choose from: • • • • •
All activity statuses: Select All activity statuses if the map you are importing provides a density of users with any activity status. Active in uplink: Select Active in uplink if the map you are importing provides a density of users active in the uplink only. Active in downlink: Select Active in downlink if the map you are importing provides a density of users active in the downlink only. Active in uplink and downlink: Select Active in uplink and downlink if the map you are importing provides a density of users with both uplink and downlink activity. Inactive: Select Inactive if the map you are importing provides a density of inactive users.
6. Click the Create button. The traffic map’s 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 percentages must equal 100.
1534
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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 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 Maps 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 Editor toolbar to draw contours. For more information on editing contours, see "Editing Polygons, Lines, and Points" on page 61. 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.
14.4.2.3.3
Creating User Density Traffic Maps from Sector Traffic Maps You can create user density traffic maps from sector traffic maps. User density traffic maps created from sector traffic maps extract and display the exact number of users per unit of surface, i.e., the density of users, taking into account any clutter weighting defined for the sector traffic maps. To create user density traffic maps from a sector traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps 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 there are 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.
14.4.2.4 Converting 2G Network Traffic Atollcan cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the number of users per km² for a particular service of a particular type, i.e., data or voice. This allows you to export your 2G network packet and circuit service traffic, and then import these maps as traffic maps per user density into your LTE document. These maps can then be used in traffic simulations like any other type of map. For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 1535, and for information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1533. To import a 2G traffic map into an LTE document: 1. Create a live data traffic map in your 2G document for each type of service, i.e., one map for packet-switched and one for circuit-switched services. For more information on creating sector traffic maps, see "Creating a Sector Traffic Map" on page 438. 2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see "Exporting Cumulated Traffic" on page 1535. 3. Import the traffic exported in step 2 to your LTE document as a user density traffic map. For more information on importing user density traffic maps, see "Importing a User Density Traffic Map" on page 1533.
14.4.2.5 Exporting Cumulated Traffic Atoll allows you to export the cumulated traffic of selected traffic maps in the form of user density traffic maps. During export, Atoll converts any traffic map to user densities. The cumulated traffic is exported in 32-bit BIL, ArcView© Grid, or Vertical
1535
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The exported traffic map can then be imported as a user density traffic map. To export the cumulated traffic: 1. Select the Geo explorer. 2. Right-click the Traffic Maps folder. The context menu appears. 3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears. 4. Enter a file name and select the file format. 5. Click Save. The Export dialogue appears. 6. Under Region, select the area to export: • •
The entire project area: This option allows you to export the cumulated traffic over the entire project. The computation zone: This option allows you to export the cumulated traffic contained by a rectangle encompassing the computation zone.
7. Define a Resolution in metres. The resolution must be an integer and the minimum resolution allowed is 1. 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. 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.
14.4.3 Exporting a Traffic Map To export a traffic map: 1. Select the Geo explorer. 2. Click the Expand button ( ) to expand the Traffic Maps folder. 3. Right-click the traffic map you want to export. The context menu appears. 4. Select Save As from the context menu. The Save As dialogue appears. 5. Enter a file name and select a file format for the traffic map. 6. Click Save. If you are exporting a raster traffic map, you have to define: •
The Export region: • • •
•
Entire project area: Saves the entire traffic map. Only pending changes: Saves only the modifications made to the map. Computation zone: Saves only the part of the traffic map inside the computation zone.
An export Resolution.
14.4.4 Working with a Subscriber Database The LTE module includes a subscriber database for modelling fixed user distributions in a network. The subscriber database consists of subscriber lists. You can create subscriber lists in Atoll by adding subscribers to the list using the mouse, or by copy-
1536
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
ing data from any other source such as a spreadsheet. You can also directly import subscriber lists in Atoll from text (TXT) and comma separated value (CSV) files. Atoll can allocate reference or serving base stations (cells) to subscribers. You can also have the subscriber antenna oriented towards its serving cell to decrease interference. The automatic server allocation performs a number of calculations on the subscriber locations. In this section, the following are explained: • •
"Creating a Subscriber List" on page 1537. "Performing Calculations on Subscriber lists" on page 1540.
14.4.4.1 Creating a Subscriber List You create subscribers in Atoll in two steps. First, you create a subscriber list, and then you add subscribers to the list. You can add subscribers to the list directly on the map using the mouse. For more information, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 1539. If you need to create a large number of subscribers, Atoll allows you to import them from another Atoll document or from an external source. For more information, see "Importing a Subscriber List" on page 1540. To create a subscriber list: 1. Select the Network explorer. 2. Right-click the Subscribers folder. The context menu appears. 3. Select New List from the context menu. The Subscriber List N Properties dialogue appears (see Figure 14.52), where N is an incremental digit.
Figure 14.52: 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 93. Filter: Click the Filter button to filter the data in the subscriber list. For information on filtering, see "Filtering Data" on page 95.
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 43. 6. Click OK. Atoll creates a new subscriber list. The following parameters are available by default in a new subscriber list: • • •
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 subscriber’s location is always fixed. Height: The altitude of the subscriber antenna with respect to the ground (DTM).
1537
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• •
•
• • • • •
•
• •
•
• • • • • • • • • • • • • • • • • • •
1538
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 1529. Terminal: The default terminal is the user equipment with an antenna, reception 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. Clutter: The name of the clutter class where the subscriber is located. This is a non-editable field whose contents are automatically updated. Indoor: This field indicates whether the subscriber is indoor or outdoor. Best server: 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 highest layer is selected as the reference cell. Distance: The distance of the subscriber from its serving base station. This is a non-editable field whose contents are automatically updated. 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. 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. RSRP (RS EPRE) (DL) (dBm): The RSRP (received reference signal energy per resource element) received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. RSSI (DL) (dBm): The RSSI received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. RSRQ (DL) (dB): The RSRQ (reference signal received quality) at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. Received RS 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 PBCH power (DL) (dBm): The PBCH signal level received at the subscriber location in the downlink. This value is calculated by Atoll during calculations on subscriber lists. Received PDCCH power (DL) (dBm): The PDCCH 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. RS 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. PBCH C/(I+N) (DL) (dB): The PBCH C/(I+N) at the subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists. PDCCH C/(I+N) (DL) (dB): The PDCCH 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. RS total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the subscriber location in the downlink on the reference signals. This value is generated by Atoll during the 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. PDCCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the subscriber location in the downlink on the PDCCH. This value is generated by Atoll during the calculations on subscriber lists. PDSCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the subscriber location in the downlink on the PDSCH. 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.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
•
• •
•
•
• •
• •
• • • •
•
BLER (DL): The Block Error Rate read from the subscriber’s terminal type’s reception 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 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. 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. 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 cell’s reception 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 subscriber’s 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 1540. For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations on Subscriber lists" on page 1540. 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 1539. You can open the subscriber list table containing all the subscribers and their parameters. To open the subscriber list table: 1. Select the Network explorer. 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 69.
14.4.4.1.1
Adding Subscribers to a Subscriber List Using the Mouse You can use the mouse to add subscribers to an existing subscriber list. Atoll applies the default parameters defined in the Table tab of the subscriber list Properties dialogue to all the subscribers you add to the list. For more information on the Table tab, see "Creating a Subscriber List" on page 1537. To add subscribers to a subscriber list using the mouse: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Subscribers folder. 3. Right-click the subscriber list to which you want to add subscribers. The context menu appears. 4. Select Add Subscribers from the context menu. The pointer changes to subscriber addition mode (
).
1539
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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.
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 49.
14.4.4.1.2
Importing a Subscriber List You can also import subscriber lists from text files (TXT) or comma separated value files (CSV), including Microsoft Excel files exported in CSV format. To import a subscriber list: 1. Select the Network explorer. 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 more information on importing table data, see "Importing Tables from Text Files" on page 82. You can also export subscriber lists. For information on exporting table data, see "Exporting Tables to Text Files and Spreadsheets" on page 80.
14.4.4.1.3
Selecting the Columns to Display in the Subscriber Lists From the columns listed in "Creating a Subscriber List" on page 1537, you can select the ones to display in the Properties dialogue of the Subscribers folder. To select the columns to display in subscriber lists: 1. Select the Network explorer. 2. Right-click the Subscribers folder. The context menu appears. 3. Select Properties from the context menu. The Subscribers Properties dialogue appears. 4. Click the Column Selection tab. 5. Under Configuration, you can Open an existing configuration of the columns to display, Save the current settings in an existing configuration file, or Save as a new configuration file. 6. Select the columns you want to display: a. Select the column in the Available columns list and click b. Select a column in the Columns to display list and click
to move it to the Columns to display list. to move it to the Available columns list.
c. Change the order of the columns by selecting a column and clicking
or
to move it up or down in the list.
7. Click OK to close the Subscribers Properties dialogue.
14.4.4.2 Performing Calculations on Subscriber lists You can perform calculations on subscriber lists without having to carry out simulations first. Atoll does not base calculations performed on subscriber lists on the path loss matrices calculated for transmitters. This is because the path loss matrices are calculated for a given receiver height (1.5 m by default) defined in the Properties dialogue of the Predictions folder, but each subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates the path loss, received power, and other output for each subscriber when you perform calculations based on subscribers. Atoll can perform an automatic server allocation for all the subscribers in a list. To perform calculations on a subscriber list: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Subscribers folder.
1540
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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 1537.
14.4.5 Calculating and Displaying Traffic Simulations To plan and optimise LTE networks, you will need to study the network capacity and to study the network coverage taking into account realistic user distribution and traffic demand scenarios. In Atoll, a simulation corresponds to a given distribution of LTE users. It is a snapshot of an LTE network. The principal outputs of a simulation are a geographic user distribution with a certain traffic demand, resources allocated to each user of this distribution, and cell loads. You can create groups for one or more simulations and carry out as many simulations as required. A new simulation for each different traffic scenario can help visualise the network’s response to different traffic demands. Each user distribution (each simulation generates a new user distribution) is a Poisson distribution of the number of active users. Therefore, each simulation may have a varying number of users accessing the network. 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 1541. "Creating Simulations" on page 1543. "Displaying the Traffic Distribution on the Map" on page 1544. "Displaying the Results of a Single Simulation" on page 1547. "Updating Cell Load Values With Simulation Results" on page 1554. "Estimating a Traffic Increase" on page 1555.
14.4.5.1 LTE Traffic Simulation Algorithm Figure 14.53 shows the LTE simulation algorithm. The simulation process in LTE consists of the following steps: 1. Mobile Generation and Distribution Simulations require traffic data, such as traffic maps (raster, vector, or live traffic data) and subscriber lists. Atoll generates a user distribution for each simulation using a Monte Carlo algorithm. This user distribution is based on the traffic data input and is weighted by a Poisson distribution. Each mobile generated during the simulations is assigned a service, a mobility type, and a terminal according to the user profile assigned to it. A transmission status is determined according to the activity probabilities. The transmission status is an important output of the simulation as it has a direct impact on the next step of the simulation process, i.e., the radio resource management (RRM), and has an impact on the interference level in the network. The geographical location of each mobile is determined randomly for the mobiles generated based on the traffic data from traffic maps. The mobiles generated based on the traffic data from subscriber lists are located on the subscriber locations.
1541
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.53: 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 reference signal power. If more than one cell cover the mobile, the one with the highest 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. During uplink noise rise control, if the maximum uplink noise rise is higher than the actual noise rise for a cell, the maximum PUSCH C/(I+N) of its neighbour cells is increased by the difference. This allows the users served by the neighbour cells to transmit at higher powers, i.e., they are allowed to create more interference. If the maximum uplink noise rise is less than the actual noise rise for a cell, the maximum PUSCH C/(I+N) of its neighbour cells is decreased by the difference. This causes the users served by the neighbour cells to transmit at lower powers, i.e., they are forced to create less interference. This can also lead to an increase or decrease in the number of users served by the neighbouring cells in the uplink. 5. Radio Resource Management and Cell Load Calculation
1542
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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 cell’s 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.
14.4.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, noise rise 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. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears. 4. On the General tab of the dialogue, enter a Name for this simulation or group of simulations. 5. You can enter some Comments if you want. 6. 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 in the Network explorer. 7. 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 use the maximum uplink traffic load as defined in the properties for each cell, click the button ( ) beside the box and select Defined per cell.
8. Under Power control on the General tab, select the UL noise rise control check box if you want to activate the uplink noise rise control in the simulations. For more information on the uplink noise rise control, see the Technical Reference Guide. 9. 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.
1543
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 1527. 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. 10. On the Advanced tab, enter the following: •
Generator initialisation: Enter an integer as the generator initialisation value. If you enter "0," the default, the user and shadowing error distribution will be random. If you enter any other integer, the same user and shadowing error distribution will be used for any simulation using the same generator initialisation value. Using the same generated user and shadowing error distribution for several simulations can be useful when you want to compare the results of several simulations where only one parameter changes.
•
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.
11. Once you have defined the simulation, you can calculate it immediately or you can save it to calculate it later: • •
Calculate: Click Calculate to save the defined simulation and calculate it immediately. OK: Click OK to save the defined simulation without calculating it. You can calculate it later clicking the Calculate button (
) on the Radio Planning toolbar.
All simulations created at the same time are grouped together in a folder in the Network explorer. 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 1555.
14.4.5.3 Displaying the Traffic Distribution on the Map Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different parameters. You can, for example, display the traffic according to activity status, service, reference cell, or throughputs. You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or, you can select the display of the traffic distribution according to value intervals, and then select the parameter and the value intervals that are to be displayed. You can also define the colours of the icon and the icon itself. For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 43. In this section are the following examples of traffic distribution: • • • • • •
"Displaying the Traffic Distribution by Activity Status" on page 1545. "Displaying the Traffic Distribution by Connection Status" on page 1545. "Displaying the Traffic Distribution by Service" on page 1545. "Displaying the Traffic Distribution by Throughput" on page 1546. "Displaying the Traffic Distribution by Uplink Transmission Power" on page 1546. "Displaying Traffic Simulation Results Using Tip Text" on page 1547 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 Windows" on page 38.
1544
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
14.4.5.3.1
Displaying the Traffic Distribution by Activity Status In this example, the traffic distribution is displayed by the activity status. To display the traffic distribution by the activity status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Activity status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 14.54).
Figure 14.54: Displaying the traffic distribution by activity status
14.4.5.3.2
Displaying the Traffic Distribution by Connection Status In this example, the traffic distribution is displayed by the connection status. To display the traffic distribution by the connection status: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Connection status" as the Field. 5. Click OK. The traffic distribution is now displayed by activity status (see Figure 14.55).
Figure 14.55: Displaying the traffic distribution by connection status
14.4.5.3.3
Displaying the Traffic Distribution by Service In this example, the traffic distribution is displayed by service. To display the traffic distribution by service: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears.
1545
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Discrete values" as the Display type and "Service" as the Field. 5. Click OK. The traffic distribution is now displayed by service (see Figure 14.56).
Figure 14.56: Displaying the traffic distribution by service
14.4.5.3.4
Displaying the Traffic Distribution by Throughput In this example, the traffic distribution is displayed by throughput. To display the traffic distribution by throughput: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value intervals" as the Display type and one of the following throughput types as the Field: •
In the downlink: • Peak RLC, effective RLC, or application channel throughput • Peak RLC, effective RLC, or application cell capacity • Peak RLC, effective RLC, or application user throughput
•
In the uplink: • Peak RLC, effective RLC, or application channel throughput • Peak RLC, effective RLC, or application cell capacity • Peak RLC, effective RLC, or application allocated bandwidth throughput • Peak RLC, effective RLC, or application user throughput
5. Click OK. The traffic distribution is now displayed by throughput (see Figure 14.57).
Figure 14.57: Displaying the traffic distribution by throughput
14.4.5.3.5
Displaying the Traffic Distribution by Uplink Transmission Power In this example, the traffic distribution is displayed by the uplink transmission power of the mobiles. You can analyse the effect of the uplink power control.
1546
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
To display the traffic distribution by uplink transmission power: 1. Select the Network explorer. 2. Right-click the Simulations folder. The context menu appears. 3. Select Properties from the context menu. The Simulations Properties dialogue appears. 4. On the Display tab of the dialogue, select "Value intervals" as the Display type and "Transmission power (UL) (dBm)" as the Field. 5. Click OK. The traffic distribution is now displayed by uplink transmission power (see Figure 14.58).
Figure 14.58: Displaying the traffic distribution by uplink transmission power
14.4.5.3.6
Displaying Traffic Simulation Results Using Tip Text You can display information by placing the pointer over a mobile generated during a simulation to read the information displayed in the tip text. The information displayed is defined by the settings you made on the Display tab. For information on defining the tip text, see "Defining the Object Type Tip Text" on page 46. To display simulation results in the form of tip text: •
In the map window, place the pointer over the user that you want more information on. After a brief pause, the tip text appears with the information defined in the Display tab of the Simulations folder properties (see Figure 14.59).
Figure 14.59: Displaying the traffic simulation results using tip text
14.4.5.4 Displaying the Results of a Single Simulation After you have created a simulation, as explained in "Creating Simulations" on page 1543, you can display the results. To access the results of a single simulation: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. 4. Right-click the simulation. The context menu appears. 5. Select Properties from the context menu. The simulation properties dialogue appears.
1547
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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.
Results: Under Results, is data on the connection results: • • •
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: • • • • • • • • • • • • • • • • • • • • • • •
1548
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. Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site. Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink, or downlink and uplink both. Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink both. Number of connected users (DL): The number of users connected to any cell of the site in downlink. Number of connected users (UL): The number of users connected to any cell of the site in uplink. No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." 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.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
•
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. Max PUSCH C/(I+N) (dB): The maximum PUSCH C/(I+N) for the cell. It is updated during uplink noise rise control based on the maximum noise rise constraints of the neighbouring cells. Angular distribution of interference (AAS): The simulation results generated for transmitters using a smart antenna. These results are the angular distributions of the downlink traffic power spectral density. AAS usage (DL) (%): The percentage of the downlink traffic load that corresponds to the traffic carried by the smart antennas. 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. Connection success rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both. Number of connected users (DL): The number of users connected to the cell in downlink. Number of connected users (UL): The number of users connected to the cell in uplink. No service: The number of users unable to connect to the cell for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to the cell for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to the cell for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to the cell for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was "Resource saturation." 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. 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).
1549
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • •
1550
User profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal and the user profile. Subscriber ID: The ID of the user if the user is generated from a subscriber list and not from a traffic map. Subscriber list: The subscriber list of the user if the user is generated from a subscriber list and not from a traffic map. Service: The service assigned during the first random trial during the generation of the user distribution. Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal and the user profile. Mobility: The mobility type assigned during the first random trial during the generation of the user distribution. Activity status: The assigned activity status. It can be Active DL, Active UL, Active DL+UL, or Inactive. Connection status: The connection status indicates whether the user is connected or rejected at the end of the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection cause is given. Clutter class: The code of the clutter class where the user is located. Indoor: This field indicates whether indoor losses have been added or not. Best server: The best server of the user. Reference cell: The reference cell of the serving transmitter of the subscriber. Azimuth: The orientation of the user’s terminal antenna in the horizontal plane. Azimuth is always considered with respect to the North. Atoll points the user antenna towards its best server. Downtilt: The orientation of the user’s terminal antenna in the vertical plane. Mechanical downtilt is positive when it is downwards and negative when upwards. Atoll points the user antenna towards its best server. Path loss (dB): The path loss from the best server calculated for the user. 2nd best server: The second best server of the user. 2nd best server path loss (dB): The path loss from the second best server calculated for the user. 3rd best server: The third best server of the user. 3rd best server path loss (dB): The path loss from the third best server calculated for the user. RSRP (RS EPRE) (DL) (dBm): The RSRP (received reference signal energy per resource element) received at the user location in the downlink. RSSI (DL) (dBm): The RSSI received at the user location in the downlink. RSRQ (DL) (dB): The RSRQ (reference signal received quality) at the user location in the downlink. Received RS power (DL) (dBm): The reference signal level received at the user location in the downlink. Received SS power (DL) (dBm): The SS signal level received at the user location in the downlink. Received PBCH power (DL) (dBm): The PBCH signal level received at the user location in the downlink. Received PDCCH power (DL) (dBm): The PDCCH signal level received at the user location in the downlink. Received PDSCH power (DL) (dBm): The PDSCH signal level received at the user location in the downlink. RS C/(I+N) (DL) (dB): The reference signal C/(I+N) at the user location in the downlink. SS C/(I+N) (DL) (dB): The SS C/(I+N) at the user location in the downlink. PBCH C/(I+N) (DL) (dB): The PBCH C/(I+N) at the user location in the downlink. PDCCH C/(I+N) (DL) (dB): The PDCCH C/(I+N) at the user location in the downlink. PDSCH C/(I+N) (DL) (dB): The PDSCH C/(I+N) at the user location in the downlink. RS total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user location in the downlink on the reference signals. SS & PBCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user location in the downlink on the SS and PBCH. PDCCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user location in the downlink on the PDCCH. PDSCH total noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user location in the downlink on the PDSCH. Bearer (DL): The highest LTE bearer available for the PDSCH C/(I+N) level at the user location in the downlink. BLER (DL): The Block Error Rate read from the user terminal’s reception 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.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• • • • • • • • • • •
• •
•
• • •
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 cell’s reception equipment for the PUSCH & PUCCH C/ (I+N) level at the serving transmitter of the user in the uplink. Diversity mode (UL): The diversity mode 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. •
•
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 network settings: • • • • • • • •
•
The input parameters specified when creating the simulation: • • • • • •
•
PDCCH overhead (number of symbol durations per subframe) PUCCH overhead (average number of frequency blocks) Switching point periodicity Default cyclic prefix ratio Uplink power adjustment margin Reference signal EPRE calculation method Serving cell layer selection method Adaptive MIMO switching criterion Generator initialisation value Maximum number of iterations Global scaling factor Uplink and downlink traffic load convergence thresholds Uplink noise rise convergence threshold Names of the traffic maps and subscriber lists used.
The parameters related to the clutter classes, including the default values.
1551
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
14.4.5.5 Displaying the Average Results of a Group of Simulations After you have created a group of simulations, as explained in "Creating Simulations" on page 1543, you can display the average results of the group. If you wish to display the results of a single simulation in a group, see "Displaying the Results of a Single Simulation" on page 1547. To display the averaged results of a group of simulations: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Simulations folder. 3. Right-click the group of simulations whose results you want to display. 4. Select Average Simulation from the context menu. A properties dialogue appears. One tab gives statistics of the simulation results. Other tabs in the simulation properties dialogue contain the averaged results for all simulations of the group. The Statistics tab: The Statistics tab contains the following sections: •
Request: Under Request, is data on the connection requests: •
• • •
Atoll calculates the total number of users who try to connect. This number is the result of the first random trial; radio resource allocation has not yet finished. The result depends on the traffic description and traffic input. During the first random trial, each user is assigned a service and an activity status. The number of users per activity status and the UL and DL throughput demands that all users could theoretically generate are provided. The breakdown per service (total number of users, number of users per activity status, and UL and DL throughput demands) is given.
Results: Under Results, is data on the connection results: • • •
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 average information per site: • • • • • • • • • • • • • • • • •
1552
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. Connection success rate (%): The percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site. Total number of connected users: The total number of users connected to any cell of the site in downlink, uplink, or downlink and uplink both. Number of connected users (DL+UL): The number of users connected to any cell of the site in downlink and uplink both. Number of connected users (DL): The number of users connected to any cell of the site in downlink. Number of connected users (UL): The number of users connected to any cell of the site in uplink. No service: The number of users unable to connect to any cell of the site for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to any cell of the site for which the rejection cause was "Resource saturation."
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• • • • • • •
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. Connection success rate (%) for each service: For each service, the percentage of users connected to any cell of the site with respect to the number of users covered by the cells of the site.
The Cells (Average) tab: The Cells (Average) tab contains the following average information per cell: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
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. Max PUSCH C/(I+N) (dB): The maximum PUSCH C/(I+N) for the cell. It is updated during uplink noise rise control based on the maximum noise rise constraints of the neighbouring cells. Angular distribution of interference (AAS): The simulation results generated for transmitters using a smart antenna. These results are the angular distributions of the downlink traffic power spectral density. AAS usage (DL) (%): The percentage of the downlink traffic load that corresponds to the traffic carried by the smart antennas. 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. Connection success rate (%): The percentage of users connected to the cell with respect to the number of users covered by the cell. Total number of connected users: The total number of users connected to the cell in downlink, uplink, or downlink and uplink both. Number of connected users (DL+UL): The number of users connected to the cell in downlink and uplink both. Number of connected users (DL): The number of users connected to the cell in downlink. Number of connected users (UL): The number of users connected to the cell in uplink. No service: The number of users unable to connect to the cell for which the rejection cause was "No service." No service (%): The percentage of users unable to connect to the cell for which the rejection cause was "No service." Scheduler saturation: The number of users unable to connect to the cell for which the rejection cause was "Scheduler saturation." Scheduler saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was "Scheduler saturation." Resource saturation: The number of users unable to connect to the cell for which the rejection cause was "Resource saturation." Resource saturation (%): The percentage of users unable to connect to the cell for which the rejection cause was "Resource saturation." 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.
1553
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• • •
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. 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 network settings: • • • • • • • •
•
The input parameters specified when creating the simulation: • • • • • •
•
PDCCH overhead (number of symbol durations per subframe) PUCCH overhead (average number of frequency blocks) Switching point periodicity Default cyclic prefix ratio Uplink power adjustment margin Reference signal EPRE calculation method Serving cell layer selection method Adaptive MIMO switching criterion Generator initialisation value Maximum number of iterations Global scaling factor Uplink and downlink traffic load convergence thresholds Uplink noise rise convergence threshold Names of the traffic maps and subscriber lists used.
The parameters related to the clutter classes, including the default values.
14.4.5.6 Updating Cell Load Values With Simulation Results After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 1543, you can update cell load values for each cell with the results calculated during the simulation. To update cell values with simulation results: 1. Display the simulation results: To display the results for a group of simulations: a. Select the Network explorer. b. Click the Expand button ( ) to expand the 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. Select the Network explorer. b. Click the Expand button ( ) to expand the Simulations folder. c. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results you want to access. 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: • • • • • • • • • • •
1554
Traffic load (DL) (%) ICIC ratio (DL) (%) Traffic load (UL) (%) UL noise rise (dB) ICIC UL noise rise (dB) Max PUSCH C/(I+N) (dB) Angular distribution of interference (AAS) AAS usage (DL) (%) MU-MIMO capacity gain (UL) No. of users (DL) No. of users (UL)
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
14.4.5.7 Estimating a Traffic Increase When you create simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the performance of the network against an increase of traffic load without changing traffic parameters or maps by using the global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for sector traffic maps). To change the global scaling factor: 1. Create a simulation or group of simulations as described in "Creating Simulations" on page 1543. 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).
14.4.6 Making Coverage Predictions Using Simulation Results In Atoll, you can analyse simulation results by making coverage predictions using simulation results. In a coverage prediction each pixel is considered as a non-interfering probe user with a defined terminal, mobility, and service. The analyses can be based on a single simulation or on an averaged group of simulations. When no simulations are available, Atoll uses the downlink traffic loads and uplink noise rise values stored for each cell to make coverage predictions. For information on cell properties, see "Cell Description" on page 1441; for information on modifying cell properties, see "Creating or Modifying a Cell" on page 1446. Once you have made simulations, Atoll can use the information from the simulations instead of the defined parameters in the cell properties to make coverage predictions. For each coverage prediction based on simulation results, you can base the coverage prediction on a selected simulation or on a group of simulations, which uses the average of all simulations in the group. The coverage predictions that can use simulation results are: • • • • •
Coverage by C/(I+N) Level: For information on making a downlink or uplink coverage by C/(I+N) level, see "Making a Coverage by C/(I+N) Level" on page 1492. Service Area Analysis: For information on making a downlink or uplink service area analysis, see "Making a Downlink or Uplink Service Area Analysis" on page 1495. Effective Service Area Analysis: For information on making an effective service area analysis, see "Studying the Effective Service Area" on page 1497. Coverage by Throughput: For information on making a downlink or uplink coverage by throughput, see "Making a Coverage Prediction by Throughput" on page 1498. Coverage by Quality Indicator: For information on making a downlink or uplink coverage by quality indicator, see "Making a Coverage Prediction by Quality Indicator" on page 1501.
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.
14.5 Optimising Network Parameters Using the ACP Atoll Automatic Cell Planning (ACP) enables radio engineers designing LTE networks to automatically calculate the optimal network settings in terms of network coverage and quality. The ACP can also be used to add sites from a list of candidate sites or to remove unnecessary sites or sectors. Atoll ACP can also be used in co-planning projects where networks using different radio access technologies must be taken into consideration when calculating the optimal network settings. Atoll ACP is primarily intended to improve existing network deployment by reconfiguring the main parameters that can be remotely controlled by operators: antenna electrical tilt and cell pilot power. ACP can also be used during the initial planning stage of a LTE network by enabling the selection of the antenna, and its azimuth, height, and mechanical tilt. ACP not only takes transmitters into account in optimisations but also any repeaters and remote antennas. Atoll ACP can also be used to measure and optimise the EMF exposure created by the network. This permits the optimisation of power and antenna settings to reduce excessive EMF exposure in existing networks and optimal site selection for new transmitters. ACP uses user-defined objectives to evaluate the optimisation, as well as to calculate its implementation cost. Once you have defined the objectives and the network parameters to be optimised, Atoll ACP uses an efficient global search algorithm to test
1555
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
many network configurations and propose the reconfigurations that best meet the objectives. The ACP presents the changes ordered from the most to the least beneficial, allowing phased implementation or implementation of just a subset of the suggested changes. The ACP is technology-independent and can be used to optimise networks using different radio access technologies. Chapter 6: Automatic Cell Planning explains how you configure the ACP module, how you create and run an optimisation setup, and how you can view the results of an optimisation. In this section, only the concepts specific to LTE networks are explained: • • •
"LTE Optimisation Objectives" on page 1556 "LTE Quality Parameters" on page 1556 "The LTE Quality Analysis Predictions" on page 1557.
14.5.1 LTE Optimisation Objectives ACP optimises the network using user-defined objectives to evaluate the quality of the network reconfiguration. The objectives are dependent on the technology used by the project and are consistent with the corresponding coverage predictions in Atoll. In projects using LTE, either alone, or in a co-planning or multi-RAT project, the following objectives are used: • •
RS coverage RS CINR
For information on setting objective parameters, see "Setting Objective Parameters" on page 242 of Chapter 6: Automatic Cell Planning.
14.5.2 LTE Quality Parameters When you create an optimisation setup, you define how the ACP evaluates the objectives. The quality parameters are technology dependent. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own predictions. However, if you have saved the display options of an ACP prediction 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. In projects using LTE, either alone, or in a co-planning or multi-RAT project, the following quality parameters are used: • • • • •
Overlap Signal level RS C \ RSRP RS C⁄N RS CINR \ RSRQ
To define the quality parameters for LTE: 1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 233 in Chapter 6: Automatic Cell Planning. 2. Click the Objectives tab. 3. Under Criteria, in the left-hand pane, under Parameters, expand LTE. You can base the evaluation of the objectives on a calculated coverage prediction or on manual configuration. If you base the coverage prediction settings on a calculated coverage prediction, ACP will use the ranges and colours defined in the selected coverage prediction as the default for its own predictions. However, if you have saved the display options of an ACP prediction 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 prediction display options as the default, see "Changing the Display Properties of ACP Predictions" on page 284. For information on saving a configuration file, see "Configuring Default Settings" on page 231. If you want to use a coverage prediction, the coverage prediction must have already been calculated.
4. Click Overlap. In the right-hand pane, you can define how the ACP will evaluate overlapping coverage. 5. Select what the objective evaluation will be based on from the Base prediction settings on list: • •
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, define an Overlap threshold margin and a Minimum signal level. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate overlapping coverage using the same parameters that were used to calculate the coverage prediction.
6. Under LTE in the left-hand pane under Parameters, select Signal Level.
1556
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
7. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box 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. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate the signal level using the same parameters that were used to calculate the coverage prediction.
8. Under LTE in the left-hand pane under Parameters, select RS C \ RSRP. 9. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box 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. Additionally you must define the Service and Terminal used to evaluate the RS C \ RSRP. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate the RS C \ RSRP using the same parameters that were used to calculate the coverage prediction.
10. Under LTE in the left-hand pane under Parameters, select RS C⁄N. 11. Select what the objective evaluation will be based on from the Base prediction settings on list: •
•
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box 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. Additionally you must define the Service and Terminal used to evaluate the RS C⁄N. Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate RS C⁄N using the same parameters that were used to calculate the coverage prediction.
12. Under LTE in the left-hand pane under Parameters, select RS CINR \ RSRQ. 13. Select what the objective evaluation will be based on from the Base prediction settings on list: •
Manual configuration: If you select Manual Configuration from the Base prediction settings on list, you can select the Enable shadowing margin check box 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 a Service and a Terminal. The service and terminal specified are used during the calculation of RS CINR \ RSRQ through gain and losses (i.e., the service body loss, the gain and loss of the terminal antenna, and terminal noise factor). Under Calculation Method, define how the RS CINR \ RSRQ will be calculated. Select Using frequency plan if you want the frequency plan to be taken into consideration when calculating the RS CINR \ RSRQ. Select Ignoring frequency plan & segmentation if you want the RS CINR \ RSRQ to be calculated without taking the frequency plan and segmentation into consideration.
Coverage Prediction: If you select a coverage prediction from the Base prediction settings on list, the ACP will evaluate the RS CINR \ RSRQ using the same parameters that were used to calculate the coverage prediction.
14.5.3 The LTE Quality Analysis Predictions The quality analysis predictions enable you to display the signal quality predictions in the Atoll map window. These predictions are the same as those displayed on the Quality tab of the optimisation’s Properties dialogue. The quality analysis predictions are the equivalent of predictions created by different Atoll coverage predictions: • • •
The RS coverage predictions correspond to the Atoll coverage by signal level. For more information, see "Studying Signal Level Coverage" on page 1463. The RS CINR coverage predictions correspond to Atoll coverage by C⁄(I+N) level. For more information, see "Making a Coverage by C/(I+N) Level" on page 1492. The overlapping zones predictions correspond to the Atoll overlapping zones coverage prediction. For more information, see "Making a Coverage Prediction on Overlapping Zones" on page 1476.
Making these predictions available within ACP enables you to quickly validate the optimisation results without having to commit the results and then calculate a coverage prediction in Atoll. The ACP predictions display results very similar to those that Atoll would display if you committed the optimisation results and calculated Atoll coverage predictions, however, before basing any decision to commit the optimisation results on the predictions produced by ACP, you should keep the following recommendations in mind: •
You should verify the results with a different Atoll coverage prediction, such as the overlapping zones prediction.
1557
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• • •
ACP generated predictions are generated using the entire set of proposed changes. They do not take into account the change subset defined on the Change Details tab. Multiple carriers are not supported by ACP; the predictions are only provided for the requested carrier. Even after committing the optimisation results, differences can remain between the ACP predictions and the predictions resulting from Atoll coverage predictions.
You can view the exact RS coverage value on any pixel by letting the pointer rest over the pixel. The RS coverage value is then displayed in a tip text. For the overlapping zones prediction, you can set the best server threshold on the User Preferences tab of the ACP Properties dialogue (see "Configuring Default Settings" on page 231) or by setting the CellOverlap parameter in the acp.ini file. For each network quality coverage prediction, ACP offers a prediction showing the initial network state, the final network state, and a prediction showing the changes between the initial and final state.
14.6 Verifying Network Capacity An important step in the process of creating an LTE network is verifying the capacity of the network. This is done using measurements of the strength of the reference signal levels, SS, PBCH, PDSCH, and PDCCH signal levels, and various C/(I+N) at different locations within the area covered by the network. This collection of measurements is called drive test data. The data contained in a drive test data path is used to verify the accuracy of current network parameters and to optimise the network. In this section, the following are explained: • • • • • • •
"Importing a Drive Test Data Path" on page 1558 "Displaying Drive Test Data" on page 1561 "Defining the Display of a Drive Test Data Path" on page 1561 "Network Verification" on page 1562 "Exporting a Drive Test Data Path" on page 1567 "Extracting CW Measurements from Drive Test Data" on page 1567 "Printing and Exporting the Drive Test Data Analysis Tool" on page 1567.
14.6.1 Importing a Drive Test Data Path In Atoll, you can analyse networks by importing drive test data in the form of ASCII text files (with tabs, commas, semi-colons, or spaces as separator), TEMS FICS-Planet export files (with the extension PLN), or TEMS text export files (with the extension FMT). For Atoll to be able to use the data in imported files, the imported files must contain the following information: • •
The position of drive test data points. When you import the data, you must indicate which columns give the abscissa and ordinate (XY coordinates) of each point. Information identifying scanned cells (for example, serving cells, neighbour cells, or any other cells). In LTE networks, a cell can be identified by its physical cell ID. Therefore, you must indicate during the import process which column contains the physical cell IDs of cells.
You can import a single drive test data file or several drive test data files at the same time. If you regularly import drive test data files with the same format, you can create an import configuration. The import configuration contains information that defines the structure of the data in the drive test data file. By using the import configuration, you will not need to define the data structure each time you import a new drive test data file. To import one or several drive test data files: 1. Select the Network explorer. 2. Right-click the Drive Test Data folder. The context menu appears. 3. Select Import from the context menu. The Open dialogue appears. 4. Select the file or files you want to open. You can import one or several files. If you are importing more than one file, you can select contiguous files by clicking the first file you want to import, pressing Shift and clicking the last file you want to import. You can select non-contiguous files by pressing CTRL and clicking each file you want to import. 5. Click Open. The Import of Measurement Files dialogue appears.
1558
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Files with the extension PLN, as well as some FMT files (created with old versions of TEMS) are imported directly into Atoll; you will not be asked to define the data structure using the Import of Measurement Files dialogue. 6. If you already have an import configuration defining the data structure of the imported file or files, you can select it from the Import configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have an import configuration, continue with step 7. a. Under Import configuration, select an import configuration from the Import configuration list. b. Continue with step 10. •
•
When importing a drive test data path file, existing configurations are available in the Files of type list of the Open dialogue, sorted according to their date of creation. After you have selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises the extension. If several configurations are associated with an extension, Atoll chooses the first configuration in the list. The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters: • • •
Name: By default, Atoll names the new drive test data path after the imported file. You can change this name if desired. Under Receiver, set the Height of the receiver antenna and the Gain and Losses. Under Measurement conditions, • •
Units: Select the measurement units used. Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document. If the coordinates used in the file you are importing are different than the coordinates used in the Atoll document, you must click the Browse button ( ) and select the coordinate system used in the drive test data file. Atoll will then convert the data imported to the coordinate system used in the Atoll document.
8. Click the Setup tab (see Figure 14.60).
1559
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.60: The Setup tab of the Import of Measurement Files dialogue a. Under File, enter the number of the 1st measurement row, select the data Separator, and select the Decimal symbol used in the file. b. Click the Setup button to link file columns and internal Atoll fields. The Drive Test Data Setup dialogue appears. c. Under Measurement point position, select the columns in the imported file that give the X-coordinates and the Y-coordinates of each point in the drive test data file. You can also identify the columns containing the XY coordinates of each point in the drive test data file by selecting them from the Field row of the table on the Setup tab.
d. In the Physical cell ID identifier box, enter a string found in the column name identifying the physical cell IDs of scanned cells. For example, if the string "PCI" is found in the column names identifying the physical cell IDs of scanned cells, enter it here. Atoll will then search for the column with this string in the column name. e. Click OK. •
•
If you have correctly entered the information under File on the Setup tab, and the necessary values in the Drive Test Data Setup dialogue, Atoll should recognise all columns in the imported file. If not, you can click the name of the column in the table in the Field row and select the column name. For each field, you must ensure that each column has the correct data type in order for the data to be correctly interpreted. The default value under Type is "". Columns marked with "" 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 want to save the definition of the data structure so that you can use it again, you can save it as an import configuration: a. On the Setup tab, under Import configuration, click Save. The Configuration dialogue appears. b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll’s installation folder. In case you cannot write into that folder, you can click Browse to choose a different location.
1560
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
c. Enter a Configuration name and an Extension of the files that this import configuration will describe (for example, "*.txt"). d. Click OK. Atoll will now select this import configuration automatically every time you import a drive test data path file with the selected extension. If you import a file with the same structure but a different extension, you can select this import configuration from the Configuration list. • •
•
You do not have to complete the import procedure to save the import configuration and have it available for future use. When importing a measurement file, you can expand the NumMeasINIfile.ini file by clicking the Expand button ( ) in front of the file under Import configuration to display all the available import configurations. When selecting the appropriate configuration, the associations are automatically made in the table at the bottom of the dialogue. You can delete an existing import configuration by selecting the import configuration under Import configuration and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import all, if you are importing more than one file. The drive test data are imported into the current Atoll document.
14.6.2 Displaying Drive Test Data When you have imported the drive test data into the current Atoll document, you can display it in the map window. Then, you can select individual drive test data points to see the information at that location. To display information about a single drive test data point: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Select the display check box of the drive test data you want to display in the map window. The drive test data is displayed. 4. Click and hold the drive test data point on which you want more information. Atoll displays an arrow pointing towards the serving cell (see Figure 14.64 on page 1565) in the same colour as the transmitter.
14.6.3 Defining the Display of a Drive Test Data Path You can manage the display of drive test data paths using the Display dialogue. The points on a drive test data path can be displayed according to any available attribute. You can also use the Display dialogue to define labels, tip text and the legend. To display the Display tab of a drive test data path’s Properties dialogue: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path whose display you wish to set. The context menu appears. 4. Select Properties from the context menu. The drive test data path’s 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 for each transmitter (a circle, triangle, cross, etc.) and a symbol size according to the altitude.
1561
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• • •
•
Fast display forces Atoll to use the lightest symbol to display the points. This is particularly useful when you have a very large number of points. You can not use Advanced display if the Fast display check box has been selected. You can sort drive test data paths in alphabetical order in the Network explorer by right-clicking the Drive Test Data Path folder and selecting Sort Alphabetically from the context menu. You can save the display settings (such as colours and symbols) of a drive test data path in a user configuration file to make them available for use on another drive test data path. To save or load the user configuration file, click the Actions button on the Display tab of the path properties dialogue and select Save or Load from the Display Configuration submenu.
14.6.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 Measurement Points Along Drive Test Data Paths" on page 1562 "Predicting the Signal Level on Drive Test Data Points" on page 1563 "Creating Coverage Predictions on Drive Test Data Paths" on page 1564 "Displaying Statistics Over a Drive Test Data Path" on page 1564 "Extracting a Field From a Drive Test Data Path for a Transmitter" on page 1565 "Analysing Measurement Variations Along the Path" on page 1565.
14.6.4.1 Filtering Measurement Points Along Drive Test Data Paths When using a drive test data path, some measured points may present values that are too far outside the median values to be useful. As well, test paths may include test points in areas that are not representative of the drive test data path as a whole. For example, a test path that includes two heavily populated areas might also include test points from a more lightly populated region between the two. You can filter out unreliable measurement points from the drive test data path either geographically, by filtering by clutter classes and the focus zone, or using an advanced filter. To filter out measurement points by clutter class: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to filter out measurement points. The context menu appears. 4. Select Filter from the context menu. The Drive Test Data Filter dialogue appears. 5. Under Clutter classes, clear the check boxes of the clutter classes you want to exclude. Measurement points located on the excluded clutter classes will be filtered out. 6. If you want to use the focus zone as part of the filter, select the Use focus zone to filter check box. Measurement points located outside the focus zone will be filtered out. 7. If you want to permanently delete the measurement points outside the filter, select the Delete points outside the filter check box. • •
You can apply a filter on all the drive test data paths in the Drive Test Data folder by selecting Filter from the context menu of the folder. If you want to use the measurement points that you permanently deleted, you will have to import the drive test data path again.
To filter out measurement points using an advanced filter: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to filter out measurement points. The context menu appears. 4. Select Filter from the context menu. The Drive Test Data Filter dialogue appears.
1562
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
5. Click More. The Filter dialogue appears. For more information on using the Filter dialogue, see "Advanced Data Filtering" on page 96. You can update heights (of the DTM, and clutter heights) and the clutter class of drive test data points after adding new geographic maps or modifying existing ones by selecting Refresh Geo Data from the context menu of the Drive Test Data folder.
14.6.4.2 Predicting the Signal Level on Drive Test Data Points To predict the signal level on drive test data points: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you want to create the point prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Point predictions, select Point Signal Level and click OK. The Point Signal Level Properties dialogue appears (see Figure 14.61).
Figure 14.61: Point Signal Level Properties Dialogue The errors between measured and predicted signal levels can be calculated and added to the drive test data table. 6. If you want to calculate errors between measured and predicted signal levels, under Select signal levels for error calculations, select the names of the columns representing measured signal level values in the drive test data table for which you want to calculate the errors (see Figure 14.62). If you do not want to add this information to the drive test data table, continue with step 7.
Figure 14.62: Selecting Measured Signal Levels for which Errors will be Calculated 7. Click OK. A new point prediction is created for the selected drive test data path. 8. Right-click the drive test data path. The context menu appears. 9. Select Calculations > Calculate All the Predictions from the context menu. If you chose to have Atoll calculate the errors between measured and predicted signal levels, new columns are added to the drive test data table for the predicted point signal level from the serving cell and the errors between the measured and predicted values.
1563
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.63: Drive Test Data table after Point Signal Level Prediction (with error calculations) New columns are also added for the predicted point signal level from each neighbour cell and the errors between the predicted and measured values. The values stored in these columns can be displayed in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1565. The propagation model used to calculate the predicted point signal levels is the one assigned to the transmitter for the main matrix. For more information on propagation models, see Chapter 5: Working with Calculations in Atoll.
14.6.4.3 Creating Coverage Predictions on Drive Test Data Paths You can create the following coverage prediction for all transmitters on each point of a drive test data path: •
Coverage by Signal Level
To create a coverage prediction along a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path on which you wish to create the coverage prediction. The context menu appears. 4. Select Calculations > Create a New Prediction from the context menu. The Prediction Types dialogue appears. 5. Under Standard predictions, 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 Predictions from the context menu. A new column for each coverage prediction is added in the table for the drive test data. The column contains the predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Working with Calculations in Atoll). You can display the information in these new columns in the Drive Test Data analysis tool. For more information on the Drive Test Data analysis tool, see "Analysing Measurement Variations Along the Path" on page 1565.
14.6.4.4 Displaying Statistics Over a Drive Test Data Path If predictions have been calculated along a drive test data path, you can display the statistics between the measured and the predicted values on that path. To display the statistics for a specific drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to display comparative statistics. The context menu appears. 4. Select Display Statistics from the context menu. The Measurement and Prediction Fields Selection dialogue appears.
1564
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
5. Under For the following transmitters, select one or more transmitters to include in the statistics. 6. Under Select the predicted values, select the fields that contain the predicted values that you wish to use in the statistics. 7. Under Select the measured values, select the fields that contain the measured values that you wish to use in the statistics. 8. Enter the Measured values range for the statistics. Only the measured values within this range will be included in the statistics. 9. Click OK. Atoll opens a window listing statistics of comparison between measured and predicted values.
14.6.4.5 Extracting a Field From a Drive Test Data Path for a Transmitter You can extract information for a selected transmitter from a field of a drive test data path. The extracted information is available in a new column in the drive test data table. To extract a field from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data from which you want to extract a field. The context menu appears. 4. Select Focus on a Transmitter from the context menu. The Field Selection for a Given Transmitter dialogue appears. 5. Under On the transmitter, select the transmitter for which you wish to extract a field. 6. Under For the fields, select the fields that you wish to extract for the selected transmitter. 7. Click OK. Atoll creates a new column in the drive test data path table for the selected transmitter and with the selected values.
14.6.4.6 Analysing Measurement Variations Along the Path In Atoll, you can analyse variations in measurements along any drive test data path using the Drive Test Data analysis tool. You can also use the Drive Test Data analysis tool to find serving cells of points. To analyse measurement variations using the Drive Test Data analysis tool. 1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears (see Figure 14.64).
Figure 14.64: The Drive Test Data analysis tool 2. In the Drive Test Data analysis tool, click the Display button. The Display Parameters dialogue appears (see Figure 14.65).
1565
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.65: The drive test data display parameters 3. In the Display Parameters dialogue: • • •
Select the check box next to each field you want to display in the Drive Test Data analysis tool. If you want, you can change the display colour by clicking the colour in the Colour column and selecting a new colour from the palette that appears. Click OK to close the Display Parameters dialogue. You can change the display status or the colour of more than one field at the same time by selecting several fields. You can select contiguous fields by clicking the first field, pressing Shift and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking each field. You can then change the display status or the colour by right-clicking on the selected fields and selecting the choice from the context menu. The selected fields are displayed in the Drive Test Data analysis tool.
4. You can display the data in the drive test data path in the following ways: • •
Click the values in the Drive Test Data analysis tool. 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 14.64 on page 1565) in the same colour as the transmitter. 5. You can display a secondary Y-axis on the right side of the window in order to display the values of a variable with different orders of magnitude than the ones selected in the Display Parameters dialogue. You select the value to be displayed from the right-hand list at the top of the Drive Test Data analysis tool. The values are displayed in the colour defined in the Display Parameters dialogue. 6. You can zoom in on the graph displayed in the Drive Test Data analysis tool in the following ways: •
Zoom in or out: i.
Right-click the Drive Test Data analysis tool. The context menu appears.
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 analysis tool on one end of the range of data you want to zoom in on. The context menu appears.
ii. Select First Zoom Point from the context menu. iii. Right-click the Drive Test Data analysis tool on the other end of the range of data you want to zoom in on. The context menu appears. iv. Select Last Zoom Point from the context menu. The Drive Test Data analysis tool zooms in on the data between the first zoom point and the last zoom point. 7. Click the data in the Drive Test Data analysis tool to display the selected point in the map window. Atoll will centre the map window on the selected point if it is not presently visible.
1566
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
If you open the table for the drive test data you are displaying in the Drive Test Data analysis tool, Atoll will automatically display in the table the data for the point that is displayed in the map and in the Drive Test Data analysis tool (see Figure 14.64 on page 1565).
14.6.5 Exporting a Drive Test Data Path You can export drive test data paths to files as vector data. To export a drive test data path to a vector file: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path 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.
14.6.6 Extracting CW Measurements from Drive Test Data You can generate CW measurements from drive test data paths and extract the results to the CW Measurements folder. To generate CW measurement from a drive test data path: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the Drive Test Data folder. 3. Right-click the drive test data path from which you wish to export CW measurements. 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 Extraction parameters of CW measurement paths: a. Enter the Min. number of points to extract per measurement path. CW measurements are not created for transmitters that have fewer points than this number. b. Enter the minimum and maximum Measured signal levels. CW measurements are created with drive test data points where the signal levels are within this specified range. 7. Click OK. Atoll creates new CW measurements for transmitters satisfying the parameters set in the CW Measurement Extraction dialogue. For more information about CW measurements, see the Model Calibration Guide.
14.6.7 Printing and Exporting the Drive Test Data Analysis Tool You can print and export the contents of the Drive Test Data analysis tool. To print or export the contents of the Drive Test Data analysis tool: 1. Select Tools > Drive Test Data from the menu bar. The Drive Test Data analysis tool appears (see Figure 14.64 on page 1565). 2. Define the display parameters and zoom level as explained in "Analysing Measurement Variations Along the Path" on page 1565. 3. Right-click the Drive Test Data analysis tool. The context menu appears. • •
To print the Drive Test Data analysis tool, select Print from the context menu. To export the Drive Test Data analysis tool, select Copy from the context menu, then paste.
1567
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
14.7 Co-planning LTE Networks with Other Networks Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and several network scenarios can be designed for any given area: a country, a region, a city, etc. For example, you can design an LTE and a GSM network for the same area in Atoll, and then work with Atoll’s co-planning features to study the mutual impacts of the two networks. Before starting a co-planning project in Atoll, the Atoll administrator must perform the pre-requisite tasks that are relevant for your project as described in the Administrator Manual. Sectors of both networks can share the same sites database. You can display base stations (sites and sectors), geographic data, and coverage predictions, etc., of one network in the other network’s Atoll document. You can also study inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-technology neighbours are allocated on criteria such as the distance between sectors or overlapping coverage. In addition, you can optimise the settings of the two networks using Atoll’s Automatic Cell Planning (ACP) module. In this section, the following are explained: • • • • • •
"Switching to Co-planning Mode" on page 1568. "Working with Coverage Predictions in an Co-Planning Project" on page 1570. "Performing Inter-technology Neighbour Allocation" on page 1573. "Creating an LTE Sector From a Sector in the Other Network" on page 1585. "Using ACP in a Co-planning Project" on page 1585. "Ending Co-planning Mode" on page 1586.
14.7.1 Switching to Co-planning Mode Before starting a co-planning project, you must have two networks designed for a given area, i.e., you must have an LTE Atoll document and an Atoll document for the other network. Atoll switches to co-planning mode as soon as the two documents are linked together. In the following sections, the LTE document will be referred to as the main document, and the other document as the linked document. Atoll does not establish any restriction on which is the main document and which is the linked document. Before starting a co-planning project, make sure that your main and linked documents have the same geographic coordinate systems.
To switch to co-planning mode: 1. Open the main document. •
Select File > Open or File > New > From an Existing Database.
2. Link the other document with the open main document. a. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document. b. Select Document > 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]. 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 Atoll’s co-planning features are now available.
1568
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
When you are working on a co-planning document, Atoll facilitates working on two different but linked documents by synchronising the display in the map window between both documents. Atoll synchronises the display for the following: • • • •
Geographic data: Atoll synchronises the display of geographic data such as clutter classes and the DTM. If you select or deselect one type of geographic data, Atoll makes the corresponding change in the linked document. Zones: Atoll synchronises the display of filtering, focus, computation, hot spot, printing, and geographic export zones. If you select or deselect one type of zone, Atoll makes the corresponding change in the linked document. Map display: Atoll co-ordinates the display of the map in the map window. When you move the map, or change the zoom level in one document, Atoll makes the corresponding changes in the linked document. Point analysis: When you use the Point Analysis tool, Atoll co-ordinates the display on both the working document and the linked document. You can select a point and view the profile in the main document and then switch to the linked document to make an analysis on the same profile but in the linked document.
Displaying Both Networks in the Same Atoll Document After you have switched to co-planning mode as explained in "Switching to Co-planning Mode" on page 1568, transmitters and predictions from the linked document are displayed in the main document. If you want, you can display other items or folders from the explorer window of the linked document to the explorer window of the main document (e.g., you can display GSM sites and measurement paths in an LTE document). To display sites from the linked document in the main document: 1. Click the linked document’s map window. The linked document’s map window becomes active and the explorer window shows the contents of the linked document. 2. Select the Network explorer. 3. Right-click the Sites folder. The context menu appears. 4. Select Make Accessible In from the context menu, and select the name of the main document from the submenu that opens. The Sites folder of the linked document is now available in the main document. The Explorer window of the main document now contains a folder named Sites in [linked document], where [linked document] is the name of the linked document. If you want the Sites folder of the linked document to appear in the main document automatically, you can set an option in the atoll.ini file. For information on setting options in the atoll.ini file, see the Administrator Manual. The same process can be used to link other folders in one document, folders such as CW Measurements, Drive Test Data, Clutter Classes, Traffic Maps, DTM, etc., in the other document. Once the folders are linked, you can access their properties and the properties of the items in the folders from either of the two documents. Any changes you make in the linked document are taken into account in the both the linked and main documents. However, because working document is the main document, any changes made in the main document are not automatically taken into account in the linked document. If you close the linked document, Atoll displays a warning icon ( ) in the main document’s Explorer window, and the linked items are no longer accessible from the main document. You can load the linked document in Atoll again by right-clicking the linked item in the explorer window of the main document, and selecting Open Linked Document. The administrator can create and set a configuration file for the display parameters of linked and main document transmitters in order to enable you to distinguish them on the map and to be able to select them on the map using the mouse. If such a configuration file has not been set up, you can choose different symbols, sizes and colours for the linked and the main document transmitters. For more information on folder configurations, see "Folder Configurations" on page 105. You can also set the tip text to enable you to distinguish the objects and data displayed on the map. For more information on tip text, see "Defining the Object Type Tip Text" on page 46. 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 Windows" on page 39. Figure 14.66 shows an example of LTE transmitters with labels and displayed in the Legend window, and GSM transmitter data displayed in a tip text.
1569
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.66: GSM and LTE Transmitters displayed on the map
14.7.2 Working with Coverage Predictions in an Co-Planning Project Atoll provides you with features that enable you to work with coverage predictions in your co-planning project. You can modify the properties of coverage predictions in the linked document from within the main document, and calculate coverage predictions in both documents at the same time. You can also study and compare the coverage predictions of the two networks. In this section, the following are explained: • •
"Updating Coverage Predictions" on page 1570 "Analysing Coverage Predictions" on page 1571.
14.7.2.1 Updating Coverage Predictions You can access the properties of the coverage predictions in the linked Predictions folder in the main document’s Explorer window. After modifying the linked coverage prediction properties, you can update them from the main document. To update a linked coverage prediction: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 4. Right-click the linked coverage prediction whose properties you want to modify. The context menu appears. 5. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 6. Modify the calculation and display parameters of the coverage prediction. 7. Click OK to save your settings. 8. Click the Calculate button (
) in the Radio Planning toolbar.
When you click the Calculate button, Atoll first calculates uncalculated and invalid path loss matrices and then unlocked coverage predictions in the main and linked Predictions folders. When you have several unlocked coverage predictions defined in the main and linked Predictions folders, Atoll calculates them one after the other. For information on locking and unlocking coverage predictions, see "Locking Coverage Predictions" on page 218. 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 Radio Planning 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.
1570
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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.
14.7.2.2 Analysing Coverage Predictions In Atoll, you can analyse coverage predictions of the two networks together. You can display information about coverage predictions in the main and the linked documents in the Legend window, use tip text to get information on displayed coverage predictions, compare coverage areas by overlaying the coverage predictions in the map window, and study the differences between the coverage areas by creating coverage comparisons. If several coverage predictions are visible on the map, it might be difficult to clearly see the results of the coverage prediction you wish to analyse. You can select which coverage predictions to display or to hide by selecting or clearing the display check box. For information on managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer Windows" on page 38. In this section, the following are explained: • • • • •
14.7.2.2.1
"Co-Planning Coverage Analysis Process" on page 1571 "Displaying the Legend Window" on page 1571 "Comparing Coverage Prediction Results Using Tip Text" on page 1572 "Comparing Coverage Areas by Overlaying Coverage Predictions" on page 1572 "Studying Differences Between Coverage Areas" on page 1573.
Co-Planning Coverage Analysis Process The aim of coverage analysis in a co-planning project is to compare the coverage areas of the two networks and to analyse the impact of changes made in one network on the other. Changes made to the sectors of one network might also have an impact on sectors in the other network if the sectors in the two networks share some antenna parameters. You can carry out a coverage analysis with Atoll to find the impact of these changes. The recommended process for analysing coverage areas, and the effect of parameter modifications in one 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 1474 and "Making a Coverage Prediction by Signal Level" on page 1472. 2. Create and calculate a Coverage by Transmitter (best server with 0 dB margin) coverage prediction and a Coverage by Signal Level coverage prediction in the linked document. 3. Choose display settings for the coverage predictions and tip text contents that will allow you to easily interpret the predictions displayed in the map window. This can help you to quickly assess information graphically and using the mouse. You can change the display settings of the coverage predictions on the Display tab of each coverage prediction’s 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 1569. 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 1572 and "Studying Differences Between Coverage Areas" on page 1573. 7. Calculate the linked coverage predictions again to study the effects of the changes on the linked coverage predictions.
14.7.2.2.2
Displaying the Legend Window When you create a coverage prediction, you can add the displayed values of the coverage prediction to the legend by selecting the Add to legend check box on the Display tab. To display the Legend window: •
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage prediction in the main and linked Predictions folders, identified by the name of the coverage prediction.
1571
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
14.7.2.2.3
© Forsk 2012
Comparing Coverage Prediction Results Using Tip Text You can compare coverage predictions by placing the pointer over an area of the coverage prediction to read the information displayed in the tip text. Atoll displays information for all displayed coverage predictions in both the working and the linked documents. The information displayed is defined by the settings you made on the Display tab when you created the coverage prediction (step 3. of "Co-Planning Coverage Analysis Process" on page 1571). To get coverage prediction results in the form of tip text: •
In the map window, place the pointer over the area of the coverage prediction that you want more information on. After a brief pause, the tip text appears with the information defined on all displayed coverage predictions in both the working and the linked documents (see Figure 14.22). The tip text for the working document is on top and the tip text for the linked document, with the linked document identified by name is on the bottom.
Figure 14.67: Comparing coverage prediction results using tip text
14.7.2.2.4
Comparing Coverage Areas by Overlaying Coverage Predictions You can compare the coverage areas of the main and linked documents by overlaying the coverage predictions in the map window. To compare coverage areas by overlaying coverage predictions in the map window: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the Predictions folder. 4. Select the visibility check box to the left of the coverage prediction of the main document you want to display in the map window. The coverage prediction is displayed on the map. 5. Right-click the coverage prediction. The context menu appears. 6. Select Properties from the context menu. The coverage prediction Properties dialogue appears. 7. Click the Display tab. 8. Modify the display parameters of the coverage prediction. For information on defining display properties, see "Display Properties of Objects" on page 43. 9. Click the Expand button ( ) to expand the Predictions in [linked document] folder, where [linked document] is the name of the linked document. 10. Select the visibility check box to the left of the linked coverage prediction you want to display in the map window. The coverage prediction is displayed 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 Windows" on page 39.
1572
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
14.7.2.2.5
Studying Differences Between Coverage Areas You can compare coverage predictions to find differences in coverage areas. To compare coverage predictions: 1. Click the main document’s map window. The main document’s map window becomes active and the explorer window shows the contents of the main document and the linked folders from the linked document. 2. Select the Network explorer. 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 document’s Predictions folder. For more information on coverage prediction comparison, see "Comparing Coverage Predictions: Examples" on page 1483.
14.7.3 Performing Inter-technology Neighbour Allocation The following sections describe the features available in Atoll that help the RF planner to carry out inter-technology neighbour planning. For example, handovers between an LTE and a GSM network can be studied in Atoll by allocating neighbour GSM sectors to LTE cells. In this section, the following are explained: • • • • • • •
"Setting Inter-technology Exceptional Pairs" on page 1573 "Configuring Importance Factors for Inter-technology Neighbours" on page 1575 "Allocating Inter-technology Neighbours Automatically" on page 1575 "Displaying Inter-technology Neighbours on the Map" on page 1578 "Allocating and Deleting Inter-technology Neighbours per Cell" on page 1579 "Calculating the Importance of Existing Inter-technology Neighbours" on page 1582 "Checking the Consistency of the Inter-technology Neighbour Plan" on page 1584.
In the sections listed above, it is assumed that Atoll is already in co-planning mode, and the Atoll documents corresponding to the two networks have already been linked. For more information on switching to co-planning mode, see "Switching to Coplanning Mode" on page 1568.
14.7.3.1 Setting Inter-technology Exceptional Pairs You can set inter-technology neighbour constraints by defining exceptional pairs in Atoll. These constraints can be taken into account when inter-technology neighbours are automatically or manually allocated. To define inter-technology exceptional pairs between the main document and the linked document: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the LTE Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Exceptional Pairs from the context menu. The Inter-technology Exceptional Pairs table appears. 5. Enter one exceptional pair per row of the table. A cell can have more than one exceptional pair. 6. For each exceptional pair, select: a. Cell: The name of the cell in the main document as the first part of the exceptional pair. The names of all the cells in the main document are available in the list. b. Neighbour: The name of the neighbour in the linked document as the second part of the exceptional pair. The names of all the transmitters/cells in the linked document are available in the list. c. Status: The status indicates whether the neighbour should always (forced) or never (forbidden) be considered as a neighbour of the cell. Atoll fills the Number and Distance (m) fields automatically. In GSM, neighbours and exceptional pairs are allocated by transmitter (i.e., by sector).
1573
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
You can access a cell’s inter-technology neighbours and exceptional pairs by using its Properties dialogue. To open a cell’s Properties dialogue: 1. Select the Network explorer. 2. Right-click the LTE 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 cell’s Properties dialogue appears. 5. Click the Inter-technology Neighbours tab. In GSM, the Inter-technology Neighbours tab is found on the transmitter’s Properties dialogue. Displaying Inter-technology Exceptional Pairs on the Map You can display inter-technology exceptional pairs on the map in order to study the forced and forbidden neighbour relations defined in the Inter-technology Exceptional Pairs table. To display exceptional pairs defined between the main and the linked documents: 1. Click the main document’s map window. 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
3. Select Display Options from the menu. The Neighbour Display 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 links: Selecting this option displays an exceptional pair link for each cell in the main document that has an exceptional pair defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its exceptional pair list. These links are represented with straight black lines.
6. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
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 Edit Relations on the Map button ( ) in the Radio Planning toolbar. Exceptional pairs are now displayed on the map. Exceptional pairs will remain displayed until you click the Edit Relations on the Map 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 41). The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display links check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional pairs on the map. Adding and Removing Inter-technology Exceptional Pairs on the Map You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours. Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on the map as explained in "Displaying Inter-technology Exceptional Pairs on the Map" on page 1574. 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.
1574
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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. 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 41).
14.7.3.2 Configuring Importance Factors for Inter-technology Neighbours You can define the relative importance of the factors that Atoll uses to evaluate possible inter-technology neighbours (for information on how Atoll calculates importance, see the Technical Reference Guide). To configure the importance factors for inter-technology neighbours: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Neighbours > Inter-technology > Configure Importance from the context menu. The Neighbour Importance Weighting dialogue appears. 4. Select the Inter-technology Neighbours tab. On the Inter-technology Neighbours tab, you can set the following importance factors: • • •
Distance Factor: Set the minimum and maximum importance of a possible neighbour transmitter being located within the maximum distance from the reference transmitter. Coverage factor: Set the minimum and maximum importance of a neighbour being admitted for coverage reasons. 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 1575.
5. Click OK.
14.7.3.3 Allocating Inter-technology Neighbours Automatically Atoll can automatically determine handover relations between networks of different technologies, for example, LTE and GSM. In this case, inter-technology handovers from LTE to GSM may occur when the LTE coverage is not continuous. The network’s overall coverage is extended by an LTE-to-GSM handover. Atoll can automatically determine neighbours in the linked document for cells in the main document and vice versa. Inter-technology neighbours are stored in the database.
1575
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
To automatically allocate neighbours in the linked document for cells in the main document: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the LTE Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > 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: • •
1576
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.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• • • • • •
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. e. In the % min covered area box, enter the minimum percentage of the cell’s coverage area that the neighbour’s 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 calculate 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
Description
When
Exceptional pair
Neighbour relation is defined as an exceptional pair.
Force exceptional pairs is selected
Co-site
The neighbour is located at the same site as the reference cell.
Force co-site as neighbours is selected
Distance
The neighbour is within the maximum distance from the reference cell.
Use Coverage Overlapping is not selected
% of covered area and overlapping area
Neighbour relation that fulfils coverage conditions.
Use Coverage Overlapping is selected
Existing
The neighbour relation existed before calculating the automatic allocation.
Reset is not selected
12. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you want to assign to cells. At this point you can compare the automatic allocation results proposed by Atoll with the current neighbour list (existing neighbours) in your document.
1577
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
To compare the proposed and existing neighbour lists: •
Click Compare. The list of automatically allocated neighbours, whose Commit check box is selected, is compared with the existing list of neighbours. A report of the comparison is displayed in a text file called NeighboursDeltaReport.txt, which appears at the end of the comparison. This file lists: • • • •
The document name and the neighbour allocation type 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 Inter-technology Neighbours tab of each cell. 14. Click Close.
14.7.3.4 Displaying Inter-technology Neighbours on the Map You can display inter-technology neighbours on the map in order to study the inter-technology handover scenarios. To display neighbours in the linked document for cells in the main document: 1. Click the main document’s map window. 2. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
3. Select Display Options from the menu. The Neighbour Display dialogue appears. 4. Under Inter-technology Neighbours, select the Display links check box. 5. Under Advanced, select the neighbour links to display: •
•
•
Outwards non-symmetric: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document. These links are represented with straight dashed lines of the same colour as the transmitter in the main document. Inwards non-symmetric: Shows a neighbour link for each transmitter/cell in the linked document that has a neighbour defined with a cell in the main document. These links are represented with straight dashed lines of the same colour as the transmitter in the linked document. Symmetric links: Shows a neighbour link for each cell in the main document that has a neighbour defined with a transmitter/cell in the linked document only if the transmitter/cell in the linked document also has the cell of the main document in its neighbours list. These links are represented with straight black lines.
6. Click the arrow ( ) next to the Edit Relations on the Map button ( appears.
) in the Radio Planning toolbar. A menu
7. Select Neighbours as the type of neighbour links to display. 8. Click the Edit Relations on the Map button ( ) in the Radio Planning toolbar. Neighbours are now displayed on the map until you click the Edit Relations on the Map button again. 9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter, 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 41). If you select the Display links check box under Inter-technology Neighbours, Atoll displays both inter-technology and intratechnology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the transmitter Site22_2.
1578
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
14.7.3.5 Allocating and Deleting Inter-technology Neighbours per Cell Although you can let Atoll allocate inter-technology neighbours automatically, you can adjust the overall allocation of intertechnology neighbours by allocating or deleting inter-technology neighbours per cell. You can allocate or delete inter-technology neighbours directly on the map, or using the Cells tab of the Transmitter Properties dialogue, or using the Inter-technology Neighbours table. This section explains the following: • • •
"Allocating or Deleting Inter-technology Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 1579. "Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table" on page 1580. "Allocating and Removing Inter-technology Neighbours on the Map" on page 1581.
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 transmitter’s Properties dialogue: 1. On the main document’s map window, right-click the transmitter whose neighbours you want to change. The context menu appears. 2. Select Properties from the context menu. The transmitter’s 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 cell’s Properties dialogue appears. 5. Click the Inter-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. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Under List, select the cell from the list in the Neighbour column in the row marked with the New row icon (
).
c. 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 Source to "manual." To create a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. Select Make Symmetrical from the context menu. A symmetric neighbour relation is created between the cell in the Neighbour column and the cell in the Cell column.
1579
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
To delete a symmetric neighbour relation: a. Click the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Right-click the neighbour in the Neighbour column. The context menu appears. d. 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 the Edit button on the bottom-right of the dialogue. The neighbour list becomes editable. b. Click in the left margin of the table row containing the neighbour to select the entire row. c. Press DEL to delete the neighbour. 8. Click OK. In GSM, the Inter-technology Neighbours tab is available in each transmitter’s Properties dialogue. Allocating or Deleting Inter-technology Neighbours Using the Inter-technology Neighbours Table To allocate or delete inter-technology neighbours between transmitters/cells in the linked document and cells in the main document using the Inter-technology Neighbours table: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the LTE Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Open Table from the context menu. The Inter-technology Neighbours table appears. 5. Enter one inter-technology neighbour per row of the table. Each cell can have more than one inter-technology neighbour. 6. Allocate or delete a neighbour. To allocate an inter-technology neighbour: a. In the row marked with the New row icon (
), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column. c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table. When the new neighbour is created, Atoll automatically calculates the distance between the reference cell and the neighbour and displays it in the Distance column and sets the Source to "manual." 7. To create a symmetric neighbour relation: a. Right-click the neighbour in the Neighbour column. The context menu appears. b. Select Make Symmetrical 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 Make Symmetrical from the context menu. To take all exceptional pairs into consideration: a. Right-click the Neighbours table. The context menu appears. b. Select Force Exceptional Pairs from the context menu. You can add or delete either forced neighbours or forbidden neighbours using the Intertechnology Exceptional Pairs 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.
1580
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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 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. To delete a neighbour: a. Click in the left margin of the table row containing the neighbour to select the entire row. b. Press DEL to delete the neighbour. In GSM, neighbours are allocated by transmitter (i.e., by sector). Allocating and Removing Inter-technology Neighbours on the Map You can allocate inter-technology neighbours directly on the map using the mouse. Atoll adds or removes neighbours to transmitters if the display option is set to Neighbours. Before you can add or remove inter-technology neighbours using the mouse, you must activate the display of inter-technology neighbours on the map as explained in "Displaying Inter-technology Neighbours on the Map" on page 1578. To add a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press Shift and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitter to the list of inter-technology neighbours of the other transmitter. To remove a symmetric neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press Shift and click the transmitter you want to remove from the list of neighbours. Atoll removes both transmitter from the list of inter-technology neighbours of the other transmitter. To add an outwards neighbour relation: 1. Click the reference transmitter on the map. Atoll displays its neighbour relations. 2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference transmitter to the list of inter-technology neighbour of the other transmitter. To 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.
1581
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 41).
14.7.3.6 Calculating the Importance of Existing Inter-technology Neighbours After you have imported inter-technology neighbours into the current Atoll document or manually defined inter-technology neighbours, Atoll can calculate the importance of each inter-technology neighbour, i.e., the weight of each neighbour. Atoll calculates the importance for inter-technology neighbours of active and filtered transmitters within the focus zone. To calculate the importance of existing inter-technology neighbours: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the LTE Transmitters folder. The context menu appears. 4. Select Neighbours > Inter-technology > Calculate Importance from the context menu. The Neighbour Importance Calculation dialogue appears. 5. Select the Inter-technology Neighbours tab. 6. Under Importance, enter the Max inter-site distance. Sites outside the defined maximum inter-site distance will not be considered as potential neighbours. 7. Under Importance, select the Take into account the co-site factor check box to verify that neighbours are located on the same site as their reference cell when calculating importance. 8. Clear the Use overlapping coverage check box in order to base the neighbour importance calculation only on the distance criterion and continue with step 10. Otherwise, select the Use overlapping coverage check box if you want to base the neighbour importance calculation on coverage conditions. 9. Under Coverage Conditions, you can set the coverage conditions between inter-technology neighbours and their reference cells for both of the projects. a. Click the Define button to change the coverage conditions for cells in the main document. The 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: • • •
1582
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.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• • • • •
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. 10. If you cleared the Use overlapping coverage check box, enter the maximum distance between the reference cell and a possible neighbour in the Max inter-site distance box. Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes (importance and reason) in a table. You can use many of Atoll’s table shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data Tables" on page 69. In addition, by clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be calculated. 11. Click Calculate. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss matrices are not valid, Atoll recalculates them. Once Atoll has finished calculating importance, the results are displayed in the table. The table contains the following information. • • • •
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
1583
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
•
Distance: The distance in kilometres between the reference cell and the neighbour.
12. Click Commit to commit the importance values and the reasons for allocation to the Neighbours table.
14.7.3.7 Checking the Consistency of the Inter-technology Neighbour Plan You can perform an audit of the current inter-technology neighbour allocation plan. When you perform an audit of the current inter-technology neighbour allocation plan, Atoll lists the results in a text file. You can define what information Atoll provides in the audit. To perform an audit of the inter-technology neighbour plan: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appear. 3. Select Neighbours > Inter-technology > Audit from the context menu. The Neighbour Audit dialogue appears. 4. Click the Inter-technology Neighbours tab. 5. Define the parameters of the audit: • • •
•
• • • •
Average no. of neighbours: Select the Average no. of neighbours check box if you want to verify the average number of neighbours per cell. Empty lists: Select the Empty lists check box if you want to verify which cells have no neighbours (in other words, which cells have an empty neighbour list). Full lists: Select the Full lists check box if you want to verify which cells have the maximum number of neighbours allowed (in other words, which cells have a full neighbour list). The maximum number of neighbours can be either set here for all the cells, or specified for each cell in the Cells table. Lists > max number: Select the Full lists check box if you want to verify which cells have more than the maximum number of neighbours allowed. The maximum number of neighbours can be either set here for all the cells, or specified for each cell in the Cells table. Missing co-sites: Select the Missing co-sites check box if you want to verify which cells have no co-site neighbours. Missing symmetrics: Select the Missing symmetrics check box if you want to verify which cells have non-symmetric neighbour relations. Exceptional pairs: Select the Exceptional pairs check box if you want to verify which cells have forced neighbours or forbidden neighbours. Distance between neighbours: Select the Distance between neighbours check box and enter the distance between neighbours that should not be exceeded.
6. Click OK to perform the audit. Atoll displays the results of the audit in a new text file: •
Average number of neighbours: X; where, X is the average number of neighbours (integer) per cell for the plan audited.
•
Empty lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list) Syntax:
•
Full lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours listed in their respective neighbours lists. Syntax:
•
|CELL|
|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| 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:
•
Non symmetric links: X; total number of non-symmetric neighbour links in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
Existing forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan. Syntax:
1584
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Missing forced: X; total number of forced neighbours missing in the audited neighbour plan. Syntax:
•
|CELL| |NEIGHBOUR|
|CELL| |NEIGHBOUR| |TYPE| |REASON|
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
•
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|
14.7.4 Creating an LTE Sector From a Sector in the Other Network You can create a new sector in the main document based on an existing sector in the linked document. To create a new sector in the main document based on an existing sector in the linked document: 1. Click the main document’s map window. 2. In the map window, right-click the linked transmitter based on which you want to create a new LTE transmitter. The context menu appears. 3. Select Copy in [main document] from the context menu. The following parameters of the new sector in the main document will be the same as the sector in the linked document it was based on: antenna position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. The new sector will be initialised with the radio parameters from the default station template in the main document. If the sector in the linked document is located at a site that does not exist in the main document, the site is created in the main document as well. If the sector in the linked document is located at a site that also exists in the main document, and the coordinates of the site in the linked and main documents are the same, the sector is created in the main document at the existing site. The site coordinates in the linked and main documents will always be the same if the Atoll administrator has set up site sharing in the database. For more information about site sharing in databases, see the Administrator Manual. If the sector in the linked document is located at a site that exists in the main document, but at a different location (geographic coordinates), the sector is not created in the main document. To update the display settings of the new sector: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Right-click the LTE Transmitters folder of the main document. The context menu appears. 4. Select Update Folder Configuration from the context menu.
Figure 14.68: New sector – Before and after applying the configuration The azimuths and mechanical tilts of secondary antennas and remote antennas are not included when you select Update Folder Configuration and have to be set up manually.
14.7.5 Using ACP in a Co-planning Project Atoll ACP enables you to automatically calculate the optimal network settings in terms of network coverage and capacity in co-planning projects where networks using different technologies, for example, LTE and GSM, must both be taken into consideration. When you run an optimisation setup in a co-planning environment, you can display the sites and transmitters of both networks in the document in which you will run the optimisation process, as explained in "Switching to Co-planning Mode" on page 1568. 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 1586 "Importing the Other Network into the Setup" on page 1586.
1585
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
14.7.5.1 Creating a New Co-planning Optimisation Setup Once you have displayed both networks in the main document as explained in "Switching to Co-planning Mode" on page 1568, you can create the new co-planning optimisation setup. To create a new co-planning optimisation setup: 1. Click the main document’s map window. 2. Select the Network explorer. 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 234. 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.
14.7.5.2 Importing the Other Network into the Setup Once you have created the co-planning optimisation setup, you must import the linked network. To import the linked network: 1. Click the main document’s map window. 2. Select the Network explorer. 3. Click the Expand button ( ) to expand the ACP - Automatic Cell Planning folder. 4. Right-click the setup you created in "Creating a New Co-planning Optimisation Setup" on page 1586. The context menu appears. 5. Select Import Project from the context menu and select the name of the linked document you want to import into the newly created setup.
The setup has been modified to include the linked network. You can modify the parameters for the optimisation setup by right-clicking it in the Network explorer and selecting Properties from the context menu. For information on the parameters available, see "Defining Optimisation Parameters" on page 234. 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 267. For information on the optimisation results, see "Viewing Optimisation Results" on page 270. Click the Create Setup button to save the defined optimisation to be run later.
14.7.6 Ending Co-planning Mode once you have linked two Atoll documents for the purposes of co-planning, Atoll will maintain the link between them. However, you might want to unlink the two documents at some point, either because you want to use a different document in co-planning or because you want to restore the documents to separate, technology-specific documents.
1586
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
To unlink the documents and end co-planning mode: 1. Select File > Open to open the main document. Atoll informs you that this document is part of a multi-technology environment and asks whether you want to open the other document. 2. Click Yes to open the linked document as well. 3. Select Document > Unlink to unlink the documents and end co-planning mode. The documents are no longer linked and co-planning mode is ended.
14.8 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 1587. "The Global Network Settings" on page 1588. "Defining LTE Radio Bearers" on page 1591. "Defining LTE Quality Indicators" on page 1592. "Defining LTE Reception Equipment" on page 1592. "Defining LTE Schedulers" on page 1595. "Defining LTE UE Categories" on page 1596. "Smart Antenna Systems" on page 1597. "Multiple Input Multiple Output Systems" on page 1599. "Modelling Shadowing" on page 1600. "Modelling Inter-technology Interference" on page 1601.
14.8.1 Defining Frequency Bands To define frequency bands: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. Click the Expand button ( ) to expand the Frequencies folder. 4. In the Frequencies folder, right-click Bands. The context menu appears. 5. Select Open Table. The Frequency Bands table appears. 6. In the Frequency Bands table, enter one frequency band per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each frequency band, enter: •
• • •
Name: Enter a name for the frequency band, for example, "2.1 GHz - 10 MHz." Each LTE frequency band has a specific channel width. Mentioning the channel width in the frequency band name is a good approach. This name will appear in other dialogues when you select a frequency band. Channel width (MHz): Enter the width for each channel in the frequency band. First channel: Enter the number of the first channel in this frequency band. Last channel: Enter the number of the last channel in this frequency band. If this frequency band has only one carrier, enter the same number as entered in the First channel field. 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 30 MHz, and you are deploying your network with 10 MHz allocated to each cell, you can find the first and last channel numbers by: Last channel - First channel = (Frequency band width/Channel width) - 1 If you plan to keep the First channel number = 0, for this example: Last channel = (30 MHz/10 MHz) - 1 = 2
•
•
Excluded channels: Enter the channel numbers which do not constitute the frequency band. You can enter nonconsecutive channel numbers separated with a comma, or you can enter a range of channel numbers separating the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5"). Start frequencies (MHz): Enter the start frequency for TDD frequency bands, and the downlink and the uplink start frequencies for FDD frequency bands.
1587
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
• • •
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. TDD-specific parameters are hidden when there is no TDD frequency band defined in the Frequency Bands table. These parameters include Switching point periodicity and Special subframe configuration (see "The Global Network Settings" on page 1588) and TDD frame configuration (see "Cell Description" on page 1441).
•
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.
7. When you have finished adding frequency bands, click the Close button (
).
You can also access the properties dialogue of each individual frequency band by double-clicking the left margin of the row with the frequency band.
14.8.2 The Global Network Settings Atoll allows you to set network level parameters which are common to all the transmitters and cells in the network. These parameters are used in coverage predictions as well as during Monte Carlo simulations by the radio resource management and scheduling algorithms. This section explains the options available on the Global Parameters and Calculation Parameters tabs of the LTE Network Settings folder properties, and explains how to access them: • • •
"The Options on the Global Parameters Tab" on page 1588. "The Options on the Calculation Parameters Tab" on page 1590. "Modifying Global Network Settings" on page 1590.
14.8.2.1 The Options on the Global Parameters Tab The global LTE parameters include: •
Default cyclic prefix: The total symbol duration in LTE comprises the useful part of the symbol, carrying the data bits, and a cyclic prefix part, which is a portion of the useful data part repeated at the beginning of each symbol. The cyclic prefix is the method used by LTE to counter inter-symbol interference (ISI). The cyclic prefix and the orthogonality of subcarriers ensure that there is negligible intra-cell interference in LTE. LTE supports two cyclic prefix types: normal and extended.
•
PDCCH overhead: The Physical Downlink Control Channel (PDCCH) can take up to 3 symbol durations in each subframe in the downlink. In Atoll, the PDCCH is considered to include the PCFICH, PHICH, and PCH as well. The PBCH, PSS, SSS, and the downlink reference signals consume a fixed amount of resources in the downlink. Their corresponding overheads are hard-coded in Atoll in accordance with the 3GPP specifications.
•
PUCCH overhead: The Physical Uplink Control Channel (PUCCH) can consume a number of frequency blocks in the uplink. The uplink demodulation and sounding reference signals consume a fixed amount of resources in the uplink. Their corresponding overheads are hard-coded in Atoll in accordance with the 3GPP specifications. The amounts of resources corresponding to different signals and channels in LTE can be calculated and displayed in Atoll. For more information, see "Displaying LTE Frame Details" on page 1607.
•
Switching point periodicity (TDD only): There can be either one or two DL-UL switching points in TDD frames in case of full-frame and half-frame periodicities, respectively. You can select the frame configuration, i.e., the configuration of uplink and downlink subframes in a frame, for each cell according to the selected switching point periodicity.
•
Special subframe configuration (TDD only): The configuration of the special subframe in TDD frames. This configuration describes the durations and formats of DwPTS, GP, and UpPTS in the special subframe. DwPTS is used for transmission of the reference signal, PDCCH, PSS, and PDSCH. Reference signals are located in a DwPTS in the same manner as in any normal subframe. The PDCCH can at most be transmitted over two OFDM symbols (symbol durations) because the third symbol duration in a DwPTS is used for the PSS transmission. The resource elements left in DwPTS after excluding the RS, PDCCH, and PSS overheads are used for data transmission, i.e., PDSCH. UpPTS is only used for SRS and PRACH.
1588
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
•
RS EPRE: The reference signal energy per resource element can be either calculated automatically using the maximum power and the EPRE offsets for different downlink channels defined per cell, or entered per cell by the user. •
•
•
• • •
Calculated (equal distribution of unused EPRE): The reference signal EPRE for each cell will be calculated by Atoll using the cell’s maximum power (user-definable) and the EPRE offsets. For transmitters with more than one transmission antenna port, the energy belonging to the unused resource elements (resource elements reserved for reference signal transmission on other antennas) will be distributed among all the downlink signals and channels equally. Calculated (with boost): The reference signal EPRE for each cell will be calculated by Atoll using the cell’s maximum power (user-definable) and the EPRE offsets. For transmitters with more than one transmission antenna port, the energy belonging to the unused resource elements (resource elements reserved for reference signal transmission on other antennas) will be allotted to the reference signal resource elements only. This corresponds to a 3 dB boost in the RS EPRE with 2 transmission antenna ports and 6 dB boost with 4 ports. Calculated (without boost): The reference signal EPRE for each cell will be calculated by Atoll using the cell’s maximum power (user-definable) and the EPRE offsets. For transmitters with more than one transmission antenna port, the energy belonging to the unused resource elements (resource elements reserved for reference signal transmission on other antennas) will be considered lost. User-defined: You will be able to enter the reference signal EPRE for each cell. The cells’ maximum power will be calculated by Atoll using the RS EPRE and the EPRE offsets. Independent of max power: You can enter the reference signal EPRE and the maximum power. Atoll does not verify the validity of the entered values.
Serving (reference) cell layer selection method: The reference cell layer selection method is used for determining the reference cell in case of transmitters supporting more than one cell. The best serving transmitter for a pixel, subscriber, or mobile is determined according to the received reference signal level from the cell with the highest reference signal power. If more than one cell of the same transmitter cover the pixel, subscriber, or mobile, the reference cell is determined according to the selected method: •
•
Random: In coverage prediction calculations and in calculations on subscriber lists, the cell with the highest layer is selected as the serving (reference) cell. In Monte Carlo simulations, a random cell is selected as the serving (reference) cell. Distributive: In coverage prediction calculations and in calculations on subscriber lists, the cell with the highest 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 highest cell layer, the second mobile to the second highest cell layer, and so on.
The reference cell once assigned to a mobile does not change during Monte Carlo simulations. •
Adaptive MIMO switching criterion: You can select whether the MIMO mode selection will be based on the reference signal C/N or C/(I+N). Depending on the selected criterion, Atoll compares either the reference signal C/N or C/(I+N) with the AMS threshold defined for the cell.
•
Uplink power adjustment margin: The margin (in dB) that will be added to the bearer selection threshold, for safety against fast fading, when performing power control in uplink.
Figure 14.69 and Figure 14.70 give examples of downlink and uplink FDD resource blocks for the single antenna case using the normal cyclic prefix.
Figure 14.69: LTE downlink resource blocks
1589
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.70: LTE uplink resource blocks
14.8.2.2 The Options on the Calculation Parameters Tab The LTE calculation parameters include: •
Min interferer C/N threshold: Minimum requirement for interferers to be considered in calculations. Interfering cells from which the received carrier-power-to-noise ratio is less than this threshold are discarded. For example, setting this value to -20 dB means that interfering cells from which the received signals are 100 times lower than the thermal noise level will be discarded in calculations. The calculation performance of interferencebased coverage predictions, interference matrices calculations, and Monte Carlo simulations can be improved by setting a high value for this threshold.
•
•
Height: The receiver height at which the path loss matrices and coverage predictions are calculated. Calculations made on mobile users (from traffic maps) in Monte Carlo simulations are also carried out at this receiver height. Calculations made on fixed subscribers (from subscriber lists) in Monte Carlo simulations are carried out at their respective heights. Max range: The maximum coverage range of transmitters in the network.
14.8.2.3 Modifying Global Network Settings You can change global network settings in the properties dialogue of the LTE Network Settings folder. To set the network level parameters: 1. Select the Parameters explorer. 2. Right-click the LTE Network Settings folder. The context menu appears. 3. Select Properties from the context menu. The Properties dialogue appears. 4. Select the Global Parameters tab. In this tab you can set the frame structure parameters. Under Frame structure you can modify the following: the Default cyclic prefix, the PDCCH overhead, the PUCCH overhead, and, for TDD networks, the Switching point periodicity and the Special subframe configuration. Switching point periodicity and Special subframe configuration are hidden when there is no TDD frequency band defined in the Frequency Bands table (see "Defining Frequency Bands" on page 1587. 5. Click the Advanced button. The Advanced Parameters dialogue appears. 6. In the Advanced Parameters dialogue, you can set: • • • •
1590
Downlink transmit power calculation: Under Downlink transmit power calculation, you can select the downlink reference signal EPRE calculation method or set it to user-defined. Serving cell layer selection: In this section, you can choose the serving cell layer selection Method. Adaptive MIMO switching: In this section, you can choose the adaptive MIMO switching Criterion. Uplink power adjustment: In this section, you can enter the uplink power adjustment Margin.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.71: LTE Global Parameters 7. Select the Calculation Parameters tab. In this tab you can set: • • •
Calculation limitation: In this section, you can enter the Min interferer C/N threshold. Receiver: In this section, you can enter the receiver Height. System: In this section, select the Max range check box if you want to apply a maximum system range limit, and enter the maximum system range in the text box to the right.
8. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
14.8.3 Defining LTE Radio Bearers LTE radio bearers carry the data in the uplink as well as in the downlink. In the Atoll LTE module, a "bearer" refers to a combination of MCS, i.e., modulation, and coding schemes. The Radio Bearers table lists the available radio bearers. You can add, remove, and modify bearer properties, if you want. To define LTE bearers: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. In the LTE Network Settings folder, right-click Radio Bearers. The context menu appears. 4. Select Open Table. The Radio Bearers table appears. 5. In the table, enter one bearer per row. For information on working with data tables, see "Working with Data Tables" on page 69. 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 reception 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 1605.
6. Click the Close button (
) to close the LTE Bearers table.
1591
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
14.8.4 Defining LTE Quality Indicators Quality indicators depict the coverage quality at different locations. The Quality Indicators table lists the available quality indicators. You can add, remove, and modify quality indicators, if you want. To define quality indicators: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. In the LTE Network Settings folder, right-click Quality Indicators. The context menu appears. 4. Select Open Table. The Quality Indicators table appears. 5. In the table, enter one quality indicator per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each quality indicator, enter: • • •
Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear in other dialogues and results. Used for data services: Select this check box to indicate that this quality indicator can be used for data services. Used for voice services: Select this check box to indicate that this quality indicator can be used for voice services.
6. Click the Close button (
) to close the Quality Indicators table.
14.8.5 Defining LTE Reception Equipment LTE reception equipment model the reception characteristics of cells and user terminals. Bearer selection thresholds and channel quality indicator graphs are defined in LTE reception equipment. To create a new piece of reception equipment: 1. Select the Network explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. In the LTE Network Settings folder, right-click Reception Equipment. The context menu appears. 4. Select Open Table. The Reception Equipment table appears. 5. In the Reception Equipment table, each row describes a piece of equipment. For the new piece of equipment you are creating, enter its name. 6. Double-click the equipment entry in the Reception Equipment table once your new equipment has been added to the table. The equipment’s Properties dialogue opens. The Properties dialogue has the following tabs: • •
General: On this tab, you can define the Name of the reception equipment. Bearer Selection Thresholds: In this tab (see Figure 14.72), you can modify the bearer selection thresholds for different mobility types. A bearer is selected for data transfer at a given pixel if the received carrier-to-interferenceand-noise ratio is higher than its selection threshold. For more information on bearers and mobility types, see "Defining LTE Radio Bearers" on page 1591 and "Modelling Mobility Types" on page 1488, respectively.
Figure 14.72: Reception Equipment - Bearer Selection Thresholds i.
Click the Best bearer thresholds button. The C/(I+N) Thresholds (dB) dialogue appears (see Figure 14.73).
ii. Enter the graph values. iii. Click OK.
1592
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Figure 14.73: C/(I+N) Thresholds (dB) dialogue For more information on the default values of the bearer selection thresholds, see "Bearer Selection Thresholds" on page 1604. For converting receiver equipment sensitivity values (dBm) into bearer selection thresholds, see "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1605. •
Quality Graphs: On this tab (see Figure 14.74), you can modify the quality indicator graphs for different bearers for different mobility types. These graphs depict the performance characteristics of the equipment under different radio conditions. For more information on bearers, quality indicators, and mobility types, see "Defining LTE Radio Bearers" on page 1591, "Defining LTE Quality Indicators" on page 1592, and "Modelling Mobility Types" on page 1488, respectively.
Figure 14.74: Reception Equipment - Quality Indicator Graphs i.
Click the Quality graph button. The Quality Graph dialogue appears (see Figure 14.75).
ii. Enter the graph values. iii. Click OK.
1593
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.75: Quality Indicator Graph dialogue •
MIMO: On this tab (see Figure 14.76), you can modify the SU-MIMO and diversity gains for different bearers, mobility types, BLER values, and numbers of transmission and reception antenna ports. The MIMO throughput gain is the increase in channel capacity compared to a SISO system. For more information on bearers and mobility types, see "Defining LTE Radio Bearers" on page 1591 and "Modelling Mobility Types" on page 1488, respectively. For more information on the different MIMO systems, see "Multiple Input Multiple Output Systems" on page 1599. No MIMO gain (diversity, SU-MIMO, and MU-MIMO) is applied if the numbers of transmission and reception antennas are both equal to 1.
Figure 14.76: Reception 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 14.77). iii. Enter the graph values. iv. Click OK.
1594
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
You can define the diversity and SU-MIMO gains for any combination of mobility type, bearer, and BLER, as well as the default gains for "All" mobility types, "All" bearers, and a Max BLER of 1. During calculations, Atoll uses the gains defined for a specific combination if available, otherwise it uses the default gains.
Figure 14.77: Max MIMO Gain dialogue 7. Click OK. The Properties dialogue closes. The settings are stored. 8. Click the Close button (
) to close the Reception Equipment table.
14.8.6 Defining LTE Schedulers In Atoll, schedulers perform the selection of users for resource allocation, the radio resource allocation and management according to the QoS classes of the services being accessed by the selected users. The scheduling process is composed of the following three steps: 1. Selection of users for resource allocation: The Max number of users defined for each cell is the maximum number of users that the cell’s 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 as long as there are remaining resources. 2. Resource allocation for supporting the Min throughput demands: This is the minimum data rate that a service must get in order to work properly. The scheduler is either able to allocate the exact amount of resources required to fully support the minimum throughput demands, or the service does not get any resources at all. The scheduler allocates resources, for supporting the minimum throughput demands, in the order of service priority. In order to be connected, users active in downlink and uplink must be able to get their minimum throughput in both directions. If a user active in downlink and uplink gets his minimum throughput in only one direction, he will be rejected. 3. Resource allocation for supporting the Max throughput demands: Once the resources have been allocated for supporting the minimum throughput demands in the previous step, the remaining resources can be allocated in different ways to support the maximum throughput demands of the users. For allocating resources to support the maximum throughput demands, the following types of scheduling methods are available: •
Proportional fair: The proportional fair scheduling method allocates the same amount of resources to all the users with a maximum throughput demand. Therefore, the resources allocated to each user are either the resources it requires to achieve its maximum throughput demand or the total amount of resources divided by the total number of users in the cell, which ever is smaller. The proportional fair scheduler can also model the effect of resource scheduling over time, i.e., how a proportional fair scheduler benefits from fast fading, by applying multiuser diversity gains (MUG) to user throughputs.
•
Proportional demand: The proportional demand scheduling method allocates resources proportional to the demands of users who have a maximum throughput demand. Therefore, users with higher maximum throughput demands will have higher resulting throughputs than the users with lower maximum throughput demands.
•
Round Robin: The round robin scheduling method allocates the same amount of resources to all the users with a maximum throughput demand. Therefore, the resources allocated to each user are either the resources it requires
1595
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
to achieve its maximum throughput demand or the total amount of resources divided by the total number of users in the cell, which ever is smaller. •
Max C/I: This scheduling method allocates the resources required by the users to achieve their maximum throughput demands in the order of their PDSCH C/(I+N) in downlink and of their PUSCH & PUCCH C/(I+N) in uplink. This means that users who are under good radio conditions will get the resources they require. The end result of this scheduling method is that the 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 available schedulers. You can add, remove, and modify scheduler properties, if you want. To define LTE schedulers: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. In the LTE Network Settings folder, right-click Schedulers. The context menu appears. 4. Select Open Table. The Schedulers table appears. 5. In the table, enter one scheduler per row. For information on working with data tables, see "Working with Data Tables" on page 69. For each scheduler, enter: • • • • •
•
Name: Enter a name for the scheduler. This name will appear in the cell properties. Scheduling method: Select the scheduling method used by the scheduler for allocating resources to support the maximum throughput demands. Target throughput for voice services: Select the throughput that the scheduler will target to satisfy for all voicetype services. Target throughput for data services: Select the throughput that the scheduler will target to satisfy for all datatype services. Bearer selection criterion: Select the criterion for the selection of the best bearer. • Bearer index: The best bearer selected for throughput calculations is the one with the highest bearer index among the bearers available in the reception equipment. • Peak RLC throughput: The best bearer selected for throughput calculations is the one with the highest peak RLC throughput (including SU-MIMO gains) among the bearers available in the reception equipment. • Effective RLC throughput: The best bearer selected for throughput calculations is the one with the highest effective RLC throughput (including SU-MIMO gains) among the bearers available in the reception equipment. Uplink bandwidth allocation target: Select the aim of the uplink bandwidth allocation. • • •
Full bandwidth: All the frequency blocks are used for the PUSCH & PUCCH C/(I+N) calculations, i.e., no bandwidth reduction is performed. Maintain connection: The number of frequency blocks is reduced one by one in order to increase the PUSCH & PUCCH C/(I+N) so that the mobile is able to get at least the lowest bearer. Best bearer: The number of frequency blocks is reduced in order to increase the PUSCH & PUCCH C/(I+N) so that the mobile is able to get the highest bearer available. The definition of the highest bearer depends on the Bearer selection criterion, i.e., highest index, highest peak RLC throughput, or highest effective RLC throughput. When the Bearer selection criterion is set to Effective RLC throughput, Atoll calculates the effective RLC throughput for all possible combinations of [number of frequency blocks, bearers], and keeps the number of frequency blocks and the bearer which provide the highest effective RLC throughput.
You can open a scheduler’s 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. On 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. 6. Click the Close button (
) to close the Schedulers table.
14.8.7 Defining LTE UE Categories LTE user equipment capabilities are standardised into different categories according to 3GPP specifications. To edit a UE category: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. In the LTE Network Settings folder, right-click UE Categories. The context menu appears. 4. Select Open Table. The LTE UE Categories table appears. 5. The LTE UE Categories table has the following columns:
1596
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
• • • • •
Name: Name of the UE category. Max number of transport block bits per TTI (DL): The maximum number of transport block bits per subframe in the downlink. This parameter defines the highest downlink throughput that a terminal can support. Max number of transport block bits per TTI (UL): The maximum number of transport block bits per subframe in the uplink. This parameter defines the highest uplink throughput that a terminal can support. Highest supported modulation (UL): The highest modulation supported in the uplink. Max number of reception antenna ports: The maximum number of antenna ports supported by a terminal in the downlink.
6. Click the Close button (
) to close the LTE UE Categories table.
14.8.8 Smart Antenna Systems Smart antenna systems use digital signal processing with more than one antenna element in order to locate and track various types of signals to dynamically minimise interference and maximise the useful signal reception. Different types of smart antenna modelling techniques exist, including beam switching, beam steering, beamforming, etc. Adaptive antenna systems are capable of using adaptive algorithms to cancel out interfering signals. Atoll includes a beamforming smart antenna model that supports linear adaptive array systems. The smart antenna model dynamically calculates and applies weights on each antenna element in order to create beams in the direction of served users. The antenna patterns thus created have a main beam pointed in the direction of the useful signal. TDD LTE networks are more suitable for smart antennas than FDD because of the similar uplink and downlink channel characteristics in TDD. Information gathered from a mobile in the uplink can be assumed valid for downlink as well. Atoll’s LTE module includes a conventional beamforming smart antenna model. The conventional beamformer works by forming beams in the direction of the served mobiles. •
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 C/(I+N) is calculated by taking into account the effects of beamforming. The smart antenna simulation results include the angular distribution of the transmitted power spectral density for each cell. These results are then used to carry out interference-based coverage predictions for the base stations using smart antennas.
•
Modelling in Coverage Predictions: The smart antenna results of Monte Carlo simulations are used in coverage predictions. Beamforming is performed to calculate the smart antenna gain towards each pixel of the studied cell dynamically in order to determine the received power. To calculate the interference, the simulation results for the angular distributions of downlink transmitted power spectral density are used in order to determine the power transmitted by an interfering cell in the direction of each served pixel of the studied cell.
The following section explains how to work with smart antenna equipment in Atoll: •
"Defining Smart Antenna Equipment" on page 1597.
14.8.8.1 Defining Smart Antenna Equipment Smart antenna equipment model adaptive antenna array systems with more than one antenna element. To create smart antenna equipment: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. Click the Expand button ( ) to expand the Smart Antennas folder. 4. In the Smart Antennas folder, right-click Smart Antenna Equipment. The context menu appears. 5. Select Open Table from the context menu. The Smart Antenna Equipment table appears. 6. In the Smart Antenna Equipment table, each row describes a piece of smart antenna equipment. For information on working with data tables, see "Working with Data Tables" on page 69. For the new smart antenna equipment, enter: • • •
Name: Enter a name for the smart antenna equipment. Antenna model: Select Conventional Beamformer from the list. Main antenna model: Select the main antenna model to be used with the smart antenna equipment. The list contains the antennas available in the Antennas table. When you assign the smart antenna equipment to a transmitter, you can choose to replace the current main antenna model with this model.
1597
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
7. Double-click the equipment entry in the Smart Antenna Equipment table once your new equipment has been added to the table. The equipment’s Properties dialogue opens. 8. Under the General tab, you can modify the parameters that you set previously. 9. To modify the properties of the smart antenna model assigned to the smart antenna equipment, click the Parameters button under Smart antenna models. The smart antenna model’s properties dialogue appears. a. Click the General tab. On the General tab, you can change the default Name of the smart antenna model. b. Click the Properties tab (see Figure 14.78). On the Properties tab, you can define: • • •
Number of elements: The number of antenna elements in the smart antenna system. Single element pattern: The antenna model to be used for each antenna element. You can select an antenna model from the list. The list contains the antennas available in the Antennas folder. Diversity gain (cross-polarisation): Select the Diversity gain (cross-polarisation) check box if you are using cross-polarised smart antennas and want to add diversity gains to the calculated downlink (all channels except RS) beamforming gains. You can define the diversity gains per clutter class on the Clutter tab of the smart antenna model’s properties dialogue.
Figure 14.78: Smart antenna model - Properties tab c. Click the Clutter tab (see Figure 14.79). On the Clutter tab, you can define the following parameters per clutter class: • •
•
Array gain offset (dB): Enter an offset to be added to the calculated beamforming array gains on the PDSCH. Positive offset values are considered as gains while negative values as losses. Power combining gain offset (dB): Enter an offset to be added to the calculated power combining gains on the RS, SS, PBCH, PDCCH, and PDSCH. Positive offset values are considered as gains while negative values as losses. Diversity gain (cross-polarisation) (dB): Enter the diversity gains for cross-polarised smart antennas to be applied to the SS, PBCH, PDCCH, and PDSCH.
Figure 14.79: Smart antenna model - Clutter tab d. Click OK. The smart antenna model properties are saved. 10. Click OK. The smart antenna equipment properties are saved. 11. Click the Close button (
1598
) to close the Smart Antenna Equipment table.
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
14.8.9 Multiple Input Multiple Output Systems Multiple Input Multiple Output (MIMO) systems use different transmission and reception diversity techniques. MIMO diversity systems can roughly be divided into the following types, all of which are modelled in Atoll: Transmit and Receive Diversity Transmit or receive diversity uses more than one transmission or reception antenna to send or receive more than one copy of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining) at the receiver to extract the useful signal. As the receiver gets more than one copy of the useful signal, the signal level at the receiver after combination of all the copies is more resistant to interference than a single signal would be. Therefore, diversity improves the C/(I+N) at the receiver. It is often used for the regions of a cell that have insufficient C/(I+N) conditions. In Atoll, you can set whether a cell supports transmit or receive diversity by selecting the corresponding diversity support modes in cell properties (see "Cell Description" on page 1441). Diversity gains on downlink and uplink can be defined in the reception equipment for different numbers of transmission and reception antenna ports, mobility types, bearers, and maximum BLER. For more information on uplink and downlink diversity gains, see "Defining LTE Reception Equipment" on page 1592. Additional gain values can be defined per clutter class. For information on setting the additional uplink and downlink diversity gain for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell that supports transmit or receive diversity, will benefit from the downlink or uplink diversity C/(I+N) gains. Single-User MIMO or Spatial Multiplexing SU-MIMO uses more than one transmission antenna to send different signals (data streams) on each antenna. The receiver can also have more than one antenna to receive different signals. Using spatial multiplexing with M transmission and N reception antenna ports, the throughput over the transmitter-receiver link can be theoretically increased M or N times, whichever is smaller, M or N. SU-MIMO improves the throughput (channel capacity) for a given C/(I+N), and is used for the regions of a cell that have sufficient C/(I+N) conditions. SU-MIMO (single-user MIMO) is also referred to as SM (spatial multiplexing) or simply MIMO. In Atoll, you can set whether a cell supports SU-MIMO by selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 1441). SU-MIMO capacity gains can be defined in the reception equipment for different numbers of transmission and reception antenna ports, mobility types, bearers, and maximum BLER. For more information on SU-MIMO gains, see "Defining LTE Reception Equipment" on page 1592. During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell that supports SU-MIMO, will benefit from the SU-MIMO gain in its throughput depending on its PDSCH or PUSCH C/(I+N). As SU-MIMO improves the channel capacity or throughputs, the PDSCH or PUSCH C/(I+N) of a user is first determined. Once the C/(I+N) is known, Atoll calculates the user throughput based on the bearer available at the user location. The obtained user throughput is then increased according to the SU-MIMO capacity gain and the SU-MIMO gain factor of the user’s clutter class. The capacity gains defined in Max SU-MIMO gain graphs are the maximum theoretical capacity gains using SU-MIMO. SU-MIMO requires rich multipath environment, without which the gain is reduced. In the worst case, there is no gain. Therefore, it is possible to define an SU-MIMO gain factor per clutter class whose value can vary from 0 to 1 (0 = no gain, 1 = 100 % gain). For information on setting the SU-MIMO gain factor for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 145. The SU-MIMO capacity gain vs. C/(I+N) graphs available in Atoll by default have been generated based on the maximum theoretical SU-MIMO capacity gains obtained using the following equations: CC MIMO G MIMO = --------------------CC SISO
Min ( N Ant, N Ant )
RX C ⁄ (I + N) Where CC MIMO = Min ( N TX is the channel capacity at a given C/(I+N) for a MIMO system Ant, N Ant ) × Log 2 1 + -----------------------------------------TX RX TX
RX
using N Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 ( 1 + C ⁄ ( I + N ) ) is the channel capacity for a single antenna system at a given C/(I+N). C/(I+N) is used as a ratio (not dB) in these formulas. You can replace the default SU-MIMO capacity gain graphs with graphs extracted from simulated or measured values. Adaptive MIMO Switch This is a technique for switching from SU-MIMO to transmit or receive diversity as the reference signal conditions get worse than a given threshold. AMS can be used in cells to provide SU-MIMO gains to users that have better reference signal C/N or C/(I+N) conditions than a given AMS threshold, and diversity gains to users that have worse reference signal C/N or C/(I+N) conditions than the threshold. AMS provides the optimum solution using transmit and receive diversity and SU-MIMO features to their best.
1599
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
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 user’s reference signal C/N or C/(I+N) and the AMS threshold defined in the cell properties. Diversity gain is applied to the user’s PDSCH or PUSCH C/(I+N) if the user’s reference signal C/N is less than the AMS threshold, and SU-MIMO is used if the reference signal C/N or C/(I+N) is higher than the AMS threshold. Multi-User MIMO or Collaborative MIMO MU-MIMO (Multi-User MIMO) or Collaborative MIMO is a technique for spatially multiplexing two user who have sufficient radio conditions at their locations. This technique is used in uplink so that a cell with more than one reception antenna port can receive uplink transmissions from two different users over the same frequency-time allocation. This technique provides considerable capacity gains in uplink, and can be used with single-antenna user equipment, i.e., it does not require more than one antenna at the user equipment as opposed to SU-MIMO, which only provides considerable gains with more than one antenna at the user equipment. In Atoll, you can set whether a cell supports MU-MIMO in uplink by selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 1441). MU-MIMO capacity gains result from the scheduling and RRM process. Using MU-MIMO, schedulers are able to allocate resources over two spatially multiplexed parallel frames in the same frequencytime resource allocation plane. MU-MIMO can only work under good radio conditions and if the cell has more than one reception antenna port. Therefore, the reference signal C/N must be higher than the MU-MIMO threshold defined by cell in order for the scheduler to be able to multiplex users in uplink. During the calculations of Monte Carlo simulations in Atoll, each new user connected to the first antenna port creates virtual resources available on the second antenna port. These virtual resources can then be allocated to a second user connected to the second antenna port without increasing the overall load of the cell. This way, each new mobile consumes the virtual resources made available be the previous mobile, and may make new virtual resources available on the other antenna port. The MU-MIMO capacity gain resulting from this uplink collaborative multiplexing is the ratio of the traffic loads of all the mobiles connected to both parallel frames in uplink to the uplink traffic load of the cell. MU-MIMO is only possible for mobiles that support MIMO and at which the reference signal C/N is greater than the MU-MIMO threshold defined for their serving cell. The MU-MIMO capacity gain can be defined per cell by the user or it can be an output of the Monte Carlo simulations. This gain is used during the calculation of uplink throughput coverage predictions. The channel throughput is multiplied by this gain for pixels where MU-MIMO is used as the diversity mode.
14.8.10 Defining ICIC Configurations ICIC (inter-cell interference coordination) configurations define the numbers of frequency blocks available in the ICIC parts of the frames when a cell uses static downlink or uplink ICIC based on fractional frequency reuse. To create a new ICIC configuration: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the LTE Network Settings folder. 3. In the LTE Network Settings folder, right-click ICIC Configurations. The context menu appears. 4. Select Open Table. The ICIC Configurations table appears. 5. In the ICIC Configurations table, each row describes an ICIC configuration. For the new ICIC configuration, enter: • • • • •
Name: The name of the ICIC configuration. Total number of frequency blocks: The total number of frequency blocks to which the ICIC configuration correspond. Group 0 frequency blocks: The frequency blocks assigned to the ICIC part of the frame for PSS ID 0. Group 1 frequency blocks: The frequency blocks assigned to the ICIC part of the frame for PSS ID 1. Group 2 frequency blocks: The frequency blocks assigned to the ICIC part of the frame for PSS ID 2. You can enter non-consecutive frequency block numbers separated with a comma, or you can enter a range of frequency blocks separating the first and last index with a hyphen (for example, entering "1-5" corresponds to "1, 2, 3, 4, 5").
6. Click the Close button (
) to close the ICIC Configurations table.
14.8.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.
1600
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
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 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 145. 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 1462) A coverage prediction (see "Studying Signal Level Coverage" on page 1463).
Atoll always takes shadowing into consideration when calculating a Monte Carlo simulations. Atoll uses the values defined for the model standard deviations per clutter class when calculating the signal level coverage predictions. Atoll uses the values defined for the C/I standard deviations per clutter class when calculating the interference- based coverage predictions. You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per Clutter Class" on page 1601.
14.8.11.1 Displaying the Shadowing Margins per Clutter Class To display the shadowing margins per clutter class: 1. Select the Network explorer. 2. Right-click the Predictions folder. The context menu appears. 3. Select Shadowing Margins from the context menu. The Shadowing Margins dialogue appears. 4. You can set the following parameters: • •
Cell edge coverage probability: Enter the probability of coverage at the edge of the cell. The value you enter in this dialogue is for information only. Standard deviation: Select the type of standard deviation to be used to calculate the shadowing margin: • •
Model: The model standard deviation. Atoll will display the shadowing margin of the signal level. C/I: The C/I standard deviation. Atoll will display the C/I shadowing margin.
5. Click Calculate. The calculated shadowing margin is displayed. 6. Click Close to close the dialogue.
14.8.12 Modelling Inter-technology Interference Analyses of LTE networks co-existing with other technology networks can be carried out in Atoll. Inter-technology interference may create considerable capacity reduction in an LTE network. Atoll can take into account interference from co-existing networks in Monte Carlo simulations and coverage predictions. The following inter-technology interference scenarios are modelled in Atoll: •
Interference received by mobiles on the downlink: Interference can be received by mobiles in an LTE network on the downlink from external base stations and mobiles in the vicinity. Interference from external base stations (also called downlink-to-downlink interference) might be created by the use of same or adjacent carriers, wideband noise (thermal noise, phase noise, modulation products, and spurious emissions), and intermodulation. In Atoll, you can define interference reduction factor (IRF) graphs for different technologies (GSM, UMTS, CDMA2000, etc.). These graphs are then used for calculating the interference from the external base stations on mobiles. This interference is taken into account in all downlink interference-based calculations. For more information, see "Defining Inter-technology IRFs" on page 1602. Interference from external mobiles (also called uplink-to-downlink interference) might be created by insufficient separation between the uplink frequency used by the external network and the downlink frequency used by your LTE network. Such interference may also come from co-existing TDD networks. The effect of this interference is modelled in Atoll using the Inter-technology DL noise rise definable for each cell in the LTE network. This noise rise is taken into account in all downlink interference-based calculations. For more information on the Inter-technology DL noise rise, see "Cell Description" on page 1441.
1601
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
Figure 14.80: 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) can be created by insufficient separation between the downlink frequency used by the external network and the uplink frequency used by your LTE network. Such interference may also come from co-existing TDD networks. Interference from external mobiles (also called uplink-to-uplink interference) can be created by the use of same or nearby frequencies for uplink in both networks. Unless the exact locations of external mobiles is known, it is not possible to separate interference received from external base stations and mobiles on the uplink. The effect of this interference is modelled in Atoll using the 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 Monte Carlo simulations but not in coverage predictions. For more information on the Inter-technology UL noise rise, see "Cell Description" on page 1441.
Figure 14.81: Interference received by cells on the uplink
14.8.12.1 Defining Inter-technology IRFs Interference received from external base stations on mobiles of your LTE network can be calculated by Atoll. Atoll uses the inter-technology interference reduction factor (IRF) graphs for calculating the interference levels. An IRF graph represents the variation of the Adjacent Channel Interference Ratio (ACIR) as a function of frequency separation. ACIR is determined from the Adjacent Channel Suppression (ACS) and the Adjacent Channel Leakage Ratio (ACLR) parameters as follows: 1 ACIR = ------------------------------------1 1 ------------- + ----------------ACS ACLR
An IRF depends on: • • • •
The interfering technology (GSM, UMTS, CDMA2000, etc.) The interfering carrier bandwidth (kHz) The interfered carrier bandwidth (kHz) The frequency offset between both carriers (MHz).
IRFs are used by Atoll to calculate the interference from external base stations only if the Atoll document containing the external base stations is linked to your LTE 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 1568. To define the inter-technology IRFs in the victim network: 1. Select the Parameters explorer. 2. Click the Expand button ( ) to expand the Radio Network Equipment folder. 3. In the Radio Network Equipment folder, right-click Inter-technology Interference Reduction Factors. The context menu appears.
1602
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
4. Select Open Table. The Inter-technology Interference Reduction Factors table appears. 5. In the table, enter one interference reduction factor graph per row. For each IRF graph, enter: • • • •
Technology: The technology used by the interfering network. Interferer bandwidth (kHz): 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): 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. i.
Enter the interference reduction factors in the Reduction (dB) column for different frequency separation, Freq. delta (MHz), values relative to the centre frequency of the channel (carrier) used in the main document. • •
Reduction values must be positive. If you leave reduction factors undefined, Atoll assumes there is no interference.
ii. When done, click OK. 6. Click the Close button (
) to close the Inter-technology Interference Reduction Factors table.
You can link more than one Atoll document with your main document following the procedure described in "Switching to Coplanning Mode" on page 1568. If the linked documents model networks using different technologies, you can define the interference reduction factors in your main document for all these technologies, and Atoll will calculate interference from all the external base stations in all the linked documents.
14.9 Tips and Tricks The following tips and tricks are described below: • • • • • • • • •
"Obtaining User Throughputs for All the Subscribers of a Subscriber List" on page 1603. "Working With User Densities Instead of User Profiles" on page 1604. "Bearer Selection Thresholds" on page 1604. "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1605. "Relation Between Bearer Efficiency And Spectral Efficiency" on page 1605. "Modelling VoIP Codecs" on page 1605. "Working with EARFCNs instead of Channel Numbers" on page 1606. "Modelling the Co-existence of Networks" on page 1606. "Displaying LTE Frame Details" on page 1607.
Obtaining User Throughputs for All the Subscribers of a Subscriber List This procedure is only recommended if you have a proper subscriber list and have complete knowledge of the services they use.
Atoll generates a realistic user distribution containing active and inactive users during Monte Carlo simulations. The status of these users is determined through the user’s service usage parameters defined in the user profile. In Atoll, subscribers in a subscriber list must have a user profile assigned to them in order to be taken into account in Monte Carlo simulations. In Monte Carlo simulations based on subscriber lists, Atoll determines active users from among the users listed in the subscriber list and carries out RRM and resource allocation for calculating user throughputs. If you wish to determine user throughputs for all the subscribers in a subscriber list, you can run a Monte Carlo simulation with the subscriber list as input after modifying the user profiles assigned to the subscribers such that the probability of activity for all the subscribers is 100 %. 1. Create a subscriber list with subscribers having an activity probability of 100%: a. Create as many user profiles as there are services used by the subscribers in the list. b. Assign only one service to each user profile. c. Assign the following service usage parameters to the user profiles that you create: i.
For Voice services, set:
• •
Calls/hour = 1. Duration (sec.) = 3600.
1603
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
ii. For Data services: • • •
Calls/hour = 1. UL volume (KBytes) = Service uplink average requested throughput x 3600/8. DL volume (KBytes) = Service downlink average requested throughput x 3600/8.
d. Assign these user profiles to subscribers in the subscriber list. 2. Create a Monte Carlo simulation based only on this subscriber list. The simulation results will contain all the subscribers in the subscriber list with their respective user throughputs determined by Atoll after the scheduling process. Working With User Densities Instead of User Profiles If you do not currently have reliable LTE multi-service traffic, you can provide Atoll with user density information per service, for example, traffic data from adapted GSM Erlang maps. In this case, you do not have to create user profiles. As well, Atoll does not have to determine the user activity probabilities to create traffic scenarios during simulations. The distribution of traffic during simulations will only depend on the user densities per service. If you know the user densities for each service, you can set user activity probabilities to 100 % in your LTE document, as shown below: 1. For Voice services, set: • •
Calls/hour = 1. Duration (sec.) = 3600.
2. For Data services: • • •
Calls/hour = 1. UL volume (KBytes) = Service uplink average requested throughput x 3600/8. DL volume (KBytes) = Service downlink average requested throughput x 3600/8.
The above settings will set the user activity probabilities to 100 %. If you create a traffic map based on environment classes, the user density values that you define in your environment classes will be the actual user densities. This means that, for X users/km² defined in the environment class for a given user profile, the Monte Carlo simulator will generate exactly X users/ km² for each service of the user profile. In this way, you can know beforehand the exact number of active users, and their services, generated during the simulations. This procedure should only be used when appropriate traffic data is not available. Bearer Selection Thresholds The default values of the bearer selection thresholds, the BLER quality graphs, and the bearer efficiency values in Atoll have been extracted from the 3GPP TR 36.942 V8.0.0 (see Figure 14.82). These values correspond to an ideal (AWGN) radio channel, and are too optimistic compared to actual radio channels. It is recommended to use more realistic values when available.
Figure 14.82: 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.
1604
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Calculating Bearer Selection Thresholds From Receiver Sensitivity Values You can convert the receiver sensitivity values, from your equipment data sheet, into bearer selection thresholds using the following conversion method: SF × NUsed CNR = RS + 114 – NF – 10 × Log ------------------------------ N Total
Where RS is the receiver sensitivity in dBm, NF is the noise figure of the receiver in dB, SF is the sampling frequency in MHz, N Used is the number of subcarriers corresponding to the number of frequency blocks, N Total is the total number of subcarriers, i.e., the FFT size. In the above explanation, the term receiver refers to the base station in uplink and to the mobile/user equipment in the downlink. Relation Between Bearer Efficiency And Spectral Efficiency Spectral efficiency of a modulation and coding scheme is defined as the number of useful bits that can be transmitted per second over 1 Hz wide channel. Spectral efficiency is hence given in terms of bps/Hz. In Atoll, the efficiency of bearers (modulation and coding schemes) are defined in the Radio Bearers table. The bearer efficiency is given in terms of bits/symbol. Remember that in Atoll symbol refers to one resource element, the data transmission unit which is 1 symbol duration long and 1 subcarrier width wide, as shown in Figure 14.83.
Figure 14.83: Symbol Bearer efficiency is similar to spectral efficiency. The only difference is in the units used. 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, let’s say that QPSK1/2 has a bearer efficiency of 1 bits/symbol. Here as well, the number of bits refers to useful data bits. The width of a subcarrier in LTE is ΔF = 15 kHz , 1 from which we can calculate the useful symbol duration as well: T U = ------= 66.67 μ sec . In one second, there can be ΔF
1 sec ⁄ 66.67 μ sec = 15000 symbol durations. If 15000 symbols are transmitted using QPSK1/2, this gives us a data rate of 15000 Symbols/sec × 1 bits/Symbol = 15000 bps , which is the data rate achievable using one subcarrier of 15 kHz. We can
find
the
spectral
efficiency
by
normalizing
the
data
rate
to
unit
bandwidth.
This
gives:
15000 bps/subcarrier ⁄ 15 kHz/subcarrier = 1 bps/Hz .
In order to compare equivalent quantities, we have ignored some system parameters, such as the cyclic prefix, and have considered that the entire frame is transmitted in one direction, uplink or downlink. Modelling VoIP Codecs VoIP codecs are application-layer elements in the OSI system model. Atoll models application throughputs using a throughput offset and a scaling factor with respect to the RLC layer throughputs. You can model different VoIP codecs by creating a new service for each VoIP codec, and setting the target throughput to the application throughput for the scheduler used. Here are two examples of the most common VoIP codecs, and how they can be modelled in Atoll: •
G.711 VoIP Codec
1605
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
The actual voice data rate needed by the G.711 codec is 64 kbps, but with the lower layer headers and other added bits, the needed RLC data rate could be between 66.4 and 107.2 kbps. In this example, we show how to model the codec with header bits that lead to 85.6 kbps RLC data rate. a. Create a new service with the following parameters: • • • • • • •
Name: VoIP (G.711) Type: Voice Min throughput demand (DL) and Min throughput demand (UL): 64 kbps Max throughput demand (DL) and Max throughput demand (UL): 64 kbps Average requested throughput (DL) and Average requested throughput (UL): 64 kbps Scaling factor: 74.77 % Offset: 0 kbps
b. Set the Target throughput for voice services to "2 - Application Throughput" for the scheduler being used. In this way, Atoll will allocate resources to the users of this service such that they get 64 kbps application throughput, and around 85.6 kbps of effective RLC throughput. •
G.729 VoIP Codec The actual voice data rate needed by the G.729 codec is 8 kbps, but with the lower layer headers and other added bits, the needed RLC data rate could be between 9.6 and 29.6 kbps. In this example, we show how to model the codec with header bits that lead to 29.6 kbps required data rate. a. Create a new service with the following parameters: • • • • • • •
Name: VoIP (G.729) Type: Voice Min throughput demand (DL) and Min throughput demand (UL): 8 kbps Max throughput demand (DL) and Max throughput demand (UL): 8 kbps Average requested throughput (DL) and Average requested throughput (UL): 8 kbps Scaling factor: 27.03 % Offset: 0 kbps
b. Set the Target throughput for voice services to "2 - Application Throughput" for the scheduler being used. In this way, Atoll will allocate resources to the users of this service such that they get 8 kbps application throughput, and around 29.6 kbps of effective RLC throughput. Working with EARFCNs instead of Channel Numbers In Atoll, carriers are assigned channel numbers in the frequency bands table. These channel numbers do not necessarily have to be unique, i.e., a channel number can be reused in different bands. The 3GPP defines unique EARFCNs (E-UTRA Absolute Radio Frequency Channel Numbers) for all the frequency bands. Each EARFCN has a fixed width of 100 kHz, whereas channels (or carriers) in Atoll can have different widths. If you want to work with EARFCNs instead of channel numbers, you can set EARFCNs as channel numbers in the frequency bands table similar to as shown in the example below: • • • • • •
Frequency band: 2110 FDD - 5 MHz (E-UTRA Band 1) Downlink EARFCN range: 0 - 599 Uplink EARFCN range: 18000 - 18599 First channel (EARFCN): 0 Last channel (EARFCN): 550 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 offset by 18000, so you can use either the downlink or the uplink EARFCNs as channel numbers in Atoll. Modelling the Co-existence of Networks In Atoll, you can study the effect of interference received by your network from other LTE networks. The interfering LTE network can be a different part of your own network, or a network belonging to another operator. To study interference from co-existing networks: 1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a Group of Base Stations" on page 1453. 2. For the interfering network’s transmitters, set the Transmitter type to Inter-network (Interferer only) as explained in "Transmitter Description" on page 1438. During calculations, Atoll will consider the transmitters of type Inter-network (Interferer only) when calculating interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interference.
1606
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network. If the interfering network is a part of your own network, this information would be readily available. However, if the interfering network belongs to another operator, the information available might not be accurate. Moreover, for other operators’ networks, and if the interfering networks use OFDM but are not LTE networks, their modelling will not be accurate using LTE transmitters and cells. The number of subcarriers used in the interfering networks might be very different. Displaying LTE Frame Details Atoll can calculate and display the numbers of resource elements corresponding to different LTE physical signals and logical channels in downlink and uplink. To calculate and list details about LTE frames: 1. Select the Network explorer. 2. Right-click the LTE Transmitters folder. The context menu appears. 3. Select Cells > Frame Details from the context menu. The Frame Details dialogue appears. The Frame Details command is also available in the context menu of a transmitter or a group of transmitters. The Frame Details dialogue lists only the cells belonging to the transmitter or folder from which it is selected. Filters are also taken into account. 4. Click the Downlink tab. 5. Under Display, you can select to display the Numbers of resource elements and the Percentages of resource elements belonging to the downlink physical signals and logical channels. 6. Click Calculate. Atoll calculates the numbers of resource elements corresponding to different parts of the downlink LTE frame for each listed cell. The following information is available: • •
Total: The total number of resource elements in the downlink subframes. RS: The number and percentage of resource elements used to transmit the cell specific reference signals. An average number of transmitted reference signals is considered in Atoll. More specifically, when four antenna ports are used, eight reference signals are transmitted on two antenna ports and four are transmitted on the other two antenna ports. In this case, Atoll considers an average of six transmitted reference signals per antenna port.
• • • • • •
SSS: 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. Unused: The number and percentage of resource elements not used for transmission.
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 displayed: • • • • •
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 1608. For more information on the LTE frame structure, see "The Global Network Settings" on page 1588.
1607
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
14.10 Glossary of LTE Terms Understanding the following terms and there use in Atoll is very helpful in understanding the LTE module: •
User: A general term that can also designate a subscriber, mobile, and receiver.
•
Subscriber: Users with fixed geographical coordinates.
•
Mobile: Users generated and distributed during simulations. These users have, among other parameters, defined services, terminal types, and mobility types assigned for the duration of the simulations.
•
Receiver: A probe mobile, with the minimum required parameters needed for the calculation of path loss, used for propagation loss and raster coverage predictions.
•
Radio Bearer: A Modulation and Coding Scheme (MCS) used to carry data over the channel.
•
Peak RLC Throughput: The maximum RLC layer throughput (user or channel) that can be achieved at a given location using the highest LTE bearer available. This throughput is the raw data rate without considering the effects of retransmission due to errors and higher layer coding and encryption.
•
Effective RLC Throughput: The net RLC layer throughput (user or channel) that can be achieved at a given location using the highest LTE bearer available computed taking into account the reduction of throughput due to retransmission due to errors.
•
Application Throughput: The application layer throughput (user or channel) that can be achieved at a given location using the highest LTE bearer available computed taking into account the reduction of throughput due to PDU/SDU header information, padding, encryption, coding, and other types of overhead.
•
Channel Throughputs: Peak RLC, effective RLC or application throughputs achieved at a given location using the highest LTE bearer available with the entire cell resources (downlink or uplink).
•
Allocated Bandwidth Throughputs: Uplink peak RLC, effective RLC or application throughputs achieved at a given location using the best possible LTE bearer with the number of subchannels calculated.
•
User Throughputs: Peak RLC, effective RLC or application throughputs achieved at a given location using the highest LTE bearer available with the amount of resources allocated to a user by the scheduler.
•
Traffic Loads: The uplink and downlink traffic loads are the percentages of the uplink and the downlink frames in use (allocated) to the traffic (mobiles) in the uplink and in the downlink, respectively.
•
Resources: In Atoll, the term "resource" is used to refer to the average number of resource units, expressed in percentage (as traffic loads, when the average is performed over a considerably long duration) of the total number of resource units in a superframe of 1 sec.
•
Uplink Noise Rise: Uplink noise rise is a measure of uplink interference with respect to the uplink noise: I UL + N UL NR UL = ------------------------ , or NR UL = 10 × Log ( I UL + N UL ) – 10 × Log ( N UL ) in dB. This parameter is one of the two N UL
methods in which uplink interference can be expressed with respect to the noise. The other parameter often used I I UL + N UL
UL - . Usually, the uplink load factor is kept as a instead of the uplink noise rise is the uplink load factor: L UL = ------------------------
linear value (in percentage) while the uplink noise rise is expressed in dB. The two parameters express exactly the same information, and can be inter-converted as follows: I I+N–N I I+N N I N N I I+N 1 ------------ = ---------------------- => ------------ = ------------ – ------------ => ------------ = 1 – ------------ => ------------ = 1 – ------------ => ------------ = --------------------I I+N I+N I+N I+N I+N I+N I+N I+N I+N N 1 – -----------I+N 1 => NR = -----------
1–L
The following table shows the relation between interference, load factor, and noise rise. Interference (I) 0 =N =9xN = 99 x N
Load Factor (%) 0 50 90 99
Noise Rise 1 2 10 100
Noise Rise (dB) 0 3.01 10 20
The reason why uplink interference is expressed in terms of noise rise (in dB) in Atoll instead of load factor (in percentage) is that the load factor varies somewhat exponentially with the increase in interference. •
1608
Frame: An LTE frame is 10 ms long. The duration of a frame is a system-level constant. Each frame comprises 10 1 mslong subframes, with each subframe containing 2 0.5 ms-long slots. Each slot can have 7 or 6 symbol durations for normal or extended cyclic prefix, respectively, and for a 15 kHz subcarrier width. A slot can have 3 symbol durations for extended cyclic prefix used with a 7.5 kHz subcarrier width. LTE includes specific frame structures for FDD and TDD
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
AT312_UM_E1
systems as shown in Figure 14.84. 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 14.84: 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 14.83.
•
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 14.85).
•
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 14.85) 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 14.85). 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.
Figure 14.85: LTE resource blocks •
LTE Logical Channels: LTE logical channels include (see Figure 14.86): • Broadcast Control Channel (BCCH) (DL): Carries broadcast control information. • Paging Control Channel (PCCH) (DL): Carries paging control information. • Common Control Channel (CCCH) (DL and UL): Carries common control information. • Dedicated Control Channel (DCCH) (DL and UL): Carries control information dedicated to users. • Dedicated Traffic Channel (DTCH) (DL and UL): Carries user traffic data. • Multicast Control Channel (MCCH) (DL): Carries multicast control information. • Multicast Traffic Channel (MTCH) (DL): Carries multicast traffic data.
•
LTE Transport Channels: LTE transport channels include (see Figure 14.86): • Broadcast Channel (BCH) (DL): Carries broadcast information. • Paging Channel (PCH) (DL): Carries paging information.
1609
Atoll 3.1.2 User Manual Chapter 14: LTE Networks
© Forsk 2012
•
• • • •
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 14.86): • 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 14.86: LTE logical, transport, and physical layer channels (DL: blue, UL: orange, DL or UL: green) •
Inter-cell interference coordination: It is a method of improving 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: •
•
1610
Static ICIC using Fractional Frequency Reuse (FFR): Static interference coordination is performed through fractional frequency planning. 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 carried out by the scheduler. 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.
Atoll 3.1.2 User Manual Index
AT312_UM_E1
Index
Symbols +MRC in Softer/Soft (CDMA) 967 +MRC in Softer/Soft (UMTS) 797
Numerics 2G network traffic, converting (CDMA) 913 2G network traffic, converting (GSM) 445 2G network traffic, converting (LTE) 1535 2G network traffic, converting (TD-SCDMA) 1089 2G network traffic, converting (UMTS) 332, 738 2G network traffic, converting (WiMAX) 1250 3-D antenna pattern defining attenuation 173 defining azimuth 173 defining tilt angle 173 importing 173 3GPP multi-RAT template 118
A acceptable noise rise margin, defining for EV-DO cells (CDMA) 818 ACP antenna azimuth, reconfiguration 225, 250, 254 antenna height, reconfiguration 225, 251, 254 antenna masking 227 antenna type, reconfiguration 225, 250, 254 antennas, AEDT 263 antennas, creating by pattern 263 antennas, electrical tilt, setting range 263 antennas, grouping automatically 265, 266 antennas, mechanical tilt, setting range 263 best server analysis predictions 282 candidates, creating 257 candidates, creating automatically 258 change analysis predictions 282 comments, adding to optimisation 267 computation zone, using 226 configuration, loading 270 configuration, saving 270 configuring 229 co-planning optimisation process, creating 1299, 1586 co-planning optimisation process, importing second technology 1299, 1586
co-planning optimisation process, second technology, importing 794, 964
co-planning optimisation setup, creating 794, 964 custom zones 236 default settings, configuring 231 default settings, storage 230 definition 225, 358, 581, 762, 933, 1270, 1555
electrical tilt, reconfiguration 225, 250, 254 EMF exposure 229 EMF exposure predictions 283 filtering zone, using 227 hot spot, using 226 hot spots, importing 236 indicators (CDMA) 933 indicators (GSM) 581 indicators (LTE) 1556 indicators, definition (UMTS) 762 indicators, definition (WiMAX) 1270 indoor coverage 227 iterations, defining number of 235 iterations, defining resolution 235 mechanical tilt, reconfiguration 225 multi-band antennas, defining 265 multi-layer networks, linking transmitters 251 objectives (CDMA) 933 objectives (GSM) 581 objectives (LTE) 1556 objectives (UMTS) 762 objectives (WiMAX) 1270 objectives, definition 226 optimisation parameters, defining 234 optimisation process, cost control 237 optimisation process, creating 233, 234 optimisation process, creating in co-planning 794, 964, 1299, 1585
optimisation process, EMF exposure 240 optimisation process, layers 235 optimisation process, multi-storey 239 optimisation process, running 234 optimisation process, site classes 238 optimisation process, zones 236 optimisation properties, changing 270 optimisation setup, running 270 optimisation, comparing 278 optimisation, deleting 270 optimisation, running saved 268 pilot power, reconfiguration 247 pilot power, reconfiguration (CDMA) 248 pilot power, reconfiguration (GSM) 248 pilot power, reconfiguration (UMTS) 248 pilot power, reconfiguration (WiMAX) 249 power (GSM), reconfiguration 247 power, reconfiguration 225 preamble power, reconfiguration 247 predictions, comparing 283 predictions, display properties 284 propagation model, not natively supported 228
1611
Atoll 3.1.2 User Manual Index
propagation models 227 propagation models, defining 230 propagation models, natively supported 228 propagation models, precalculated path loss matrices 230 propagation models, precalculated pathloss matrices 229 quality analysis predictions 282, 359, 582, 763, 935, 1272, 1557 quality indicators, definition 226 quality parameters (CDMA) 934 quality parameters (GSM) 582 quality parameters (LTE) 1556 quality parameters (UMTS) 359, 762 quality parameters (WiMAX) 1270 reconfiguration options 246 reconfiguration, importing parameters 250, 252 repeater amplifier gain, reconfiguration 255 results, viewing in histogram 286 results, viewing in map window 280 results, viewing in Properties dialogue 271 shadowing margin 227 site selection 225 site selection, defining 255 target, definition 226 total power, reconfiguration 247 traffic maps, using 227 weighting 245 zones, using 226 ACP coverage predictions exporting 285 active set conditions for entering (CDMA) 972 conditions for entering (UMTS) 805 defining size in terminals (CDMA) 868 defining size in terminals (UMTS) 686 displaying per simulation user (CDMA) 921 displaying per simulation user (UMTS) 748 size, used in predictions (CDMA) 867 size, used in predictions (UMTS) 685 threshold, defining in cells (UMTS) 634 active set analysis (CDMA) 880 active set analysis (UMTS) 696 activity status displaying traffic distribution by (LTE) 1545 displaying traffic distribution by (WiMAX) 1259 adaptive beam smart antenna modelling (TD-SCDMA) 1139 adaptive modulation and coding, see "fast link adaptation" adjacent channels definition (GSM) 457 AFP scope 489 antenna azimuth, reconfiguring with ACP 225, 250, 254 beamwidth, defining 172 changing azimuth on the map 42 changing relative position on the map 42 creating 171 electrical tilt, reconfiguring with ACP 225, 250, 254 fixing scale 175
1612
© Forsk 2012
gain 171 height, reconfiguring with ACP 225, 251, 254 importing 3-D patterns 173 importing Planet-format 173 mechanical tilt, reconfiguring with ACP 225 model, reconfiguring with ACP 225, 250, 254 pasting antenna pattern 171 pattern electrical tilt 171 smart, creating (LTE) 1597 smart, creating (WiMAX) 1313 smoothing vertical pattern 175 antenna patterns printing 88, 175 archiving all modifications to the database 127 only site data to the database 127 attenuation 3-D antenna pattern 173 audit of frequency allocation (TD-SCDMA) 1057 audit of inter-technology neighbour plan (CDMA) 962 audit of inter-technology neighbour plan (LTE) 1584 audit of inter-technology neighbour plan (TD-SCDMA) 1132 audit of inter-technology neighbour plan (UMTS) 305, 314, 792 audit of inter-technology neighbour plan (WiMAX) 1297 audit of neighbour allocation plan (CDMA) 895 audit of neighbour allocation plan (GSM) 434 audit of neighbour allocation plan (LTE) 1515 audit of neighbour allocation plan (TD-SCDMA) 1068 audit of neighbour allocation plan (UMTS) 718 audit of neighbour allocation plan (WiMAX) 1228 audit of physical cell ID plan (LTE) 1525 audit of PN offset plan (CDMA) 900 audit of preamble index plan (WiMAX) 1240 audit of scrambling code plan (TD-SCDMA) 1074 audit of scrambling code plan (UMTS) 724 automatic backup 129 configuring 130 recovering a backup 130 Automatic Cell Planning, see "ACP" azimuth 3-D antenna pattern 173 antenna, changing on the map 42
B backup 129 configuring 130 recovering a backup 130 base station assigning equipment (CDMA) 815 assigning equipment (GSM) 367 assigning equipment (TD-SCDMA) 983 assigning equipment (UMTS) 632 components of subsystem 176 copying into document (CDMA) 828 copying into document (GSM) 384 copying into document (LTE) 1453 copying into document (TD-SCDMA) 997
Atoll 3.1.2 User Manual Index
AT312_UM_E1
copying into document (UMTS) 292, 647 copying into document (WiMAX) 1165 creating (LTE) 1437 creating (Wi-Fi) 1334 creating (WiMAX) 1151 creating with template (CDMA) 820 creating with template (GSM) 377 creating with template (LTE) 1446 creating with template (TD-SCDMA) 989 creating with template (UMTS) 638 creating with template (WiMAX) 1159 definition (CDMA) 812 definition (GSM) 364, 365 definition (LTE) 1437 definition (TD-SCDMA) 980, 981 definition (UMTS) 291, 628, 629 definition (WiMAX) 1151 displaying information (CDMA) 829 displaying information (GSM) 384 displaying information (LTE) 1453 displaying information (TD-SCDMA) 997 displaying information (UMTS) 293, 648 displaying information (WiMAX) 1166 duplicating (GSM) 382 duplicating (LTE) 1451 duplicating (TD-SCDMA) 995 duplicating (UMTS) 646 duplicating (WiMAX) 1164 equipment, assigning (LTE) 1439 equipment, assigning (WiMAX) 1153 importing (CDMA) 828 importing (GSM) 384 importing (LTE) 1453 importing (TD-SCDMA) 997 importing (UMTS) 292, 647 importing (WiMAX) 1165 base station ID, see "BSID" baton handover coverage prediction (TD-SCDMA) 1051 BCCH displaying on transmitter (GSM) 576 BCMCS (CDMA) 818 BCMCS throughput (CDMA) 818 beamwidth defining antenna 172 bearer selection, HSDPA, explanation 1093 bearer selection, HSDPA, explanation (UMTS) 741 bearer, 1xEV-DO, see "1xEV-DO radio bearer" bearer, downgrading (UMTS) 744 bearer, HSDPA, see "HSDPA radio bearer" bearer, R99, see "R99 radio bearer" BER coverage prediction (CDMA) 875 BER coverage prediction (UMTS) 691 best bearer coverage prediction (LTE) 1495 best bearer coverage prediction (WiMAX) 1208 BLER coverage prediction (GSM) 564 BLER coverage prediction (UMTS) 691 BLER_DCH coverage prediction (CDMA) 875
Broadcast/Multicast Services, see "BCMS" BSIC displaying on transmitter (GSM) 576 domains, defining (GSM) 458 format, defining (GSM) 458 groups, defining (GSM) 458 BSID (WiMAX) 1155 BWA, definition (WiMAX) 1149
C C/(I+N) level coverage prediction (LTE) 1492 C/(I+N) level coverage prediction (WiMAX) 1205 C/I levels coverage prediction (GSM) 549 calculation defining Min. interferer reception threshold (CDMA) 967 defining Min. interferer reception threshold (TD-SCDMA) 1136 defining Min. P-CCPCH RSCP threshold 1137 defining Min. pilot RSCP threshold (CDMA) 967 defining Min.P-CCPCH RSCP threshold (TD-SCDMA) 1137 min. interferer reception threshold, defining (UMTS) 797 min. pilot RSCP threshold, defining (UMTS) 797 calculation process, explanation (CDMA) 846 calculation process, explanation (GSM) 402 calculation process, explanation (LTE) 1470 calculation process, explanation (TD-SCDMA) 1014 calculation process, explanation (UMTS) 665 calculation process, explanation (WiMAX) 1183 calculations 181 subscriber list (LTE) 1540 subscriber list (WiMAX) 1255 carrier types (TD-SCDMA) allocating per cell 1056 audit of allocation 1057 displaying coverage 1056 displaying master carrier on the map 1056 master carrier 1054 slave carrier 1054 standalone carrier 1054 CDMA Rho factor, transmitter equipment 177 CDMA2000 1xRTT 1xEV-DO template 118 cell creating (LTE) 1446 creating (TD-SCDMA) 989 creating (UMTS) 638 creating (WiMAX) 1159 creating 1xEV-DO (CDMA) 819 creating 1xRTT (CDMA) 819 definition (LTE) 1441 definition (Wi-Fi) 1334 definition (WiMAX) 1150, 1155 EV-DO parameters (CDMA) 816 modifying (LTE) 1446 modifying (TD-SCDMA) 989 modifying (UMTS) 638 modifying (WiMAX) 1159 modifying 1xEV-DO (CDMA) 819
1613
Atoll 3.1.2 User Manual Index
modifying 1xRTT (CDMA) 819 parameters (TD-SCDMA) 985 parameters (UMTS) 633 RTT parameters (CDMA) 816 setting as active (CDMA) 847 setting as active (TD-SCDMA) 1015 setting as active (UMTS) 666 updating load values with simulation (LTE) 1554 updating load values with simulation (WiMAX) 1268 updating values with simulation (CDMA) 929 updating values with simulation (TD-SCDMA) 1104 updating values with simulation (UMTS) 357, 757 cell type applying new (GSM) 376 creating (GSM) 601 definition (GSM) 600 examples (GSM) 602 cell-to-cell interference coverage prediction (TD-SCDMA) 1048 channel element calculation of consumption (UMTS) 740 consumption per site equipment-HSUPA radio bearer, defining (UMTS) 801 consumption per site equipment-R99 radio bearer, defining (UMTS) 801 defining consumption per site equipment-terminal (CDMA) 970 defining on forward link (CDMA) 813 defining on reverse link (CDMA) 813 downlink, defining (UMTS) 630 simulations (CDMA) 918 simulations (UMTS) 338, 745 uplink and downlink consumption (CDMA) 970 uplink and downlink consumption (UMTS) 800 uplink, defining (UMTS) 630 channels Find on Map, using with (GSM) 575 codec equipment codec mode adaptation thresholds, setting (GSM) 606 codec mode quality thresholds, setting (GSM) 607 creating (GSM) 606 modifying (GSM) 606 terminals, assigning to (GSM) 608 transmitters, assigning to (GSM) 608 codec equipment (GSM) 605 codec mode table, opening (GSM) 605 coding scheme table, opening 608 coding scheme throughput graphs displaying (GSM) 611 column headers formatting 73 columns changing width 73 displaying 74 freezing 75 hiding 74 moving 75
1614
© Forsk 2012
unfreezing 75 compressed mode (UMTS) 343, 685, 686, 749, 797 computation zone ACP 226 drawing 55 drawing (CDMA) 846 drawing (GSM) 402 drawing (LTE) 1470 drawing (TD-SCDMA) 1014 drawing (UMTS) 665 drawing (WiMAX) 1183 editing 61 explanation (CDMA) 841 explanation (GSM) 397 explanation (LTE) 1465 explanation (TD-SCDMA) 1010 explanation (UMTS) 294, 660 explanation (WiMAX) 1178 Fit to Map Window 56 Fit to Map Window (CDMA) 847 Fit to Map Window (GSM) 403 Fit to Map Window (LTE) 1471 Fit to Map Window (TD-SCDMA) 1015 Fit to Map Window (UMTS) 666 Fit to Map Window (WiMAX) 1184 importing 56 importing (CDMA) 847 importing (GSM) 403 importing (LTE) 1471 importing (TD-SCDMA) 1015 importing (UMTS) 666 importing (WiMAX) 1184 polygon, creating from 56 polygon, creating from (CDMA) 846 polygon, creating from (GSM) 403 polygon, creating from (LTE) 1471 polygon, creating from (TD-SCDMA) 1015 polygon, creating from (UMTS) 666 polygon, creating from (WiMAX) 1184 configuration loading ACP 270 saving ACP 270 Connection Properties 124 connection status displaying traffic distribution by (CDMA) 920 displaying traffic distribution by (LTE) 1545 displaying traffic distribution by (TD-SCDMA) 1096 displaying traffic distribution by (UMTS) 339 displaying traffic distribution by (WiMAX) 1259 traffic distribution, displaying by (UMTS) 747 constraint costs, defining PN offsets (CDMA) 897 constraint costs, defining scrambling code (TD-SCDMA) 1072 constraint costs, defining scrambling code(UMTS) 722 conventional beamformer modelling (LTE) 1597 conventional beamformer modelling (TD-SCDMA) 1140 conventional beamformer modelling (WiMAX) 1313 coordinate system 120
Atoll 3.1.2 User Manual Index
AT312_UM_E1
setting 121 coordinates, searching by 109 co-planning CDMA 947 co-planning mode, ending (CDMA) 965 co-planning mode, ending (LTE) 1586 co-planning mode, ending (TD-SCDMA) 1133 co-planning mode, ending (UMTS) 795 co-planning mode, ending (WiMAX) 1300 co-planning mode, switching to (CDMA) 948 co-planning mode, switching to (LTE) 1568 co-planning mode, switching to (TD-SCDMA) 1117 co-planning mode, switching to (UMTS) 776 co-planning mode, switching to (WiMAX) 1283 inter-technology exceptional pairs, displaying (CDMA) 953 inter-technology exceptional pairs, displaying (LTE) 1574 inter-technology exceptional pairs, displaying (TD-SCDMA) 1123 inter-technology exceptional pairs, displaying (UMTS) 317, 783 inter-technology exceptional pairs, displaying (WiMAX) 1289 inter-technology exceptional pairs, setting (CDMA) 953 inter-technology exceptional pairs, setting (LTE) 1573 inter-technology exceptional pairs, setting (TD-SCDMA) 1122 inter-technology exceptional pairs, setting (UMTS) 298, 307, 782 inter-technology exceptional pairs, setting (WiMAX) 1288 inter-technology exceptional pairs, setting on the map (CDMA) 954
inter-technology exceptional pairs, setting on the map (LTE) 1574
inter-technology exceptional pairs, setting on the map (TD-SCDMA) 1124 inter-technology exceptional pairs, setting on the map (UMTS) 319, 783
inter-technology exceptional pairs, setting on the map (WiMAX) 1289
inter-technology neighbour allocation (CDMA) 952 inter-technology neighbour allocation (LTE) 1573 inter-technology neighbour allocation (TD-SCDMA) 1122 inter-technology neighbour allocation (UMTS) 782 inter-technology neighbour allocation (WiMAX) 1288 inter-technology neighbours, allocating automatically (CDMA) 955
inter-technology neighbours, allocating automatically (LTE) 1575 inter-technology neighbours, allocating automatically (TD-SCDMA) 1125 inter-technology neighbours, allocating automatically (UMTS) 308, 784
inter-technology neighbours, allocating automatically (WiMAX) 1291
inter-technology neighbours, allocating per cell (CDMA) 958 inter-technology neighbours, allocating per cell (LTE) 1579 inter-technology neighbours, allocating per cell (TD-SCDMA) 1127
inter-technology neighbours, allocating per cell (UMTS) 302, 310, 787
inter-technology neighbours, allocating per cell (WiMAX) 1293 inter-technology neighbours, allocating using Neighbours table (CDMA) 959 inter-technology neighbours, allocating using Neighbours table (LTE) 1580
inter-technology neighbours, allocating using Neighbours table (TD-SCDMA) 1128 inter-technology neighbours, allocating using Neighbours table (UMTS) 303, 311, 788 inter-technology neighbours, allocating using Neighbours table (WiMAX) 1294 inter-technology neighbours, displaying (CDMA) 957 inter-technology neighbours, displaying (LTE) 1578 inter-technology neighbours, displaying (TD-SCDMA) 1127 inter-technology neighbours, displaying (UMTS) 315, 786 inter-technology neighbours, displaying (WiMAX) 1292 inter-technology neighbours, setting on the map (CDMA) 960 inter-technology neighbours, setting on the map (LTE) 1581 inter-technology neighbours, setting on the map (TD-SCDMA) 1129
inter-technology neighbours, setting on the map (UMTS) 316, 789
inter-technology neighbours, setting on the map (WiMAX) 1295 legend window, displaying (CDMA) 951 legend window, displaying (LTE) 1571 legend window, displaying (TD-SCDMA) 1121 legend window, displaying (UMTS) 779 legend window, displaying (WiMAX) 1286 LTE 1568 neighbours, configuring importance of (CDMA) 955 neighbours, configuring importance of (LTE) 1575 neighbours, configuring importance of (TD-SCDMA) 1124 neighbours, configuring importance of (UMTS) 784 neighbours, configuring importance of (WiMAX) 1290 networks, coverage areas, comparing (CDMA) 951 networks, coverage areas, comparing (LTE) 1572 networks, coverage areas, comparing (TD-SCDMA) 1121 networks, coverage areas, comparing (UMTS) 780 networks, coverage areas, comparing (WiMAX) 1287 networks, coverage areas, studying differences (CDMA) 952 networks, coverage areas, studying differences (LTE) 1573 networks, coverage areas, studying differences (TD-SCDMA) 1122
networks, coverage areas, studying differences (UMTS) 781 networks, coverage areas, studying differences (WiMAX) 1287 networks, coverage predictions, analysing (CDMA) 950 networks, coverage predictions, analysing (LTE) 1571 networks, coverage predictions, analysing (TD-SCDMA) 1120 networks, coverage predictions, analysing (UMTS) 779 networks, coverage predictions, analysing (WiMAX) 1286 networks, coverage predictions, updating (CDMA) 949 networks, coverage predictions, updating (LTE) 1570 networks, coverage predictions, updating (TD-SCDMA) 1119 networks, coverage predictions, updating (UMTS) 778 networks, coverage predictions, updating (WiMAX) 1285 networks, displaying both in same document (CDMA) 948 networks, displaying both in same document (LTE) 1569 networks, displaying both in same document (TD-SCDMA) 1118 networks, displaying both in same document (UMTS) 777 networks, displaying both in same document (WiMAX) 1284 TD-SCDMA 1117 UMTS 776
1615
Atoll 3.1.2 User Manual Index
unlinking documents (CDMA) 965 unlinking documents (LTE) 1586 unlinking documents (TD-SCDMA) 1133 unlinking documents (UMTS) 795 unlinking documents (WiMAX) 1300 WiMAX 1283 Cost-Hata propagation model 190 creating environment formula 191 defining default environment formula 191 modifying environment formula 191 taking diffraction into account 191 coverage by C/I based on test mobile data path (GSM) 590 coverage by signal level based on test mobile data path (GSM) 590 coverage of master carriers, displaying (TD-SCDMA) 1056 coverage of neighbours, displaying (CDMA) 890 coverage of neighbours, displaying (GSM) 430 coverage of neighbours, displaying (LTE) 1511 coverage of neighbours, displaying (TD-SCDMA) 1063 coverage of neighbours, displaying (UMTS) 713 coverage of neighbours, displaying (WiMAX) 1224 coverage prediction adding values to legend (CDMA) 852 adding values to legend (GSM) 414 adding values to legend (TD-SCDMA) 1024 analysing results (CDMA) 852 analysing results (LTE) 1477 analysing results (TD-SCDMA) 1024 analysing results (WiMAX) 1190 assigning a default propagation model 201, 845 based on drive test data path (LTE) 1564 based on drive test data path (WiMAX) 1279 based on test mobile data path (CDMA) 942 baton handover (TD-SCDMA) 1051 best bearer (LTE) 1495 best bearer (WiMAX) 1208 BLER (GSM) 564 by packet throughput per timeslot (GSM) 561 by transmitter (CDMA) 850 by transmitter (GSM) 406, 408, 409, 410, 411 by transmitter (LTE) 1474 by transmitter (TD-SCDMA) 1018 by transmitter (UMTS) 669 by transmitter (WiMAX) 1187 C/(I+N) level (LTE) 1492 C/(I+N) level (WiMAX) 1205 C/I levels (GSM) 549 calculating 217, 218 calculating several 217 cell-to-cell interference (TD-SCDMA) 1048 cloning 216 comparing (CDMA) 858 comparing (GSM) 418 comparing (LTE) 1483 comparing (TD-SCDMA) 1029 comparing (UMTS) 677 comparing (WiMAX) 1196 coverage by C/I based on test mobile data path (GSM) 590
1616
© Forsk 2012
coverage by signal level based on test mobile data path (GSM) 590
creating 215 creating from existing 216 default propagation model, assigning (GSM) 402 displaying results with tip text (CDMA) 853 displaying results with tip text (GSM) 414 displaying results with tip text (LTE) 1477 displaying results with tip text (TD-SCDMA) 1024 displaying results with tip text (WiMAX) 1190 downlink and uplink traffic channel (TD-SCDMA) 1041 downlink total noise (CDMA) 876 downlink total noise (TD-SCDMA) 1046 downlink total noise (UMTS) 692 duplicating 216 DwPTS signal quality (TD-SCDMA) 1039 effective service area (CDMA) 874 effective service area (LTE) 1497 effective service area (TD-SCDMA) 1045 effective service area (UMTS) 296, 690 effective service area (WiMAX) 1210 effective signal (LTE) 1489 effective signal (WiMAX) 1202 exporting in user configuration 220 exporting results 67 filtering base stations studied by computation zone (UMTS) 656 filtering base stations studied by filter (UMTS) 656 forcing calculation 218 forward link EV-DO throughput (CDMA) 872 geographic export zone, defining 59 geographic export zone, defining (CDMA) 882 geographic export zone, defining (GSM) 422 geographic export zone, defining (LTE) 1504 geographic export zone, defining (UMTS) 701 geographic export zone, defining (WiMAX) 1217 geographic exportt zone, defining (TD-SCDMA) 1054 GPRS/EGPRS coding schemes (GSM) 558, 569 handoff status (CDMA) 879 handover status (UMTS) 695 histogram, viewing (CDMA) 857 histogram, viewing (GSM) 418 histogram, viewing (LTE) 1482 histogram, viewing (TD-SCDMA) 1028 histogram, viewing (UMTS) 676 histogram, viewing (WiMAX) 1195 HSDPA 1052 HSDPA (UMTS) 697 HSUPA (UMTS) 700 legend, adding values to (LTE) 1477 legend, adding values to (UMTS) 672 legend, adding values to (WiMAX) 1190 locking coverage predictions 218, 219 network capacity (TD-SCDMA) 1080 new 215 on interfered zones (GSM) 552 on overlapping zones (CDMA) 851 on overlapping zones (GSM) 412
Atoll 3.1.2 User Manual Index
AT312_UM_E1
on overlapping zones (LTE) 1476 on overlapping zones (WiMAX) 1189 on P-CCPCH pollution (TD-SCDMA) 1020 overlapping zones (UMTS) 670 pilot pollution (CDMA) 877 pilot pollution (UMTS) 693 pilot reception analysis (Ec/I0) based on test mobile data path (CDMA) 942 pilot reception analysis (Ec/I0) based on test mobile data path (UMTS) 771 pilot signal quality (CDMA) 870 pilot signal quality (TD-SCDMA) 1038 pilot signal quality (UMTS) 687 PN offset interference zone (CDMA) 902 preamble analysis based on drive test data path (WiMAX) 1279 printing results (CDMA) 882 printing results (GSM) 422 printing results (LTE) 1504 printing results (TD-SCDMA) 1054 printing results (UMTS) 701 printing results (WiMAX) 1217 quality indicator (CDMA) 875 quality indicator (LTE) 1501 quality indicator (UMTS) 691 quality indicator (WiMAX) 1214 report, displaying (CDMA) 855 report, displaying (GSM) 416 report, displaying (LTE) 1480 report, displaying (TD-SCDMA) 1026 report, displaying (UMTS) 674 report, displaying (WiMAX) 1193 report, displaying using focus zone 56 report, displaying using focus zone (CDMA) 854 report, displaying using focus zone (GSM) 415 report, displaying using focus zone (LTE) 1479 report, displaying using focus zone (TD-SCDMA) 1025 report, displaying using focus zone (UMTS) 673 report, displaying using focus zone (WiMAX) 1192 report, displaying using hot spot (TD-SCDMA) 1025 report, displaying using hot spot (UMTS) 673 report, displaying using hot spot zone 56 report, displaying using hot spot zone (CDMA) 854 report, displaying using hot spot zone (GSM) 415 report, displaying using hot spot zone (LTE) 1479 report, displaying using hot spot zone (WiMAX) 1192 report, exporting (CDMA) 856 report, exporting (GSM) 417 report, exporting (LTE) 1482 report, exporting (TD-SCDMA) 1028 report, exporting (UMTS) 675 report, exporting (WiMAX) 1195 restricting base stations studied by computation zone (CDMA) 837
restricting base stations studied by computation zone (GSM) 393 restricting base stations studied by computation zone (LTE) 1462 restricting base stations studied by computation zone (TD-SCDMA) 1006
restricting base stations studied by computation zone (UMTS) 294
restricting base stations studied by computation zone (WiMAX) 1175
restricting base stations studied by filter (CDMA) 836 restricting base stations studied by filter (GSM) 393 restricting base stations studied by filter (LTE) 1461 restricting base stations studied by filter (TD-SCDMA) 1006 restricting base stations studied by filter (UMTS) 294 restricting base stations studied by filter (WiMAX) 1174 restricting base stations studied by filtering (TD-SCDMA) 1006 results, analysing (GSM) 413 results, analysing (UMTS) 671 results, displaying with tip text (UMTS) 672 results, exporting (CDMA) 882 results, exporting (GSM) 422 results, exporting (LTE) 1505 results, exporting (TD-SCDMA) 1054 results, exporting (UMTS) 701 results, exporting (WiMAX) 1217 RSCP UpPCH (TD-SCDMA) 1022 scrambling code interference zone (TD-SCDMA) 1077 scrambling code interference zone (UMTS) 727 service area (C/I) (TD-SCDMA) 1043 service area (Eb/Nt) (TD-SCDMA) 1043 service area (Eb/Nt) downlink based on test mobile data path (CDMA) 942 service area (Eb/Nt) downlink based on test mobile data path (UMTS) 772 service area (Eb/Nt) downlink or uplink (CDMA) 871 service area (Eb/Nt) downlink or uplink (UMTS) 688 service area (Eb/Nt) reverse link for EV-DO (CDMA) 873 service area (Eb/Nt) uplink based on test mobile data path (CDMA) 943 service area (Eb/Nt) uplink based on test mobile data path (UMTS) 772 service area analysis (LTE) 1495 service area analysis (WiMAX) 1208 signal level - single station (CDMA) 839 signal level - single station (GSM) 395 signal level - single station (LTE) 1463 signal level - single station (TD-SCDMA) 1008 signal level - single station (UMTS) 658 signal level - single station (WiMAX) 1176 signal level (CDMA) 848 signal level (GSM) 404 signal level (LTE) 1472 signal level (TD-SCDMA) 1017, 1021 signal level (UMTS) 667 signal level (WiMAX) 1185 simulation results, based on (UMTS) 761 simulation results, using (CDMA) 932 statistics, viewing (CDMA) 857 statistics, viewing (GSM) 418 statistics, viewing (LTE) 1482 statistics, viewing (TD-SCDMA) 1028 statistics, viewing (UMTS) 676
1617
Atoll 3.1.2 User Manual Index
statistics, viewing (WiMAX) 1195 stopping calculation 218 template, saving as 220 test mobile data path, based on (GSM) 590 test mobile data path, based on (UMTS) 771 throughput (LTE) 1498 throughput (WiMAX) 1211 tip text, comparing coverage predictions with (CDMA) 951 tip text, comparing coverage predictions with (LTE) 1572 tip text, comparing coverage predictions with (TD-SCDMA) 1121 tip text, comparing coverage predictions with (UMTS) 779 tip text, comparing coverage predictions with (WiMAX) 1287 UpPCH interference (TD-SCDMA) 1049 using simulation results (LTE) 1555 using simulation results (TD-SCDMA) 1107 using simulation results (WiMAX) 1269 coverage predictions 215 cursors 65 CW Measurement Analysis Tool printing data 88 CW measurements drive test data path, generating from (LTE) 1567 drive test data path, generating from (TD-SCDMA) 1116 drive test data path, generating from (WiMAX) 1282 test mobile data path, generating from (CDMA) 946 test mobile data path, generating from (GSM) 594, 595 test mobile data path, generating from (UMTS) 775 cyclic prefix ratio (LTE) 1588 cyclic prefix ratio (WiMAX) 1301
D Data Rate Control, see "DRC" data tables adding a field 71 changing column width 73 changing row height 73 copying data 77 deleting a field 72 displaying columns 74 editing 76 exporting data 80 filtering 93 filtering by selection 95 filtering by several criteria 96 filtering, examples 98 find text 79 formatting column headers 73 formatting table columns 73 freezing columns 75 hiding columns 74 importing data 82 moving columns 75 opening 70 opening record properties from table 72 pasting data 77 printing 84 replace text 79
1618
© Forsk 2012
restoring after filtering 97 sorting 93 sorting by one column 94 sorting by several columns 94 unfreezing columns 75 viewing properties 70 XML files, exporting to 83 XML files, importing from 83 database archiving all modifications 127 archiving only site data 127 connecting to 124 Connection Properties 124 creating a document from 123 refreshing document 126 resolving data conflicts 127 working with 122 defining 214, 221 definition (Wi-Fi) 1333 defraction smoothing vertical antenna pattern 175 display changing properties 43 defining display type 44 display type, automatic 45 display type, discrete values 44 display type, unique 44 display type, value intervals 44 display coordinate system 120 display resolution (CDMA) 839 display resolution (GSM) 395 display resolution (TD-SCDMA) 1008 display resolution (UMTS) 659 Distance Measurement tool 52 diversity reception (TD-SCDMA) 1144 reception (UMTS) 641, 802 transmission (TD-SCDMA) 1144 transmission (UMTS) 641, 802 document creating from database 117, 123 creating from template 117, 118 geographic data 117 information needed to create 117 radio data 117 radio equipment 117 refreshing from the database 126 setting basic parameters 120 document templates, see "templates" domains, creating physical cell ID (LTE) 1519 domains, creating preamble index (WiMAX) 1232 domains, creating scrambling code (TD-SCDMA) 1070 domains, creating scrambling code(UMTS) 721 downgrading bearer (UMTS) 744 downlink total noise coverage prediction (CDMA) 876 downlink total noise coverage prediction (TD-SCDMA) 1046 downlink total noise coverage prediction (UMTS) 692
AT312_UM_E1
downlink total power, setting (UMTS) 682 downlink traffic channel coverage prediction (TD-SCDMA) 1041 downlink traffic power, setting (TD-SCDMA) 1033 DRC error rate (CDMA) 818 drive test data analysis tool exporting (LTE) 1567 exporting (TD-SCDMA) 1117 exporting (WiMAX) 1282 printing (LTE) 1567 printing (TD-SCDMA) 1117 printing (WiMAX) 1282 drive test data path analysing variations 1114 analysing variations (LTE) 1565 analysing variations (WiMAX) 1280 exporting (LTE) 1567 exporting (TD-SCDMA) 1116 exporting (WiMAX) 1282 exporting to CW measurements (LTE) 1567 exporting to CW measurements (TD-SCDMA) 1116 exporting to CW measurements (WiMAX) 1282 extracting a field for a transmitter (LTE) 1565 extracting a field for a transmitter (TD-SCDMA) 1114 extracting a field for a transmitter (WiMAX) 1280 filtering out points (LTE) 1562 filtering out points (TD-SCDMA) 1112 filtering out points (WiMAX) 1276 importing (LTE) 1558 importing (TD-SCDMA) 1108 importing (WiMAX) 1272 refresh geo data (LTE) 1563 Refresh Geo Data (TD-SCDMA) 1112 refresh geo data (WiMAX) 1277 using for preamble analysis (WiMAX) 1279 using in coverage prediction (LTE) 1564 using in coverage prediction (WiMAX) 1279 DTM maps representing different areas 156 dual-band network, creating (CDMA) 829 dual-band network, creating (TD-SCDMA) 998 dual-band network, creating (UMTS) 648 DwPTS signal quality coverage prediction (TD-SCDMA) 1039
E Ec/I0 threshold (UMTS) 685 effective service area coverage prediction (CDMA) 874 effective service area coverage prediction (LTE) 1497 effective service area coverage prediction (TD-SCDMA) 1045 effective service area coverage prediction (UMTS) 296, 690 effective service area coverage prediction (WiMAX) 1210 effective signal coverage prediction (LTE) 1489 effective signal coverage prediction (WiMAX) 1202 EMF exposure ACP, studying with 229 environment creating (CDMA) 907 creating (GSM) 440 creating (LTE) 1529
Atoll 3.1.2 User Manual Index
creating (TD-SCDMA) 1084 creating (UMTS) 327, 732 creating (WiMAX) 1244 modifying (CDMA) 907 modifying (GSM) 440 modifying (LTE) 1529 modifying (TD-SCDMA) 1084 modifying (UMTS) 327, 732 modifying (WiMAX) 1244 equipment creating (LTE) 1592 creating (WiMAX) 1306 modifying (LTE) 1592 modifying (WiMAX) 1306 Equipment Specifications dialogue (CDMA) 815 Equipment Specifications dialogue (GSM) 367 Equipment Specifications dialogue (LTE) 1439 Equipment Specifications dialogue (TD-SCDMA) 983 Equipment Specifications dialogue (UMTS) 632 Equipment Specifications dialogue (WiMAX) 1153 equipment, repeater, see "repeater equipment" Erceg-Greenstein (SUI) propagation model 193 assigning environment formulas 194 creating environment formula 194 defining default environment formula 194 modifying environment formula 194 taking diffraction into account 194 EV-DO acceptable noise rise margin, defining (CDMA) 818 active set size on reverse link on terminal (CDMA) 868 application throughput, defining for EV-DO Rev. 0 (CDMA) 864 application throughput, defining for EV-DO Rev. A (CDMA) 865 BCMCS throughput, defining (CDMA) 818 body loss, defining for EV-DO Rev. 0 (CDMA) 865 body loss, defining for EV-DO Rev. A (CDMA) 865 carrier type, defining globally (CDMA) 967 carrier type, defining in cell (CDMA) 816 carriers, parameters for (CDMA) 818 data rates, available (CDMA) 968 DRC error rate, defining (CDMA) 818 FCH active set size on terminal (CDMA) 868 forward link radio bearer index 969 forward link radio bearer, defining 969 forward link throughput, studying (CDMA) 872 handoff status coverage prediction (CDMA) 879 idle power gain, defining (CDMA) 818 max channel elements per carrier, equipment (CDMA) 813 max rate = f/C/1), defining for mobility (CDMA) 867 maximum number of users per cell, defining (CDMA) 818 maximum power transmitted, defining (CDMA) 818 maximum UL load factor, defining (CDMA) 818 min. Ec/Nt (UL), defining for mobility (CDMA) 867 mobility type parameters 867 MUG table, defining (CDMA) 818 noise rise threshold, defining (CDMA) 818 pilot pollution, calculating (CDMA) 877 point analysis 837
1619
Atoll 3.1.2 User Manual Index
power control simulation algorithm 916 preferred carrier, defining for EV-DO Rev. 0 (CDMA) 864 preferred carrier, defining for EV-DO Rev. A (CDMA) 865 priority, defining for EV-DO Rev. 0 (CDMA) 864 priority, defining for EV-DO Rev. A (CDMA) 865 rate control, using to study capacity (CDMA) 904 rate probabilities UL, defining for EV-DO Rev. 0 (CDMA) 864 rate probabilities UL, defining for EV-DO Rev. A (CDMA) 865 Rev.0 reverse link data rates 863 reverse link power control 915 reverse link radio bearer index 969 reverse link radio bearer, defining 969 service area (Eb/Nt) reverse link, studying (CDMA) 873 service parameters, EV-DO Rev. 0-specific (CDMA) 864 service parameters, EV-DO Rev. A-specific (CDMA) 865 service parameters, EV-DO-specific (CDMA) 863 simulation results, cells (CDMA) 923 simulation results, maximum number of channel elements per carrier (CDMA) 922 simulation results, mobiles (CDMA) 925 simulation results, number of channel elements (CDMA) 922 simulation results, number of channel elements due to SHO overhead (CDMA) 922 simulation results, rejected users due to EV-DO resources saturation (CDMA) 924, 928 terminal options, EV-DO Rev. 0-specific (CDMA) 869 terminal options, EV-DO Rev. A-specific (CDMA) 869 terminal parameters, EV-DO Rev. 0-specific (CDMA) 867 terminal parameters, EV-DO Rev. A-specific (CDMA) 867 timeslots dedicated to BCMCS (CDMA) 818 timeslots dedicated to control channels (CDMA) 818 total transmitted power on DL, defining (CDMA) 818 transition flag in traffic simulations, assigned 915 UL load factor, defining (CDMA) 818 UL throughput due to TCP acknowledgement, defining for EV-DO Rev. 0 (CDMA) 865 EV-DO Rev. A forward link radio bearer defining (CDMA) 969 EV-DO Rev. A reverse link radio bearer defining (CDMA) 969 exceptional pairs inter-technology, displaying (CDMA) 953 inter-technology, displaying (LTE) 1574 inter-technology, displaying (TD-SCDMA) 1123 inter-technology, displaying (UMTS) 317, 783 inter-technology, displaying (WiMAX) 1289 inter-technology, setting (CDMA) 953 inter-technology, setting (LTE) 1573 inter-technology, setting (TD-SCDMA) 1122 inter-technology, setting (UMTS) 298, 307, 782 inter-technology, setting (WiMAX) 1288 inter-technology, setting on the map (CDMA) 954 inter-technology, setting on the map (LTE) 1574 inter-technology, setting on the map (TD-SCDMA) 1124 inter-technology, setting on the map (UMTS) 319, 783 inter-technology, setting on the map (WiMAX) 1289 neighbour, defining (CDMA) 883
1620
© Forsk 2012
exceptional pairs, defining neighbour (GSM) 423 exceptional pairs, defining neighbour (LTE) 1505 exceptional pairs, defining neighbour (TD-SCDMA) 1058 exceptional pairs, defining neighbour (UMTS) 706 exceptional pairs, defining neighbour (WiMAX) 1218 exceptional pairs, defining scrambling code (CDMA) 897 exceptional pairs, defining scrambling code (TD-SCDMA) 1071 exceptional pairs, defining scrambling code (UMTS) 721 experience matrix, see "separation rules" explorer window 35, 36 Geo explorer 36 layers 39 Network explorer 36 Parameters explorer 36 extended cell defining (GSM) 612
F fast link adaptation (TD-SCDMA) 1093 fast link adaptation (UMTS) 741 feeder assigning (CDMA) 815 assigning (GSM) 367 assigning (TD-SCDMA) 983 assigning (UMTS) 632 defining cables 176 defining length (CDMA) 815 defining length (TD-SCDMA) 983 length, defining (GSM) 368 length, defining (LTE) 1439 length, defining (UMTS) 632 length, defining (WiMAX) 1153 feeder, assigning (LTE) 1439 feeder, assigning (WiMAX) 1153 FER coverage prediction (CDMA) 875 FER coverage prediction (UMTS) 691 field adding to a table 71 deleting from a table 72 filter site list, using for 105 transmitter list, using for 105 filtering data tables by selection 95 data tables by several criteria 96 examples 98 restoring after filtering 97 using a polygon 54, 107 with views 107 filtering zone deleting 59 drawing 54 Fit to Map Window 55 importing 55 polygon, creating from 55 find in data tables 79
Atoll 3.1.2 User Manual Index
AT312_UM_E1
Find on Map 108 scrambling codes, displaying with (UMTS) 725 searching by coordinates 109 searching by text property 109 using to display channel reuse (GSM) 575 using to display frequencies (LTE) 1523 using to display frequencies (WiMAX) 1237 using to display physical cell IDs (LTE) 1523 using to display PN offsets (CDMA) 901 using to display preamble indexes (WiMAX) 1237 using to display scrambling codes (TD-SCDMA) 1075 focus zone coverage prediction report, using to display (UMTS) 673 creating 56 creating (CDMA) 854 creating (GSM) 415 creating (LTE) 1479 creating (TD-SCDMA) 1026 creating (UMTS) 673 creating (WiMAX) 1192 editing 61 explanation 56 explanation (CDMA) 854 explanation (GSM) 415 explanation (TD-SCDMA) 1025 explanation (UMTS) 673 Fit to Map Window 57 Fit to Map Window (CDMA) 854 Fit to Map Window (GSM) 415 Fit to Map Window (LTE) 1480 Fit to Map Window (TD-SCDMA) 1026 Fit to Map Window (UMTS) 674 Fit to Map Window (WiMAX) 1193 importing 57 importing (CDMA) 854 importing (GSM) 415 importing (LTE) 1480 importing (TD-SCDMA) 1026 importing (UMTS) 674 importing (WiMAX) 1193 polygon, creating from 57 polygon, creating from (CDMA) 854 polygon, creating from (GSM) 415 polygon, creating from (LTE) 1480 polygon, creating from (TD-SCDMA) 1026 polygon, creating from (UMTS) 673 polygon, creating from (WiMAX) 1193 population statistics (CDMA) 856 population statistics (GSM) 417 population statistics (LTE) 1481 population statistics (TD-SCDMA) 1028 population statistics (UMTS) 675 population statistics (WiMAX) 1194 using to display coverage prediction report 56 using to display coverage prediction report (CDMA) 854 using to display coverage prediction report (GSM) 415 using to display coverage prediction report (TD-SCDMA) 1025
folder configuration 105 applying a saved configuration 105 creating 105 deleting 106 exporting 106 importing 106 reapplying current configuration 106 forward link radio bearer index, EV-DO 969 forward link radio bearer, EV-DO, defining 969 forward link total power, setting (CDMA) 862 frame configuration creating (WiMAX) 1304 frame configuration (WiMAX) 1156, 1304 Frame details (LTE) 1607 frame duration (LTE) 1590 frame duration (WiMAX) 1301 frequencies allocating manually (LTE) 1521 allocating manually (WiMAX) 1234 automatically allocating (LTE) 1520 automatically allocating (WiMAX) 1233 displaying allocation (LTE) 1523 displaying allocation (WiMAX) 1237 displaying on transmitter (LTE) 1524 displaying on transmitter (WiMAX) 1238 grouping transmitters by (GSM) 577 grouping transmitters by (LTE) 1524 grouping transmitters by (WiMAX) 1239 using Find on Map with (LTE) 1523 using Find on Map with (WiMAX) 1237 frequencies (TD-SCDMA) allocating automatically 1055 displaying on the map 1056 frequency allocation displaying on transmitter (GSM) 576 frequency bands defining (CDMA) 966 defining (GSM) 456 defining (LTE) 1587 defining (TD-SCDMA) 982, 1134 defining (UMTS) 631, 796 defining (WiMAX) 1300 frequency domains defining (GSM) 457 frequency groups defining (GSM) 457 frequency, planning (TD-SCDMA) 1055
G gain defining antenna 171 Geo explorer 35, 36 geographic export zone creating 59 creating (CDMA) 882 creating (GSM) 422 creating (LTE) 1504
1621
Atoll 3.1.2 User Manual Index
creating (TD-SCDMA) 1054 creating (UMTS) 701 creating (WiMAX) 1217 Fit to Map Window 60 importing 60 polygon, creating from 60 global network settings modifying (CDMA) 968 modifying (TD-SCDMA) 1137 global network settings (CDMA) 967 global network settings (TD-SCDMA) 1135 global network settings (UMTS) 796 global scaling factor (CDMA) 931 global scaling factor (GSM) 449 global scaling factor (LTE) 1555 global scaling factor (TD-SCDMA) 1107 global scaling factor (UMTS) 358, 760 global scaling factor (WiMAX) 1269 global transmitter parameters modifying (UMTS) 797 GPRS/EGPRS coding schemes coverage prediction (GSM) 558, 569 GPRS/EGPRS equipment coding scheme thresholds, adapting (GSM) 611 coding scheme throughput graphs, displaying (GSM) 611 terminals, assigning to (GSM) 610 transmitters, assigning to (GSM) 610 grid of beams (GOB) smart antenna model (TD-SCDMA) 1138 grid of beams (GOB), creating (TD-SCDMA) 1138 grid of beams (GOB), import format (TD-SCDMA) 1139 grid of beams (GOB), importing (TD-SCDMA) 1139 grouping 89 by a property 89, 90 by several properties 90 examples 91 with views 107 groups, creating physical cell ID (LTE) 1519 groups, creating preamble index (WiMAX) 1232 groups, creating scrambling code (TD-SCDMA) 1070 groups, creating scrambling code (UMTS) 721 GSM/GPRS/EGPRS template 118
H handoff status coverage prediction (CDMA) 879 displaying traffic distribution by (CDMA) 919 handover status coverage prediction (UMTS) 695 displaying traffic distribution by (TD-SCDMA) 1096 traffic distribution, displaying by (UMTS) 746 HCS layers defining (GSM) 596 selecting (GSM) 366 hexagonal design definition (CDMA) 820 definition (GSM) 378 definition (LTE) 1447 definition (TD-SCDMA) 990
1622
© Forsk 2012
definition (UMTS) 639 definition (WiMAX) 1160 hiding (CDMA) 821 histogram coverage prediction, viewing (UMTS) 676 PN offsets (CDMA) 902 results, viewing ACP 286 scrambling code (UMTS) 727 histogram, physical cell ID 1525 histogram, preamble index 1240 histogram, scrambling code 1076 histogram, viewing coverage prediction (CDMA) 857 histogram, viewing coverage prediction (GSM) 418 histogram, viewing coverage prediction (LTE) 1482 histogram, viewing coverage prediction (TD-SCDMA) 1028 histogram, viewing coverage prediction (WiMAX) 1195 hopping gain advanced modelling (GSM) 620 hot spot coverage prediction report, using to display (UMTS) 673 creating (UMTS) 673 Fit to Map Window (UMTS) 674 importing (UMTS) 674 population statistics (UMTS) 675 hot spot zone creating 56 creating (CDMA) 854 creating (GSM) 415 creating (LTE) 1479 creating (TD-SCDMA) 1026 creating (WiMAX) 1192 editing 61 explanation 56 explanation (CDMA) 854 explanation (GSM) 415 explanation (TD-SCDMA) 1025 Fit to Map Window 57 Fit to Map Window (CDMA) 854 Fit to Map Window (GSM) 415 Fit to Map Window (LTE) 1480 Fit to Map Window (TD-SCDMA) 1026 Fit to Map Window (WiMAX) 1193 importing 57 importing (CDMA) 854 importing (GSM) 415 importing (LTE) 1480 importing (TD-SCDMA) 1026 importing (WiMAX) 1193 population statistics (CDMA) 856 population statistics (GSM) 417 population statistics (LTE) 1481 population statistics (TD-SCDMA) 1028 population statistics (WiMAX) 1194 using to display coverage prediction report 56 using to display coverage prediction report (CDMA) 854 using to display coverage prediction report (GSM) 415 using to display coverage prediction report (TD-SCDMA) 1025
Atoll 3.1.2 User Manual Index
AT312_UM_E1
HSDPA activating (TD-SCDMA) 986 activating (UMTS) 635 bearer selection, explanation 1093 bearer selection, explanation (UMTS) 741 configuring (TD-SCDMA) 986 configuring (UMTS) 635 coverage prediction 1052 coverage prediction (UMTS) 697 editing user equipment category 1145 scheduler algorithm 636 scheduler algorithm (TD-SCDMA) 986 service, enabling (UMTS) 682 template 118 terminal, enabling 323 terminal, enabling (UMTS) 685 user equipment category 687, 1037 user equipment category, editing (UMTS) 803 HSDPA radio bearer defining (TD-SCDMA) 1143 defining (UMTS) 799 HSN domains, defining (GSM) 459 groups, defining (GSM) 459 HSPA activating 994 activating (TD-SCDMA) 986 configuring 994 configuring (TD-SCDMA) 986 HSPA+ activating (UMTS) 635, 643 HSUPA activating (TD-SCDMA) 986 activating (UMTS) 635, 643 configuring (TD-SCDMA) 986 configuring (UMTS) 636 coverage prediction (UMTS) 700 editing user equipment category 1145 service, enabling (UMTS) 682 template 118 terminal, enabling 323 terminal, enabling (UMTS) 685 user equipment category 1037 user equipment category, editing (UMTS) 803 HSUPA radio bearer defining (TD-SCDMA) 1143 defining (UMTS) 799
I ICIC configuration creating (LTE) 1600 ICIC configuration (LTE) 1600 idle power gain, defining for EV-DO cells (CDMA) 818 indoor coverage ACP 227 activating in AS analysis (CDMA) 880, 903 activating in coverage prediction (CDMA) 840
activating in coverage prediction (TD-SCDMA) 1009, 1017, 1019, 1020, 1022, 1023, 1077
activating in point analysis (CDMA) 838, 854 activating in point analysis (GSM) 394, 415 activating in simulation (CDMA) 874, 876 activating in simulation (UMTS) 692 AS analysis, activating in (UMTS) 696 AS analysis, activating in(UMTS) 728 calculating 214, 221 coverage prediction, activating in (GSM) 396 coverage prediction, activating in (LTE) 1464 coverage prediction, activating in (UMTS) 659 coverage prediction, activating in (WiMAX) 1178 defining when modelling environment (CDMA) 908 defining when modelling environment (LTE) 1530 defining when modelling environment (TD-SCDMA) 1084 defining when modelling environment (UMTS) 327 defining when modelling environment (WiMAX) 1245 defining when modelling user profile traffic map (CDMA) 909 defining when modelling user profile traffic map (LTE) 1532 defining when modelling user profile traffic map (TD-SCDMA) 1086
defining when modelling user profile traffic map (UMTS) 329 defining when modelling user profile traffic map (WiMAX) 1246 in traffic map (CDMA) 906 in traffic map (TD-SCDMA) 1082 in traffic map (UMTS) 325 modelling environment, defining when (UMTS) 733 modelling user profile traffic map, defining when (UMTS) 734 point analysis, activating in (GSM) 556 point analysis, activating in (UMTS) 657, 673 simulation results (CDMA) 924, 926 simulation results (LTE) 350, 1550 simulation results (TD-SCDMA) 1100 simulation results (UMTS) 346, 752 simulation results (WiMAX) 1264 simulation, activating in (UMTS) 296, 690 traffic map (UMTS) 730 indoor losses 214, 221 interactive frequency allocation (GSM) 504 inter-carrier interference defining (CDMA) 966 inter-carrier interference, defining (TD-SCDMA) 1134 inter-carrier interference, defining (UMTS) 795 interfered zones coverage prediction (GSM) 552 interference inter-carrier, defining (CDMA) 966 inter-carrier, defining (TD-SCDMA) 1134 inter-carrier, defining (UMTS) 795 Sector-to-Sector Interference Tool, using with (GSM) 571 interference matrices calculating (LTE) 1517 calculating (WiMAX) 1230 editing (LTE) 1518 editing (WiMAX) 1231 exporting (LTE) 1518 exporting (WiMAX) 1231
1623
Atoll 3.1.2 User Manual Index
importing (LTE) 1518 importing (WiMAX) 1231 LTE 1517 viewing probabilities (LTE) 1518 viewing probabilities (WiMAX) 1231 WiMAX 1230 interference reduction factor using assistant (MW) 178 interference zone coverage prediction, PN offset (CDMA) 902 interference zone coverage prediction, scrambling code (TD-SCDMA) 1077
interference zone coverage prediction, scrambling code (UMTS) 727 interferer reception threshold defining (GSM) 620 Inter-technology DL Noise Rise (CDMA) 817 Inter-technology DL Noise Rise (GSM) 374 Inter-technology DL Noise Rise (LTE) 1444 inter-technology DL noise rise (UMTS) 635 Inter-technology DL Noise Rise (WiMAX) 1157 inter-technology neighbours allocation (multi-RAT) 307 Inter-technology UL Noise Rise (CDMA) 817 Inter-technology UL Noise Rise (LTE) 1444 inter-technology UL noise rise (UMTS) 635 Inter-technology UL Noise Rise (WiMAX) 1157 ITU 1546 propagation model 196 ITU 370-7 propagation model (Vienna 93) 192, 193 ITU 526-5 propagation model 195 ITU 529-3 propagation model assigning environment formulas 192 creating environment formula 193 defining default environment formula 192 modifying environment formula 193 taking diffraction into account 192 Iub backhaul throughput consumption per site equipment-HSUPA radio bearer, defining (UMTS) 801 consumption per site equipment-R99 radio bearer, defining (UMTS) 801
J JD, see "joint detection" joint detection factor defining in site equipment (TD-SCDMA) 1144
L label 46 Lambert Conformal-Conic projection 120 layers 39 legend adding object type 47 co-planning, displaying window in (UMTS) 779 displaying 47 displaying (UMTS) 672 displaying Legend window 53 displaying window in co-planning (CDMA) 951 displaying window in co-planning (LTE) 1571
1624
© Forsk 2012
displaying window in co-planning (TD-SCDMA) 1121 displaying window in co-planning (WiMAX) 1286 printing Legend window 88 legend, displaying (CDMA) 852 legend, displaying (GSM) 414 legend, displaying (LTE) 1477 legend, displaying (TD-SCDMA) 1024 legend, displaying (WiMAX) 1190 lines editing 61 Longley-Rice propagation model 196 LTE 1435 cyclic prefix ratio 1588 frame duration 1590 glossary 1608 template 118 LTE radio bearer defining 1591 definition 321, 1526 LTE schedulers defining 1596 scheduling methods 1595 LTE, definition 1435
M macro-diversity gain clutter class, displaying per (CDMA) 973 clutter class, displaying per (UMTS) 805 map centring on a selected object 51, 52 exporting as image 65 measuring distances 52 moving 51 printing 84 refreshing display 108 saving as image 59 map scale displaying 53 Map toolbar 111 master carrier (TD-SCDMA) 1054 masthead amplifier, see "TMA" matrix, see "path loss matrix" max number of inter-carrier neighbours (CDMA) 817 max number of inter-technology neighbours (CDMA) 817 max number of intra-carrier neighbours (CDMA) 817 maximum UL load factor (CDMA) 818 measurement units, setting 122 measuring distances on the map 52 MIMO adaptive MIMO switch (LTE) 1599 adaptive MIMO switch (WiMAX) 1316 collaborative MIMO (LTE) 1600 collaborative MIMO (WiMAX) 1316 maximum ratio combining (WiMAX) 1315 MU-MIMO (LTE) 1600 MU-MIMO (WiMAX) 1316 number of antenna ports, defining (LTE) 1440
Atoll 3.1.2 User Manual Index
AT312_UM_E1
number of antennas, defining (WiMAX) 1154 receive diversity (LTE) 1599 receive diversity (UMTS) 804 space-time transmit diversity (WiMAX) 1315 space-time transmit diversity gains (WiMAX) 1308 spatial multiplexing (LTE) 1599 spatial multiplexing (UMTS) 804 spatial multiplexing (WiMAX) 1315 spatial multiplexing gains (LTE) 1594 spatial multiplexing gains (WiMAX) 1308 SU-MIMO (LTE) 1599 SU-MIMO (WiMAX) 1315 transmit diversity (LTE) 1599 transmit diversity (UMTS) 804 transmit diversity gains (LTE) 1594 Min Ec/Nt (UL) (CDMA) 866 mobility type creating (CDMA) 866 creating (GSM) 618 creating (LTE) 323, 1488 creating (TD-SCDMA) 1036 creating (UMTS) 685 creating (WiMAX) 1201 definition (CDMA) 904 definition (GSM) 437 definition (LTE) 1526 definition (TD-SCDMA) 1081 definition (UMTS) 321, 729 definition (WiMAX) 1241 EV-DO Rev. 0 parameters (CDMA) 867 modelling (GSM) 618 modifying (CDMA) 866 modifying (GSM) 618 modifying (LTE) 323, 1488 modifying (TD-SCDMA) 1036 modifying (UMTS) 685 modifying (WiMAX) 1201 parameters used in predictions (CDMA) 866 parameters used in predictions (TD-SCDMA) 1035 parameters used in predictions (UMTS) 685 mobility types table displaying (GSM) 618 modifying network settings (LTE) 1590 modifying network settings (WiMAX) 1303 Monte-Carlo-based user distribution (CDMA) 914 Monte-Carlo-based user distribution (TD-SCDMA) 1091 Monte-Carlo-based user distribution (UMTS) 334, 739 MUD, see "multi-user detection" MUG table defining for EV-DO cells (CDMA) 818 multi-band network, creating (LTE) 1454 multi-band network, creating (WiMAX) 1167 multi-band transmitters modelling (GSM) 613 multi-carrier network (CDMA) 816 multi-carrier network (TD-SCDMA) 985 multi-carrier network (UMTS) 633
multi-point analysis active set analysis (UMTS) 701 adding to a group (UMTS) 703 changing display (UMTS) 705 creating (UMTS) 702 potential server analysis (UMTS) 701 results, accessing (UMTS) 703 multi-point analysis (UMTS) 701 multi-RAT template 118 multi-service traffic data (GSM) 616 multi-user detection factor defining in site equipment (CDMA) 970 defining in terminals (TD-SCDMA) 1037 site equipment, defining in (UMTS) 800 terminals, defining in (UMTS) 687 multi-user environment 122
N neighbours allocating automatically (CDMA) 884 allocating automatically (GSM) 424 allocating automatically (LTE) 1506 allocating automatically (TD-SCDMA) 1059 allocating automatically (UMTS) 299, 707 allocating automatically (WiMAX) 1219 allocating on the map (CDMA) 893 allocating on the map (GSM) 432 allocating on the map (LTE) 1513 allocating on the map (TD-SCDMA) 1066 allocating on the map (UMTS) 716 allocating on the map (WiMAX) 1226 allocating per cell (CDMA) 891 allocating per cell (LTE) 1512 allocating per cell (TD-SCDMA) 1064 allocating per cell (UMTS) 714 allocating per cell (WiMAX) 1225 allocating per transmitter (GSM) 431 allocating using Cells tab of Transmitter Properties (CDMA) 891 allocating using Cells tab of Transmitter Properties (LTE) 1512 allocating using Cells tab of Transmitter Properties (TD-SCDMA) 1064
allocating using Cells tab of Transmitter Properties (UMTS) 714 allocating using Cells tab of Transmitter Properties (WiMAX) 1225
allocating using Intra-Technology Neighbours tab of Transmitter Properties (GSM) 431 allocating using Neighbours table (CDMA) 892 allocating using Neighbours table (GSM) 431 allocating using Neighbours table (LTE) 1512 allocating using Neighbours table (TD-SCDMA) 1065 allocating using Neighbours table (UMTS) 715 allocating using Neighbours table (WiMAX) 1225 audit of allocation (CDMA) 895 audit of allocation (GSM) 434 audit of allocation (LTE) 1515 audit of allocation (TD-SCDMA) 1068
1625
Atoll 3.1.2 User Manual Index
audit of allocation (UMTS) 718 audit of allocation (WiMAX) 1228 audit of inter-technology (CDMA) 962 audit of inter-technology (LTE) 1584 audit of inter-technology (TD-SCDMA) 1132 audit of inter-technology (UMTS) 305, 314, 792 audit of inter-technology (WiMAX) 1297 comparing existing and allocated (CDMA) 885, 886 comparing existing and allocated (GSM) 426 comparing existing and allocated (LTE) 1508 comparing existing and allocated (TD-SCDMA) 1060 comparing existing and allocated (UMTS) 709, 710 comparing existing and allocated (WiMAX) 1221 configuring importance (CDMA) 299, 307, 883 configuring importance (GSM) 424 configuring importance (LTE) 1506 configuring importance (TD-SCDMA) 1058 configuring importance (WiMAX) 1219 configuring importance in co-planning (CDMA) 955 configuring importance in co-planning (LTE) 1575 configuring importance in co-planning (TD-SCDMA) 1124 configuring importance in co-planning (WiMAX) 1290 defining exceptional pairs of (LTE) 1505 defining exceptional pairs of (TD-SCDMA) 1058 defining exceptional pairs of (WiMAX) 1218 deleting on the map (CDMA) 893 deleting on the map (GSM) 432 deleting on the map (LTE) 1513 deleting on the map (TD-SCDMA) 1066 deleting on the map (UMTS) 716 deleting on the map (WiMAX) 1226 deleting per cell (CDMA) 891 deleting per cell (LTE) 1512 deleting per cell (TD-SCDMA) 1064 deleting per cell (UMTS) 714 deleting per cell (WiMAX) 1225 deleting per transmitter (GSM) 431 deleting using Cells tab of Transmitter Properties (CDMA) 891 deleting using Cells tab of Transmitter Properties (LTE) 1512 deleting using Cells tab of Transmitter Properties (TD-SCDMA) 1064
deleting using Cells tab of Transmitter Properties (UMTS) 714 deleting using Cells tab of Transmitter Properties (WiMAX) 1225 deleting using Intra-Technology Neighbours tab of Transmitter Properties (GSM) 431 deleting using Neighbours table (CDMA) 892 deleting using Neighbours table (GSM) 431 deleting using Neighbours table (LTE) 1512 deleting using Neighbours table (TD-SCDMA) 1065 deleting using Neighbours table (UMTS) 715 deleting using Neighbours table (WiMAX) 1225 displaying (CDMA) 887 displaying (GSM) 427 displaying (LTE) 1509 displaying (TD-SCDMA) 1061 displaying (UMTS) 711 displaying (WiMAX) 1222
1626
© Forsk 2012
displaying coverage (CDMA) 890 displaying coverage (LTE) 1511 displaying coverage (TD-SCDMA) 1063 displaying coverage (UMTS) 713 displaying coverage (WiMAX) 1224 displaying coverage of (GSM) 430 exceptional pairs of, defining (CDMA) 883 exceptional pairs of, defining (GSM) 423 exceptional pairs, defining (UMTS) 706 exporting (CDMA) 896 exporting (GSM) 435 exporting (LTE) 1516 exporting (TD-SCDMA) 1069 exporting (UMTS) 719 exporting (WiMAX) 1229 importance in co-planning, configuring (UMTS) 784 importance, configuring (UMTS) 706 importing (CDMA) 882 importing (GSM) 423 importing (LTE) 1505 importing (TD-SCDMA) 1058 importing (UMTS) 298, 706 importing (WiMAX) 1218 intertechnology, allocating (CDMA) 952 intertechnology, allocating (LTE) 1573 inter-technology, allocating (multi-RAT) 307 intertechnology, allocating (TD-SCDMA) 1122 inter-technology, allocating (UMTS) 782 intertechnology, allocating (WiMAX) 1288 inter-technology, allocating automatically (CDMA) 955 inter-technology, allocating automatically (LTE) 1575 inter-technology, allocating automatically (TD-SCDMA) 1125 inter-technology, allocating automatically (UMTS) 308, 784 inter-technology, allocating automatically (WiMAX) 1291 inter-technology, allocating per cell (CDMA) 958 inter-technology, allocating per cell (LTE) 1579 inter-technology, allocating per cell (TD-SCDMA) 1127 inter-technology, allocating per cell (UMTS) 302, 310, 787 inter-technology, allocating per cell (WiMAX) 1293 inter-technology, allocating using Neighbours table (CDMA) 959 inter-technology, allocating using Neighbours table (LTE) 1580 inter-technology, allocating using Neighbours table (TD-SCDMA) 1128
inter-technology, allocating using Neighbours table (UMTS) 303, 311, 788
inter-technology, allocating using Neighbours table (WiMAX) 1294
inter-technology, comparing existing and allocated (CDMA) 956 inter-technology, comparing existing and allocated (LTE) 1577 inter-technology, comparing existing and allocated (TD-SCDMA) 1126
inter-technology, comparing existing and allocated (UMTS) 301, 310, 786
inter-technology, comparing existing and allocated (WiMAX) 1292
inter-technology, displaying (CDMA) 957 inter-technology, displaying (LTE) 1578
Atoll 3.1.2 User Manual Index
AT312_UM_E1
inter-technology, displaying (TD-SCDMA) 1127 inter-technology, displaying (UMTS) 315, 786 inter-technology, displaying (WiMAX) 1292 inter-technology, setting on the map (CDMA) 960 inter-technology, setting on the map (LTE) 1581 inter-technology, setting on the map (TD-SCDMA) 1129 inter-technology, setting on the map (UMTS) 316, 789 inter-technology, setting on the map (WiMAX) 1295 possible (CDMA) 882 possible (GSM) 422 possible (LTE) 1505 possible (TD-SCDMA) 1057 possible (UMTS) 297, 705 possible (WiMAX) 1217 network global parameters (CDMA) 967 global parameters (TD-SCDMA) 1135 global parameters (UMTS) 796 modifying global settings (CDMA) 968 modifying global settings (TD-SCDMA) 1137 network capacity calculating (TD-SCDMA) 1079 dimensioning (TD-SCDMA) 1079 displaying on the map (TD-SCDMA) 1080 Network explorer 35, 36 network settings calculation parameters (LTE) 1590 calculation parameters (WiMAX) 1303 global parameters (LTE) 1588 global parameters (WiMAX) 1301 modifying (LTE) 1590 modifying (WiMAX) 1303 network, creating dual-band (CDMA) 829 network, creating dual-band (TD-SCDMA) 998 network, creating dual-band (UMTS) 648 network, creating multi-band (LTE) 1454 network, creating multi-band (WiMAX) 1167 N-frequency mode (TD-SCDMA) carrier types 1055 definition 1055 setting up 1055 noise figure 178 noise figure (TD-SCDMA) 983 noise figure (UMTS) 632 noise rise threshold, defining for EV-DO cells (CDMA) 818 non-symmetric neighbours, displaying (CDMA) 887 non-symmetric neighbours, displaying (GSM) 427 non-symmetric neighbours, displaying (LTE) 1509 non-symmetric neighbours, displaying (TD-SCDMA) 1061 non-symmetric neighbours, displaying (UMTS) 711 non-symmetric neighbours, displaying (WiMAX) 1222
O objects changing transparency 45 deleting 40 displaying 38
displaying properties 40 grouping 89 grouping by a property 89, 90 grouping by several properties 90 grouping, examples 91 hiding 38 label 46 tip text 46 visibility scale 46 Okumura-Hata model 189, 190 Okumura-Hata propagation model 189, 190 assigning environment formulas 189 creating environment formula 190 defining default environment formula 189 modifying environment formula 190 taking diffraction into account 189 optimisation ACP optimisation parameters, defining 234 co-planning ACP setup, creating 794, 964 creating and defining site classes 238 creating new ACP process 234 creating new co-planning ACP process 1299, 1586 defining cost control 237 defining layers 235 defining zones 236 deleting 270 EMF exposure parameters, defining 240 importing second technology 1299, 1586 multi-storey parameters, defining 239 properties, changing 270 running ACP process 234 running ACP setup 270 running saved ACP 268 second technology, importing 794, 964 optimum beamformer modelling (TD-SCDMA) 1140 optimum beamformer modelling (WiMAX) 1312 overlapping zones coverage prediction (CDMA) 851 overlapping zones coverage prediction (GSM) 412 overlapping zones coverage prediction (LTE) 1476 overlapping zones coverage prediction (UMTS) 670 overlapping zones coverage prediction (WiMAX) 1189 OVSF codes calculation of consumption (TD-SCDMA) 1092 consumption, calculating (UMTS) 740 maximum number of codes available for HS-PDSCH (TD-SCDMA) 986
maximum number of codes available for HS-PDSCH (UMTS) 636 minimum number of codes available for HS-PDSCH (TD-SCDMA) 986
minimum number of codes available for HS-PDSCH (UMTS) 636 orthogonality factor, default (UMTS) 797 simulations (UMTS) 338, 745
P packet throughput per timeslot coverage prediction (GSM) 561 Page Setup, see "printing" Panoramic window 32, 51
1627
Atoll 3.1.2 User Manual Index
Parameters explorer 35, 36 path loss calculation radial 187, 188 path loss matrices adjusting using CW measurements 206, 207 defining area to be adjusted with measurement data 205 tuning using measurement data 204, 205 path loss matrix calculation process (CDMA) 846 calculation process (GSM) 402 calculation process (LTE) 1470 calculation process (UMTS) 665 calculation process (WiMAX) 1183 checking validity (CDMA) 843 checking validity (GSM) 399 checking validity (LTE) 1467 checking validity (TD-SCDMA) 1011 checking validity (WiMAX) 1180 exporting 211 resolution (CDMA) 823 resolution (GSM) 380, 615 resolution (LTE) 1448 resolution (TD-SCDMA) 992 resolution (UMTS) 641 resolution (WiMAX) 1161 storing 202 storing (CDMA) 842 storing (GSM) 398 storing (LTE) 1466 storing (TD-SCDMA) 1011 storing (UMTS) 661 storing (WiMAX) 1179 validity, checking 203 validity, checking (UMTS) 662 path lost matrix calculation process (TD-SCDMA) 1014 pattern electrical tilt 171 P-CCPCH pollution coverage prediction (TD-SCDMA) 1020 permutation zone creating (WiMAX) 1304 permutation zone (WiMAX) 1304 permutation zone permbases allocating manually (WiMAX) 1237 automatically allocating (WiMAX) 1236 permutation zone permbases (WiMAX) 1236 physical cell IDs allocating manually (LTE) 1522 audit of plan (LTE) 1525 automatically allocating (LTE) 1521 defining available (LTE) 1519 displaying allocation (LTE) 1523 displaying on transmitter (LTE) 1524 domains and groups, creating (LTE) 1519 grouping transmitters by (LTE) 1524 histogram (LTE) 1525 using Find on Map with (LTE) 1523 physical cell IDs (LTE) 1521
1628
© Forsk 2012
pilot channel, power control for EV-DO (CDMA) 915 pilot pollution coverage prediction (CDMA) 877 pilot pollution coverage prediction (UMTS) 693 pilot power reconfiguration with ACP 247 reconfiguration with ACP (CDMA) 248 reconfiguration with ACP (GSM) 248 reconfiguration with ACP (UMTS) 248 reconfiguration with ACP (WiMAX) 249 pilot reception analysis (Ec/I0) based on test mobile data path (CDMA) 942 pilot reception analysis (Ec/I0) based on test mobile data path (UMTS) 771 pilot signal quality coverage prediction (CDMA) 870 pilot signal quality coverage prediction (TD-SCDMA) 1038 pilot signal quality coverage prediction (UMTS) 687 Planet importing antennas 173 PN offsets audit of plan (CDMA) 900 automatically allocating (CDMA) 898 defining constraint costs (CDMA) 897 defining per cell (CDMA) 817 displaying allocation (CDMA) 901 displaying on transmitter (CDMA) 901 domain, defining per cell (CDMA) 816 grouping transmitters by (CDMA) 902 histogram (CDMA) 902 interference zone coverage prediction (CDMA) 902 manually allocating (CDMA) 900 reuse distance, defining per cell (CDMA) 816 using Find on Map with (CDMA) 901 PN offsets (CDMA) 896 point analysis EV-DO (CDMA) 837 opening Point Analysis Tool window 212 shadowing, calculating 214 starting 212 Point Analysis window active set analysis of simulation (CDMA) 932 active set analysis of simulation (UMTS) 760 AS Analysis view (CDMA) 880 AS Analysis view (UMTS) 696 Interference view (GSM) 555 Interference view (LTE) 1503 Interference view(WiMAX) 1216 printing 88 Profile view (CDMA) 837 Profile view (GSM) 393 Profile view (LTE) 1462 Profile view (TD-SCDMA) 1006 Profile view (UMTS) 656 Profile view (WiMAX) 1175 Reception tab (LTE) 1478 Reception view (CDMA) 853 Reception view (GSM) 414 Reception view (TD-SCDMA) 1025
AT312_UM_E1
Reception view (UMTS) 672 Reception view (WiMAX) 1191 Results view (LTE) 1504 Results view (WiMAX) 1217 points editing 61 polygon computation zone, using as (GSM) 403 computation zone, using as (UMTS) 666 deleting polygon filter 59 drawing a polygon filter 54 editing 61 focus zone, using as 57 focus zone, using as (CDMA) 854 focus zone, using as (GSM) 415 focus zone, using as (LTE) 1480 focus zone, using as (TD-SCDMA) 1026 focus zone, using as (UMTS) 673 focus zone, using as (WiMAX) 1193 geographic export zone, using as 60 printing zone, using as 86 using as computation zone 56 using as computation zone (CDMA) 846 using as computation zone (LTE) 1471 using as computation zone (TD-SCDMA) 1015 using as computation zone (WiMAX) 1184 using as filter 54, 107 using as filtering zone 55 population statistics including in report (CDMA) 856 including in report (GSM) 417 including in report (LTE) 1481 including in report (TD-SCDMA) 1028 including in report (WiMAX) 1194 integrable data (CDMA) 856 integrable data (GSM) 417 integrable data (LTE) 1481 integrable data (TD-SCDMA) 1028 integrable data (UMTS) 675 integrable data (WiMAX) 1194 report, including in (UMTS) 675 possible neighbours, definition (CDMA) 882 possible neighbours, definition (GSM) 422 possible neighbours, definition (LTE) 1505 possible neighbours, definition (TD-SCDMA) 1057 possible neighbours, definition (UMTS) 297, 705 possible neighbours, definition (WiMAX) 1217 power maximum power in cells, defining (CDMA) 817 maximum power in cells, defining (UMTS) 634 maximum power transmitted by EV-DO cells, defining (CDMA) 818
other CCH power in cells, defining (UMTS) 634 paging power in cells, defining (CDMA) 817 pilot power in cells, defining (CDMA) 817 pilot power in cells, defining (UMTS) 634 reconfiguration with ACP 225
Atoll 3.1.2 User Manual Index
SCH power in cells, defining (UMTS) 634 synchro power in cells, defining (CDMA) 817 power (GSM) reconfiguration with ACP 247 power control simulation algorithm EV-DO 916 power control simulation algorithm (CDMA) 915 power control simulation algorithm (TD-SCDMA) 1091 power control simulation algorithm (UMTS) 740 power, defining defining DwPTS power in cells (TD-SCDMA) 985 defining maximum power in cells (TD-SCDMA) 985 defining other CCH power in cells (TD-SCDMA) 985 defining P-CCPCH power in cells (TD-SCDMA) 985 defining UpPTS power (TD-SCDMA) 1037 preamble analysis based on drive test data path (WiMAX) 1279 preamble index (WiMAX) 1155 preamble indexes allocating manually (WiMAX) 1236 audit of plan (WiMAX) 1240 automatically allocating (WiMAX) 1235 defining available (WiMAX) 1232 displaying allocation (WiMAX) 1237 displaying on transmitter (WiMAX) 1238 domains and groups, creating (WiMAX) 1232 grouping transmitters by (WiMAX) 1239 histogram (WiMAX) 1240 using Find on Map with (WiMAX) 1237 preamble indexes (WiMAX) 1234 preamble power reconfiguration with ACP 247 predictions overview 215 Predictions folder sub-folder, organising predictions 67 printing antenna patterns 88, 175 coverage prediction results (CDMA) 882 coverage prediction results (GSM) 422 coverage prediction results (LTE) 1504 coverage prediction results (TD-SCDMA) 1054 coverage prediction results (UMTS) 701 coverage prediction results (WiMAX) 1217 CW Measurement Analysis Tool 88 data tables and reports 84 defining print layout 86 docking windows 88 Legend window 88 map 84 Point Analysis window 88 print preview 88 recommendations 85 Test Mobile Data Analysis Tool 88 printing zone drawing 85 Fit to Map Window 86 importing 86
1629
Atoll 3.1.2 User Manual Index
polygon, creating from 86 Profile 187, 188 Systematic extraction 187, 188 profile radial extraction 187, 188 projection coordinate system 120 Lambert Conformal-Conic projection 120 Universal Transverse Mercator projection 120 propagation model ACP, natively supported 228 ACP, not natively supported 228 ACP, using precalculated path loss matrices with 230 ACP, using precalculated pathloss matrices with 229 ACP, using with 227 all transmitters, assigning to (GSM) 400 all transmitters, assigning to (LTE) 1468 all transmitters, assigning to (WiMAX) 1181 assigning a default model for predictions 201, 845 assigning to a transmitter 845 assigning to a transmitter (TD-SCDMA) 1014 assigning to a transmitter (UMTS) 664 assigning to all transmitters 200, 844 assigning to all transmitters (TD-SCDMA) 1013 assigning to all transmitters (UMTS) 663 assigning to group of transmitters 200, 844 assigning to group of transmitters (TD-SCDMA) 1013 assigning to group of transmitters (UMTS) 664 Cost-Hata 190 Cost-Hata, diffraction 191 default model for predictions, assigning (GSM) 402 Erceg-Greenstein (SUI) 193 Erceg-Greenstein (SUI), diffraction 194 group of transmitters, assigning to (GSM) 400 group of transmitters, assigning to (LTE) 1469 group of transmitters, assigning to (WiMAX) 1182 ITU 1546 196 ITU 370-7 (Vienna 93) 192, 193 ITU 526-5 195 ITU 529-3, diffraction 192 Longley-Rice 196 Okumura-Hata 189, 190 Okumura-Hata, diffraction 189 Sakagami extended 197 signature 198 Standard Propagation Model 182 Standard Propagation Model, correction factor for hilly regions 188
Standard Propagation Model, defining parameters 186 Standard Propagation Model, diffraction 184 Standard Propagation Model, recommendations 183 transmitter, assigning to (GSM) 401 transmitter, assigning to (LTE) 1469 transmitter, assigning to (WiMAX) 1182 WLL 195 properties changing display 43 grouping objects by 89, 90
1630
© Forsk 2012
switching between property dialogues 40 pseudo noise offset, see "PN offset" 817
Q QoS Class, defining (WiMAX) 1200 quality indicator coverage prediction (CDMA) 875 quality indicator coverage prediction (LTE) 1501 quality indicator coverage prediction (UMTS) 691 quality indicator coverage prediction (WiMAX) 1214 quality indicators defining (LTE) 1592 defining (WiMAX) 1306
R R99 radio bearer creating (UMTS) 798 defining (TD-SCDMA) 1142 definition (TD-SCDMA) 1081 definition (UMTS) 321, 729 radial 187, 188 radio configuration definition (CDMA) 904 radio resource management calculation of channel element consumption (UMTS) 740 calculation of OVSF code consumption (TD-SCDMA) 1092 calculation of resource unit consumption (TD-SCDMA) 1092 channel element consumption per site equipment-R99 radio bearer, defining (UMTS) 801 channel element consumption per site equipment-terminal, defining (CDMA) 970 channel elements on downlink, defining (UMTS) 630 channel elements on forward link, defining (CDMA) 813 channel elements on reverse link, defining (CDMA) 813 channel elements on uplink, defining (UMTS) 630 channel elements, simulations (CDMA) 918 channel elements, simulations (UMTS) 338, 745 maximum number of OVSF codes available for HS-PDSCH (TD-SCDMA) 986 maximum number of OVSF codes available for HS-PDSCH (UMTS) 636
minimum number of OVSF codes available for HS-PDSCH (TD-SCDMA) 986 minimum number of OVSF codes available for HS-PDSCH (UMTS) 636
orthogonality factor, default (CDMA) 967 orthogonality factor, default (UMTS) 797 OVSF code consumption, calculating (UMTS) 740 OVSF codes, simulations (UMTS) 338, 745 uplink and downlink channel element consumption (CDMA) 970 uplink and downlink channel element consumption (UMTS) 800 Walsh codes, simulations (CDMA) 918 radio reverse indicator channel gain (CDMA) 869 Radio toolbar 111 receiver defining height 967 defining height (CDMA) 971 height, defining (UMTS) 797 receiver antenna diversity gain, defining (CDMA) 815
AT312_UM_E1
receiver antenna diversity gain, defining (TD-SCDMA) 983 receiver antenna diversity gain, defining (UMTS) 632 reception equipment creating (CDMA) 971 creating (TD-SCDMA) 1144 creating (UMTS) 801 modifying (CDMA) 971 modifying (TD-SCDMA) 1144 modifying (UMTS) 801 reconfiguration ACP parameters, importing 250 importing ACP parameters 252 redo 108 reflection smoothing vertical antenna pattern 175 refresh 108 from the database 126 Refresh Geo Data (GSM) 589 refresh geo data (LTE) 1563 Refresh Geo Data (TD-SCDMA) 1112 Refresh Geo data (UMTS) 770 refresh geo data (WiMAX) 1277 relativity clusters defining scrambling code (TD-SCDMA) 1071 remote antenna copying into document (CDMA) 834 copying into document (GSM) 391 copying into document (LTE) 1459 copying into document (TD-SCDMA) 1003 copying into document (UMTS) 654 copying into document (WiMAX) 1172 defining properties (CDMA) 835 defining properties (LTE) 1460 defining properties (TD-SCDMA) 1004 defining properties (WiMAX) 1173 importing (CDMA) 834 importing (GSM) 391 importing (LTE) 1459 importing (TD-SCDMA) 1003 importing (UMTS) 654 importing (WiMAX) 1172 placing on the map (CDMA) 834 placing on the map (GSM) 390 placing on the map (LTE) 1459 placing on the map (TD-SCDMA) 1003 placing on the map (UMTS) 653 placing on the map (WiMAX) 1172 properties, defining (GSM) 391 properties, defining (UMTS) 654 remote antenna table, opening (CDMA) 834 remote antenna table, opening (GSM) 390 remote antenna table, opening (LTE) 1459 remote antenna table, opening (UMTS) 653 remote antenna table, opening (WiMAX) 1172 renaming 40 repeater amplifier gain, reconfiguring with ACP 255
Atoll 3.1.2 User Manual Index
cascading (CDMA) 830 cascading (GSM) 386 cascading (LTE) 1455 cascading (TD-SCDMA) 999 cascading (UMTS) 649 cascading (WiMAX) 1168 copying into document (CDMA) 831 copying into document (GSM) 387 copying into document (LTE) 1456 copying into document (TD-SCDMA) 1000 copying into document (UMTS) 650 copying into document (WiMAX) 1168 defining properties (CDMA) 831 defining properties (GSM) 387 defining properties (LTE) 1456 defining properties (TD-SCDMA) 1000 defining properties (WiMAX) 1169 definition (CDMA) 829 definition (GSM) 385 definition (LTE) 1454 definition (TD-SCDMA) 998 definition (UMTS) 293, 648 definition (WiMAX) 1167 importing (CDMA) 831 importing (GSM) 387 importing (LTE) 1456 importing (TD-SCDMA) 1000 importing (UMTS) 650 importing (WiMAX) 1168 placing on the map (CDMA) 830 placing on the map (GSM) 386 placing on the map (LTE) 1455 placing on the map (TD-SCDMA) 999 placing on the map (UMTS) 649 placing on the map (WiMAX) 1168 properties, defining (UMTS) 650 repeater table, opening (CDMA) 830 repeater table, opening (GSM) 386 repeater table, opening (LTE) 1455 repeater table, opening (TD-SCDMA) 999, 1003 repeater table, opening (UMTS) 649 repeater table, opening (WiMAX) 1167 repeater equipment creating (CDMA) 830, 834 creating (GSM) 386, 390 creating (LTE) 1455, 1459 creating (TD-SCDMA) 999, 1003 creating (UMTS) 649, 653 creating (WiMAX) 1167, 1168, 1172 modifying (CDMA) 830, 834 modifying (GSM) 386, 390 modifying (LTE) 1455, 1459 modifying (TD-SCDMA) 999, 1003 modifying (UMTS) 649, 653 modifying (WiMAX) 1167, 1168, 1172 replace in data tables 79
1631
Atoll 3.1.2 User Manual Index
report coverage prediction, exporting (CDMA) 856 coverage prediction, exporting (GSM) 417 coverage prediction, exporting (LTE) 1482 coverage prediction, exporting (TD-SCDMA) 1028 coverage prediction, exporting (UMTS) 675 coverage prediction, exporting (WiMAX) 1195 report, displaying a coverage prediction (CDMA) 855 report, displaying a coverage prediction (GSM) 416 report, displaying a coverage prediction (LTE) 1480 report, displaying a coverage prediction (TD-SCDMA) 1026 report, displaying a coverage prediction (UMTS) 674 report, displaying a coverage prediction (WiMAX) 1193 reports printing 84 resolution display (CDMA) 839 display (GSM) 395 display (TD-SCDMA) 1008 display (UMTS) 659 path loss matrix (CDMA) 823 path loss matrix (GSM) 380, 615 path loss matrix (LTE) 1448 path loss matrix (TD-SCDMA) 992 path loss matrix (UMTS) 641 path loss matrix (WiMAX) 1161 resource unit calculation of consumption (TD-SCDMA) 1092 reverse link load factor, setting (CDMA) 862 reverse link radio bearer index, EV-DO 969 reverse link radio bearer, EV-DO, defining 969 row height changing 73 RRI, see "radio reverse indicator channel gain" RSCP UpPCH coverage prediction (TD-SCDMA) 1022 RTT carrier type, defining globally (CDMA) 967 data rates, available (CDMA) 968 handoff status coverage prediction (CDMA) 879 power control based on, defining globally (CDMA) 967 power control simulation algorithm (CDMA) 915 service parameters, RTT-specific (CDMA) 863, 864 simulation results, cells (CDMA) 922 simulation results, mobiles (CDMA) 924 rulers displaying 53
S Sakagami extended propagation model 197 scale level, choosing 50 SC-FDMA, definition (LTE) 1435 scheduler choosing the HSDPA scheduler algorithm (TD-SCDMA) 986 explanation of scheduling technique (TD-SCDMA) 1093 explanation of scheduling technique (UMTS) 742 HSDPA scheduler algorithm, selecting 636 scrambling codes
1632
© Forsk 2012
allocating, automatically (UMTS) 722 allocating, manually (UMTS) 724 audit of plan (TD-SCDMA) 1074 audit of plan (UMTS) 724 automatic allocation costs (TD-SCDMA) 1073 automatically allocating (TD-SCDMA) 1072 constraint costs, defining (UMTS) 722 creating domains and groups (TD-SCDMA) 1070 defining available (TD-SCDMA) 1070 defining available (UMTS) 721 defining constraint costs (TD-SCDMA) 1072 defining exceptional pairs (CDMA) 897 defining exceptional pairs (TD-SCDMA) 1071 defining format (TD-SCDMA) 1070 defining relativity clusters (TD-SCDMA) 1071 displaying allocation (TD-SCDMA) 1075 displaying allocation (UMTS) 725 displaying on transmitter (TD-SCDMA) 1075 displaying on transmitter (UMTS) 726 domains and groups, creating (UMTS) 721 exceptional pairs, defining (UMTS) 721 Find on Map, finding with (UMTS) 725 format, defining (UMTS) 720 grouping transmitters by (TD-SCDMA) 1076 grouping transmitters by (UMTS) 726 histogram (TD-SCDMA) 1076 histogram (UMTS) 727 interference zone coverage prediction (TD-SCDMA) 1077 interference zone coverage prediction (UMTS) 727 manually allocating (TD-SCDMA) 1074 using Find on Map with (TD-SCDMA) 1075 scrambling codes (TD-SCDMA) 1069 scrambling codes (UMTS) 720 searching for map objects 108, 109 secondary antenna, assigning (CDMA) 816 secondary antenna, assigning (GSM) 368 secondary antenna, assigning (LTE) 1440 secondary antenna, assigning (TD-SCDMA) 984 secondary antenna, assigning (UMTS) 633 secondary antenna, assigning (WiMAX) 1154 Sector-to-Sector Interference Tool using to study interference (GSM) 571 separation matrix, see "separation rules" service area (C/I) coverage prediction (TD-SCDMA) 1043 service area (Eb/Nt) coverage prediction (TD-SCDMA) 1043 service area (Eb/Nt) downlink based on test mobile data path (CDMA) 942 service area (Eb/Nt) downlink based on test mobile data path (UMTS) 772 service area (Eb/Nt) downlink or uplink coverage prediction (CDMA) 871
service area (Eb/Nt) downlink or uplink coverage prediction (UMTS) 688
service area (Eb/Nt) uplink based on test mobile data path (CDMA) 943
service area (Eb/Nt) uplink based on test mobile data path (UMTS) 772
AT312_UM_E1
services creating (CDMA) 863 creating (GSM) 616 creating (LTE) 1487 creating (Multi-RAT) 322 creating (TD-SCDMA) 1034 creating (UMTS) 682 creating (WiMAX) 1200 definition (CDMA) 904 definition (GSM) 321, 437 definition (LTE) 1526 definition (Multi-RAT) 321 definition (TD-SCDMA) 1081 definition (UMTS) 729 definition (WiMAX) 1241 displaying traffic distribution by (CDMA) 920 displaying traffic distribution by (LTE) 1545 displaying traffic distribution by (Multi-RAT) 340 displaying traffic distribution by (TD-SCDMA) 1097 displaying traffic distribution by (UMTS) 748 displaying traffic distribution by (WiMAX) 1260 HSDPA, enabling (UMTS) 682 HSUPA, enabling (UMTS) 682 modelling (GSM) 616 modifying (CDMA) 863 modifying (GSM) 616 modifying (LTE) 1487 modifying (Multi-RAT) 322 modifying (TD-SCDMA) 1034 modifying (UMTS) 682 modifying (WiMAX) 1200 parameters used in predictions (CDMA) 863 parameters used in predictions (LTE) 1487 parameters used in predictions (Multi-RAT) 321 parameters used in predictions (TD-SCDMA) 1033 parameters used in predictions (UMTS) 682 parameters used in predictions (WiMAX) 1200 priority, defining (UMTS) 683 setting priority (TD-SCDMA) 1034 soft handover, activating (UMTS) 683 services table displaying (GSM) 617 shadowing 214, 221 point analysis, calculating in 214 shadowing (CDMA) 967, 973 shadowing (GSM) 621 shadowing (LTE) 1600 shadowing (TD-SCDMA) 1145 shadowing (UMTS) 797, 805 shadowing (WiMAX) 1316 shadowing margin ACP 227 clutter class, displaying per (CDMA) 973 clutter class, displaying per (GSM) 622 clutter class, displaying per (LTE) 1601 clutter class, displaying per (TD-SCDMA) 1146 clutter class, displaying per (UMTS) 805
Atoll 3.1.2 User Manual Index
clutter class, displaying per (WiMAX) 1317 signal level coverage single station (CDMA) 839 single station (GSM) 395 single station (TD-SCDMA) 1008 single station (UMTS) 658 signal level coverage prediction single station (LTE) 1463 single station (WiMAX) 1176 signal level coverage prediction (CDMA) 848 signal level coverage prediction (GSM) 404 signal level coverage prediction (LTE) 1472 signal level coverage prediction (TD-SCDMA) 1017, 1021 signal level coverage prediction (UMTS) 667 signal level coverage prediction (WiMAX) 1185 simulation active set per user, displaying (CDMA) 921 adding to a group (CDMA) 929, 930 adding to a group (TD-SCDMA) 1105 adding to a group (UMTS) 758 average results of group (CDMA) 927 average results of group (LTE) 1552 average results of group (TD-SCDMA) 1102 average results of group (UMTS) 352, 754 average results of group (WiMAX) 1266 cell load values, updating (LTE) 1554 cell load values, updating (WiMAX) 1268 coverage predictions, using results for (CDMA) 932 coverage predictions, using results for (UMTS) 761 creating (CDMA) 917 creating (LTE) 1543 creating (TD-SCDMA) 1094 creating (UMTS) 337, 745 creating (WiMAX) 1257 displaying active set per user (UMTS) 748 displaying results with tip text (LTE) 1547 displaying results with tip text (WiMAX) 1261 duplicating (CDMA) 930, 931 duplicating (TD-SCDMA) 1105, 1106 duplicating (UMTS) 758, 760 estimating a traffic increase (LTE) 1555 estimating a traffic increase (TD-SCDMA) 1107 estimating a traffic increase (UMTS) 358 estimating a traffic increase (WiMAX) 1269 generator initialisation number (CDMA) 929, 931 generator initialisation number (TD-SCDMA) 1105, 1106 generator initialisation number (UMTS) 758, 759 global scaling factor (CDMA) 931 global scaling factor (LTE) 1555 global scaling factor (TD-SCDMA) 1107 global scaling factor (UMTS) 358, 760 global scaling factor (WiMAX) 1269 maximum number of EV-DO channel elements per carrier (CDMA) 922 number of EV-DO channel elements (CDMA) 922 number of EV-DO channel elements due to SHO overhead (CDMA) 922
1633
Atoll 3.1.2 User Manual Index
power control algorithm (CDMA) 915 power control algorithm (TD-SCDMA) 1091 power control algorithm (UMTS) 740 rejected users due to EV-DO resources saturation (CDMA) 924, 928
replaying (CDMA) 930 replaying (TD-SCDMA) 1105 replaying (UMTS) 758, 759 results of single (CDMA) 921 results of single (LTE) 1547 results of single (TD-SCDMA) 1098 results of single (UMTS) 341, 748 results of single (WiMAX) 1262 traffic increase, estimating (CDMA) 931 traffic increase, estimating (UMTS) 760 traffic simulation algorithm (LTE) 336, 1541 traffic simulation algorithm (WiMAX) 1256 updating cell values with results (CDMA) 929 updating cell values with results (TD-SCDMA) 1104 updating cell values with results (UMTS) 357, 757 using results for coverage predictions (LTE) 1555 using results for coverage predictions (TD-SCDMA) 1107 using results for coverage predictions (WiMAX) 1269 simulation results EV-DO cells (CDMA) 923 EV-DO mobiles (CDMA) 925 EV-DO, cells average and standard deviation (CDMA) 928 RTT cells (CDMA) 922 RTT mobiles (CDMA) 924 RTT, average and standard deviation cells (CDMA) 927 site creating (CDMA) 818 creating (GSM) 375 creating (LTE) 1445 creating (TD-SCDMA) 988 creating (UMTS) 637 creating (WiMAX) 1158 definition (CDMA) 811 definition (GSM) 364 definition (LTE) 1436 definition (TD-SCDMA) 980 definition (UMTS) 291, 628 definition (Wi-Fi) 1334 definition (WiMAX) 1150 modifying (CDMA) 818 modifying (GSM) 375 modifying (LTE) 1445 modifying (TD-SCDMA) 988 modifying (UMTS) 637 modifying (WiMAX) 1158 moving on the map 41 moving to a higher location 42 parameters (CDMA) 813 parameters (GSM) 365 parameters (LTE) 1437 parameters (TD-SCDMA) 981 parameters (UMTS) 630
1634
© Forsk 2012
parameters (WiMAX) 1151 properties, accessing from the explorer window 40 properties, accessing from the map 40 Site Configuration tab 37 site equipment channel element consumption per R99 radio bearer, defining (UMTS) 801 creating (CDMA) 970 creating (TD-SCDMA) 1143 creating (UMTS) 800 defining channel element consumption per terminal (CDMA) 970 Iub backhaul throughput, defining (UMTS) 801 max EV-DO channel elements per carrier (CDMA) 813 site list 102 adding 103 adding site 102 creating 102 editing 103 exporting 104 filter, using as 105 importing 104 slave carrier (TD-SCDMA) 1054 slow fading, see "shadowing" smart antenna adaptive beam modelling (TD-SCDMA) 1139 assigning (LTE) 1440 assigning (WiMAX) 1154 conventional beamformer modelling (LTE) 1597 conventional beamformer modelling (TD-SCDMA) 1140 conventional beamformer modelling (WiMAX) 1313 creating (LTE) 1597 creating (WiMAX) 1313 creating grid of beams (GOB) (TD-SCDMA) 1138 equipment (TD-SCDMA) 1141 grid of beams (GOB) import format (TD-SCDMA) 1139 grid of beams (GOB) modelling (TD-SCDMA) 1138 importing grid of beams (GOB) (TD-SCDMA) 1139 modelling (TD-SCDMA) 1137 optimum beamformer modelling (TD-SCDMA) 1140 optimum beamformer modelling (WiMAX) 1312 statistical modelling (TD-SCDMA) 1140 third-party modelling (TD-SCDMA) 1141 snapshot, definition (CDMA) 904 snapshot, definition (LTE) 1526 snapshot, definition (TD-SCDMA) 1078 snapshot, definition (UMTS) 320, 729 snapshot, definition (WiMAX) 1241 SOFDMA, definition (LTE) 1435 SOFDMA, definition (WiMAX) 1149 soft handoff modelling on the uplink (CDMA) 967 soft handover activating per service (UMTS) 683 modelling on the downlink (UMTS) 352, 755 modelling on the uplink (UMTS) 352, 683, 755, 797 sorting sorting tables by one column 94
Atoll 3.1.2 User Manual Index
AT312_UM_E1
sorting tables by several columns 94 with views 107 SPM Parameters tab window 187, 188 standalone carrier (TD-SCDMA) 1054 Standard Propagation Model 182, 187, 188 calculating diffraction 184 correction factor for hilly regions 188 defining parameters 186 recommendations 183 sample values for constants 184 typical values for losses per clutter class 186 Standard toolbar 110 station duplicating (CDMA) 826 station template copying properties from another template (CDMA) 825 copying properties from another template (GSM) 381 copying properties from another template (LTE) 1451 copying properties from another template (TD-SCDMA) 995 copying properties from another template (UMTS) 645 copying properties from another template (WiMAX) 1164 creating (GSM) 378 creating (LTE) 1447 creating (TD-SCDMA) 991 creating (UMTS) 640 creating (WiMAX) 1160 creating base station (CDMA) 820 creating base station (LTE) 1446 creating base station (TD-SCDMA) 989 creating base station (UMTS) 638 creating base station (WiMAX) 1159 creating base station from (GSM) 377 deleting (LTE) 1451 deleting (TD-SCDMA) 382, 645, 826, 995 deleting (WiMAX) 1164 field, modifying (UMTS) 645 modifying (CDMA) 821, 822 modifying (GSM) 379 modifying (LTE) 1448 modifying (TD-SCDMA) 991 modifying (UMTS) 640 modifying (WiMAX) 1161 modifying a field (CDMA) 826 modifying a field (GSM) 382 modifying a field (LTE) 1451 modifying a field (TD-SCDMA) 995 modifying a field (WiMAX) 1164 multi-band, creating (GSM) 614 statistical smart antenna model (TD-SCDMA) 1140 statistics, viewing coverage prediction (CDMA) 857 statistics, viewing coverage prediction (GSM) 418 statistics, viewing coverage prediction (LTE) 1482 statistics, viewing coverage prediction (TD-SCDMA) 1028 statistics, viewing coverage prediction (UMTS) 676 statistics, viewing coverage prediction (WiMAX) 1195 study, see "coverage prediction"
subcell definition (GSM) 369 modifying (GSM) 376 parameters (GSM) 369 subscriber database (LTE) 1536 subscriber database (WiMAX) 1251 subscriber list adding subscribers with the mouse (LTE) 1539 adding subscribers with the mouse (WiMAX) 1254 calculations (LTE) 1540 calculations (WiMAX) 1255 creating (LTE) 1537 creating (WiMAX) 1251 importing (LTE) 1540 importing (WiMAX) 1254 symmetric neighbours, displaying (CDMA) 887 symmetric neighbours, displaying (GSM) 427 symmetric neighbours, displaying (LTE) 1509 symmetric neighbours, displaying (TD-SCDMA) 1061 symmetric neighbours, displaying (UMTS) 711 symmetric neighbours, displaying (WiMAX) 1222
T T_Drop, defining per cell (CDMA) 817 table columns formatting 73 Table toolbar 112 tables, see "data tables" TDD frame configuration (LTE) 1443 TD-SCDMA template 118 template coverage prediction, using as 220 templates 118 3GPP multi-RAT 118 CDMA2000 1xRTT 1xEV-DO 118 GSM/GPRS/EGPRS 118 LTE 118 TD-SCDMA 118 UMTS HSDPA HSUPA 118 WiMAX 118 terminal creating (CDMA) 867 creating (GSM) 618 creating (LTE) 1488 creating (TD-SCDMA) 1037 creating (UMTS) 323, 685 creating (WiMAX) 1201 defining EV-DO Rev. 0-specific options (CDMA) 869 defining EV-DO Rev. A-specific options (CDMA) 869 definition (CDMA) 904 definition (GSM) 437 definition (LTE) 1526 definition (TD-SCDMA) 1081 definition (UMTS) 321, 729 definition (WiMAX) 1241 HSDPA, enabling 323
1635
Atoll 3.1.2 User Manual Index
HSDPA, enabling (UMTS) 685 HSUPA, terminal 323 HSUPA, terminal (UMTS) 685 modelling (GSM) 618 modifying (CDMA) 867 modifying (GSM) 618 modifying (LTE) 1488 modifying (TD-SCDMA) 1037 modifying (UMTS) 323, 685 modifying (WiMAX) 1201 parameters used in predictions (CDMA) 867 parameters used in predictions (TD-SCDMA) 1036 parameters used in predictions (UMTS) 685 terminals table displaying (GSM) 619 Test Mobile Data Analysis Tool printing 88 test mobile data path analysing variations (CDMA) 944 analysing variations (GSM) 592 coverage by C/I, using for (GSM) 590 coverage by signal level, using for (GSM) 590 coverage prediction, using in (GSM) 590 coverage prediction, using in (UMTS) 771 exporting (CDMA) 946 exporting (GSM) 594 exporting (UMTS) 775 exporting to CW measurements (CDMA) 946 exporting to CW measurements (GSM) 594, 595 exporting to CW measurements (UMTS) 775 extracting a field for a transmitter (GSM) 592 extracting a field for a transmitter (UMTS) 773 extracting a field for a transmitter (WiMAX) 944 filtering out points (CDMA) 939 filtering out points (GSM) 587 filtering out points (UMTS) 768 importing (CDMA) 935 importing (GSM) 583 importing (UMTS) 764 pilot reception analysis (Ec/I0), using for (UMTS) 771 Refresh Geo Data (GSM) 589 Refresh Geo Data (UMTS) 770 service area (Eb/Nt) downlink, using for (UMTS) 772 service area (Eb/Nt) uplink, using for (UMTS) 772 using for pilot reception analysis (Ec/I0) (CDMA)) 942 using for service area (Eb/Nt) downlink (CDMA) 942 using for service area (Eb/Nt) uplink (CDMA) 943 using in coverage prediction (CDMA) 942 variations, analysing (UMTS) 773 Test Mobile Data window exporting (CDMA) 947 exporting (GSM) 595 exporting (UMTS) 775 printing (CDMA) 947 printing (GSM) 595 printing (UMTS) 775 third-party smart antenna modelling (TD-SCDMA) 1141
1636
© Forsk 2012
throughput displaying traffic distribution by (LTE) 1546 displaying traffic distribution by (WiMAX) 1260 for all subscribers of a list (LTE) 1603 for all subscribers of a list (WiMAX) 1319 throughput coverage prediction (LTE) 1498 throughput coverage prediction (WiMAX) 1211 tilt angle 3-D antenna pattern 173 timeslot configurations creating (GSM) 612 modifying (GSM) 612 tip text 46 comparing coverage predictions, co-planning (CDMA) 951 comparing coverage predictions, co-planning (LTE) 1572 comparing coverage predictions, co-planning (TD-SCDMA) 1121 comparing coverage predictions, co-planning (UMTS) 779 comparing coverage predictions, co-planning (WiMAX) 1287 displaying coverage prediction results (CDMA) 853 displaying coverage prediction results (GSM) 414 displaying coverage prediction results (LTE) 1477 displaying coverage prediction results (TD-SCDMA) 1024 displaying coverage prediction results (WiMAX) 1190 displaying coverage prediction results with (UMTS) 672 displaying simulation results with (LTE) 1547 displaying simulation results with (WiMAX) 1261 TMA defining 176 TMA, assigning (LTE) 1439 TMA, assigning (TD-SCDMA) 983 TMA, assigning (WiMAX) 1153 TMS, assigning (CDMA) 815 TMS, assigning (GSM) 367 TMS, assigning (UMTS) 632 tool tips, see "tip text" toolbar icons 110 Map 111 Radio 111 Standard 110 Table 112 Vector Editor 111 Windows 112 total losses, updating 177 total noise on downlink, see "downlink total noise" total power reconfiguration with ACP 247 total transmitted power on DL (CDMA) 818 traffic capture global scaling factor (GSM) 449 traffic increase, estimating a (GSM) 449 traffic channel coverage prediction (TD-SCDMA) 1041 traffic distribution connection status, displaying by (UMTS) 747 creating, see "simulation" displaying by activity status (LTE) 1545 displaying by activity status (WiMAX) 1259
Atoll 3.1.2 User Manual Index
AT312_UM_E1
displaying by connection status (CDMA) 920 displaying by connection status (LTE) 1545 displaying by connection status (TD-SCDMA) 1096 displaying by connection status (UMTS) 339 displaying by connection status (WiMAX) 1259 displaying by handoff status (CDMA) 919 displaying by handover status (TD-SCDMA) 1096 displaying by service (CDMA) 920 displaying by service (LTE) 1545 displaying by service (Multi-RAT) 340 displaying by service (TD-SCDMA) 1097 displaying by service (UMTS) 748 displaying by service (WiMAX) 1260 displaying by throughput (LTE) 1546 displaying by throughput (WiMAX) 1260 displaying by uplink transmission power (LTE) 1546 displaying by uplink transmission power (WiMAX) 1261 handover status, displaying by (UMTS) 746 traffic increase, estimating (CDMA) 931 traffic increase, estimating (GSM) 449 traffic increase, estimating (LTE) 1555 traffic increase, estimating (TD-SCDMA) 1107 traffic increase, estimating (UMTS) 358, 760 traffic increase, estimating (WiMAX) 1269 traffic load, setting (LTE) 1492 traffic load, setting (WiMAX) 1205 traffic map converting 2G (LTE) 1535 cumulated traffic, exporting (GSM) 446 cumulated traffic, exporting (LTE) 1535 cumulated traffic, exporting (WiMAX) 1250 data sources (CDMA) 904 data sources (GSM) 437 data sources (LTE) 1527 data sources (TD-SCDMA) 1081 data sources (UMTS) 324, 729 data sources (WiMAX) 1241 exporting cumulated traffic (CDMA) 913 exporting cumulated traffic (TD-SCDMA) 1090 exporting cumulated traffic (UMTS) 333, 738 importing traffic map based on user profile densities (CDMA) 908 importing traffic map based on user profile densities (GSM) 441 importing traffic map based on user profile densities (LTE) 1530 importing traffic map based on user profile densities (TD-SCDMA) 1084 importing traffic map based on user profile densities (UMTS) 327, 733
importing traffic map based on user profile densities (WiMAX) 1245
importing user density traffic map (WIMAX) 1248 live data, creating from (CDMA) 905 live data, creating from (GSM) 324, 438 live data, creating from (LTE) 1527 live data, creating from (TD-SCDMA) 1081 live data, creating from (UMTS) 324, 730 live data, creating from (WiMAX) 1242 marketing-based (CDMA) 906
marketing-based (LTE) 1528 marketing-based (TD-SCDMA) 1083 marketing-based (WiMAX) 1243 sector (CDMA) 905 sector (GSM) 438 sector (LTE) 1527 sector (TD-SCDMA) 1081 sector (UMTS) 324, 730 sector (WiMAX) 1242 statistics on user profile environment based traffic map (CDMA) 911
statistics on user profile environment based traffic map (GSM) 444
statistics on user profile environment based traffic map (LTE) 1533
statistics on user profile environment based traffic map (TD-SCDMA) 1087 statistics on user profile environment based traffic map (UMTS) 330, 736
statistics on user profile environment based traffic map (WiMAX) 1248
user density (CDMA) 911 user density (GSM) 444 user density (LTE) 1533 user density (TD-SCDMA) 1087 user density (UMTS) 330, 736 user density (WiMAX) 1248 user density traffic map, importing (CDMA) 911 user density traffic map, importing (GSM) 444 user density traffic map, importing (LTE) 1533 user density traffic map, importing (TD-SCDMA) 1088 user density traffic map, importing (UMTS) 330, 736 user density, creating (CDMA) 912 user density, creating (GSM) 445 user density, creating (LTE) 1534 user density, creating (TD-SCDMA) 1088 user density, creating (UMTS) 331, 737 user density, creating (WiMAX) 1249 user density, creating from sector traffic maps (CDMA) 913 user density, creating from sector traffic maps (GSM) 445 user density, creating from sector traffic maps (LTE) 1535 user density, creating from sector traffic maps (TD-SCDMA) 1089 user density, creating from sector traffic maps (UMTS) 332, 738 user density, creating from sector traffic maps (WiMAX) 1250 user profile (GSM) 439 user profile (UMTS) 326, 731 user profile environment based, creating (CDMA) 910 user profile environment based, creating (GSM) 443 user profile environment based, creating (LTE) 1532 user profile environment based, creating (TD-SCDMA) 1086 user profile environment based, creating (UMTS) 329, 735 user profile environment based, creating (WiMAX) 1247 user profile environment based, importing (CDMA) 910 user profile environment based, importing (GSM) 443 user profile environment based, importing (LTE) 1532 user profile environment based, importing (TD-SCDMA) 1086 user profile environment based, importing (UMTS) 329, 735
1637
Atoll 3.1.2 User Manual Index
user profile environment based, importing (WiMAX) 1247 traffic maps ACP, using with 227 converting 2G (CDMA) 913 converting 2G (GSM) 445 converting 2G (TD-SCDMA) 1089 converting 2G (UMTS) 332, 738 converting 2G (WiMAX) 1250 traffic quality studies, see "quality studies" traffic simulation algorithm (LTE) 336, 1541 traffic simulation algorithm (WiMAX) 1256 transmitter calculating network capacity (TD-SCDMA) 1079 coverage prediction by transmitter (CDMA) 850 coverage prediction by transmitter (GSM) 406, 408, 409, 410, 411
coverage prediction by transmitter (LTE) 1474 coverage prediction by transmitter (TD-SCDMA) 1018 coverage prediction by transmitter (UMTS) 669 coverage prediction by transmitter (WiMAX) 1187 creating (CDMA) 819 creating (GSM) 375 creating (LTE) 1445 creating (TD-SCDMA) 988 creating (UMTS) 637 creating (WiMAX) 1158 definition (CDMA) 811, 814 definition (GSM) 364, 365 definition (LTE) 1436 definition (TD-SCDMA) 980, 981 definition (UMTS) 291, 628, 630 definition (Wi-Fi) 1334 definition (WiMAX) 1150 displaying frequencies (LTE) 1524 displaying frequencies (WiMAX) 1238 displaying physical cell IDs (LTE) 1524 displaying preamble indexes (WiMAX) 1238 displaying scrambling codes (TD-SCDMA) 1075 extracting a field from a drive test data path (LTE) 1565 extracting a field from a drive test data path (TD-SCDMA) 1114 extracting a field from a drive test data path (WiMAX) 1280 extracting a field from a test mobile data path (GSM) 592 extracting a field from a test mobile data path (UMTS) 773 extracting a field from a test mobile data path (WiMAX) 944 frequency allocation, displaying (GSM) 576 grouping by frequencies (GSM) 577 grouping by frequencies (LTE) 1524 grouping by frequencies (WiMAX) 1239 grouping by physical cell IDs (LTE) 1524 grouping by preamble indexes (WiMAX) 1239 grouping by scrambling codes (TD-SCDMA) 1076 grouping by scrambling codes (UMTS) 726 modifying (CDMA) 819 modifying (GSM) 375 modifying (LTE) 1445 modifying (TD-SCDMA) 988 modifying (UMTS) 637
1638
© Forsk 2012
modifying (WiMAX) 1158 modifying global properties (UMTS) 797 network capacity dimensioning (TD-SCDMA) 1079 PN offsets, displaying (CDMA) 901 PN offsets, grouping by (CDMA) 902 scrambling codes, displaying (UMTS) 726 setting as active (CDMA) 847 setting as active (GSM) 403 setting as active (LTE) 1471 setting as active (TD-SCDMA) 1015 setting as active (UMTS) 666 setting as active (WiMAX) 1184 transmitter equipment assigning (CDMA) 815 assigning (GSM) 368 assigning (TD-SCDMA) 983 assigning (UMTS) 632 CDMA Rho factor 177 defining 176 noise figure, updating 177 transmitter equipment, assigning (LTE) 1439 transmitter equipment, assigning (WiMAX) 1153 transmitter list 102 adding 103 adding transmitter 102 creating 102 editing 103 editing filter 105 exporting 104 importing 104 transmitters automatic display type 45 transparency, changing 45 TRX creating (GSM) 377 modifying (GSM) 377 TRX equipment creating (GSM) 604 importing (GSM) 604 TRX equipment (GSM) 604 TRX types (GSM) 601
U ue categories defining (LTE) 1596 UL load factor (CDMA) 818 UMTS HSDPA HSUPA template 118 undo 108 Universal Transverse Mercator projection 120 uplink load factor, setting (TD-SCDMA) 1033 uplink load factor, setting (UMTS) 682 uplink noise rise, setting (LTE) 1492 uplink noise rise, setting (WiMAX) 1205 uplink power control displaying traffic distribution by (LTE) 1546 displaying traffic distribution by (WiMAX) 1261
Atoll 3.1.2 User Manual Index
AT312_UM_E1
uplink traffic channel coverage prediction (TD-SCDMA) 1041 UpPCH interference coverage prediction (TD-SCDMA) 1049 user configuration 100 coverage prediction, exporting 220 creating 101 exporting 101 importing 101 user densities using instead of user profiles (LTE) 1604 using instead of user profiles (WiMAX) 1319 user density traffic map creating (CDMA) 912 creating (GSM) 445 creating (TD-SCDMA) 1088 creating (UMTS) 331, 737 creating (WiMAX) 1249 creating from sector traffic maps (CDMA) 913 creating from sector traffic maps (GSM) 445 creating from sector traffic maps (LTE) 1535 creating from sector traffic maps (TD-SCDMA) 1089 creating from sector traffic maps (UMTS) 332, 738 creating from sector traffic maps (WiMAX) 1250 user distribution (CDMA) 914 user distribution (TD-SCDMA) 1091 user distribution (UMTS) 334 user distribution, Monte-Carlo-based (UMTS) 739 user equipment category, HSDPA 687, 1037 user equipment category, HSDPA, editing 1145 user equipment category, HSDPA, editing (UMTS) 803 user equipment category, HSUPA 1037 user equipment category, HSUPA, editing 1145 user equipment category, HSUPA, editing (UMTS) 803 user profile creating (CDMA) 907 creating (GSM) 439 creating (LTE) 1529 creating (TD-SCDMA) 1083 creating (UMTS) 326, 731 creating (WiMAX) 1243 modifying (CDMA) 907 modifying (GSM) 439 modifying (LTE) 1529 modifying (TD-SCDMA) 1083 modifying (UMTS) 326, 731 modifying (WiMAX) 1243 user profile densities importing traffic map based on (CDMA) 908 importing traffic map based on (GSM) 441 importing traffic map based on (LTE) 1530 importing traffic map based on (TD-SCDMA) 1084 importing traffic map based on (UMTS) 327, 733 importing traffic map based on (WiMAX) 1245 user profile environment based traffic map creating (CDMA) 910 creating (GSM) 443 creating (LTE) 1532
creating (TD-SCDMA) 1086 creating (UMTS) 329, 735 creating (WiMAX) 1247 importing (CDMA) 910 importing (GSM) 443 importing (LTE) 1532 importing (TD-SCDMA) 1086 importing (UMTS) 329, 735 importing (WiMAX) 1247 statistics on (CDMA) 911 statistics on (GSM) 444 statistics on (LTE) 1533 statistics on (TD-SCDMA) 1087 statistics on (UMTS) 330, 736 statistics on (WiMAX) 1248 user profiles user densities, replacing with (LTE) 1604 user densities, replacing with (WiMAX) 1319
V Vector Editor toolbar 111 Vienna 93 model 192, 193 views creating 107 visibility scale 46
W Walsh codes orthogonality factor, default (CDMA) 967 simulations (CDMA) 918 Wi-Fi 1333 Wi-Fi, definition 1333 WiMAX 1149 cyclic prefix ratio 1301 frame duration 1301 glossary 1327 template 118 WiMAX radio bearer defining 1306 definition 1241 WiMAX schedulers defining 1311 scheduling methods 1309 WiMAX, definition 1149 Windows toolbar 112 wireless local loop propagation model 195 WLL (Wireless Local Loop) propagation model 195
X XML exporting data tables to 83 importing data tables from 83
Z zooming choosing a scale 50 in on a specific area 50
1639
Atoll 3.1.2 User Manual Index
1640
© Forsk 2012
Atoll Quick Reference Card Toolbars Standard
Map New from template (Ctrl+N)
Refresh (F5)
Open a document (Ctrl+O)
Pointer (Esc)
Save (Ctrl+S)
Move map (Ctrl+D)
New from database (Ctrl+Shift+N)
Set map scale
Refresh from database
Previous view (Alt+Left Arrow)
Import file
Next view (Alt+Right Arrow)
Load user configuration
Zoom in or out (Ctrl+Q)
Save user configuration
Define zoom area (Ctrl+W)
Cut (Ctrl+X)
Height Profile
Copy (Ctrl+C)
Measure distance
Paste (Ctrl+V)
Tip text
Undo (Ctrl+Z)
Find on map (Ctrl+F)
Redo (Ctrl+Y) Print table or map (Ctrl+P) Print preview (table or map) Help (F1)
Radio Planning
Microwave Link Planning Station template
Microwave link template
New transmitter
New microwave link
Hexagonal design
New repeater
New repeater or remote antenna
New multi-hop microwave link
Edit relations on the map
New multipoint microwave link
Point analysis
Microwave link analysis
Calculate (F7)
Victim and interferer links
Force calculation (Ctrl+F7)
Channel arrangement
Stop calculations
Stop calculations
Network tab
Event viewer
Geo tab
Panoramic window
Parameters tab
Legend window
New vector layer
Draw points
Vector layer to edit
Combine polygons
New polygon
Cut out areas in polygons
New rectangle
Polygon from overlapping area
New line
Split a polygon
Windows
Vector Editor
Atoll Quick Reference Card Toolbars Table Import data
Sort in descending order
Export data
Display statistics
Properties of current record
Fill down (Ctrl+D)
Centre current record on map
Fill up (Ctrl+U)
Display columns
Select all (Ctrl+A)
Hide selected columns
Align left
Freeze selected columns
Align centre
Unfreeze all columns
Align right
Filter by selected values
Bold
Filter excluding selected values
Italic
Advanced filter
Find
Remove filter
Replace
Sort in ascending order
Keyboard Shortcuts You can access some of the more common functions in Atoll by using keyboard shortcuts.
General You can use the following shortcuts anywhere in Atoll. New document from a template New document from a database Open a file Print Save the current document On-line help Find on map / Find in table Refresh display
Ctrl+N Ctrl+Shift+N Ctrl+O Ctrl+P Ctrl+S F1 Ctrl+F F5
Undo last action Redo last action Calculate Force calculations Access add-ins and macros Export contents of a folder Import into a folder Open Atoll.ini file in a text editor
Ctrl+Z Ctrl+Y F7 Ctrl+F7 Alt+F8 Ctrl+E Ctrl+I Ctrl+Shift+I
Zoom on area Zoom in Zoom out Zoom in/out
Ctrl+W Ctrl++ Ctrl+Ctrl+Q
Fill down Fill up Find Replace
Ctrl+D Ctrl+U Ctrl+F Ctrl+H
Map Shortcuts You can use the following shortcuts in the map window. Next view Previous view Move map Find on map
Alt+Right Arrow Alt+Left Arrow Ctrl+D Ctrl+F
Table Shortcuts You can use the following shortcuts in a table. Copy Cut Paste Select all
Ctrl+C Ctrl+X Ctrl+V Ctrl+A
Atoll 3.1.2 User Manual AT312_UM_E1
1643
User Manual
version 3.1.2 AT312_UM_E1 June 2012
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 4800 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
