atoll 3.2.1 administrator manual

Version 3.2.1

Administrator Manual

AT321_AM_E1

Atoll 3.2.1 Administrator Manual

Release: AT321_AM_E1 (February 2014)

© Copyright 1997‐2014 Forsk. All Rights Reserved.

Published by:

Forsk7 rue des Briquetiers31700 Blagnac, FranceTel: +33 562 747 210Fax: +33 562 747 211

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 the contents of this document may be reproduced or transmitted in any form or by any means without written permission from the publisher.

The product or brand names mentioned in this document are trademarks or registered trademarks of their respective registering parties.

The publisher has taken care in the preparation of this document, but makes no expressed or implied warranty of any kind and assumes no responsibility for errors or omissions. Noliability is assumed for incidental or consequential damages in connection with or arising out of the use of the information contained herein.

Atoll 3.2.1 Administrator Manual © Forsk 2014

4

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Table of Contents

Table of Contents

1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131.1 Supported Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3 Supported Database Management Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4 Supported Installation Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.5 Recommended Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.5.1 User Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.5.2 Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.5.3 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.5.4 Floating Licence Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.5.5 File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.6 Recommended Computer Network Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2 Installing Atoll and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172.1 Installing Atoll Using the Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.2 Installing a Language Pack Using the Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3 Installing Atoll C++ Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.4 Setup Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5 Installing and Uninstalling Add‐ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.6 Installing and Uninstalling Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.7 Atoll Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.8 Troubleshooting and Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 Setting Up Distributed Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273.1 Setting Up Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2 Setting Up Atoll to Access the Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.3 Distributed Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4 Managing Licences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314.1 Working with Floating Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.1.1 HASP Licence Manager and Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.1.2 nhsrv.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.1.3 nethasp.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.2 Using the Atoll Licence Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.2.1 Licence Manager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.2.2 Updating Licence Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.2.3 Testing Licence Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.2.4 Reducing the Number of Module Tokens in ALIC Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.2.4.1 Activating the Option in the Licence Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.2.4.2 Reducing the Number of Module Tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.2.4.3 Programming a Blank Licence Key Using the Restricted ALIC File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5 Managing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395.1 Atoll Database Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.2 Customising Atoll Database Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.3 Atoll Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425.4 Creating New Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.4.1 Creating a New Database Using the Atoll Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.4.2 Creating a New Database Using Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.5 Upgrading Existing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.6 Working With a Multi‐level Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.6.1 Creating Project Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.6.2 Archiving Project Databases to Master Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525.6.3 Refreshing Project Databases from Master Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.7 Setting Database Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.8 Managing Data Modifications History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5

Atoll 3.2.1 Administrator ManualTable of Contents © Forsk 2014

5.8.1 Setting Up Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .545.8.2 Enabling/Disabling Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .555.8.3 Updating After Data Structure Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .555.8.4 Purging Old Data Modification Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .565.8.4.1 Purging Old Data Modification Records of a Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .565.8.4.2 Purging Old Data Modification Records of a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

5.9 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .585.9.1 Appendix 1: Advanced Customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .585.9.2 Appendix 2: Setting Up Databases for Co‐planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

6 Multi‐user Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636.1 Setting Up Multi‐user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .636.2 Components of Multi‐user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .636.2.1 Master Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .646.2.2 Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .646.2.3 Shared Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .646.2.4 Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .656.2.5 User Atoll Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

6.3 Managing User Accounts and Access Rights in Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .656.3.1 Defining Database and Interface Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .666.3.2 Creating and Editing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .686.3.3 Resetting User Database Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

6.4 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .696.4.1 Appendix 1: Checking Data Integrity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .696.4.2 Appendix 2: Database Regionalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .706.4.3 Appendix 3: Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .706.4.4 Appendix 4: Path Loss Matrices From Different Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

7 Coordinate Systems and Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737.1 Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .737.1.1 Definition of a Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .737.1.2 Types of Coordinate Systems in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .747.1.3 Coordinate Systems File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .757.1.4 Creating a Coordinate System in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

7.2 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .797.3 BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

8 Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818.1 Geographic Header File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .828.1.1 HDR Header File for BIL Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .828.1.2 TFW Header File for TIFF Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .838.1.3 BPW/BMW Header Files for BMP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .848.1.4 PGW Header File for PNG Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .848.1.5 JGW Header File for JPG Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .848.1.6 Generic Raster Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

9 Radio Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879.1 XML Import/Export Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .879.1.1 Index.xml File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .879.1.2 XML File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

9.2 RF 2D Antenna Pattern Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .899.3 Import Format of 3D Antenna Pattern Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .919.4 Microwave 2D Antenna Pattern Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .919.5 Path Loss Matrix File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .929.5.1 Pathloss.dbf File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .929.5.2 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .959.5.3 LOS File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

9.6 Path Loss Tuning File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .969.6.1 Pathloss.dbf File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .969.6.2 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .969.6.3 PTS File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

9.7 Interference Matrix File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .979.7.1 CLC Format (One Value per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .979.7.1.1 CLC File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .979.7.1.2 DCT File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

6


9.7.2 IM0 Format (One Histogram per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999.7.3 IM1 Format (One Value per Line, TX Name Repeated). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009.7.4 IM2 Format (Co‐ and Adjacent‐channel Probabilities) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

9.8 "Per Transmitter" Prediction File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029.8.1 <per_transmitter_prediction>.dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039.8.2 <per_transmitter_prediction>.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

10 Administration and Usage Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . .10510.1 Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10510.2 Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10610.3 Atoll Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10710.4 Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10710.5 Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10810.6 Atoll Administration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10810.7 Process Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10910.8 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10910.9 Coverage Prediction Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11010.10 CW Measurements and Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11010.11 Antenna Patterns and Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11010.12 Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11010.13 Atoll API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11110.14 Performance and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11110.15 Appendix: Memory Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11310.15.1 Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11310.15.2 RAM Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

11 Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11711.1 Contents of User Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11811.1.1 Geographic Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11811.1.2 Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12111.1.3 Map Centre and Zoom Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12211.1.4 Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12211.1.5 Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12911.1.6 Automatic Neighbour Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13111.1.7 Automatic Frequency Planning Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13311.1.8 Automatic Scrambling Code Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13411.1.9 Automatic PN Offset Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13611.1.10 Automatic OFDM Resource Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13711.1.11 Microwave Radio Links Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13811.1.12 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

11.2 Contents of Additional Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14111.2.1 Print Setup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14111.2.2 Table Import/Export Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14311.2.3 Coverage Prediction Report Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14311.2.4 CW Measurement Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14411.2.5 Drive Test Data Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

11.3 Content of the Custom Predictions File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14511.4 Content of the "Value Intervals" Predictions Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

12 Initialisation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14712.1 Atoll Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14712.1.1 General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14712.1.1.1 Modifying the Default Formats of Site and Transmitter Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14712.1.1.2 Disabling Automatic Renaming of Transmitters and Cells. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14812.1.1.3 Setting the TIFF Colour Convention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14812.1.1.4 Creating an Event Viewer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14812.1.1.5 Displaying Insufficient Permission Messages in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14912.1.1.6 Increasing the Maximum Printing Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14912.1.1.7 Duplicating Linked Path Loss Matrices on Save As. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14912.1.1.8 Disabling External Storage of Numerical Results Files for Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15012.1.1.9 Restricting the List of Predictions for Creating Sector Traffic Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15012.1.1.10 Displaying Path Loss Calculation Details in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15012.1.1.11 Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15012.1.1.12 Exporting Coverage Prediction Polygons in Text Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15112.1.1.13 Defining Web Map Services Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

7


12.1.1.14 Improving Point Analysis Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15212.1.1.15 Loading Vector Files Dynamically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15212.1.1.16 Excluding Vectors from Imported KML/KMZ Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15212.1.1.17 Setting the Precision for the Antenna Pattern Verification at Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15212.1.1.18 Opening Exported XLS Files Automatically in MS Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15312.1.1.19 Disabling Creation of New Documents from Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15312.1.1.20 Blocking Access to Macros and Add‐ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15312.1.1.21 Disabling Saving and Opening ZIP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15312.1.1.22 Enabling Notification for Donor Transmitter Parameter Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15312.1.1.23 Setting the Display Precision of Floating Point Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15312.1.1.24 Changing the Path to Linked Geo Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15412.1.1.25 Exporting/Importing Vector Data with a Display Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15412.1.1.26 Using Only Visible Geo Data in Prediction Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15412.1.1.27 Exporting BMP, TIF, and PNG Files with a TAB Reference File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15412.1.1.28 Co‐Planning: Linking the Sites Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15412.1.1.29 Disabling Normalisation of MIF/TAB Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15512.1.1.30 Adding the Duplicate Site to the Original Site’s Site List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15512.1.1.31 Using Only Visible Clutter Classes in Interference Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15512.1.1.32 Displaying % of Covered Clutter Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15512.1.1.33 Displaying % of Covered Traffic Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15512.1.1.34 Synchronising Private and Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15512.1.1.35 Selecting the Logo 2 Check Box by Default in Print Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15612.1.1.36 Filtering Predictions by Technology When Reading the XML Studies File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15612.1.1.37 Enabling Event Viewer Messages for MapInfo File Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15612.1.1.38 Setting the Resolution of Population Maps in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15612.1.1.39 Setting the Precision in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15712.1.1.40 Including Pixel‐free Ranges in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15712.1.1.41 Changing Hot Spot Reference Surface in Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15712.1.1.42 Exporting Only Visible Value Interval Layers of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15712.1.1.43 Avoiding Overlapping Pixels in Best Server Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15712.1.1.44 Setting the Minimum ATL File Size Requiring Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15812.1.1.45 Loading, Activating, and Setting Add‐ins as Visible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15812.1.1.46 Defining Online Map URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15812.1.1.47 Changing the Default Cache Location for the Loaded Map Tiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15812.1.1.48 Managing Carriage Returns in Imported TXT/CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15912.1.1.49 Deleting the Filtering Zone on Removing Filters From Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

12.1.2 GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15912.1.2.1 Defining the Parameters for the Default Sites Symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15912.1.2.2 Using a Unique Symbol for Remote Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15912.1.2.3 Keeping Transmitter Symbols From Changing on Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16012.1.2.4 Displaying Filled Symbols for Inactive Transmitters on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16012.1.2.5 Refreshing the Display Automatically When a New Station is Dropped. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16012.1.2.6 Hiding Information Displayed in the Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16012.1.2.7 Displaying Date and Time in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16012.1.2.8 Setting the Maximum Number of Lines in Coverage Prediction Tool Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16012.1.2.9 Changing the Display for Downlink Smart Antenna Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16112.1.2.10 Adding Exposure Analysis to the List of Multi‐RAT Coverage Predictions (Hidden en 3.2.0.02, ces infos sont dans TN013)

16112.1.2.11 Displaying Coverage Prediction Comments in the Legend Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16112.1.2.12 Displaying Leading Zeros in the CELL_IDENTITY Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16112.1.2.13 Making the Antenna Additional Electrical Downtilt Accessible. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16112.1.2.14 Increasing the Width of the Clutter Description Pane in the Status Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16212.1.2.15 Hiding the Technology Name in the Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16212.1.2.16 Displaying Objects’ Discrete Values with User‐defined Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16212.1.2.17 Displaying Vertical Beamwidth in Profile Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

12.1.3 Distributed Calculation Server Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16312.1.3.1 Detecting and Listing Distributed Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16312.1.3.2 Setting the Distributed Calculation Server Priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16312.1.3.3 Modifying the Default Detection Time‐out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

12.1.4 Licence Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16412.1.4.1 Setting an Alarm for the Licence End Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16412.1.4.2 Blocking Access to Technology Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16412.1.4.3 Blocking Access to ACP and AFP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16412.1.4.4 Changing the NetHASP Licence Manager Idle Time Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

12.1.5 Database Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16512.1.5.1 Checking Data Integrity After Database Upgrade and Data Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16512.1.5.2 Automatically Running a Database Integrity Check at Open or Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

8


12.1.5.3 Allowing Null Entries in Non‐nullable Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16512.1.5.4 Automatically Running GSM Subcell Audit at Open or Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16512.1.5.5 Modifying the Default Database Connection Time‐out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16612.1.5.6 Making Atoll Case‐Sensitive for Database Import From Planet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16612.1.5.7 Setting the Sign for KClutter When Importing Data From Planet EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16612.1.5.8 Enabling/Disabling Password Prompt at Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16612.1.5.9 Archiving Data to Databases Using Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16712.1.5.10 Keeping Separate Work and Master Path Loss Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16712.1.5.11 Enabling Partial Refresh from Recently Upgraded Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16712.1.5.12 Setting the Type of Database Being Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

12.1.6 Common Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16812.1.6.1 Setting the Antenna Patterns Modelling Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16812.1.6.2 Disabling Automatic Locking of Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16812.1.6.3 Enabling Shadowing Margin in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16812.1.6.4 Setting a Default Value for the Cell Edge Coverage Probability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16912.1.6.5 Enabling Indoor Coverage in Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16912.1.6.6 Modifying the Resolution for the LOS Area Calculation Around a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16912.1.6.7 Embedding Path Losses in New Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16912.1.6.8 Stopping Calculations on Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16912.1.6.9 Warning About Prediction Validity When Display Options are Modified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17012.1.6.10 Reading Exact Altitudes From the DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17012.1.6.11 Setting a Common Display Resolution For All Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17012.1.6.12 Setting the Priorities for GUI and Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17012.1.6.13 Setting the Number of Parallel Processors and Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17112.1.6.14 Disabling Parallel Calculation of Monte Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17112.1.6.15 Performing Calculations in Read‐Only Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17112.1.6.16 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17212.1.6.17 Changing the Rounding Method Used for Profile Extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17212.1.6.18 Estimating Required and Used Memory Size for UMTS Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17212.1.6.19 Disabling Calculations Over NoData Values for DTM and Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17212.1.6.20 Co‐planning: Calculating Predictions in the Current Document Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17212.1.6.21 Co‐planning: Calculating Predictions in Serial or in Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17212.1.6.22 Forcing Neighbour Symmetry Only Inside Focus Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17312.1.6.23 Using Poisson Distribution in Monte Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17312.1.6.24 Calculating EIRP from Max Power in Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17312.1.6.25 Excluding Filtered Transmitters from the List of Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17312.1.6.26 Changing the Weighting Factor of the Effective Inter‐transmitter Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17312.1.6.27 Extending the Maximum Inter‐site Distance to Repeaters and Remote Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17412.1.6.28 Forcing the Real Inter‐site Distance Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17412.1.6.29 Prioritising Individual Inter‐site Distances in Neighbour Importance Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17412.1.6.30 Keeping the Assigned Neighbours which are not Symmetrised with the Reference Transmitter . . . . . . . . . . . . . . . . . . 17412.1.6.31 Enabling and Disabling Per‐site Path Loss Matrix Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17412.1.6.32 Defining a Global Maximum Path Loss Calculation Radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

12.1.7 GSM GPRS EDGE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17512.1.7.1 Considering Inter‐technology Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17512.1.7.2 Considering Overlapping Zones for IM Calculation Based on Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17512.1.7.3 Setting the Default BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17512.1.7.4 Checking Database Consistency Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17512.1.7.5 Disabling the Maximum Range Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17512.1.7.6 Enabling the Support for Multi‐band Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17612.1.7.7 Setting the Best Server Calculation Method in Same Priority HCS Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17612.1.7.8 Hiding Advanced AFP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17612.1.7.9 Modifying the Thresholds for Important Violations in AFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17712.1.7.10 Hiding Violations Between Low Importance GSM Neighbours in AFP Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17712.1.7.11 Hiding Violations Between Non‐synchronised MALs‐MAIOs in AFP Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17712.1.7.12 Selecting the Interference Matrices Used During the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17712.1.7.13 Defining the Maximum Number of Transmitters for Reuse Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17812.1.7.14 Making Redundant Fields in the Transmitters Table Read‐only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17812.1.7.15 Setting the Transmission Diversity Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17812.1.7.16 Adding Grouped HCS Servers Option in Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17812.1.7.17 Deactivating Frequency Band Filtering in IM Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17812.1.7.18 Starting TRX Indexes at 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17912.1.7.19 Hiding the TRX Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17912.1.7.20 Extending the Allowed Value Range for C/I and Reception Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17912.1.7.21 Automatically Correcting Out‐of‐range Subcell Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

12.1.8 UMTS HSPA, CDMA2000, and TD‐SCDMA Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18012.1.8.1 Suppressing Cell Name Carrier Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

9


12.1.8.2 Disabling Macro‐diversity (SHO) Gains in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18012.1.8.3 Calculating and Displaying Peak or Instantaneous HSDPA Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18012.1.8.4 Setting the Power to Use for Intra‐cell Interference in HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18112.1.8.5 Enabling Coverage Predictions of Connection Probabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18112.1.8.6 Setting the Calculation Method for HS‐PDSCH CQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18112.1.8.7 Enabling Orthogonality Factor in Pilot EC/NT Calculation in HSDPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18112.1.8.8 Setting the Maximum Number of Rejections for Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18112.1.8.9 Setting the Maximum Number of Rejections for HSDPA Mobiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18212.1.8.10 Defining an Offset With Respect to The Thermal Noise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18212.1.8.11 Setting Precision of the Rasterisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18212.1.8.12 Defining the Number of Iterations Before Downgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18312.1.8.13 Adjusting the Working of the Proportional Fair Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18312.1.8.14 Displaying Ec/I0 of Rejected Mobiles in Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18312.1.8.15 Switching Back to the Old Best Server Determination Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18412.1.8.16 Displaying Automatic Allocation Cost Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18412.1.8.17 Selecting SC and PN Offset Allocation Strategies Available in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18412.1.8.18 Defining a Fixed Interval Between Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18412.1.8.19 Compressed Mode: Restricting Inter‐carrier and Inter‐technology Neighbour Allocation. . . . . . . . . . . . . . . . . . . . . . . 18412.1.8.20 Setting the Maximum AS Size for SC Interference Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18512.1.8.21 Displaying Uplink Total Losses in Coverage by Signal Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18512.1.8.22 Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

12.1.9 LTE, WiMAX, and Wi‐Fi Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18512.1.9.1 Blocking Access to IEEE Parameters in WiMAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18512.1.9.2 Using Only Bearers Common Between the Terminal’s and Cell’s Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18612.1.9.3 Enabling Display of Signals per Subcarrier Point Analysis in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18612.1.9.4 Including Cyclic Prefix Energy in LTE Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18612.1.9.5 Excluding Cyclic Prefix Energy in WiMAX and Wi‐Fi Signal Level Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18612.1.9.6 Ignoring Inter‐Neighbour Preamble Index Collision in WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18612.1.9.7 Ignoring Inter‐Neighbour Physical Cell ID Collision in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18712.1.9.8 Applying Transmit Diversity Gains to Reference Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18712.1.9.9 Renaming OPUSC Zone to PUSC UL in WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18712.1.9.10 Deactivating Uniform Distribution of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18712.1.9.11 Taking Second Order Neighbours into Account in the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18712.1.9.12 Excluding the Adjacent Channel Overlap from the AFP Cost Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18812.1.9.13 Switching Between Synchronised and Unsynchronised Interference Calculation Methods. . . . . . . . . . . . . . . . . . . . . . 18812.1.9.14 Setting PDCCH to 100% Loaded in LTE Interference Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18812.1.9.15 Calculating EIRP from RS EPRE in LTE Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18812.1.9.16 Averaging the Uplink Noise Rise in dB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18912.1.9.17 Deactivating Service Max Throughput Demand Downgrading in LTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18912.1.9.18 Displaying Pixels with Zero Throughput in Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18912.1.9.19 Setting Uplink Noise Rise Control Parameters in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18912.1.9.20 Using the ABS Patterns Throughout a Cell in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19012.1.9.21 Applying the ABS Collision Probability on Interference from RS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19012.1.9.22 Enabling Multi‐eNode‐B Carrier Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19012.1.9.23 Switching Between Carrier Aggregation Scheduling Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

12.1.10 3GPP Multi‐RAT Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19012.1.10.1 BSIC, SC, and PCI Allocation with Inter‐technology Neighbour Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

12.1.11 Microwave Radio Links Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19112.1.11.1 Updating A>>B and B>>A Profiles in Real‐time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19112.1.11.2 Disabling Shielding Factor on Wanted Signal at Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19112.1.11.3 Making the ITU‐R P.530‐5 Method Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19112.1.11.4 Decreasing Calculation Time of Path Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19112.1.11.5 Using Old Min C/I Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19112.1.11.6 Solving Alignment Issue in Generated Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19212.1.11.7 Using Default Method for Calculating Unavailability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19212.1.11.8 Defining Default Configuration Files for Link Budgets Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19212.1.11.9 Defining a Default Configuration File for the Channel Arrangement Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19212.1.11.10 Defining a Default Template for Microwave Links Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

12.1.12 Measurement Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19312.1.12.1 Displaying Additional Information in Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19312.1.12.2 Setting the Number of Transmitters per Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19312.1.12.3 Recalculating Distances of Points From There Serving Cells at Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19312.1.12.4 Defining the BCCH and BSIC Columns for FMT Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19312.1.12.5 Importing Drive Test Data with Scrambling Codes as Integers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19412.1.12.6 Importing Drive Test Data for Active and Filtered Transmitters Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

12.1.13 ACP Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19412.1.13.1 Specifying the Location of the Acp.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

10


12.2 ACP Initialisation File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19412.2.1 Managing Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19412.2.2 GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19512.2.2.1 Default Values on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19512.2.2.2 Displaying Advanced Cost Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19512.2.2.3 Automatically Creating Custom Zones on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19612.2.2.4 Default Values on the Objectives Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19612.2.2.5 Default Values on the Reconfiguration page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20312.2.2.6 Default Values on Sites tab of Reconfiguration page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20512.2.2.7 Custom Columns on Sites tab of Reconfiguration page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20512.2.2.8 Default Values on the Transmitters Tab of the Reconfiguration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20512.2.2.9 Custom Columns on Transmitters/Remotes tabs of Reconfiguration page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20612.2.2.10 Default Values on the Patterns tab of the Antenna Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20612.2.2.11 Default Values for EMF Exposure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20612.2.2.12 Controlling Antenna Pattern Smoothing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20712.2.2.13 Default Values on the Antennas Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20812.2.2.14 Defining the Antenna Masking Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20812.2.2.15 Defining Multi‐Storey Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20812.2.2.16 Defining Reconfiguration Values in Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20812.2.2.16.1 Defining Reconfiguration Values for Transmitters and Repeaters Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . 20912.2.2.16.2 Defining Reconfiguration Values for Secondary Antennas Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . 21012.2.2.16.3 Defining Reconfiguration Values for Cells Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21012.2.2.16.4 Defining Reconfiguration Values for Sites Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21112.2.2.16.5 Defining Reconfiguration Values for Antennas Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

12.2.2.17 Defining Site Class Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21312.2.2.17.1 Defining Automatic Site Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21312.2.2.17.2 Automatic Assignment of Site Classes in the ACP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

12.2.2.18 Defining the Appearance of the Optimisation Dialog Box During a Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21412.2.2.18.1 Defining the Colours in the Analysis Maps on the Quality Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21412.2.2.18.2 Other Components of the Optimisation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

12.2.2.19 Defining the Appearance of Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21512.2.2.20 Defining New Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21612.2.2.21 Defining the Functionality of the Commit Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21612.2.2.22 Defining the Appearance of the Overlay Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21712.2.2.23 Defining the Appearance of the Graph Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21712.2.2.24 Defining the Default Font. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21712.2.2.25 Exporting Optimisation Results in XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21712.2.2.26 Changing the Colour Legend for the Optimisation Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

12.2.3 ACP Core Engine Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21812.2.3.1 Log File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21812.2.3.2 Calculation Thread Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21812.2.3.3 Number of Threads Used for Propagation Model Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21812.2.3.4 Memory Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21912.2.3.5 Signal Level and Macro Diversity Gain Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21912.2.3.5.1 Signal Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21912.2.3.5.2 Macro Diversity Gain (UMTS Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

12.2.3.6 Determining Transmitter Altitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22012.2.3.7 Automatic Candidate Positioning Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22012.2.3.8 Balancing Speed, Memory Use, and Accuracy in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22012.2.3.9 Accessing Raster Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22112.2.3.10 Accessing Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22112.2.3.11 Filtering Clutter Class Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22112.2.3.12 Preamble Segmentation (WiMAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22212.2.3.13 Multi‐antenna Interference Calculation (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22212.2.3.14 Multi‐antenna Interference Calculation (WiMAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22212.2.3.15 Cyclic Prefix Energy in Signal Level Calculation (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22212.2.3.16 Cyclic Prefix Energy in Signal Level Calculation (WiMAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22312.2.3.17 Applying Transmit Diversity Gains to Reference Signals (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22312.2.3.18 Fixed Ratio Between Pilot Power and Max Power (UMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22312.2.3.19 Showing Initial/Final "Total Power"or "DL Load" on Sectors Tab (UMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22312.2.3.20 Enabling Multi‐technology Optimisation Including WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

12.2.4 EMF Exposure Core Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22312.2.5 Other Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22412.2.5.1 Validity of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

11


12

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 1: Getting Started

1 Getting StartedAtoll is an open, scalable, and flexible multi‐technology network design and optimisation platform that supports wirelessoperators throughout the network life cycle, from initial design to densification and optimisation. Atoll supports a wide rangeof implementation scenarios, from standalone to enterprise‐wide server‐based configurations using distributed and multi‐threaded computing.

This manual explains how to install, configure, and deploy Atoll and how to set up back‐end databases and manage users ina multi‐user environment.

In this chapter, the following are explained:

• "Supported Technologies" on page 13• "Supported Operating Systems" on page 13• "Supported Database Management Systems" on page 14• "Supported Installation Configurations" on page 14• "Recommended Hardware and Software" on page 14• "Recommended Computer Network Architecture" on page 16.

1.1 Supported TechnologiesAtoll supports the following radio technologies: GSM GPRS EDGE, UMTS HSPA, CDMA2000 1xRTT EV‐DO, LTE, TD‐SCDMA,WiMAX, and Wi‐Fi. It also supports 3GPP Multi‐RAT (combined GSM, UMTS, and LTE) and 3GPP2 Multi‐RAT (combinedCDMA2000 and LTE). Atoll Microwave supports detailed design and analysis of microwave link networks.

1.2 Supported Operating SystemsAtoll supports the following versions of Microsoft Windows operating systems. Atoll also supports VMWare ESXi 4.x and 5.1virtualisation platforms.

Supported Operating Systems for Atoll 32‐bit

• Microsoft Windows XP Professional SP3 (32‐bit and 64‐bit)• Microsoft Windows Vista SP2 (32‐bit and 64‐bit)• Microsoft Windows 7 (32‐bit and 64‐bit)• Microsoft Windows 8 Professional and Enterprise (32‐bit and 64‐bit)• Microsoft Windows Server 2003• Microsoft Windows Server 2008 (32‐bit and 64‐bit)• Microsoft Windows Server 2008 R2 SP1• Microsoft Windows Server 2012

Supported Operating Systems for Atoll64‐bit

• Microsoft Windows 7 (64‐bit)• Microsoft Windows 8 Professional and Enterprise (64‐bit)• Microsoft Windows Server 2008 SP2 (64‐bit)• Microsoft Windows Server 2008 R2 SP1• Microsoft Windows Server 2012

Among other Microsoft Windows components, Atoll 64‐bit uses Microsoft AccessDatabase Engine 64‐bit. Microsoft Access Database Engine 64‐bit is included in MicrosoftOffice 64‐bit, and is also available as a free redistributable Microsoft Windowscomponent from the Forsk support website.

• If the computer on which you wish to install and run Atoll 64‐bit already hasMicrosoft Office installed, you must upgrade it to Microsoft Office 64‐bit (version2010 SP1 or newer).

• If you do not have Microsoft Office installed, you can download and install theMicrosoft Access Database Engine 64‐bit redistributable (version 2010 SP1)needed by Atoll 64‐bit from the Forsk support website.

Note: Installing Microsoft Office 64‐bit or the Microsoft Access Database Engine 64‐bitrequires uninstalling any 32‐bit Microsoft Office components that may be installed onthe computer.

13

Atoll 3.2.1 Administrator ManualChapter 1: Getting Started © Forsk 2014

1.3 Supported Database Management SystemsIn a multi‐user environment, databases allow several users to share data without the risk of data inconsistency. In a multi‐userenvironment, user documents are connected to a central database, in which users store their work on a common project.

Atoll supports the following RDBMS:

• Oracle 10g and 11g. Oracle client version 10.0.2.3 or later should be used.• Microsoft SQL Server 2005 and 2008• Microsoft Access 2003 and later

The physical location of databases varies according to the type of the database. The following table shows where the databasemust be installed:

1.4 Supported Installation ConfigurationsDepending on your requirements, Atoll can be installed in a:

• Standalone configuration:Atoll installed on each individual user computer with a fixed licence key plugged in each computer.

• Workstation‐based multi‐user configuration:Atoll installed on each individual user computer on a network with a floating licence management server thatallocates licence tokens to Atoll sessions run by users on their computers.

• Server‐based multi‐user configuration:Atoll installed on servers connected to user computers and a floating licence management server on a network. Thefloating licence management server allocates licence tokens to Atoll sessions run by the users on the servers. Theservers can be Citrix‐based, where users run Atoll sessions on the servers through the Citrix interface.

1.5 Recommended Hardware and SoftwareThis section provides guidelines for dimensioning client computers and servers on your network for optimum performancewith Atoll. This section lists the recommended hardware and software for:

• "User Computers" on page 14• "Database Servers" on page 15• "Application Servers" on page 15• "Floating Licence Servers" on page 15• "File Servers" on page 15.

1.5.1 User ComputersThe following table lists the required and recommended hardware and software for user computers (clients) intended forrunning with Atoll.

User computers must also have a USB port available for plugging in a fixed licence key, or the nethasp.ini file providinginformation on accessing floating licence server.

If you are working with an Oracle database, you must install Oracle client on the user computers as well. The Oracle clientversion 10.0.2.3 or later should be used.

Database Server Client computer

Microsoft Access No Yesa

a. It is possible to work with an Atoll document connected to a Microsoft Access database even if Microsoft Access is notinstalled on the computer.

Microsoft SQL server Yes No

Oracle Yes Yes (Oracle client)

Processor Core i7

RAM 8 GB or more

Storage 512 GBa (preferably SSD)

a. Depends on the size of the locally stored geographic data and path loss matrices, if any.

Operating system Windows 7 or Windows 8 Professional or Enterprise

14

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 1: Getting Started

1.5.2 Database ServersThe following table lists the required and recommended hardware and software for an Oracle database server. The sameconfiguration can be considered valid for other database systems as well.

1.5.3 Application ServersApplication servers are intended for installing and running Atoll, defining user rights, etc. Users can work with Atoll installedon these servers through thin clients such as Remote Desktop or Citrix.

The following table lists the required and recommended hardware and software for application servers intended for runningwith Atoll.

The minimum bandwidth between application servers and client computers for satisfactory performance is 300 kbps per user.

1.5.4 Floating Licence ServersThe floating licence management server:

• Must be accessible to all the user computers / Citrix servers on the network in order to provide licence tokens for Atollsessions.

• Must have a steady and reliable network connection with user computers / Citrix servers.• Must have the HASP licence manager installed and running. For more information, see "Working with Floating

Licences" on page 31.• Must have the floating licence key plugged in.• Can be one of the application servers.

1.5.5 File ServersFile servers can store geographic data, path loss matrices, Atoll configuration and initialisation files, and user projects. Therequired hard disk space has to be determined from the file sizes of these data.

Gigabit Ethernet is recommended for connecting user computers, application servers, and file servers. Network bandwidth isrequired for data exchange between Atoll sessions and file servers.

Geographic data and shared path loss matrices should be stored on file servers so that the calculation processes accessingthese data do not affect Atoll’s usage and unnecessarily slow down the GUI.

Processor Xeon E3/E5 family or equivalent

RAM 8 GB or more

Storage 2x146 GB (RAID 1) or morea

a. Tablespace of around 100 MB per 10000 transmitters.

Operating systemOracle: Windows / UNIX / Linux / Solaris

SQL Server: Microsoft Windows

Connectivity Gigabit Ethernet or better

RDBMSOracle 10g or 11g

Microsoft SQL Server 2005

Processor 1 quad‐core for 2 to 3 users

RAM 4 GB per user (minimum 8 GB)

Storage 2x146 GB (RAID 1)

Connectivity Gigabit Ethernet or better

Operating systemWindows Server 2008 R2 SP1

Windows Server 2012

Thin‐client configurationRemote Desktop

Citrix XenApp 6.0 or later

Virtualisation VMWare ESXi 4.x or 5.1

15

Atoll 3.2.1 Administrator ManualChapter 1: Getting Started © Forsk 2014

1.6 Recommended Computer Network ArchitectureThe following network architecture recommendations are based on benchmark tests carried out on the network of anaverage‐size operator, with around 40 to 60 Atoll licences. The results show the requirements in terms of network, hardware,and software. Based on these following, you can set up your network environment for any number of users.

The benchmark tests were based on the following scenario:

• Number of end‐users: 40

• Each user working on an Atoll document with:

• Total number of sites: 1660 sites (around 5000 cells)• Number of sites in the calculation area: 300 sites (900 cells)• Per‐sector path loss calculation radius: 20 km (i.e., matrices of 40 km x 40 km each)• Path loss calculation resolution: 50 m

In order to simulate the average activity of Atoll users, each user is assumed to carry out a "Routine Operation" 5 times duringa three‐hour working period. The "Routine Operation" consists in modifying parameters for 40 cells in 30 minutes,recalculating path loss matrices for these 40 cells, and calculating a best server coverage prediction.

Although a best server coverage prediction does not require a lot of computer resources for calculations, it requires Atoll toload all the path loss matrices in memory. When the path loss matrices are stored on a file server, as recommended, thisoperation creates a considerable data transfer activity over the network. The benchmark tests have been based on thissimulated data transfer activity.

Computer Network Architecture

A centralised network architecture is the most widely used network architecture by Atoll users. The figure below shows therecommended architecture along with a per‐user network bandwidth requirement between network components.

Citrix XenApp is used to centralise data and balance user loads between servers. A network based on such an architecture withCitrix servers must provide high speed connections between the Citrix servers and the file servers.

The required number of Citrix servers depends on the number of users. On the average, one processor per 2 to 3 users isrecommended. Thus, the required number of Citrix servers depends on the number of processors and end‐users.

Computer Network Dimensioning

You should set up your network according to the number of Atoll users, which is related to the size of the planning project. Acountry‐wide project would have larger network dimensions than a project that covers a city.

Figure 1.1: Recommended Network Architecture and Bandwidth Requirements

LinkRecommended Bandwidth

From To

End‐user Citrix server 300 kbps per user

Citrix server File server 30 Mbps per user performing calculations

16

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 2: Installing Atoll and Components

2 Installing Atoll and ComponentsThe following sections describe the installation procedures for Atoll and its following components:

• Driver for Fixed Licence Keys• Distributed Calculation Server• Atoll Management Console• Add‐ins and macros

You need administrator rights for installing Atoll and its components.

2.1 Installing Atoll Using the Setup WizardTo install Atoll:

• If you work with fixed licences, you must unplug the key before the installation and wait for the installation to finishbefore plugging it back in.

• Disable UAC (User Account Control) for the following versions of Microsoft Windows. If you are installing Atoll onother versions of Microsoft Windows, proceed to step 1.

• Microsoft Windows Vista• Microsoft Windows 7• Microsoft Windows 8• Microsoft Windows Server 2008• Microsoft Windows Server 2008 R2• Microsoft Windows Server 2012

To disable UAC:

a. Go to Control Panel > User Accounts.

b. Select Change User Account Control settings. The User Account Control Settings dialogue appears.

c. Choose Never notify.

d. Click OK.

• If you are installing Atoll 64‐bit, make sure that the Microsoft Access Database Engine 64‐bit is already installed on thecomputer. Microsoft Access Database Engine 64‐bit is included in Microsoft Office 64‐bit, and is also available as a freeredistributable Microsoft Windows component from Forsk’s support website.

If the computer on which you wish to install and run Atoll 64‐bit already has Microsoft Office installed, you mustupgrade it to Microsoft Office 64‐bit (version 2010 SP1 or newer). This will automatically install the Microsoft AccessDatabase Engine 64‐bit.

If you do not have Microsoft Office installed, you can download and install the Microsoft Access Database Engine 64‐bit redistributable (version 2010 SP1) needed by Atoll 64‐bit from Forsk’s support website.

1. Run the Atoll setup.

The setup program uses a wizard interface, with a step‐wise description of the installation. You can:

• Click Next to proceed to the next step,• Click Back to go back and modify previously set options, or• Click Cancel to cancel the installation.

2. Click Next. The Select Destination Location dialogue appears.

3. Select the destination folder for the installation:

• If you are installing Atoll 32‐bit, the default installation folder is:• C:\Program Files\Forsk\Atoll in the 32‐bit versions of Microsoft Windows, or• C:\Program Files (x86)\Forsk\Atoll in the 64‐bit versions of Microsoft Windows

• If you are installing Atoll 64‐bit, the default installation folder is:• C:\Program Files\Forsk\Atoll in the 64‐bit versions of Microsoft Windows

You can select a different location by clicking Browse.

Installing Microsoft Office 64‐bit or the Microsoft Access Database Engine 64‐bit requiresuninstalling any 32‐bit Microsoft Office components that may be installed on thecomputer.

17

Atoll 3.2.1 Administrator ManualChapter 2: Installing Atoll and Components © Forsk 2014

4. Select the Create a system restore point check box if you wish to the Atoll setup to create a system restore point.

5. Click Next. The Select Components dialogue appears.

6. Select the components to install.

• Full installation: Atoll and all its components will be installed.• Compact installation: Only Atoll will be installed.• Custom installation: Atoll and the selected components will be installed.

7. Click Next.

If you selected the Distributed Calculation Server component for installation, the Logon Information dialogueappears.

If you did not select this component, the Select Start Menu Folder dialogue appears. In which case, proceed to step 8.

a. Enter the Domain name, Username, and Password.

This information will be used to run the distributed calculation service on the computer, and allow other users ofthe domain to access this service.

b. Click Next. The Select Start Menu Folder dialogue appears

8. Select the Start Menu folder for Atoll.

Figure 2.1: Select Destination Location Dialogue for Atoll

Figure 2.2: Select Components Dialogue

Figure 2.3: Select Components Dialogue

18


The default Start Menu folder for Atoll is Atoll. You can select a different folder by clicking Browse.

9. Click Next. The Ready to Install dialogue appears.

10. Review the installation parameters.

11. Click Install. Atoll and its selected components are installed on the computer.

• If you work with fixed licences and you installed the Driver for Fixed Licence Keys, restart the computer. Restartingthe computer is necessary for the driver to work.

• If you work with fixed licences, plug in the fixed licence key.

• On the versions of Microsoft Windows that support UAC (disabled before the installation), run Atoll once using anadministrator account and with UAC disabled when the installation is complete.

2.2 Installing a Language Pack Using the Setup WizardYou can install additional languages to view menus, dialogues, and other user interface items in your preferred language. Inthe current version of Atoll, only the French language pack is available.

Figure 2.4: Select Start Menu Folder Dialogue

Figure 2.5: Ready to Install Dialogue

• If the following files do not already exist in the installation folder, empty ones arecreated by the setup:• [Atoll installation folder]\Atoll.ini• [Atoll installation folder]\coordsystems\Favourites.cs• [Atoll installation folder]\CWMeasurementsImport.ini• [Atoll installation folder]\DriveTestDataImport.ini

These files are not removed when Atoll is uninstalled.

• If you have installed Atoll on a Citrix server, you must publish it to make it accessibleto users.

To restrict access to the Atoll installation folder, you can assign read/write access rightsto this folder to administrators and read‐only rights to end‐users.

19


To install the Atoll language pack:

1. Run the Atoll language setup for the language of your choice.

The setup program uses a wizard interface, with a step‐wise description of the installation.

2. Click Next. The Select Destination Location dialogue appears in the language you chose.

3. Select the destination folder for the installation:

• If you are installing a language pack for Atoll 32‐bit, the default installation folder is:• C:\Program Files\Atoll in the 32‐bit versions of Microsoft Windows, or• C:\Program Files (x86)\Atoll in the 64‐bit versions of Microsoft Windows

• If you are installing a language pack for Atoll 64‐bit, the default installation folder is:• C:\Program Files\Atoll in the 64‐bit versions of Microsoft Windows


The next time you launch Atoll, the user interface will be displayed in the language corresponding to the installed languagepack.

2.3 Installing Atoll C++ Development KitTo install the Atoll C++ development kit:

• Visual C++ must be installed before installing the Atoll C++ development kit.

• Atoll should be installed for testing the add‐ins.

• Disable UAC (User Account Control) for the following versions of Microsoft Windows. If you are installing Atoll C++development kit on other versions of Microsoft Windows, proceed to step 1.

• Microsoft Windows Vista• Microsoft Windows 7• Microsoft Windows 8• Microsoft Windows Server 2008• Microsoft Windows Server 2008 R2• Microsoft Windows Server 2012

To disable UAC:

a. Go to Control Panel > User Accounts.

b. Select Change User Account Control settings. The User Account Control Settings dialogue appears.

c. Choose Never notify.

d. Click OK.

1. Run the Atoll C++ development kit setup.

The setup program uses a wizard interface, with a step‐wise description of the installation. You can,

• Click Next to proceed to the next step,• Click Back to go back and modify previously set options, or• Click Cancel to cancel the installation.

2. Click Next. The Select Destination Location dialogue appears.

3. Select the destination folder for the installation.

• If you are installing the Atoll C++ development kit with Atoll 32‐bit, the default installation folder is:

Figure 2.6: Select Destination Location Dialogue for a Language Pack

20


• C:\Program Files\Forsk\Atoll in the 32‐bit versions of Microsoft Windows, or• C:\Program Files (x86)\Forsk\Atoll in the 64‐bit versions of Microsoft Windows

• If you are installing the Atoll C++ development kit with Atoll 64‐bit, the default installation folder is:• C:\Program Files\Forsk\Atoll in the 64‐bit versions of Microsoft Windows


4. Click Next. The Ready to Install dialogue appears.

5. Review the installation parameters.

6. Click Install. Atoll C++ Development Kit is installed on the computer.

2.4 Setup Command Line ParametersYou can also install Atoll and its components from the command line. The Atoll setup program accepts optional command lineparameters, which can be useful to administrators, and to other programs calling the setup program. For example, whenautomating the installation through batch files.

The following command line parameters are accepted by the Atoll setup program.

• /SILENT, /VERYSILENT

Instructs the setup to be silent or very silent. When the setup is silent the wizard window is not displayed but theinstallation progress window is. When a setup is very silent the installation progress window is not displayed.Everything else is normal. So, for example, error messages during installation are displayed, and also the startupprompt.

If the setup is silent and it requires to restart the computer, but the /NORESTART option is not used (see below), it willdisplay a Reboot now? message box. If it is very silent it will reboot without asking.

• /NOCANCEL

Prevents the user from cancelling the installation by disabling the Cancel button and ignoring clicks on the Closebutton. Useful along with /SILENT or /VERYSILENT.

• /NORESTART

Instructs the setup not to restart the computer even if necessary.

• /SAVEINF="file name"

Figure 2.7: Select Destination Location Dialogue

Figure 2.8: Ready to Install Dialogue

21


Instructs the setup to save installation settings to the specified file. Use quotes if the file name contains spaces.

• /LOADINF="file name"

Instructs the setup to load the settings from the specified file after having checked the command line. This file can beprepared using the /SAVEINF command as explained above. Use quotes if the file name contains spaces.

• /DIR="x:\folder name"

Overrides the default installation folder displayed on the Select Destination Location wizard page. Use quotes if thefolder name contains spaces.

• /GROUP="folder name"

Overrides the default start menu folder name displayed on the Select Start Menu Folder wizard page. Use quotes ifthe folder name contains spaces.

• /LOG="file name"

Causes the setup to create a log file listing file installation and actions taken during the installation process. This canbe helpful for troubleshooting. For example, if you suspect a file is not being installed as it should be, the log file willtell you if the file was actually skipped and why. Use quotes if the filename contains spaces. If the file cannot becreated, the setup will abort with an error message.

• /SVRACCOUNT="domainname\username"

The domain name and user name for installing the distributed calculation server.

• /SVRPASSWD=password

Password for installing the distributed calculation server.

• /TYPE=type name

Overrides the default setup type. The setup type names are:

• Full installation: full• Compact installation: compact• Custom installation: custom

For full and compact setup types, the /COMPONENTS parameters are ignored.

• /COMPONENTS="comma separated list of component names"

Overrides the default component settings. Using this command line parameter causes the setup to automaticallyselect a custom installation type. Only the specified components will be selected. Component names are:

• Atoll: Atoll• Export to Google Earth add‐in: "Addins\GoogleEarth"• Best Signal Export add‐in: "Addins\SignalsExport"• Driver for fixed licence keys: RainbowDongle• Distributed calculation server: Atoll_Server• Atoll Management Console: AMC

Example: To install Atoll, the distributed calculation server, and the driver for fixed licence keys:

/COMPONENTS="Atoll,Atoll_Server,RainbowDongle"

2.5 Installing and Uninstalling Add‐insAdd‐ins are compiled DLL files which can be placed in any folder and activated by registering them in the Windows registry.Add‐ins developed by Forsk have dedicated setup programs, which place the add‐ins’ DLLs in appropriate locations andregister them. The setup procedures in these cases are described in the add‐ins’ documentation.

To install an add‐in by registering its DLL:

1. Close Atoll.

2. Right‐click the DLL file in Windows Explorer. The context menu appears.

3. Select Register. The DLL is registered.

You can also register the DLL from the command prompt using regsrv32.exe. Once an add‐in is installed, Atoll loads itin the list of available add‐ins. It is possible to access and work with add‐ins and macros when there is no ATL file openin Atoll.

22


To activate or deactivate an installed add‐in in Atoll:

1. In Atoll, select Tools > Add‐ins and Macros. The Add‐ins and Macros dialogue appears (see Figure 2.9 on page 23).

2. Select the add‐in’s check box to activate it, or clear the check box to deactivate it.

Add‐ins installed by the Atoll setup are uninstalled when Atoll is uninstalled. To uninstall any other add‐in by unregistering itsDLL:

1. Close Atoll.

2. Right‐click the DLL file in Windows Explorer. The context menu appears.

3. Select Unregister. The DLL is unregistered.

You can also unregister the DLL from the command prompt using regsrv32.exe /u.

2.6 Installing and Uninstalling MacrosAtoll can load and execute macros written in VBScript.

To load a macro in Atoll:


2. Click Add. The Open dialogue appears.

3. Select the macro file you wish to load.

4. Click Open. The New Script window opens.

5. Specify the script settings:

• Timeout: This is delay after which an unresponsive macro is stopped. To disable the macro timeout, set it to 0. Ifyou leave the timeout empty, a value of 24 days is used. The default value is 60 seconds.

• UTF‐8 Encoding: Select this option if the macro file contains non‐ASCII characters (for example: "°" or "µ").

Lists of macros available in Atoll can be stored in user configuration files. Macros listed in the user configuration files areadded to Atoll when the user configuration files are loaded. For more information, refer to "Contents of User ConfigurationFiles" on page 118.

Installed add‐ins are automatically loaded by Atoll and appear in the Add‐ins and Macrosdialogue (Figure 2.9 on page 23). If you wish that a certain add‐in not be loaded, andhence be unavailable for activation in this dialogue, you can do so by adding an option inthe Atoll.ini file. For more information, see "Loading, Activating, and Setting Add‐ins asVisible" on page 158.

Figure 2.9: Add‐ins and Macros Dialogue

23


To remove a macro from Atoll:


2. In the list of available macros, select the macro you wish to remove.

3. Click Delete.

Other commands available in the Add‐ins and Macros dialogue are:

• Edit: Edit the selected macro in the default text editor.• Run: Execute the selected macro.• Icon: Assign an icon to the selected macro. Icons assigned to macros appear in the Macros toolbar.• Refresh: To reload the selected macro file.

2.7 Atoll Command Line ParametersAtoll supports the following optional command line parameters:

• ‐log "logfilename"

Instructs Atoll to create a log file containing all the messages listed in the Events tab. This can be helpful fortroubleshooting. "logfilename" is the full path and file name of the log file inside quotes.

• ‐Ini "inifilename"

Instructs Atoll to load the specified initialisation file when run. This can be used to override the default loading of theAtoll.ini file located in the Atoll installation folder. "inifilename" is the full path and file name of the initialisation fileinside quotes.

• ‐Cfg "cfgfilename"

Instructs Atoll to load the specified user configuration file when run. This can be used to override the default loadingof the Atoll.cfg file located in the Atoll installation folder. "cfgfilename" is the full path and file name of the userconfiguration file inside quotes.

• ‐Provider providername

Instructs Atoll to use the mentioned providername to access the database server:

• ‐DataSource server

Instructs Atoll to access the mentioned database server using the given provider.

• ‐UserId username

Instructs Atoll to access the mentioned Oracle database server using the mentioned username.

• ‐Password password

Instructs Atoll to access the mentioned Oracle database server using the mentioned password.

• ‐Project projectaccount

Instructs Atoll to access the mentioned Oracle database server using the mentioned projectaccount.

Atoll.exe [-log "logfilename"] [-Ini "inifilename"] [-Cfg "cfgfilename"]

[-Provider providername -UserId username -Password password

-DataSource server -Project projectaccount]

Provider Atoll version providername

Microsoft Access32‐bit64‐bit

Microsoft.Jet.OLEDB.4.0Microsoft.ACE.OLEDB.12.0

SQL Server 32/64‐bit SQLOLEDB

Oracle (Oracle driver) 32/64‐bit OraOLEDB.Oracle

• The keywords Provider, Password, UserId, DataSource, and Project are case sensitive.

24


2.8 Troubleshooting and Other InformationRead and follow carefully the instructions in "Installing Atoll Using the Setup Wizard" on page 17 for a smooth installation.

If problems occur and you are unable to resolve them with the help of the following information, contact Forsk’s customersupport.

Microsoft Windows Updates

• It is recommended to install new Windows updates. However, it is also recommended to go through the descriptionof each update patch to see whether it might have a negative effect on your system or network. Pay special attentionto updates and patches related to networking.

• It is also recommended to keep the Windows updates uninstall folders, named "$NtUninstall...", under the Windowsfolder, in case you have to uninstall a certain patch. Some of the update patches might require uninstall folders ofolder patches to be available for their own installation.

Fixed licence keys

• Fixed licence keys cannot be used with "Server"‐type operating systems. Therefore, you should not install the driverfor fixed licence keys on:

• Microsoft Windows Server 2003• Microsoft Windows Server 2008• Microsoft Windows Server 2008 R2• Microsoft Windows Server 2012

• The current version of the driver for fixed licence keys (Sentinel SuperPro driver) installed with Atoll is the 7.6.3.• If Atoll is unable to access the fixed licence key, even after a clean installation, try reinstalling the Sentinel SuperPro

driver manually. The driver’s setup program (SPI763.exe) is copied by the setup to the Sentinel subfolder in the Atollinstallation folder if you selected the Driver for Fixed Licence Keys component during the installation. You can alsodownload the driver from http://www.safenet‐inc.com.

• Restart the computer when asked by the setup. Restarting the computer is necessary for the driver for fixed licencekeys to work.

• If you get a protection key error message, verify that the fixed licence key is correctly plugged in and that the licencehas not expired.

• In case the fixed or the floating licence key becomes unavailable, Atoll will ask the users currently accessing the keyto save their open documents before Atoll closes. If the key becomes available again, Atoll will let the users continueworking.

• Do not change the computer’s date.

Citrix

• If you have installed Atoll on a Citrix XenApp server, you must publish it to make it available to the users.

Atoll version and build

• You can get information about Atoll (version, build, type of licence and remaining time before expiration, etc.) byselecting Help > About Atoll in the main menu in Atoll.

Atoll file version and technology

ATL file properties store the Atoll version and build number in which the file was last saved, and the technologies containedin the file. To access the ATL file properties:

1. Right‐click the ATL file in the Windows Explorer. The context menu appears.

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

3. In Windows XP, click the Summary tab and then the Advanced button.In Windows Vista, 7 and 8, click the Details tab.

The Atoll version and build number in which the ATL file was last saved are stored in the Revision number property.The technologies of the document are listed in the Category property.

Support website

• You can download the latest versions of Atoll from the Forsk’s support website by logging in with the user name andpassword provided to you by Forsk.

• The Atoll User Manual and other documents are available on the installation CD. More documents are available fordownload on the Forsk’s support website.

• The support website also offers you:

25

http://www.safenet-inc.com


• Sample add‐ins, macros, and scripts• Sample geographic data,• List of fixed issues in the versions available for download,• List of known issues, and possible workarounds,• Schedule for upcoming versions,• List of holidays.

For full contact details for customer support, see back cover.

Acknowledgement

• Atoll uses Inno Setup for installation. For more information, see http://www.jrsoftware.org/isinfo.php.

Uninstalling Atoll and its components

It is recommended to uninstall Atoll and its components through the Control Panel.

To uninstall Atoll:

• In Windows XP or Windows Server 2003:

a. Go to Control Panel > Add or Remove Programs.

b. In the Install/Uninstall tab, select Atoll from the list of installed programs.

c. Click the Remove button.

• In Windows Vista, Windows 7 and 8, or Windows Server 2008 and 2012:

a. Go to Control Panel > Programs and Features.

b. In the Uninstall or change a program window, right‐click Atoll. The context menu appears.

c. Select Uninstall.

26

http://www.jrsoftware.org/isinfo.php

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 3: Setting Up Distributed Calculation Server

3 Setting Up Distributed Calculation ServerDistributed calculation enables you to distribute the calculation of path loss matrices over many computers in a network. Thedistributed calculation service is an optional service that can be installed at the same time as Atoll. For more information oninstallation, see "Installing Atoll and Components" on page 17.

A computer on which the distributed calculation service is installed and running is called a distributed calculation server. Thiscomputer, the distributed calculation server, is visible to all the other computers on the network through Atoll. You can setup as many distributed calculation servers as required.

The distributed calculation service does not have a user interface, and hence has lower memory requirements than Atoll. Thedistributed calculation server uses the standard Atoll API to exchange data with the path loss calculator and Atoll. Thedistributed calculation service supports dual‐processor configurations and up to four threads.

Any version of Atoll can work with the distributed calculation service of the same or later version. Consequently, any versionof the distributed calculation service can work with the same or previous versions of Atoll (versions still maintained by Forsk).

For distributed calculation server options available through the Atoll.ini file, see "Distributed Calculation Server Options" onpage 163.

3.1 Setting Up ServersWhen installed, the distributed calculation service automatically starts and remains available as long as the computer isturned on. The service does not require any active user session on the computer, i.e., the service keeps running even whenthere is no user logged on. The service’s executable (AtollSvr.exe) is installed in the Atoll installation folder.

The Atoll distributed calculation service is listed as Atoll Server in the Services management console under ControlPanel >Administrative Tools.

During calculations, the distributed calculation servers require access to geographic data for calculating the path loss matrices.The distributed calculation service must be run with a user account that has sufficient privileges to access the required data.

To modify the user account through which the distributed calculation service is run on a computer:

1. Log on to the computer with a user account with administrator rights.

2. Go to Control Panel > Administrative Tools > Services.

3. In the list of services, right‐click the Atoll Server service. The context menu appears.

4. Select Properties. The Atoll Server Properties dialogue appears.

5. On the Log On tab, enter the user name and password for the user account through which you wish to run this service.

6. Click OK.

Figure 3.1: Atoll Server Properties

27

Atoll 3.2.1 Administrator ManualChapter 3: Setting Up Distributed Calculation Server © Forsk 2014

Running More Than One Instance of the Service

By default, a single instance of the distributed calculation service is run. You can, however, run up to 9 additional distributedcalculation services (a total of 10 including the first one) manually.

To manually run additional distributed calculation services, double‐click the AtollSvr.exe file located in the Atoll installationfolder. For each new instance of the service, a command prompt window opens. To stop an additional, manually run service,close the command prompt window corresponding to it.

Stopping and Starting the Distributed Calculation Server

To stop the distributed calculation service:


2. Go to Control Panel > Administrative Tools > Services.

3. In the list of services, right‐click the Atoll Server service, and select Stop or Start from the context menu.

Uninstalling the Distributed Calculation Server

To uninstall the distributed calculation service:


2. Stop the distributed calculation service:

a. Go to Control Panel > Administrative Tools > Services.

b. In the list of services, right‐click the Atoll Server service, and select Stop from the context menu.

3. Unregister the service:

a. Select Start > Run. The Run dialogue appears.

b. Type "<Atoll Installation Path>\AtollSvr.exe /UnregServer". <Atoll Installation Path> is the path to the Atollinstallation folder.

c. Click Run.

This will remove the distributed calculation service from the computer.

3.2 Setting Up Atoll to Access the ServersTo activate distributed calculations in Atoll:

1. Select Tools > Distributed Calculations from the main menu. The Distributed Calculations dialogue appears.

2. Select the Activate distributed calculation check box.

a. To use all the available distributed calculation servers, click All.

b. To use selected distributed calculation servers only, click Detect.

Atoll searches for the available distributed calculation servers on the network. The available distributedcalculation servers are listed in the edit box.

c. Remove the distributed calculation servers that you do not wish to include.

3. Click OK. The selected distributed calculation servers are now available for path loss calculations.

3.3 Distributed Calculation ProcessOnce distributed calculations have been set up on the calculation server and on the user sides, the path loss calculations runby the user are distributed over the available calculation servers. The calculation process is as follows:

1. Atoll user runs path loss calculations.

2. Atoll sends the needed network data to the available calculation servers.

3. Either Atoll sends the needed geographic data to the calculation servers or the servers access the geographic data ona file server.

Atoll can detect a total of 10 instances of the distributed calculation service. If you runmore than 9 additional distributed calculation services, they will not be detected by Atolland can cause the operating system to stop responding.

28

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 3: Setting Up Distributed Calculation Server

4. Distributed calculation servers calculate the path loss matrices one by one.

Distributed calculation servers that have spare threads start the calculations using these threads. If no thread isavailable, the request is placed in a queue to wait for a thread to become available.

5. For each calculated path loss matrix, a confirmation is sent to the Atoll session. Any error or warning messagesgenerated are passed back to the Atoll session and displayed in the Event Viewer.

If an error occurs on any of the distributed calculation servers, Atoll transfers the calculations back to the localcomputer. However, to avoid memory saturation, Atoll uses one thread on the local computer and calculates the pathloss matrices one by one. It does not attempt creating more than one thread.

6. In order to reduce the amount of data flow in the network, distributed calculation servers send the results directly tothe storage location (which can also be on a file server, not necessarily on the user’s computer that requested thecalculations).

7. Atoll user can then request the path loss matrices from the file server if they are needed for coverage predictions.

29

Atoll 3.2.1 Administrator ManualChapter 3: Setting Up Distributed Calculation Server © Forsk 2014

30

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 4: Managing Licences

4 Managing LicencesAtoll can be used on:

• Computers with fixed licence keys plugged in to USB slots on the computers themselves, or• Computers connected to a licence server with a floating licence key plugged in to a USB port on the server.

The driver for fixed licence keys can be installed at the same time as Atoll. For more information, see "Installing Atoll andComponents" on page 17.

The software for managing floating licence keys must be installed on a server accessible to the computers on which Atoll isgoing to be used. For more information, see "Working with Floating Licences" on page 31.

For information on the Atoll licence management utility, see "Using the Atoll Licence Manager" on page 33.

4.1 Working with Floating LicencesA floating licence key can be used when users work with Atoll on computers on a network. In a floating licence environment,licence keys are not plugged in to each individual user’s computer, but a shared licence key with multiple tokens is availableto users through a server.

A floating licence server is a computer, accessible to other computers on a network, on which the floating licencemanagement software has been installed and a floating licence key plugged in. The floating licence server can be one of thecomputers on which Atoll is installed.

The floating licence management software and the floating licence key control the number of potential Atoll users. A floatinglicence system has a defined maximum number of tokens available. This is the maximum number of computers on which Atollcan be run simultaneously. Each computer that runs Atoll takes one token from the floating licence key, even if more thanone Atoll session is run on the same computer. The token is released and made available for other users when all the Atollsessions on the computer are closed.

If a computer is connected to a floating licence server and also has a fixed licence key plugged in, the fixed licence key isaccessed first.

Atoll uses a 3rd‐party floating licence management system called HASP from Aladdin. The floating licence managementsystem includes:

• HASP floating licence key: Hardware key programmed with the numbers of tokens available for each module.• HASP licence manager: Interface between Atoll and the floating licence key.• HASP device driver: Interface between the HASP licence manager and floating licence key.• HASP monitor: Enables you to check the number of used and available tokens.• nhsrv.ini file: Installed on the floating licence server to enable computers to use tokens. • nethasp.ini file: Installed on the computers to facilitate access to the floating licence server.

nhsrv.ini and nethasp.ini files are used if they exist. Default settings are used otherwise.

4.1.1 HASP Licence Manager and Device DriverThe HASP licence manager controls the allocation and retrieval of licence tokens available on a floating licence key. It uses theHASP device driver for communicating with the floating licence key.

The HASP licence manager can be installed on a computer running Windows 2000 or later. A USB port must be available onthe server for plugging in the floating licence key.

• You can download the HASP licence manager, the HASP device driver, and the HASPmonitor from http://www3.safenet‐inc.com/support/hasp/hasp4/enduser.aspx.Newer versions can be available for download at the website than those provided onthe Atoll installation disk.

• When downloading setup files from the Aladdin website, remember to downloadsetup files for HASP4, not HASP HL.

• The correct (recommended) version of the device driver setup to download is the onethat works with "HASP4 API v8.x or Envelope 12.x".

• HASP hardware key is supported by Windows 2000 Server and Windows Server 2003with HASP Licence Manager 8.20 or above.

31

http://www3.safenet-inc.com/support/hasp/hasp4/enduser.aspx

Atoll 3.2.1 Administrator ManualChapter 4: Managing Licences © Forsk 2014

Installation and Startup

The HASP licence manager, the HASP device driver, and the floating licence key must be installed on the server.

The following options should be selected when installing the HASP licence manager:

• Choose "Service" as the type of installation.

This means that the licence manager will run as a service, and will be accessible even if there is no user logged on. Youcan choose to install it as an application, but in that case you will have to run the licence manager manually every timeyou log on to the server and you will have to stay logged on for the licence server to be available to the Atoll users.

• Accept automatic driver installation.

This will install the HASP device driver required by the HASP licence manager.

• Once the device driver is successfully installed, plug in the floating licence key.

• Once installed, start the HASP licence manager.

If you selected "Service" as the type of installation, the licence manager will start in service mode. An icon will beavailable in the task bar. You can access the network communication protocols by double‐clicking this icon.

The HASP licence manager window displays a list of supported protocols which can be modified through the Load andRemove menus. Closing this window does not stop the licence manager. The icon remains available in the taskbar aslong as the service is running.

To stop the HASP licence manager:

a. Go to Control Panel > Administrative Tools > Services.

b. In the list of services, right‐click the HASP Loader service, and select Stop from the context menu.

• You can also copy (from the installation CD) or create the nhsrv.ini file on the floating licence server (in the HASPlicence manager installation folder). The HASP licence manager settings in this file can be modified according to theyour requirements. For more information on the contents of the nhsrv.ini file, see "nhsrv.ini File" on page 32.

HASP Monitor (Optional)

You can install the HASP monitor on the floating licence server, or on one or several other computers, to monitor the tokenallocation and retrieval activity. The HASP monitor displays the list of computers using tokens available on the floating licencekey.

4.1.2 nhsrv.ini FileThe nhsrv.ini file can be used to define a list of computers allowed to request tokens from the floating licence server.

File Location

If used, the nhsrv.ini file must be located in a folder listed in the system path variable, such as the Windows folder (usuallyC:\Windows).

• Do not plug the floating licence key in the server before installing the device drivers.Wait for the HASP licence manager setup to indicate when to plug in the key.

• If the floating licence server is protected by a firewall, port 475 must be open whenusing the UDP or TCP protocols.

• Once the HASP licence manager has been installed, the floating licence key mustalways remain plugged in.

• In case the fixed or the floating licence key becomes unavailable, Atoll will ask theusers currently accessing the key to save their open documents before Atoll closes. Ifthe key becomes available again, Atoll will let the users continue working.

• The floating licence key can become unavailable and a key protection error messageappears in Atoll if the licence management server is heavily loaded. Check if there isany application running on the server that might be causing the problem. If this is thecase, remove any such application from memory. If this is not possible, try changingthe latency associated to the HASP licence manager in accessing the key.

To restrict access to the HASP licence manager installation folder, you can assign read/write access rights to this folder to administrators and read‐only rights to end‐users.

32


File Contents

The following is a sample of the nhsrv.ini file that shows how to set a list of computers allowed access to the floating licenceserver. Complete syntax can be found on the HASP installation CD or on the Aladdin website.

4.1.3 nethasp.ini FileThe nethasp.ini file enables Atoll to locate the floating licence server quickly. Without the nethasp.ini file, finding the floatinglicence server on the network can take a long time.

File Location

The nethasp.ini file should be located in the Atoll installation folder (recommended). If, for some reason, it is not possible tostore the file in the Atoll installation folder, it can be stored in (in the order in which it is searched for by Atoll):

• The Windows folder (usually C:\Windows)

• A folder listed in the system path variable

A nethasp.ini file located in the Atoll installation folder has priority over any nethasp.ini file located in the Windows folder,which in turn has priority over any nethasp.ini file located in a folder listed in the system path variable.

Storing the nethasp.ini file in the Windows folder instead of the Atoll installation folder can be useful if you have more thanone version of Atoll installed, and you wish to access the same floating licence server. This avoids making a copy of the file ineach Atoll installation folder.

File Contents

The following is a sample of the nethasp.ini file with the minimum required information. Complete syntax can be found onthe HASP installation CD or on the Aladdin website.

4.2 Using the Atoll Licence ManagerAtoll Licence Manager enables you to monitor, troubleshoot, and update licence keys. You must not use the licence managerwithout full instructions and details from Forsk customer support. Modifying parameters in the licence manager withoutproper input from Forsk customer support can damage your fixed or floating licences and block access of Atoll users to thelicences.

[NHS_SERVER]

;NHS_IP_LIMIT = <IpAddr0>[,<IpAddr1>,<IpAddr2>,...];Specifies the IP addresses of computers served by the licence manager;Example: 10.1.1.1, 10.1.1.*;For use, remove the semi-colon before NHS_IP_LIMIT

[NH_COMMON]

NH_IPX = Disabled ;Use the IPX protocol - Enabled or Disabled

NH_NETBIOS = Disabled ;Use the NETBIOS protocol - Enabled or Disabled

NH_TCPIP = Enabled ;Use the TCP/IP protocol - Enabled or Disabled

[NH_TCPIP]

NH_SERVER_ADDR = 3CT000J ;(a)IP address of the floating licence server

a. It is recommended to enter the server name within the domain.For example, for servername.domainname.com, enter servername only.Only one server name is supported in the nethasp.ini file.

NH_TCPIP_METHOD = UDP ;(b)Send TCP or UDP packets

b. For HASP Licence Manager 8.20 and later, Aladdin recommends UDP as the default TCP/IP method.

NH_USE_BROADCAST = Disabled ;Use TCP/IP broadcast - Enabled or Disabled

• Remove the NH_SESSION and NH_SEND_RCV entries from the nethasp.ini file if theseexist.

• These fields define the timeout delays depending to the network. They can be usefulin slow networks and should be set only if required.

33


4.2.1 Licence Manager InterfaceTo open the Atoll licence manager:

1. Close Atoll.

2. Go to the Atoll installation folder.

3. Run Lic.exe. The licence manager opens (see Figure 4.1 on page 34).

4. Under Available licences, select a licence key in order to display the information related to it.

Under Selected key the following information is available for the selected key:

• Number: Unique key number given by the key provider. This number must be communicated to Forsk, whenrequested, for reprogramming the licence key.

• Type: The type of key, Fixed licence or Floating licence.• Reference: Unique floating licence key reference provided by Forsk. This number must be communicated to Forsk,

when requested, for reprogramming the licence key. This reference is also printed on the sticker on the key.• Location (server): Name of the floating licence management server on which the floating licence key is plugged.• Under Modules and licences, all the Atoll modules available on the selected key are listed along with the numbers

of licence tokens of each.• Under Number of licences, the Modify buttons are reserved for Forsk use only.• Under Dates and durations, the following dates and durations are available:

• Licence start• Licence end• Duration of validity• Time bomb

Figure 4.1: Atoll Licence Manager

The Clear all button is reserved for Forsk use only.

34


A purchased Atoll licence corresponds to a particular Atollversion. There is no time limit on using this version.However, yearly maintenance must be purchased in order to access newer versions with updates and bug fixes.When you purchase maintenance, Forsk reprograms your licence keys to allow access to new versions.

The Time bomb date is the end date for maintenance. When the time bomb date passes, the licence key stopsworking. You can then choose to either purchase maintenance for the next year, and benefit from the newfeatures and bug fixes, or have the licence key reprogrammed without maintenance for the next year, in whichcase users can continue working with the existing version.

Atoll can inform you about the approaching time bomb date 30 days in advance. This alert can be configuredthrough the Atoll.ini file.

• Under Profile signature, the PID (profile signature or ID) is the encrypted description of the user rights availableon the key. Each key has a unique PID.

• Under Current profile summary, all of the above information is summarised.

4.2.2 Updating Licence KeysAtoll licence manager enables administrators to update licence keys by loading new key programming data from ALIC filesprovided by Forsk. To update a licence key, you must have the ALIC file sent by Forsk.

To update a licence key:

1. Close all Atoll sessions.

Atoll reads licence information from the key at the start of each session. This information is kept in memory as longas a session is running. If a licence key is updated while a session is still running, the running session will not read theupdated licence information from the key and will expire according to the old licence information.



4. Under Available licences, select the key to update. If the key does not appear in the available licences list, check thatit is plugged in to your computer.

5. Under Key programming, click Load. The Open dialogue appears.

6. Select the ALIC file provided by Forsk.

7. Click Save. The key is updated.

4.2.3 Testing Licence KeysThe Atoll licence manager enables administrators to test licence keys.

To test a licence key:

1. Close Atoll.



4. Under Available licences, select the key to test. If the key does not appear in the available licences list, check that itis plugged in to your computer.

5. Under Key programming, click Test. The Key test dialogue appears.

• Do not attempt to modify the Time bomb settings on the fixed licence key. ContactForsk’s customer support.

• Do not change the computer’s date.

Do not attempt to reprogram a licence key without full information and support fromForsk customer support.

35


6. In the Key test dialogue, under Modules, select the module that you wish to test.

7. Click Test. The test shows whether the selected module is available on the key or not.

4.2.4 Reducing the Number of Module Tokens in ALIC FilesALIC files are used by ForskAlcatel‐Lucent to program fixed or floating licence keys. ALIC files consist of a prefix which includeseither the letter A (for floating licence keys) or R (for fixed licence keys) followed by the reference number of the key. OneALIC file corresponds to one unique key with the same reference number on its sticker.

OEM clients can create new ALIC files, containing reduced numbers of module tokens, from an existing ALIC file. The ALIC filescontaining reduced numbers of module tokens can then be used for programming floating licence keys allowing the use ofonly the selected modules.

The following sections describe how you can activate this feature and use it for creating reduced token ALIC files.

4.2.4.1 Activating the Option in the Licence Manager

The feature is available through the Licence Manager (Lic.exe). To activate this feature, add the following lines in the Atoll.inifile before running Lic.exe:

4.2.4.2 Reducing the Number of Module Tokens

Once you have activated the feature, you can use the licence manager to reduce the number of modules allowed on a newALIC file as follows:


2. Run the licence manager. For more information, see "Using the Atoll Licence Manager" on page 33.

A fixed or floating licence key must be plugged in to the computer on which you are running the licence manager. Thiskey is required for opening the licence manager window. The ALIC file that you will create will not be for this key. Thedongle for which you are going to create the new ALIC file with the reduced number of tokens should be blank andnot plugged in to any computer.

3. Click the Reducing programming file tokens button. The Open dialogue appears.

4. Select the ALIC file from which you wish to create another ALIC file with a reduced number of tokens.

5. Click Open. The Module Restriction dialogue appears.

6. In the Module Restriction dialogue, set the number of tokens of each module that you wish to allow in the new ALICfile.

You can only reduce the numbers of tokens. To reduce the number of the Base modules, you must first reduce thecorresponding numbers of other modules.

7. Click Generate. A new ALIC file is generated with the numbers of module tokens that you selected. This file is locatedin the same folder as the original ALIC file.

Figure 4.2: Test Key Dialogue

Never test a module for a future date. If you enter a future date when testing a key, thiscan reduce the time left for using the key.

[RestrictAlicModuleCount]

AD384D8F-93EF-481D-B007-8F5B7E0033BC = 1

36


8. Close the licence manager.

9. Make a backup copy of the original ALIC file.

10. Remove the ".restricted" extension from the new ALIC file name.

4.2.4.3 Programming a Blank Licence Key Using the Restricted ALIC File

Once you have generated the new ALIC file with the reduced numbers of module tokens, you can programme a new blanklicence key using this file.

To program the licence key with the new ALIC file with reduced numbers of tokens:


2. Plug the licence key in to the computer.

If it is a floating licence key, set the ADDR_SERVER in the nethasp.ini file equal to the name of your computer.

To check that the key is available:

a. Run Lic.exe.

b. Under Available licences, select the blank key. The Modules and licences section should be empty for the blankkey.

c. Close Lic.exe.

3. Double‐click the ALIC file. A message will appear indicating that the programming was successful.

4. Check the new contents of the key with Lic.exe.

If the contents of the key are correct, you can send the key to your customer.

Forsk sends a new ALIC file every year to update the time bomb and maintenance dates. One year after this first programming,after receiving the ALIC corresponding to the key, the same process has to be carried out using the new ALIC file, and thegenerated ALIC files have to be sent to the customers to enable them to update their keys.

37


38

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 5: Managing Databases

5 Managing DatabasesIn Atoll, you can work with standalone documents, i.e., documents without any back‐end database, or with documentsconnected to databases. Standalone documents are more portable, however a back‐end database is required when workingin a multi‐user environment. In multi‐user environments, several users work on the same project and a central data storageis necessary for keeping the data modifications made by a team of radio planning and optimisation engineers.

Atoll enables you create databases, upgrade them to newer versions, archive and refresh data with databases, manage andresolve data conflicts, and create and work with multi‐level databases.

A database server can store one or more databases. For example, a GSM, a UMTS, and a microwave links database can bestored on the same database server using the same RDBMS (Oracle, for example).

In this chapter, the following are explained:

• "Atoll Database Templates" on page 39• "Customising Atoll Database Structures" on page 40• "Atoll Management Console" on page 42• "Creating New Databases" on page 43• "Upgrading Existing Databases" on page 45• "Working With a Multi‐level Databases" on page 49• "Setting Database Access Privileges" on page 53• "Managing Data Modifications History" on page 54

5.1 Atoll Database TemplatesAll the technology modules available in Atoll (GSM, UMTS, LTE, CDMA2000, TD‐SCDMA, WiMAX, Wi‐Fi, and Microwave RadioLinks) are based on database templates. These templates are used for creating Atoll documents with the appropriate datastructure required for planning for any technology. Databases (using RDBMS) can then be created from any Atoll document.These databases are hence also based on the data structure defined by the Atoll database templates.

In each new major release, database templates undergo modifications required to support new features. These modificationsare applied to existing Atoll documents and databases by Atoll and the Atoll Management Console, respectively. It is alsopossible to upgrade an existing database manually, but due to the complex nature of the upgrade process, it is highlyrecommended to use the Atoll Management Console for upgrading existing databases.

Each database template is an MS Access MDB file located in the templates folder in the Atoll installation folder. For the list oftables and fields, and their relationships, in each database template, see these chapters in the Data Structure Reference Guide:

• Chapter 1: "GSM GPRS EDGE Data Structure"• Chapter 2: "UMTS HSPA Data Structure"• Chapter 3: "CDMA2000 Data Structure"• Chapter 4: "LTE Data Structure"• Chapter 5: "3GPP Multi‐RAT Data Structure"• Chapter 6: "3GPP2 Multi‐RAT Data Structure"• Chapter 7: "TD‐SCDMA Data Structure"• Chapter 8: "WiMAX and Wi‐Fi Data Structure"• Chapter 9: "Microwave Links Data Structure"

The following table lists the types of fields used in Atoll database templates, their sizes, and the equivalent field types andsizes in different RDBMS:

Database template files must not be modified without consulting Forsk customer support.

• The relationships in the database schema figures are represented by arrows. These

unidirectional arrows should be read as: =

• In the tables, primary keys are listed in bold and italic characters.• In the database schema figures, primary keys are in bold and underlined characters,

and required fields are in bold characters.

n or 1

39

Atoll 3.2.1 Administrator ManualChapter 5: Managing Databases © Forsk 2014

1. Lengths for these fields are specified in parentheses in the database structure tables.

2. CLOB: Character large object

3. BLOB: Binary large object

For more information on the Atoll Management Console and upgrading databases, see "Atoll Management Console" onpage 42 and "Upgrading Existing Databases" on page 45, respectively.

5.2 Customising Atoll Database StructuresAtoll database structures can be customised by:

• Adding custom fields to data tables,• Setting user‐defined default values for fields, and• Setting user‐defined choice lists for text fields.

Custom fields, as well as user‐defined default values and choice lists for standard and custom fields, are stored in theCustomFields table.

Adding Custom Fields to Data Tables

Custom fields can be added to data tables at different stages keeping in mind that:

• Custom fields added directly to the Atoll database templates (MDB files), using Microsoft Access 2003, will beavailable in all new Atoll documents created from that template. A new database created by exporting such adocument will also contain these custom fields.

• Custom fields added to an Atoll document through the Atoll user interface will not be automatically added to thecorresponding Atoll database template. However, a new database created by exporting such a document will containthese custom fields. For more information on adding custom fields to Atoll documents through the user interface, seethe User Manual.

• Custom fields added to an Atoll database will be available in all new Atoll documents created from that database.

To add a custom field to a data table:

1. Add the custom field to the definition of the data table by defining its name, type, and size.

2. Add a corresponding record in the CustomFields table and enter values for each of the following fields:

Atoll Oracle Equivalent Microsoft SQL Server Equivalent Microsoft Access

EquivalentField Type Length Field Type Length Field Type Length

Float 4 FLOAT 32 real 4 Single

Double 8 FLOAT 64 float 8 Double

Integer 4 NUMBER 11 int 4 Long Integer

Short 2 NUMBER 6 tinyint 1 Integer

Boolean 2 NUMBER 1 bit 1 Yes/No

Text Variable1 VARCHAR2 Variable1 varchar Variable1 Text1

Memo Variable VARCHAR2 2000 varchar 4000 Memo

Binary VariableCLOB2 > 2000

image 16 OLE ObjectBLOB3 Variable

If you export the contents of an Atoll document, already connected to a database, toanother RDBMS (for example, if you export a document connected to an Oracle databaseto SQL Server), some field types will be converted according to the above table. Thisconversion does not have any impact on the document in Atoll.

FieldUser Interface

CaptionDescription

TABLE_NAME Database name of the data table that contains the field

COLUMN_NAME Name Database name of the field

DEFAULT_VALUE Default value User‐defined default value (optional)

CHOICE_LIST Choice list User‐defined choice list for text fields (optional)

40


Setting User‐defined Default Values for Fields

You can set your own default values for standard as well as custom fields using the CustomFields table. User‐defined defaultvalues entered in the CustomFields table have precedence over the predefined default values.

To enter a user‐defined default value for any field, add a new record in the CustomFields table and enter values for each ofthe following fields:

Setting User‐defined Choice Lists for Text Fields

You can set your own choice lists for standard as well as custom text fields using the CustomFields table. User‐defined choicelists entered in the CustomFields table have precedence over the predefined choice lists.

To enter a user‐defined choice list for any text field, add a new record in the CustomFields table and enter values for each ofthe following fields:

For example, you can replace the default choice list available for the SUPPORT_INFO field in the Sites table with a differentlist of options corresponding to the different types of towers and pylons that may exist in your network.

CAPTION LegendCaption of the field as it will appear in the user interface (optional but

recommended)

GROUP_NAME GroupSemicolon‐separated list of the names of groups to which the field belongs

(optional)

CHOICE_TYPE Restricted1: Custom field only accepts values listed in the choice list

0: Custom field accepts values other that those listed in the choice list

DISPLAY_TYPE Read‐only1: Custom field is read‐only in the user interface0: Custom field is modifiable in the user interface

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

FieldUser Interface

CaptionDescription

TABLE_NAME Database name of the data table that contains the field

COLUMN_NAME Name Database name of the field

DEFAULT_VALUE Default value User‐defined default value

For floating point default values, make sure that all the users have the same decimalsymbol.

FieldUser Interface

CaptionDescription

TABLE_NAME Database name of the data table that contains the text field

COLUMN_NAME Name Database name of the text field

CHOICE_LIST Choice list Choice list items, one per line

• You can enter one of the choice list items in the DEFAULT_VALUE in order to set adefault value for the text field.

• For custom text fields, you can set the CHOICE_TYPE to 1 if you want the custom textfield to only accept values listed in the choice list. By default, CHOICE_TYPE isconsidered to be 0 meaning that users are allowed to enter values other than thosedefined in the choice list.

FieldUser Interface

CaptionDescription

41


5.3 Atoll Management ConsoleThe Atoll Management Console provides the database administrator the possibility of globally managing the database withthe easy‐to‐use step‐by‐step procedures which use wizard interfaces. The Atoll Management Console lets you:

• Create databases (see "Creating New Databases" on page 43)• Upgrade database structures from one major version to the next (see "Upgrading Existing Databases" on page 45)• Work with multi‐level databases (see "Working With a Multi‐level Databases" on page 49)• Manage data modifications history in databases (see "Managing Data Modifications History" on page 54)• Manage user accounts and access rights (see "Managing User Accounts and Access Rights in Oracle" on page 65)

The Atoll Management Console supports:

• Oracle• Microsoft SQL Server

The Atoll Management Console can be installed with Atoll. For more information, see "Installing Atoll and Components" onpage 17. You can run the Atoll Management Console from the Windows Start menu program group or by double‐clickingAMC.msc in the management subfolder of the Atoll installation folder. The Atoll Management Console runs using theMicrosoft Management Console environment.

When the Atoll Management Console is run for the first time, you must register your database server in order to have thedatabases installed on the server to be available in the Atoll Management Console.

To register a database server:

1. In the Atoll Management Console window, in the left pane, right‐click the Database item under the AdministrationAtoll. The context menu appears.

2. Select Register a New Server. The Data Link Properties dialogue appears.

3. Click the Provider tab. On the Provider tab, select the provider for your database server depending on whether it isOracle or SQL Server.

4. Click Next. On the Connection tab, enter the server name, and the user name and password required to access thedatabase server.

You can check to see if the entered information is correct by clicking the Test Connection button.

5. Click OK. The selected database server is registered and available in the Atoll Management Console (see Figure 5.2on page 42). You now have access to the features offered by the Atoll Management Console.

Figure 5.1: Data Link Properties dialogue ‐ Provider Tab

Figure 5.2: Atoll Management Console

42


The tree in the left pane lists the registered database servers. Registered database servers can be connected ( ) or

disconnected ( ).

The right pane lists the databases available on the connected database server currently selected in the left pane. The currentuser can be the owner of one of the listed databases. The user name of the owner of a database appears in parentheses inthe title bar. One Oracle user can create and own one database. For each new database, you must create a new user ownerof the database.

The following details are available for databases created or upgraded using the Atoll Management Console:

• Whether the database corresponds to the current Atoll version ( ) or a previous version ( ), not yet upgraded to

the current version.• The type of the database: master or project.

A master database can have one or more project databases created from and connected to it. For more informationon master and project databases, see "Working With a Multi‐level Databases" on page 49.

• The technology of the network modelled by the database.• The path of the shared path loss folder.

To view details of a database:

1. In the right pane, right‐click the database in the list. The context menu appears.

2. Select Properties. The database Properties dialogue appears.

3. The Properties dialogue contains two tabs:

• General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database.• Statistics tab: The Statistics tab displays the number of records in each table of the database.

5.4 Creating New DatabasesNew databases can be created using the Atoll Management Console or by directly exporting a document to a database fromAtoll. In this section, the following are explained:

• "Creating a New Database Using the Atoll Management Console" on page 43• "Creating a New Database Using Atoll" on page 45

5.4.1 Creating a New Database Using the Atoll Management ConsoleYou can create new databases using the Atoll Management Console.

To create a new database:

1. In the Atoll Management Console window, in the left pane, right‐click the database server on which you want tocreate a new database. The context menu appears.

2. Select New > Database. The New Database Wizard dialogue appears.

You must have administrator rights to the database and to the server for creating newdatabases.

Figure 5.3: New Database Wizard

43


3. Click Next. The Specify the database owner page appears.

4. Select Use the current connection if you want to create a new database using the current user, or select Create a newuser and enter a Name and Password to create a new user that will be owner of the new database.

5. Click Next. The Name the database and specify a network type page appears.

6. Enter a Name for the new database and select the Network type. The Network type can be one of the databasetemplates installed with Atoll.

7. Click Next. The Specify units and coordinate systems page appears.

8. Select a Transmission power unit and a Reception threshold unit.

9. Under Coordinate systems, select a Cartographic projection system and the System to be used in the database.

10. Click Next. The Ready to create database page appears. This page provides a summary of the selected parameters.

11. Click Execute. The Atoll Management Console creates the new database with the defined parameters on the selecteddatabase server.

A database created using the Atoll Management Console contains an ATOLL_ADMIN table with the following structure:

If your password must contain special characters, for example, !, ?, etc., type thepassword inside double quotation marks: "mypassword!" instead of mypassword!

Atoll and the Atoll Management Console must have the same version. This means thatthe Atoll Management Console can create databases based on the database templatesinstalled with Atoll of the same version.

Field Type Description

NAME Text (50) The name of the database

DESCRIPTIONText (255)

Description of the database

ATOLL_VERSION Text (10) The current version of Atoll

ATOLL_BUILD Integer Current build of Atoll

ATOLL_DBTYPE Text (10) Type of Atoll database (i.e., Master or Project)

Figure 5.3: New Database Wizard

44


Among other uses, the ATOLL_ADMIN table is used to speed up the database upgrade to the next version. This table storesthe data required by the Atoll Management Console for database upgrade.

Databases created with Atoll, instead of the Atoll Management Console, and databases that have never been upgraded usingthe Atoll Management Console contain a smaller ATOLL_ADMIN table, with just the NAME, ATOLL_VERSION, andATOLL_BUILD fields. Upgrading such databases using the Atoll Management Console can take a long time because the AtollManagement Console must search for the data required for the upgrade in the whole database.

For more information on upgrading databases, see "Upgrading Existing Databases" on page 45.

All the tables in a database created using the Atoll Management Console (except the COORDSYS and UNITS tables) contain anon‐modifiable, integer DB_RECORD_ID field. This field is used to store the ID of every record in the table. It is not added toMicrosoft Access databases.

5.4.2 Creating a New Database Using AtollYou can create new databases in all supported RDBMS using Atoll.

To create a new database:

1. Run Atoll.

2. Create a new Atoll document or open an existing one. The new database will be created from this document.

3. Select Document > Database > Export. The Export to a Database dialogue appears.

4. In the Export to a Database dialogue, select the database type in the Save as type list.

5. Depending on the selected database type, enter the user name and password of the database owner.

6. Click Save. Atoll asks whether you want to connect the document to the new database.

7. Click Yes or No. Atoll creates a new database based on the document.

A database created using Atoll contains an ATOLL_ADMIN table with the following structure:

5.5 Upgrading Existing DatabasesIn each new major release, data structure changes must be made in the database in order to support the new features addedin the version. The data structures of standalone Atoll documents, i.e., documents not connected to any database areupgraded when they are opened in the new Atoll version. You can upgrade databases using the Atoll Management Console.

ATOLL_TEMPLATE Text (50) Atoll database template used to create the database

DBSCHEMA Memo An image of the schema of the original database


By setting an option in the Atoll.ini file, you can instruct Atoll to always use a defineddatabase type (MS Access, SQL Server, or Oracle). In this case, the Export to a Databasedialogue will be skipped and the database‐specific authentication dialogue will appearimmediately. For more information, see "Setting the Type of Database Being Used" onpage 167.


NAME Text (50) The name of the database

ATOLL_VERSION Text (10) The current version of Atoll

ATOLL_BUILD Integer Current build of Atoll

• Before creating the database, make sure that you have defined the coordinatesystems and units in the source document.

• Before creating the database, make sure that you have added any required customfields. Custom fields of the source document are created in the new database.

• If you want to add a custom field to the data structure after you have created thedatabase, you will have to add it directly in the database and not through Atoll.Custom fields added to a database are available to users connected to the databasewhen they create a new Atoll document from the database or refresh an existing one.

45


To upgrade a database using the Atoll Management Console:

1. In the Atoll Management Console window, in the right pane, right‐click the database that you want to upgrade. Thecontext menu appears.

2. Select Upgrade Database. The Database Update Wizard dialogue appears.

The Database Upgrade Wizard displays the current database version and the version to which the database will beupgraded.

3. Click Next. The Name the database page appears.

4. Enter a Name and description for the database.

5. Click Next.

The Database Upgrade Wizard reads the database to determine the Atoll database template using which it wascreated. If there is more than one template corresponding to the network, select the template to be used for theupgrade and click Next.

The Atoll Management Console upgrades the database.

Obsolete fields in the data structure are automatically deleted from the database by the Atoll Management Console duringthe upgrade.

Once the database has been upgraded to the new version,

1. Install the new Atoll versions for the end‐users, and

2. Ask all the end‐users to fully refresh data in their Atoll documents from the database.

• Do not skip a major version of Atoll. For example, if you are currently using Atoll 2.8.x,you should first upgrade the database to Atoll 3.1.x before upgrading to Atoll 3.2.x.Upgrading your database will be simpler if you do not skip a major version. If you skipor have skipped an intermediate major version, you must upgrade your databasetwice in order to make it compatible with the new version.

• If you are upgrading a database which was neither created nor already upgraded (atleast once) using the Atoll Management Console, see "Upgrading Databases for theFirst Time" on page 47 first.

The Microwave Radio Links template now supports Radio Series. Similar microwaveradios belong to the same radio series. In order to organise the microwave radios(microwave equipment) in radio series before the database upgrade:

1. In Atoll 2.8.x, add a custom field named FAMILY of type Text (50) to theMWEquipments table.

2. Enter the radio series names in this field for each radio, i.e., group the radios ofthe same series under the same radio series name in the FAMILY field.

Without this manual organisation of the microwave radios into radio series, the databaseupgrade will create one radio series for each microwave radio.

• If some of the tables in a database have been replaced by views, the DatabaseUpgrade Wizard asks to select the views to upgrade. Select the views that you wantthe Atoll Management Console to upgrade and click Execute.If, for example, the definition of a view is given by the condition:Select Field1, Field2 from Table1 where (Condition1);The wizard first upgrades the schema of Table1 and then upgrades the definition ofthe view. The upgraded definition will take the newly added fields into account.

• When you upgrade a 3GPP Multi‐RAT database, the Atoll Management Console addsany missing tables to the database. For example, a database created by exporting a3GPP Multi‐RAT document containing only GSM contains only GSM tables. Whenupgraded, the Atoll Management Console will add the UMTS and LTE tables to thedatabase as well.

If you use the Atoll Management Console’s history management tool, you must repairthe upgraded database in order to continue using this tool. For more information, see"Managing Data Modifications History" on page 54.

46


When users open their existing documents in the new Atoll version, they are asked whether they want to upgrade thedocuments’ data structures to the new version or to disconnect the documents from the database. On selecting theupgrade option, Atoll upgrades the document data structures to make them compatible with the new version.

It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields asrequired by the new version. For information on manually upgrading a database, see "Upgrading Databases Manually" onpage 48.

Upgrading Databases for the First Time

If you want to upgrade a database which was neither created nor already upgraded (at least once) using the AtollManagement Console, you must first upgrade the database to the same version as the current version of the database. Thisis required so that the Atoll Management console adds the required information to the database to make it upgradable tonewer versions.

To upgrade the database:

1. Before installing the new version of Atoll, install the Atoll Management Console (if not already installed) compatiblewith the existing version of Atoll.

2. Upgrade the database (as described in "Upgrading Existing Databases" on page 45) using the Atoll ManagementConsole to the existing version of Atoll.

The Atoll Management Console adds additional fields to the ATOLL_ADMIN table and DB_RECORD_ID fields in all thetables, as described in "Creating a New Database Using the Atoll Management Console" on page 43. Once the AtollManagement Console has performed the necessary modifications, you can upgrade the database to the new Atollversion.

3. Install the new version of Atoll and the Atoll Management Console.

4. Upgrade the database (as described in "Upgrading Existing Databases" on page 45), using the new version of the AtollManagement Console, to the new version of Atoll.

When a new version of the Atoll Management Console is installed, the setup overwrites the Windows registry key that storesthe information about the Admin.dll file, and the existing version of the Atoll Management Console can no longer be used.

If you have already installed the new version of the Atoll Management Console, you will have to register the old Admin.dllagain, upgrade the database to the existing version, register the new Admin.dll, and upgrade the database to the new versionusing the new Atoll Management Console.

Notes on Document Data Structure Upgrade

• The data structure of an Atoll document not connected to any database isautomatically upgraded to the new Atoll version when the document is opened andsaved in the new version.

• Once saved, it is not possible to open the document in an earlier Atoll version.• The data structure of an Atoll document connected to a database not yet upgraded

to the new version can be upgraded by:• Either opening the document in the new Atoll version, disconnecting it from the

database, and saving it in the new version, or• Upgrading the database to the new version and then opening and saving the

document in the new Atoll version.• Once disconnected from its database, it is not possible to reconnect the document

to any database.• Obsolete fields in the data structure of a document not connected to any database

are automatically deleted by Atoll when the document is saved in the new version.• If the database has been upgraded to the new version but an Atoll document

connected to the database has not yet been upgraded, it is possible to open thedocument in the previous Atoll version as read‐only. It is also not possible tointeract with the upgraded database (archive, refresh, etc., are not allowed). Tomake the document write‐accessible in the previous Atoll version, it must bedisconnected from the upgraded database.

For the Atoll Management Console to be able to recognise obsolete or deleted fieldsfrom database tables, it is imperative that the ATOLL_ADMIN table exist in the database.This means that when upgrading a database for the first time using the AtollManagement Console, the database administrator will have to remove the obsoletefields manually. Once the Atoll Management Console has been used to upgrade adatabase, it will be able to recognise obsolete or deleted fields in the following upgrades.

47


Upgrading Databases Manually

Due to the complex nature of the database upgrade process, it is highly recommended to use the Atoll Management Consolefor upgrading existing databases. You should only proceed with a manual upgrade of your database, as described below, ifand only if an automatic upgrade using the Atoll Management Console is not possible.

The following procedure is not recommended for customised Atoll databases and only suits very simple databases.Parameters and settings (triggers, views, user privileges, custom fields, etc.) defined in advanced database configurations arelost following the manual database upgrade.

1. In the previous version of Atoll, create a new document from the database.

2. In the new version of Atoll, open the document created in step 1. Atoll upgrades the document data structure to makeit compatible with the new version.

3. Using the upgraded document, create a new database as explained in "Creating a New Database Using Atoll" onpage 45.

Adding a Technology in a Multi‐RAT Database

A multi‐RAT Atoll document can be based on one or two radio technologies out of a maximum of three (GSM, UMTS, and LTE).Provided such a document has already been exported to a database, you can add a technology to the corresponding databasethrough the Atoll Management Console.

1. Start the Atoll Management Console.

2. When the Atoll Management Console opens, right‐click on Database in the left pane. The context menu appears.

3. Select Register a New Server. The Data Link Properties dialogue is displayed.

4. On the Provider tab, select an OLE DB provider and click Next.

5. On the Connection tab, specify a database in the Select or enter a database name field.

6. Click the Test Connection button. If the connection is successful, click OK to close the Data Link Properties dialogue.

7. Upgrade the database if necessary, as explained in "Upgrading Existing Databases" on page 45.

8. In the right pane, right‐click the database you want to upgrade with an additional technology and select Multi‐RAT:View/Add Technologies. The Technologies in the Multi‐RAT Database dialogue is displayed.

9. Select the technology you want to add and click OK.

If you are upgrading your database using a script based on the data structuremodifications listed in the Data Structure Reference Guide, you must:

• Add the ATOLL_ADMIN table to the database. For more information on this table,see "Creating a New Database Using the Atoll Management Console" on page 43.

• For LTE databases, rename the smart antenna models and equipment as follows:• Delete existing smart antenna equipment ("Optimum Beamforming Smart

Antenna") from the SmartAntennas table.• Delete existing smart antenna model ("Optimum Beamformer") from the

SmartAntennasModels table.• Create a new smart antenna equipment ("Conventional Beamforming Smart

Antenna") in the SmartAntennas table. Set the smart antenna model for thisequipment to "Conventional Beamformer."

Figure 5.4: Technologies in the Multi‐RAT Database

48


A new record is added to the networks table for each technology added to the database.

5.6 Working With a Multi‐level DatabasesAtoll Management Console allows you to set up and work with multi‐level databases using Oracle. In this optional databasearchitecture, the master database is not directly accessible to end‐users. Groups of end‐users work with their respectiveproject databases which are in turn connected to the master database. The end‐users archive data to and refresh data fromtheir respective project databases, and the database administrator manages the connections and data exchange between theproject databases and the master database.

For example, you can have a country‐wide master database and more than one regional project databases. End‐users can herework with their local region’s project database, and would not have to unnecessarily load country‐wide data.

Project databases are intermediate databases created from a common master database. A project database contains theoriginal master database, that remains hidden from the end‐users, and an copy of the master database accessible to the end‐users. When a user modifies a record, only its accessible copy is modified in the project database. The original value in themaster database remains unchanged until the database administrator archives all the modifications from the projectdatabases to the master database.

Project databases can be used to improve performance and ensure data security and reliability. Instead allowing all the end‐users to work directly with the master database, one or many project databases can be created with copies of the entiremaster database or a part of the master database corresponding to a given physical location or region.

Creating and working with project databases restricts the number of users who have access to the master database. Thisreduces the risk of conflicts in the database as only the database administrator can archive modifications from projectdatabases to the master database.

For example, if a country‐wide network database is accessible to all end‐users:

• You cannot deselect a technology already present in a multi‐RAT database.

Figure 5.5: Working With a Single Level Database

Figure 5.6: Working With Project Databases

49


• The probability of human error increases with the number of users who can modify data.• The probability of conflicts increases with the number of users accessing the database.• The performance is reduced because the entire network is loaded every time a user accesses the database.• For routine city‐wide planning, an end‐user does not require the entire country’s database to be loaded.

Project databases can be created using filters on sites, thus allowing users to work with regional databases. A possible scenariois depicted in the figure below:

Multi‐level databases can be set up using the Atoll Management Console. In this section, the following are explained:

• "Creating Project Databases" on page 50• "Archiving Project Databases to Master Databases" on page 52• "Refreshing Project Databases from Master Databases" on page 53

5.6.1 Creating Project DatabasesYou can create project databases using the Atoll Management Console.

To create a project database from an existing master database:

1. In the Atoll Management Console window, in the right pane, right‐click the master database from which you want tocreate a project database. The context menu appears.

2. Select Create a Project Database. The Project Database Creation Wizard dialogue appears.

3. Click Next. The Specify the server and the owner of the project database page appears.

4. Select the Destination server for the project database.

5. Under Owner, select Current user if you want to create the new project database using the current user, or selectCreate a new user and enter a User name and Password to create a new user that will be owner of the new projectdatabase.

6. Click Next. The Name the database page appears.

Figure 5.7: Multiple Project Databases From a Single Master Database

For creating a project database, you must have enough rights to be able to create newtables in the master database schema.

Some versions of Oracle let you create a new user through this dialogue but the new useris not assigned DBA rights, which makes the new user unable to create the projectdatabase. Therefore, it is recommended to create the new user with DBA rights directlyin the database before create the project database using the Atoll Management Consoleusing the new user account.

50


7. Enter a Name and Description for the new project database.

8. Click Next. The Specify the sites to include in the project database page appears.

9. On this page, choose from one of the following options:

• Include all the sites of the master database

Select this option if you want to create a project database that contains all the data of the master database.

• Include a site list contained in the master database

Select this option if you want to create a project database containing the network data corresponding to the sitesincluded in a site list of the master database, and select a site list. This option is only available when at least onesite list exists in the master database.

• Select the sites to include using an SQL condition

Select this option if you want to create a project database containing the network data corresponding to the sitesthat verify an SQL condition (for example, sites that have a common parameter or flag), and enter the SQLcondition.

• Include the sites contained within a polygon contained in a file

Select this option if you want to create a project database containing the network data corresponding to the sitesthat are located inside a polygon, and select the file containing the polygon to use.

10. Click Next. The Atoll Management Console creates the new project database with the defined parameters on theselected database server.

The project database will have the type PROJECT listed in the Atoll Management Console window.

A project database created using the Atoll Management Console contains an ATOLL_ADMIN_PRJ table, in addition to theATOLL_ADMIN table, with the following structure:

Figure 5.8: New Project Database Wizard


NAME Text (50) The name of the project database

MASTER_CONNECTIONText (255)

Connection parameters to the master database

MASTER_DBSCHEMA Text (50) The name of the original schema of the master database

SEL_METHOD ShortData extraction method used to select the sites to include in the project

database

51


You can view the details stored in the ATOLL_ADMIN_PRJ table in the project database properties. To view the above detailsof a project database:

1. In the right pane, right‐click the project database in the list. The context menu appears.

2. Select Properties. The database Properties dialogue appears.

3. The Properties dialogue contains three tabs:

• General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database.• Project Database tab: Under Source master database, the Project Database tab displays the Connection settings

to and the Owner of the master database. Under Site selection, this tab displays the site filtering Method andSettings used for creating the project database.

• Statistics tab: The Statistics tab displays the number of records in each table of the project database.

The project database contains a copy of all the original tables of the master database. The names of the original tables areprefixed with "O_". For example, the ANTENNAS table of the master database is stored in the project database under thename O_ANTENNAS. The COORDSYS and UNITS are not copied to the project database because their contents cannot bedifferent from those of the master database.

All the tables in a project database contain a non‐modifiable, integer O_RECORD_ID field and a Boolean O_CHANGED field.The O_RECORD_ID field is used to locate records in the master database. Modified records are archived in master databaseusing the O_RECORD_ID of the project database and DB_RECORD_ID of the master database. The O_CHANGED field is set toTRUE for records modified in the project database.

5.6.2 Archiving Project Databases to Master DatabasesChanges made in the project databases can be archived to the master database using the Atoll Management Console. TheArchive dialogue lets you select changes you want to archive.

To archive the changes from a project database to its master database:

1. In the Atoll Management Console window, in the right pane, right‐click the project database from which you want toarchive changes to its master database. The context menu appears.

2. Select Archive. If pending changes exist, the Archive dialogue appears. The Archive dialogue lists the records of theproject database for which the O_CHANGED field is TRUE.

3. In the Archive dialogue, you can do the following:

• Select a site list in Filter by site list to filter the pending changes by a site list.• Click Archive All to archive all the changes to the master database.• Select the check boxes to the left of the changes that you want to archive and click Archive Sel. to archive only the

selected changes.• Click Undo All to overwrite all the changes in the project database with data from the master database.• Select the check boxes to the left of the changes that you want to undo and click Undo Sel. to overwrite only the

selected changes in the project database with data from the master database.• Select the Check conflicts check box to see whether conflicts occurred during the archive.

A conflict occurs when the project database contains a different original value of a field than the current value ofthe field in the master database. This can occur if the master database has been updated with changes fromanother source and the project database has not yet been refreshed with data from the master database.

SEL_PARAMText (255)

Site selection method parameters (the SQL condition, if any)

SEL_PGON Memo Site selection polygon (if used)


52


Under Errors, Atoll Management Console displays errors that occurred during archive.

4. Once archive is complete, click Close.

5.6.3 Refreshing Project Databases from Master DatabasesProject databases can be refreshed with data from the master database using the Atoll Management Console.

To refresh a project database with data from its master database:

1. In the Atoll Management Console window, in the right pane, right‐click the project database that you want to refreshwith data from its master database. The context menu appears.

2. Select Refresh. If pending changes exist, the Refresh a Project Database dialogue appears.

3. In the Refresh a Project Database dialogue, you can:

• Select Refresh unmodified data only to keep any changes in the project database and only update unmodifiedrecords from the master database. During the refresh, the Atoll Management Console will reload records fromthe master database for which the O_CHANGED field is FALSE in the project database.

• Select Cancel your changes and reload all data from the master database to overwrite modified and unmodifiedrecords in the project database with data from the master database.

1. Click OK. The project database is refreshed with data from the master database.

5.7 Setting Database Access PrivilegesYou can assign different levels of privileges to different users for accessing (reading/writing) tables and views of a database.You can grant user privileges for Database, Table, Column, and Row levels keeping the following in mind:

• Database Level:

Users trying to create a new Atoll document from a database are provided a list of available databases to select from.The list can be limited to a few databases based on the user connection properties (log in).

• Table Level:

For consistency reasons, all the tables available in an Atoll database must be readable by all the users who have accessto the database. However, write access (INSERT, DELETE, UPDATE) can be granted on a limited number of tables.

• Column Level:

Similar to table level, all the columns of all the tables in an Atoll database must be readable and selectable by all theusers who have access to the database. Different write permissions can be granted for columns of the tables. Forexample, custom fields can be assigned read and write permissions without restrictions.

• Row Level:

Row level permissions can be set by defining custom views on Atoll tables. Access to these views can be based on userconnection properties (log in), on external table references, or on the geographic locations of sites (e.g., throughpolygons, or when using the spatial features of databases).

Figure 5.9: Archiving Changes in Master Databases

53


All of these permissions can be set as regular SELECT, INSERT, UPDATE, and DELETE privileges on database objects. Triggerscan also be used to prevent users making certain actions on the database.

Different permissions for different users can be granted directly or through database roles. Database roles enable you todefine permission templates, which can then be assigned to existing or new users of the database.

You can use the Atoll Management Console for defining user access rights to database tables and elements in the Atoll GUI.For more information on managing user access rights, see "Managing User Accounts and Access Rights in Oracle" on page 65.

5.8 Managing Data Modifications HistoryThe Atoll Management Console allows you to keep and manage the history of modifications made in the network data bydifferent users. The history management tool keeps track of all the modifications made in the following Atoll tables:

You can, however, enable or disable history management for table as required (see "Enabling/Disabling Data ModificationsHistory Management" on page 55 for more information). If you want, you can also purge old data modifications history (see"Purging Old Data Modification Records" on page 56 for more information).

The history management tool is available for Oracle databases. The following section describes how to set up the historymanagement tool using the Atoll Management Console.

5.8.1 Setting Up Data Modifications History ManagementWhen you set up history management for any database, the Atoll Management Console adds new tables to the databasestructure. For each tracked table, it adds a corresponding history table that has the same name as the tracked table with thesuffix "_H". Each history table has the same structure as the corresponding tracked table, but with the following fouradditional fields. These fields enable the Atoll Management Console to store the modifications made by users to each trackedtable:

The above fields are also added to all the tracked tables in order to store information about the latest modification. Therefore,opening any tracked table, you can see when a record was last modified, by whom, and the type of modification.

To set up data modifications history management for a database:

1. In the Atoll Management Console window, in the right pane, right‐click the database for which you want to set updata modifications history management. The context menu appears.

2. Select Manage Data Modifications History. The Data Modifications History Management dialogue appears.

3. Click Yes when asked whether you want to make your database compatible with the data modifications history tool.

Technology Tracked Tables

GSM GPRS EDGESites, Transmitters, TRGs, TRXs, Repeaters, SecondaryAntennas, Neighbours,

NeighboursExt

UMTS HSPASites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours,

NeighboursExt

LTESites, Transmitters, T4GCells, Repeaters, SecondaryAntennas, Neighbours,

NeighboursExt

3GPP Multi‐RAT

sites, ltransmitters, utransmitters, gtransmitters, lcells, ucells, gtrgs, gtrxs, lrepeaters, urepeaters, grepeaters, lsecondaryantennas, usecondaryantennas,

gsecondaryantennas, lneighbours, uneighbours, gneighbours, lneighext, uneighext, gneighext, guneighbours, ugneighbours, glneighbours, lgneighbours, ulneighbours,

luneighbours

CDMA2000 1xRTT 1xEV‐DOSites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours,

NeighboursExt

WiMAXSites, Transmitters, WCells, Repeaters, SecondaryAntennas, Neighbours,

NeighboursExt

Microwave Radio LinksSites, MWLinks, MWHubs, MWPMP, MWMultiHops, MWMultiHopsLinks,

MWRepeaters


HISTORY_ID Integer A unique ID of the modification history record

MODIFIED_BY Text (50) The user who made the modification

MODIFIED_DATE Date The date when the modification was made

HISTORY_STATUS Text (10) Status of the modification history record

54


The Atoll Management Console updates the database structure to make it compatible with the data modificationshistory tool. Data modifications history is enabled for the database.

Once finished, it opens the Data Modifications History Management dialogue (see Figure 5.10 on page 56). Thisdialogue lists all the tables for which the data modifications history management has been enabled, the total numbersof records in these tables, and the status of the history management.

All the modifications made in the tables listed in "Managing Data Modifications History" on page 54 are stored in the historytables added to the database.

If you want, you can disable the data modifications history management for any table. For more information, see "Enabling/Disabling Data Modifications History Management" on page 55.

5.8.2 Enabling/Disabling Data Modifications History ManagementYou can enable or disable data modifications history management for any table. You can enable or disable historymanagement for each individual table. When history management is enabled for a table, the MODIFIED_BY, MODIFIED_DATE,and HISTORY_STATUS fields are updated with each modification, and a copy of each modification is stored in the history tablecorresponding to the table. When history management is disabled for a table, the MODIFIED_BY, MODIFIED_DATE, andHISTORY_STATUS fields are still updated with each modification, but the history of modifications is not stored in thecorresponding history table.

To enable data modifications history management for a table:

1. In the Atoll Management Console window, in the right pane, right‐click the database for which you want to enabledata modifications history management. The context menu appears.


3. In the Data Modifications History Management dialogue, right‐click the table for which you want to enable datamodifications history management. The context menu appears.

4. Select Enable in the context menu.

Data modifications history management is now enabled for this table. The Status in the Data Modifications HistoryManagement dialogue is set to OK for this table.

To disable data modifications history management for a table:

1. In the Atoll Management Console window, in the right pane, right‐click the database for which you want to disabledata modifications history management. The context menu appears.


3. In the Data Modifications History Management dialogue, right‐click the table for which you want to enable datamodifications history management. The context menu appears.

4. Select Disable in the context menu.

History management is now disabled for this table. The Status in the Data Modifications History Managementdialogue is set to Deactivated for this table.

5.8.3 Updating After Data Structure UpgradeWhen you modify the structure of a tracked database table (for which data modifications history management is enabled),either automatically upgrading your database using the Atoll Management Console, or manually by adding or removing fields,or by modifying a field type, the corresponding data modifications history management table becomes invalid and has to beupdated to match the new structure of the tracked table.

The Status column of the Data Modifications History Management dialogue shows an error for the tracked table whosehistory management table does not match its structure.

To update the data modifications history management tables:

1. In the Atoll Management Console window, in the right pane, right‐click the database whose tables you want toupdate. The context menu appears.


3. In the Data Modifications History Management dialogue, right‐click the table that you want to update. The contextmenu appears.

4. Select Install/Repair in the context menu.

The Atoll Management Console repairs the data structure of the history management table to match the structure ofthe corresponding tracked table.

55


5.8.4 Purging Old Data Modification RecordsHistory management tables store the lists of all the modifications made by all the users. These tables can therefore quicklybecome very large and require a lot of disk space. You can purge old data modifications history (records) from these tables inorder to gain disk space.

In this section, the following is explained:

• "Purging Old Data Modification Records of a Table" on page 56• "Purging Old Data Modification Records of a Database" on page 57.

5.8.4.1 Purging Old Data Modification Records of a Table

To purge old data modification records from a history management table:

1. In the Atoll Management Console window, in the right pane, right‐click the database in which you want to purge olddata modifications history. The context menu appears.

2. In the context menu, select Manage Data Modifications History. The Data Modifications History Managementdialogue appears (see Figure 5.10 on page 56).

3. In the Data Modifications History Management dialogue, right‐click the table for which you want to purge old datamodifications history. The context menu appears.

4. In the context menu, select Purge. The table record purge dialogue appears (see Figure 5.11 on page 56).

5. Under Purge data modifications recorded before, move the slider to select from which date onwards you want tokeep the data modification history records.

All the data modification history records before this date will be deleted. Number of records shows the number ofrecords that will be left after the purge. Data size shows the size of the records that will be left after the purge.

6. Under Options, select the Keep creation and deletion records check box if you want to keep the records related tocreation and deletion.

7. Click Purge. All the history records before the selected date are deleted from the history management table.

If you selected the Keep creation and deletion records check box, creation and deletion records before the selecteddate are not deleted.

Figure 5.10: Data Modifications History Management Dialogue

Figure 5.11: Table Record Purge Dialogue

56


5.8.4.2 Purging Old Data Modification Records of a Database

To purge old data modification records from all the history management tables of a database:

1. In the Atoll Management Console window, in the right pane, right‐click the database in which you want to purge olddata modifications history. The context menu appears.

2. In the context menu, select Manage Data Modifications History. The Data Modifications History Managementdialogue appears (see Figure 5.10 on page 56).

3. In the Data Modifications History Management dialogue, click the Scheduler button. The database record purgedialogue appears (see Figure 5.12 on page 57).

4. Under Conditions, select the records to purge:

• None: Select None if you do not want to purge any record.• Keep only records of N last months: Select Keep only records of N last months and enter the number of months

prior to which records of data modifications will be purged.• Keep creation and deletion records: Select the Keep creation and deletion records check box if you want to keep

all the creation and deletion records, independent of the above options.

5. If you wish to purge records now, click the Run now button.

6. If you wish to schedule regular purges, under Scheduling, define the purge frequency:

a. Period: Select the frequency of the scheduled regular purges.

b. Day: Select the day of the week (Monday to Sunday), month (1 to 28), or year (1 to 365), depending on the purgeperiodicity defined in Period, on which the scheduled purges will run.

c. Time: Enter the time, i.e., the hour (0 to 23) and minutes (0 to 59) at which scheduled purges will run.

Scheduled regular purges will delete all the data modification records according to the criteria defined underConditions.

7. Set the Off/On slider to On to turn on the scheduled purges.

Setting the Off/On slider to Off lets you suspend the scheduled purges and keep the schedule settings.

8. Click the Update button to store the schedule parameters.

The current purge status is shown under Status. Status information includes:

• Last execution: Time of execution of the last purge.• Result: Whether the last purge was successful or not.• Next execution: Time of execution of the next scheduled purge.

You can click the View logs under Status to view the history of past purges (see Figure 5.12 on page 57).

9. Click the Close button.

Figure 5.12: Database Record Purge Dialogue

57


Scheduled regular purges are programmed as a scheduled job in Oracle using the DBMS_SCHEDULER.create_job function. Thefollowing SQL string generates scheduled job:

Here:

5.9 AppendicesThe first appendix shows how to use SQL for Oracle database customisation and the second appendix shows how to set updatabases for co‐planning taking the example of GSM and UMTS MS Access databases.

5.9.1 Appendix 1: Advanced CustomisationYou can use SQL in order to manage access to and share the Sites table (example 1), or to restrict the connection to a set oftransmitters for some users (example 2). To implement the following two examples, you must log on as the owner of thetables through SQL Plus 8.

Example 1: Managing Site Sharing

Assumptions:

• Connection string = AtollDB• GSM Project account = AtollADMINGSM, password = ADMINGSM• UMTS Project account = AtollADMINUMTS, password = ADMINUMTS• Common Project account = AtollADMIN, password = ADMIN

To share the Sites table:

1. Create the AtollADMIN.SITES table and copy all sites from AtollADMINGSM.SITES to AtollADMIN.SITES.

2. Replace the AtollADMINGSM.SITES table by an AtollADMINGSM.SITES view.

"BEGIN DBMS_SCHEDULER.create_job ("

"job_name => 'AHMS_%s',"

"job_type => '%s',"

"job_action => '%s',"

"start_date => SYSTIMESTAMP,"

"repeat_interval => '%s',"

"end_date => NULL,"

"enabled => %s,"

"comments => '%s'); END;"

Parameter Description

job_name AHMS_<schema_name>

job_type PLSQL_BLOCK

job_action Actual PL‐SQL code for the purge

start_date SYSTIMESTAMP

repeat_intervalFrequency of the scheduled purge

For example, once a month, on the 15th, at 1:30am: "freq=month;monthday=15;byhour=1;byminute=30"

end_date NULL

enabled TRUE or FALSE, based on the user input

comments Custom character string with codes for easy identification of the scheduler type

SQL > connect AtollADMIN/ADMIN@AtollDB;

SQL > create table AtollADMIN.SITES as select * from AtollADMINGSM.SITES;

SQL > create unique index AtollADMIN_SITES on AtollADMIN.SITES(NAME);

SQL > connect AtollADMINGSM/ADMINGSM@AtollDB;

SQL > drop table AtollADMINGSM.SITES;


SQL > grant delete on AtollADMIN.SITES to AtollADMINGSM with grant option;

58


3. Follow the same procedure for UMTS (AtollADMIN.SITES already created).

4. Commit.

Example 2: Managing Users by Postal Code

To restrict access to transmitters for some users by postal code:

1. Add a ‘POSTCODE’ field to the SITES table.

2. Rename the SITES table to be able to hide it by a view.

3. Create a POSTCODETABLE table to link users and postcodes (one user can be linked to several postcodes).

You can fill this table using this instruction.

4. Create a view owned by this user hiding the actual SITES table through these commands.

"with check option" is very important as it specifies that insert and update operations performed through the viewmust result in rows that the view query can select.

5. Hide the TRANSMITTERS table, so that Atoll can only select transmitters whose associated sites are present in theSITES view.

6. Commit.

SQL > grant insert on AtollADMIN.SITES to AtollADMINGSM with grant option;

SQL > grant select on AtollADMIN.SITES to AtollADMINGSM with grant option;

SQL > grant update on AtollADMIN.SITES to AtollADMINGSM with grant option;

SQL > create view AtollADMINGSM.SITES as select * from AtollADMIN.SITES;

SQL > connect AtollADMINUMTS/ADMINUMTS@AtollDB;

SQL > drop table AtollADMINUMTS.SITES;


SQL > grant delete on AtollADMIN.SITES to AtollADMINUMTS with grant option;

SQL > grant insert on AtollADMIN.SITES to AtollADMINUMTS with grant option;

SQL > grant select on AtollADMIN.SITES to AtollADMINUMTS with grant option;

SQL > grant update on AtollADMIN.SITES to AtollADMINUMTS with grant option;

SQL > create view AtollADMINUMTS.SITES as select * from AtollADMIN.SITES;

SQL > commit;

SQL > alter table SITES add (POSTCODE number);

SQL > rename SITES to PRIVATE_SITES;

SQL > create table POSTCODETABLE (USERNAME varchar2(30), POSTCODE number);

SQL > insert into POSTCODETABLE values (‘USER1’, 75);

SQL > create view SITES as

select * from PRIVATE_SITES

where POSTCODE in

(select POSTCODE from POSTCODETABLE where USERNAME =USER)

with check option;

SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS;

SQL > create view TRANSMITTERS as

select * from PRIVATE_TRANSMITTERS

where SITE_NAME in (select NAME from SITES);

SQL > commit;

59


5.9.2 Appendix 2: Setting Up Databases for Co‐planningTwo co‐planning approaches are possible in Atoll:

• Co‐planning GSM, UMTS, and LTE using a unified multi‐technology data structure, i.e., working with a 3GPP Multi‐RATdocument.

• Co‐planning any two radio technologies (GSM, UMTS, LTE, CDMA2000, TD‐SCDMA, and WiMAX), with two separatedata structures, by linking Atoll documents.

In terms of database, while the first approach provides an integrated multi‐technology co‐planning environment, the secondrequires setting up sharing of the Sites table between the databases of the two technologies being co‐planned. The Sites tablemust be shared between the databases of the two technologies being co‐planned so that the sites where sectors of bothtechnologies are installed are listed only once in a common Sites table. In other words, the Sites tables in the databases of thetwo technologies must be views of a common Sites table.

This section describes table sharing between GSM and UMTS, although the same description can be applied to any two radiotechnology modules of Atoll

You can create views to share tables that have the same structure in the databases of the two technologies being co‐planned,i.e., the Sites and Antennas tables. In the following, we assume that the Sites tables of the GSM and UMTS documents containthe same data and that two users, named GSMUser and UMTSUser in this example, exist in the databases.

To set up a shared Sites table for a GSM‐UMTS co‐planning project in Oracle or SQL Server:

1. Make backups of the GSM and UMTS documents.

2. Open the GSM document in Atoll.

3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.

4. Export the GSM document to the database by entering the user name and password for GSMUser.

5. Log in as GSMUser to the database.

6. Delete the Sites table.

7. Open the UMTS document in Atoll.

8. Export the UMTS document to the database by entering the user name and password for UMTSUser.

9. Log in as UMTSUser to the database.

10. Right‐click the Sites table and select Create a View from the context menu. The Create View dialogue appears.

a. Enter Sites as the view name.

b. Enter GSMUser as the name of the schema which will contain the view.

c. Select Table as object type.

d. Enter UMTSUser as the name of the schema you want to use.

e. Select Sites as the object used to model the view.

11. Click Create. The view of the Sites table from UMTSUser is created in GSMUser. The GSMUser Sites table is now thesame as UMTSUser Sites table.

12. Set up user privileges for the Sites view in GSMUser to allow each user to Import, Update, Delete, and Select.

To set up a shared Sites table for a GSM‐UMTS co‐planning project in Microsoft Access:

1. Make backups of the GSM and UMTS documents.

2. Open the GSM document in Atoll.

3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.

4. Export the GSM document to a Microsoft Access database (GSM.mdb).

5. Open GSM.mdb in Microsoft Access.

6. Delete the Sites table.

7. Open the UMTS document in Atoll

8. Export the UMTS document to a Microsoft Access database (UMTS.mdb).

9. Open GSM.mdb in Microsoft Access.

The error message "ORA‐01402: view WITH CHECK OPTION ‐ clause violation" appears ifyou try to archive a record that does not match the project.

60


10. In Microsoft Access 2003 and earlier, select File > Get External Data > Link Tables. In Microsoft Access 2007 and later,select External Data > Access Database.

11. In Microsoft Access 2003 and earlier, the Link dialogue appears. Select UMTS.mdb. In Microsoft Access 2007 and later,the Get External Data ‐ Access Database dialogue appears, specify UMTS.mdb as data source and select Link to datasource by creating a linked table.

12. Click OK. The Link Tables dialogue appears.

13. Select the Sites table.

14. Click OK. Microsoft Access creates a Sites table in GSM.mdb which is linked to the Sites table in UMTS.mdb. The tablescontain the same data.

Once the linked Sites table has been created in the GSM database, you have to define the relations of this table with the othertables in the database. See the Data Structure Reference Guide for detailed information on database tables.

Ensuring Database Consistency Between Linked Documents

When users work with two Atoll documents and databases at the same time, it is important to have a protection mechanismagainst database inconsistencies. If a user archives the changes made in one document but forgets to archive the changesmade in the other, this can create inconsistencies between the two networks.

To ensure database consistency, you can save or archive the linked documents at the same time, i.e., when a user saves orarchives one document, Atoll automatically saves or archives the other. This can be done using a macro triggered by the saveor archive operation.

• The UMTS Sites table has more fields than the GSM Sites table. Therefore, you shouldreplace the GSM Sites table with the UMTS one.

• When you upgrade one by one the databases that share the Sites table, any triggersthat you might have set on the Sites table of the database that is upgraded first mightbe overwritten by the triggers set on the Sites table of the database upgraded last. Inorder to avoid the triggers being overwritten, you can rename the triggers on theSites table of the database upgraded first (by adding, for example, the databasetechnology as prefix to the trigger names) before upgrading the other database(s).

61


62

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 6: Multi‐user Environments

6 Multi‐user EnvironmentsA multi‐user environment is where more than one user work simultaneously on an Atoll project, sharing data over a network.In large, structured multi‐user environments, groups of users can work on specific parts of a common, large‐scale project. Forexample, different user groups can work on different regions of a country‐wide network. In this chapter, the following areexplained:

• "Setting Up Multi‐user Environments" on page 63• "Components of Multi‐user Environments" on page 63• "Managing User Accounts and Access Rights in Oracle" on page 65

6.1 Setting Up Multi‐user EnvironmentsThe general process of setting up a multi‐user environment is described below. Each component is described in detail in"Components of Multi‐user Environments" on page 63.

1. Create the master Atoll document with the required network data and geographic data. For more information, see"Master Atoll Document" on page 64 and "Shared Geographic Data" on page 64.

2. Export the master Atoll document to a new database and keep the document connected to the new database. Formore information, see "Master Database" on page 64.

3. Create the private path loss matrices folder for the master Atoll document and calculate the private path lossmatrices. For more information, see "Shared Path Loss Matrices" on page 65.

4. Create user Atoll documents from the master database. For more information, see "User Atoll Documents" onpage 65.

5. In the user Atoll documents, add the required geographic data and set the master Atoll document’s private path lossmatrices folder as the shared path loss matrices folder of the user documents.

6.2 Components of Multi‐user EnvironmentsFigure 6.1 on page 63 shows the components of a multi‐user environment.

• The Atoll administrator should regularly update the shared path loss matrices.• As the users work on the network and archive changes in the database, the Atoll

administrator should regularly run data integrity checks on the master Atolldocument after loading modified data from the master database. For moreinformation, see "Appendix 1: Checking Data Integrity" on page 69.

Figure 6.1: Components of Multi‐user Environments

63

Atoll 3.2.1 Administrator ManualChapter 6: Multi‐user Environments © Forsk 2014

In this section, the following are explained:

• "Master Atoll Document" on page 64• "Master Database" on page 64• "Shared Geographic Data" on page 64• "Shared Path Loss Matrices" on page 65• "User Atoll Documents" on page 65

6.2.1 Master Atoll DocumentIt is the source Atoll document that contains the entire project’s network data. It is created and maintained by the Atolladministrator. This document is initially used to create the radio network database with which all the end‐users work. Themaster Atoll document allows the administrator to globally manage all the data shared by the end‐users.

The master Atoll document is also used for calculating path loss matrices for the transmitters of the entire network andkeeping the path loss matrices up to date with the user modifications to the radio network data. The document also containsthe required geographic data for path loss calculations. Geographic data are usually located on file servers and linked to thedocument, not embedded in the ATL file. The private path loss matrices of this document are used as shared path loss matricesby the end‐users. The shared path loss matrices folder is usually located on a file server accessible to all the users on thenetwork.

For exceptionally large networks, you can also work with more than one master Atoll document (for example, one masterdocument per region). However, the multi‐user environment set up remains the same. Master Atoll documents should nothave redundant radio network data (same sites, for example), and should ideally cover different geographical regions. Formore information on regionalisation, see "Appendix 2: Database Regionalisation" on page 70.

6.2.2 Master DatabaseThe master database stores the radio network data shared by all the end‐users. It can be created by exporting the radionetwork data in the master Atoll document to a database from Atoll (for more information, see "Creating a New DatabaseUsing Atoll" on page 45). An empty database can also be created using the Atoll Management Console, and populated withdata later on (for more information, see "Creating a New Database Using the Atoll Management Console" on page 43).

Only radio network data are stored in the database, i.e., sites, transmitters, antennas, etc. Parameters related to geographicdata files, their paths, folder configurations, prediction definitions, zones, traffic maps, measurements can be stored in userconfiguration files (see "Configuration Files" on page 117 for details).

For large networks, you can subdivide the network’s master database into regions. For more information on regionalisation,see "Appendix 2: Database Regionalisation" on page 70. For more information on database management, see "ManagingDatabases" on page 39. The recommended database server configuration is provided in "Recommended Hardware andSoftware" on page 14.

6.2.3 Shared Geographic DataGeographic data files are usually stored on a file server accessible to and shared by all the users working on the same network.User configuration files (CFG or GEO) are used to store the parameters related to geographic data. For more information, see"Configuration Files" on page 117.

The administrator can set up different user configuration files (CFG) for separate user groups. User configuration files can becreated so that only the geographic data required by a user are loaded. It is possible to load a user configuration fileautomatically when running Atoll. User configuration files can be shared and exchanged between users working on the sameproject. For more information, see "Atoll Command Line Parameters" on page 24.

Geographic data files are usually large files, and it is recommended that these be stored externally and not embedded in Atolldocuments. The recommended file server configuration is provided in "Recommended Hardware and Software" on page 14.

If you wish to add custom fields in the Atoll document, you should first add the field inthe database, and then update your Atoll document from the database. Custom fieldsadded in an Atoll document connected to a Microsoft Access database are automaticallyadded to the database. However, this is not the case with other RDBMS, such as Oracle.

The same database server can be used to store one or more master databasescorresponding to different technologies. For example, a GSM database and a UMTSdatabase can be stored on the same database server using the same RDBMS (Oracle, forexample).

64


6.2.4 Shared Path Loss MatricesShared path loss matrices are usually stored on a file server accessible to and shared by all the users working on the sameproject. These path losses are calculated using the master Atoll document by the Atoll administrator. The private path lossmatrices of the master Atoll document are used as shared path loss matrices by the end‐users.

The Atoll administrator is the owner of the shared path loss matrices, and must have read/write access to the shared pathloss matrices folder. End‐users should have read‐only access to this folder.

It is the administrator’s duty to regularly update the master Atoll document with the modifications made to the masterdatabase by the end‐users, and to calculate the shared path loss matrices using the master Atoll document on a routine basis.This task can be carried out using a macro. For more information, see "Appendix 3: Calculating Path Loss Matrices" on page 70.

Shared path loss matrices are available for use in calculations to all the end‐users. However, end‐users are not allowed tomodify the shared path loss matrices.

6.2.5 User Atoll DocumentsUser Atoll documents are created from the master database. These can contain the entire project network data or only a partof it. User documents are the working documents of the Atoll end‐users connected to the master database, the geographicdata, and the shared path loss matrices folder.

You should load data from the master database in each user Atoll document and save it before setting the shared path lossmatrices folder for the document. For any modifications made by end‐users in their Atoll documents that render some sharedpath losses invalid, Atoll calculates the invalid path loss matrices locally for the end‐users and stores them in their private pathloss matrices location. Shared path loss matrices are only used in calculations if valid private path loss matrices are notavailable. Therefore, in order to use shared path loss matrices, you must delete the corresponding private path loss matrices.

If users are going to work on regions of a network, the regionalisation should be set up before creating the user documents.For more information on regionalisation, see "Appendix 2: Database Regionalisation" on page 70.

6.3 Managing User Accounts and Access Rights in OracleThe Atoll Management Console enables you to create and delete database user accounts, edit user account information, anddefine user access rights to different components of a project such as database tables, and radio data and parameters in Atoll.

In order to be able to manage user accounts and access rights using the Atoll Management Console, you first have to makethe database compatible with the user management tool. This is done automatically when the user management tool is runon a database for the first time. The database has to be of the same version as the Atoll Management Console being used tomanage user accounts and access rights.

To make your database compatible with the user management tool:

1. In the Atoll Management Console window, right‐click the database whose user accounts you wish to manage.

2. Select Manage Users. The User Management dialogue appears (see Figure 6.2 on page 66).

3. Click Yes when asked whether you want to make your database compatible with the user management tool.

The Atoll Management Console adds a GUIUserRights table in the database with the following structure:

If users modify geographic data locally, for example edit clutter or traffic in theirrespective projects, they should store these modified geographic data locally so that themodifications do not impact other users.

The shared path loss matrices must be unlocked in order for users to be able to work withthem. You can check whether path loss matrices are unlocked in the Propagation tab ofthe Transmitters folder’s properties dialogue.

If you wish to add custom fields in the Atoll document, you should first add the field inthe database, and then update your Atoll document from the database. Custom fieldsadded in an Atoll document connected to a Microsoft Access database are automaticallyadded to the database. However, this is not the case with other RDBMS, such as Oracle.


ATOLL_USER Text (50) Name of the user account

65


Each user’s interface access rights are stored in a unique record in the GUIUserRights table. The contents of the RIGHTS fieldhave the following syntax:

RADIOPARAMS;CALCPARAMS;PROPAGMODELS;PASSWORD

The syntax is explained in detail in "Defining Database and Interface Access Rights" on page 66.

If interface access rights are not defined for a database, i.e., the GUIUserRights table does not exist, all the users haveunrestricted access to the Atoll interface.

If interface access rights are defined for a database, and a user creates a document from the database or opens a documentconnected to the database, Atoll retrieves the interface access rights for the user when he enters his user name and passwordto access the database.

If the database is not reachable, the user is not listed in the GUIUserRights table, or if the password is not correct, the user’sinterface access rights are set to read‐only by default (for more information, see "Defining Database and Interface AccessRights" on page 66). If the user is listed in the GUIUserRights table, his interface access rights are read and applied to the Atollinterface (table grids and properties dialogues). A message is displayed in the Event Viewer window to inform the user of hisinterface access rights. It is possible to remove interface access restrictions by disconnecting the document from the database.However, a disconnected document cannot be reconnected to the database.

The GUIUserRights table is also stored in the Atoll document, and is updated when the document is saved. Hence, users canwork on their documents without actually being connected to the database, and still have their usual interface access rightsapplied in the document.

When database connection properties are modified for a document, for example, when a different user enters his user nameand password in the connection properties, Atoll reads and applies the interface access rights defined for the new user.

6.3.1 Defining Database and Interface Access RightsFor any existing user account, you can set the database and Atoll interface access rights using the Atoll Management Console.

To manage database and Atoll interface access rights for an existing user account:

1. In the Atoll Management Console window, right‐click the database whose user accounts you wish to manage.


3. Under Atoll projects, select the project for which you want to manage user accounts.

RIGHTS Memo Semi‐colon separated set of interface access rights

Atoll does not ask for the user name and password when a document is opened using theAPI. The interface access rights stored in the document are used.


Figure 6.2: User Account and Access Rights Management Dialogue

66


4. Under List of users, select the user account whose database and interface access rights you want to set.

Users who have database access rights in the selected database are marked with the green icon ( ). Users who do

not have any database access rights in the selected database (Category = No Access) are marked with the red icon

( ). Locked (deactivated) user accounts are marked with a yellow lock icon ( ). For more information on locked

user accounts, see "Creating and Editing User Accounts" on page 68.

You can use the Filter list to display:

• All users: Users with access ( ), without access ( ), or locked ( )

• Users with access ( )

• Administrators: Users with administrator rights among the users with access• Standard users: Users with standard rights among the user with access• Read‐only users: Users with read‐only access rights among the users with access

5. Under Database rights, you can select a database access Rights category:

• No access: User without read and write access to the database. The database is not visible to these users and theyare not allowed to create Atoll documents based on this database.

• Read‐only: Users allowed to create Atoll documents from the database but without write permissions to any tableof the database, i.e., users cannot archive changes made in the Atoll document to the database.

• Standard: Users with read and write access to some tables of the database. These tables include radio networkdata tables including sites, transmitters, cells, subcells, repeaters, remote antennas, secondary antennas, intra‐and inter‐technology neighbours and exceptional pairs, site and transmitter lists, microwave point‐to‐point, point‐to‐multipoint, and multi‐hop links, microwave repeaters, microwave hubs.

• Administrator: Users with read and write access to all the tables of the database.

Database access rights are stored in the user account properties in Oracle. If you are working with an RDBMS otherthan Oracle, you will not be able to set database access rights. You can, however, still set interface access rights asexplained below.

6. Under Interface rights, you can select interface access rights for:

• Access to radio data: • Full: (RADIOPARAMS = ALL) Users with read and write access to all the tables and properties dialogues.• Standard: (RADIOPARAMS = STD) Users with read and write access to radio network data tables and

properties dialogues including sites, transmitters, cells, subcells, repeaters, remote antennas, secondaryantennas, intra‐ and inter‐technology neighbours and exceptional pairs, site and transmitter lists, microwavepoint‐to‐point, point‐to‐multipoint, and multi‐hop links, microwave repeaters, microwave hubs.

• Read‐only: (RADIOPARAMS = NONE) Users with read‐only access to tables and properties dialogues, i.e., usersare not allowed to modify radio network data and parameters.

• Access to calculation settings: • All: (CALCPARAMS = ALL) Users with read and write access to all coverage predictions, their calculation

settings, and to microwave calculation settings (Models, Objectives, and Clutter Categories tabs of theProperties dialogue of the Microwave Radio Links folder).

• Standard: (CALCPARAMS = STD) Users with access to customised coverage predictions only, and allowed tomodify coverage conditions and display settings. These users do not have access to the microwave calculationsettings mentioned above.

• Customised only: (CALCPARAMS = NONE) Users with access to customised coverage predictions only, but notallowed to modify coverage conditions and display settings. These users do not have access to the microwavecalculation settings mentioned above.

• Access to propagation models: • Full: (PROPAGMODELS = ALL) Users with read and write access to all propagation models and their properties.• Read only: (PROPAGMODELS = NONE) Users with read‐only access to the properties of all the propagation

models. Adding and deleting propagation models is also not allowed.

• Password confirmation: • Yes: (PASSWORD = STD) Atoll will ask users for password when opening a document connected to this

database or creating a new document from this database.• No: (PASSWORD = NONE) Atoll will not ask users for password when opening a document connected to this

database or creating a new document from this database.

• Database access rights and access rights to radio data in Atoll can be setindependently. For example, a user can have full access rights in the interface but notbe allowed to archive changes to the database.

• However, access rights in the interface should only be granted if the user has at leastread‐only access to the database.

67


7. Click OK. The database and interface access rights of the selected user are saved in the database.

6.3.2 Creating and Editing User AccountsYou can create and edit user accounts using the Atoll Management Console.

To manage user accounts:

1. In the Atoll Management Console window, right‐click the database whose user accounts you want to manage.


3. To create a new user account:

a. Under Users, click Create. The Create/Edit User dialogue appears (Figure 6.3 on page 68).

b. Under Identification, enter a User name (in block letters) and Password, and select a Tablespace for the new useraccount.

c. Under Advanced, select Use operating system authentication if you want to use OS authentication prefix with theuser name, and Unlimited tablespace privilege if you want to assign this system privilege to the user.

d. Click OK. The new user account is created.

4. To edit a user account:

a. Under List of users, select the user account whose information you want to edit.

b. Under Users, click Edit. The Create/Edit User dialogue appears (Figure 6.3 on page 68).

c. Under Identification, modify the user’s Password or assigned Tablespace.

d. Under Advanced, select Use operating system authentication if you want to use OS authentication prefix with theuser name, and Unlimited tablespace privilege if you want to assign this system privilege to the user.

e. Click OK. The modified user account information is saved.

5. To deactivate (lock) a user account:

a. Under List of users, select the user account you want to deactivate.

b. Under Users, click Edit. The Create/Edit User dialogue appears (Figure 6.3 on page 68).

c. Under Advanced, select Account locked check box.

d. Click OK. The user account is deactivated and can no longer be used.

6. To delete a user account:

a. Under List of users, select the user account you want to delete.

b. Under Users, click Delete. The user account is deleted.

6.3.3 Resetting User Database PermissionsThe permissions reset feature enables you to rebuild user database permissions while keeping existing role assignments.

You can reset user permissions from the Atoll Management Console.

Figure 6.3: Creating or Editing a User Account

68


This feature is particularly useful after a major Atoll upgrade or after tables were added as a result of a project customization,and for all unforeseen reasons which can require fixing user database permissions.

The permissions reset process does not remove any object privileges which assigned prior to rebuilding the database. It justlooks for new objects and assigns permissions based on existing user profiles ("Administrator", "Standard" or "Read‐only").

To reset user permissions:

1. Open the database for which you want to reset user permissions in the Atoll Management Console window.

2. Under Database rights, click on the Reset button.

3. Acknowledge the message informing you about the rebuilding process duration.

6.4 AppendicesThe following appendices provide additional information on:

• "Appendix 1: Checking Data Integrity" on page 69• "Appendix 2: Database Regionalisation" on page 70• "Appendix 3: Calculating Path Loss Matrices" on page 70• "Appendix 4: Path Loss Matrices From Different Sources" on page 71

6.4.1 Appendix 1: Checking Data IntegrityAtoll includes data consistency and integrity checking tools that allow you to check data consistency between the differentAtoll tables (Sites, Transmitters, etc.). It is recommended that the Atoll administrator runs data integrity checks regularly onthe master Atoll document after it is updated with data modifications in the master database.

To perform data integrity check:

• In Atoll, select Document > Data Audit > Integrity Check.

Atoll searches for records with integrity problems which can occur with objects that have foreign keys. Integrityproblems occur when records refer records that do not exist. For example, transmitters located on sites that do notexist in the Sites table, transmitters referring to an antenna that does not exist in the Antennas table, etc.). Recordswith integrity problems can be deleted when found.

To perform undefined record check:

• In Atoll, select Document > Data Audit > Undefined Record Check.

Atoll searches for undefined records such as sites without transmitters, transmitters without subcells, TRXs, andneighbours in GSM, transmitters without cells, and cells without neighbours in UMTS, CDMA2000, TD‐SCDMA, LTE,WiMAX, and Wi‐Fi. Atoll lists all the undefined records found in the Event Viewer.

To perform duplicate record check:

• In Atoll, select Document > Data Audit > Duplicate Record Check.

Atoll searches for records that have the same identifier. For example, sites with the same name, transmitters with thesame name, etc. Atoll lists all the duplicate records in the Event Viewer.

To perform microwave data check:

1. In Atoll, select Document > Data Audit > Microwave Link Data Check. The Microwave Data Check dialogue appears.

2. In the Microwave Data Check dialogue, select the data to check.

3. Select List all the checks to list all the checks in the Event Viewer.

4. Click OK.

Atoll searches the microwave links tables for problems related to the selected checks. Atoll lists the problems foundin the Event Viewer.

The duration of the database rebuilding process depends on the number of users and onthe database processing speed.

If you fix any problems in the Atoll document, you must archive the changes in thedatabase in order to fix the problems for all the users working with that database.

69


6.4.2 Appendix 2: Database RegionalisationYou can subdivide the network into regions in the following ways:

• Static regionalisation using multi‐level databases

Static regionalisation can be based on site lists, SQL filters, or geographic zones in the form of filtering polygons. Staticregionalisation is carried out by creating project databases from the master database, i.e., multi‐level databases asexplained in "Working With a Multi‐level Databases" on page 49.

Static regionalisation requires manual synchronisation between the master database and the regional projectdatabases using the Atoll Management Console. In a multi‐level database environment, end‐users work with projectdatabases, refreshing and archiving data as they continue to work on their respective regions of the network. Dataarchive and refresh between the project databases and the master database are performed by the administratoralone.

• Advantage: High performance.• Disadvantage: Manual Synchronisation between the master and the project databases.

• Dynamic regionalisation using Oracle Spatial or Oracle Locator

Dynamic regionalisation can be based on Oracle Spatial, which does not create separate regional databases from themaster database, but rather lets the different users work with the master database directly while managing theiraccess privileges according to their user connection properties. In an Atoll multi‐user environment, you can createsuch regionalisation without installing Oracle Spatial. You can implement this solution using Oracle Locator, which isprovided in the standard Oracle installation.

Specific documents explaining how to set up this regionalisation, using Oracle, in any Atoll master database areavailable on demand from Forsk. These documents provide scripts for creating different types of users, e.g., theadministrator, advanced user, read‐only user, etc., and give examples of how to set up regions in the network and howto assign user rights to each region.

• Advantage: Once set up, does not require administrator intervention.• Disadvantage: Slow performance (archiving data in the database takes a long time).

6.4.3 Appendix 3: Calculating Path Loss MatricesYou can calculate only the invalid path loss matrices or all the path loss matrices in Atoll or using a macro.

To calculate invalid path loss matrices only:

1. Right‐click the Transmitters folder. The context menu appears.

2. Select Calculations > Calculate Path Loss Matrices.

Atoll calculates path loss matrices for all active transmitters in the folder or subfolder. Only invalid and nonexistentmatrices are calculated.

To calculate all the path loss matrices (valid and invalid):

1. Right‐click the Transmitters folder. The context menu appears.

2. Select Calculations > Force Path Loss Matrix Calculation.

Atoll calculates all the path loss matrices for all active transmitters in the folder or subfolder.

You can write a script or macro to update path loss matrices automatically at regular intervals. The script or macro should:

1. Start Atoll (Start).

2. Open the master Atoll document (Open).

3. Refresh the contents of the document with data from the database (Refresh).

4. Calculate path loss matrices (Calculate).

5. Save the master Atoll document (Save).

6. Close Atoll (Exit).

A path loss update macro is available from Forsk on demand.

You should only calculate the shared path loss matrices when they are not being accessedby users.

70


6.4.4 Appendix 4: Path Loss Matrices From Different SourcesAtoll calculates path loss matrices and creates path loss matrix storage files using the propagation models assigned totransmitters. Atoll can also work with path loss matrices calculated by other tools. To use path loss matrices from differentsources, make sure that the path loss matrices are:

• Available in a format compatible with Atoll. File formats are described in "Path Loss Matrix File Format" on page 92.• Stored at the location set in the Atoll document.• Valid. If the path loss matrices are not valid, Atoll will automatically calculate them the next time they are used.

The shared path loss matrices architecture can contain path loss matrices from different sources. The Pathloss.dbf fileprovides the means to manage several sources of path loss matrices. This file stores, among other information, the validitystatus and the location (path) of the path loss matrix files for each transmitter.

Let us assume that users of group A wish to work with the path loss matrices generated by Atoll only, and users of group Bwish to work with path loss matrices generated by a different tool for a part of the network and with path loss matricesgenerated by Atoll where the matrices from the other tool are not available.

Let us assume that the shared path loss matrices folder where Atoll stores the generated path loss matrices files isC:\Path_Loss_Internal, and the folder where the other tool stores its path loss matrices is C:\Path_Loss_External.

The Pathloss.dbf file in the Path_Loss_Internal folder will store the path to the LOS files for each transmitter in the network.This folder can be set as the shared path loss matrices folder in the ATL files of group A users.

To set up the shared path loss matrices folder for group B users, you must create a new folder with a Pathloss.dbf file in it.This folder can be called C:\Path_Loss_Mixed. The Pathloss.dbf file in this folder can be a copy of the Pathloss.dbf file in thePath_Loss_Internal folder with the paths to the LOS files modified. For example, if the path loss matrices generated by theother tool include Transmitter_1, the Pathloss.dbf file in the Path_Loss_Mixed folder will have all the same entries asPathloss.dbf file in the Path_Loss_Internal folder except for the path for the Transmitter_1 path loss matrices file. Figure 6.4on page 71 explains this concept.

Once the Pathloss.dbf file in the Path_Loss_Mixed folder is updated with the correct paths corresponding to the differenttransmitters, the Path_Loss_Mixed folder can be set as the shared path loss matrices folder in the ATL files of group B users.

If a group B user changes some parameters which make some path loss matrices invalid, Atoll will recalculate the private pathloss matrices with the propagation models assigned to the transmitters. The external path loss matrix will no longer be used.

You should also make regular backups of the master Atoll document. The above macrocould also create a backup ATL file of the master Atoll document on a regular basis. Thisfile can be overwritten daily, whenever path losses are calculated.

Path loss matrices calculated by other tools should include antenna pattern attenuation(i.e., should be masked) in order to be consistent with the path loss matrices calculatedby Atoll.

Figure 6.4: Path Loss Architecture for Multiple Source Path Loss Matrices

71


72

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 7: Coordinate Systems and Units

7 Coordinate Systems and Units

7.1 Coordinate SystemsA map or a geo‐spatial database is a flat representation of data collected over a curved surface. Projection is a means ofproducing all or part of a spheroid on a flat surface, which cannot be done without distortion. It is up to the cartographer tochoose the characteristic (distance, direction, scale, area, or shape) that he wants to produce accurately on a flat surface atthe expense of the other characteristics, or to make a compromise on several characteristics. The projected zones arereferenced using cartographic coordinates (metre, yard, etc.). Two projection methods are widely used:

• The Lambert Conformal‐Conic Method: A portion of the earth is projected on a cone conceptually secant at one ortwo standard parallels. This projection method is useful for representing countries or regions that have a predominanteast‐west expanse.

• The Universal Transverse Mercator (UTM) Method: A portion of the earth is projected on a cylinder tangent to ameridian (which is transverse or crosswise to the equator). This projection method is useful for mapping large areasthat are oriented north‐south.

A geographic system is not a projection, but a representation of a location on the surface of the earth in geographiccoordinates (degree‐minute‐second, gradient) with the latitude and longitude with respect to a meridian (e.g., Paris for NTFsystem and Greenwich for ED50 system). Locations in a geographic system can be converted into other projections.

7.1.1 Definition of a Coordinate SystemA geographic coordinate system is a latitude and longitude coordinate system. The latitude and longitude are related to anellipsoid, a geodetic datum, and a prime meridian. The geodetic datum provides the position and orientation of the ellipsoidrelative to the earth.

Cartographic coordinate systems are obtained by transforming each (latitude, longitude) value into an (easting, northing)value. A projection coordinate system is obtained by transforming each (latitude, longitude) value into an (easting, northing)value. Projection coordinate systems are geographic coordinate systems that provide longitude and latitude, and thetransformation method characterised by a set of parameters. Different methods might require different sets of parameters.For example, the parameters required for Transverse Mercator coordinate systems are:

• The longitude of the natural origin (central meridian)• The latitude of the natural origin• The False Easting value• The False Northing value• A scaling factor at the natural origin (central meridian)

Basic definitions are presented below.

Geographic Coordinate System

The geographic coordinate system is a datum and a meridian. Atoll enables you to choose the most suitable geographiccoordinate system for your geographic data.

Datum

The datum consists of the ellipsoid and its position relative to the WGS84 ellipsoid. In addition to the ellipsoid, translation,rotation, and distortion parameters define the datum.

Meridian

The standard meridian is Greenwich, but some geographic coordinate systems are based on other meridians. These meridiansare defined by the longitude with respect to Greenwich.

References:

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.

2. http://www.colorado.edu/geography/gcraft/notes/gps/gps_f.html

3. http://www.epsg.org/Geodetic.html

4. http://geodesie.ign.fr/contenu/fichiers/documentation/pedagogiques/transfo.pdf (French)

73

http://www.colorado.edu/geography/gcraft/notes/gps/gps_f.html

http://www.epsg.org/Geodetic.html

http://geodesie.ign.fr/contenu/fichiers/documentation/pedagogiques/transfo.pdf

http://geodesie.ign.fr/contenu/fichiers/documentation/pedagogiques/transfo.pdf

Atoll 3.2.1 Administrator ManualChapter 7: Coordinate Systems and Units © Forsk 2014

Ellipsoid

The ellipsoid is the pattern used to model the earth. It is defined by its geometric parameters.

Projection

The projection is the transformation applied to project the ellipsoid of the earth on to a plane. There are different projectionmethods that use specific sets of parameters.

Projection Coordinate System

The projection coordinate system is the result of the application of a projection to a geographic coordinate system. Itassociates a geographic coordinate system and a projection. Atoll enables you to choose the projection coordinate systemmatching your geographic data.

7.1.2 Types of Coordinate Systems in AtollDepending on the working environment, there can be either two or four coordinate systems used in Atoll. If you are workingwith stand‐alone documents, i.e., documents not connected to databases, there are two coordinate systems used in Atoll:

• Projection coordinate system• Display coordinate system

If you are working in a multi‐user environment, Atoll uses four coordinate systems:

• Projection coordinate system for the Atoll document• Display coordinate system for the Atoll document• Internal projection coordinate system for the database• Internal display coordinate system for the database

Projection Coordinate System

The projection coordinate system is the coordinate system of the available raster geographic data files. You should set theprojection coordinate system of your Atoll document so that it corresponds to the coordinate system of the available rastergeographic data. You can set the projection coordinate system of your document in the Options dialog.

All the raster geographic data files that you want to import and use in an Atoll document must have the same coordinatesystem. You cannot work with raster geographic data files with different coordinate systems in the same document.

The projection coordinate system is used to keep the coordinates of sites (radio network data) consistent with the geographicdata.

When you import a raster geographic data file, Atoll reads the geo‐referencing information from the file (or from its headerfile, depending on the geographic data file format), i.e., its Northwest pixel, to determine the coordinates of each pixel. Atolldoes not use any coordinate system during the import process. However, the geo‐referencing information of geographic datafiles are considered to be provided in the projection coordinate system of the document.

Display Coordinate System

The display coordinate system is the coordinate system used for the display, e.g., in dialogs, in the Map window rulers, in thestatus bar, etc. The coordinates of each pixel of geographic data are converted to the display coordinate system from theprojection coordinate system for display. The display coordinate system is also used for sites (radio network data). You canset the display coordinate system of your document in the Options dialog.

If you import sites data, the coordinate system of the sites must correspond to the display coordinate system of your Atolldocument.

If you change the display coordinate system in a document which is not connected to a database, the coordinates of all thesites are converted to the new display system.

If you import vector geographic data (e.g., traffic, measurements, etc.) with differentcoordinate systems, it is possible to convert the coordinate systems of these data intothe projection coordinate system of your Atoll document.

If the coordinate systems of all your geographic data files and sites (radio network data)are the same, you do not have to define the projection and display coordinate systemsseparately. By default, the two coordinate systems are the same.

74


Internal Coordinate Systems

The internal coordinate systems are the projection and the display coordinate systems stored in a database. The projectionand display coordinate systems set by the administrator in the central Atoll project are stored in the database when thedatabase is created, and cannot be modified by users. Only the administrator can modify the internal coordinate systemsmanually by editing the entries in the CoordSys and the Units tables. All Atoll documents opened from a database will havethe internal coordinate systems of the database as their default projection and display coordinate systems.

When exporting an Atoll project to a database, the currently chosen display coordinate system becomes the internal displaycoordinate system for the database, and the currently chosen projection coordinate system becomes the internal projectioncoordinate system for the database.

Although Atoll stores both the coordinate systems in the database, i.e., the projection and the display coordinate systems,the only relevant coordinate system for the database is the internal display coordinate system because this coordinate systemis the one used for the coordinates of sites (radio network data).

Users working on documents connected to a database can modify the coordinate systems in their documents locally, and savethese changes in their documents, but they cannot modify the coordinate systems stored in the database.

If you change the display coordinate system in a document which is not connected to a database, the coordinates of all thesites are converted to the new display system.

If you change the display coordinate system in a document which is connected to a database, the coordinates of all the sitesare converted to the new coordinate system in the Atoll document locally but not in the database because the internalcoordinate systems cannot be changed.

Atoll uses the internal coordinates systems in order to keep the site coordinates consistent in the database which is usuallyaccessed by a large number of users in a multi‐user environment.

7.1.3 Coordinate Systems File FormatThe Coordsystems folder located in the Atoll installation directory contains all the coordinate systems, both geographic andcartographic, offered in the tool. Coordinate systems are grouped by regions. A catalogue per region and a "Favourites"catalogue are available in Atoll. The Favourites catalogue is initially empty and can be filled by the user by adding coordinatesystems to it. Each catalogue is described by an ASCII text file with .cs extension. In a .cs file, each coordinate system isdescribed in one line. The line syntax for describing a coordinate system is:

Examples:

You should keep the following points in mind when editing or creating .cs files:

• The identification code enables Atoll to differentiate coordinates systems. In case you create a new coordinatesystem, its code must be an integer value higher than 32767.

• When describing a new datum, you must enter the ellipsoid code and parameters instead of the datum code inbrackets. There can be 3 to 7 parameters defined in the following order: Dx, Dy, Dz, Rx, Ry, Rz, S. The syntax of the linein the .cs file will be:

• There can be up to seven projection parameters. These parameters must be ordered according to the parameter index(see "Projection Parameter Indices" on page 78). Parameter with index 0 is the first one. Projection parameters aredelimited by commas.

• For UTM projections, you must provide positive UTM zone numbers for north UTM zones and negative numbers forsouth UTM zones.

• You can add all other information as comments (such as usage or region).

Codes of units, data, projection methods, and ellipsoids, and projection parameter indices are listed in the tables below.

Code = "Name of the system"; Unit Code; Datum Code; Projection Method Code, ProjectionParameters; "Comments"

4230 = "ED50"; 101; 230; 1; "Europe - west"

32045 = "NAD27 / Vermont"; 2; 267; 6, -72.5, 42.5, 500000, 0, 0.9999643; "UnitedStates - Vermont"

Code = "Name of the system"; Unit Code; {Ellipsoid Code, Dx, Dy, Dz, Rx, Ry, Rz, S};Projection Method Code, Projection Parameters; "Comments"

75


Unit Codes

Datum Codes

Code Cartographic Units Code Geographic Units

0 Metre 100 Radian

1 Kilometre 101 Degree

2 Foot 102 Grad

3 Link 103 ArcMinute

4 Chain 104 ArcSecond

5 Yard

6 Nautical mile

7 Mile

‐1 Unspecified ‐1 Unspecified

Code Datum Code Datum

121 Greek Geodetic Reference System 1987 260 Manoca

125 Samboja 261 Merchich

126 Lithuania 1994 262 Massawa

130 Moznet (ITRF94) 263 Minna

131 Indian 1960 265 Monte Mario

201 Adindan 266 M'poraloko

202 Australian Geodetic Datum 1966 267 North American Datum 1927

203 Australian Geodetic Datum 1984 268 NAD Michigan

204 Ain el Abd 1970 269 North American Datum 1983

205 Afgooye 270 Nahrwan 1967

206 Agadez 271 Naparima 1972

207 Lisbon 272 New Zealand Geodetic Datum 1949

208 Aratu 273 NGO 1948

209 Arc 1950 274 Datum 73

210 Arc 1960 275 Nouvelle Triangulation Française

211 Batavia 276 NSWC 9Z‐2

212 Barbados 277 OSGB 1936

213 Beduaram 278 OSGB 1970 (SN)

214 Beijing 1954 279 OS (SN) 1980

215 Reseau National Belge 1950 280 Padang 1884

216 Bermuda 1957 281 Palestine 1923

217 Bern 1898 282 Pointe Noire

218 Bogota 283 Geocentric Datum of Australia 1994

219 Bukit Rimpah 284 Pulkovo 1942

221 Campo Inchauspe 285 Qatar

222 Cape 286 Qatar 1948

223 Carthage 287 Qornoq

224 Chua 288 Loma Quintana

225 Corrego Alegre 289 Amersfoort

226 Cote d'Ivoire 290 RT38

227 Deir ez Zor 291 South American Datum 1969

228 Douala 292 Sapper Hill 1943

229 Egypt 1907 293 Schwarzeck

230 European Datum 1950 294 Segora

76


Projection Method Codes

Ellipsoid Codes

231 European Datum 1987 295 Serindung

232 Fahud 296 Sudan

233 Gandajika 1970 297 Tananarive 1925

234 Garoua 298 Timbalai 1948

235 Guyane Francaise 299 TM65

236 Hu Tzu Shan 300 TM75

237 Hungarian Datum 1972 301 Tokyo

238 Indonesian Datum 1974 302 Trinidad 1903

239 Indian 1954 303 Trucial Coast 1948

240 Indian 1975 304 Voirol 1875

241 Jamaica 1875 305 Voirol Unifie 1960

242 Jamaica 1969 306 Bern 1938

243 Kalianpur 307 Nord Sahara 1959

244 Kandawala 308 Stockholm 1938

245 Kertau 309 Yacare

247 La Canoa 310 Yoff

248 Provisional South American Datum 1956 311 Zanderij

249 Lake 312 Militar‐Geographische Institut

250 Leigon 313 Reseau National Belge 1972

251 Liberia 1964 314 Deutsche Hauptdreiecksnetz

252 Lome 315 Conakry 1905

253 Luzon 1911 322 WGS 72

254 Hito XVIII 1963 326 WGS 84

255 Herat North 901 Ancienne Triangulation Française

256 Mahe 1971 902 Nord de Guerre

257 Makassar 903NAD 1927 Guatemala/Honduras/Salvador

(Panama Zone)

258 European Reference System 1989

Code Projection Method Code Projection Method

0 Undefined 8 Oblique Stereographic

1 No projection > Longitude / Latitude 9 New Zealand Map Grid

2 Lambert Conformal Conical 1SP 10 Hotine Oblique Mercator

3 Lambert Conformal Conical 2SP 11 Laborde Oblique Mercator

4 Mercator 12 Swiss Oblique Cylindrical

5 Cassini‐Soldner 13 Oblique Mercator

6 Transverse Mercator 14 UTM Projection

7 Transverse Mercator South Oriented

Code Name Major Axis Minor Axis

1 Airy 1830 6377563.396 6356256.90890985

2 Airy Modified 1849 6377340.189 6356034.44761111

3 Australian National Spheroid 6378160 6356774.71919531

4 Bessel 1841 6377397.155 6356078.96261866

5 Bessel Modified 6377492.018 6356173.50851316

6 Bessel Namibia 6377483.865 6356165.38276679

Code Datum Code Datum

77


Projection Parameter Indices

7.1.4 Creating a Coordinate System in AtollAtoll provides a large default catalogue of coordinate systems. However, it is possible to add new geographic and cartographiccoordinate systems. New coordinate systems can be created from scratch or initialised based on existing ones.

To create a new coordinate system from scratch:

1. Select Document > Properties. The Properties dialogue opens.

2. Select the Coordinates tab.

3. Click the Browse button ( ) to the right of Projection. The Coordinate Systems dialogue appears.

4. Click New. The Coordinate System dialogue appears.

7 Clarke 1858 6378293.63924683 6356617.98173817

8 Clarke 1866 6378206.4 6356583.8

9 Clarke 1866 Michigan 6378693.7040359 6357069.45104614

10 Clarke 1880 (Benoit) 6378300.79 6356566.43

11 Clarke 1880 (IGN) 6378249.2 6356515

12 Clarke 1880 (RGS) 6378249.145 6356514.86954978

13 Clarke 1880 (Arc) 6378249.145 6356514.96656909

14 Clarke 1880 (SGA 1922) 6378249.2 6356514.99694178

15 Everest 1830 (1937 Adjustment) 6377276.345 6356075.41314024

16 Everest 1830 (1967 Definition) 6377298.556 6356097.5503009

17 Everest 1830 (1975 Definition) 6377301.243 6356100.231

18 Everest 1830 Modified 6377304.063 6356103.03899315

19 GRS 1980 6378137 6356752.31398972

20 Helmert 1906 6378200 6356818.16962789

21 Indonesian National Spheroid 6378160 6356774.50408554

22 International 1924 6378388 6356911.94612795

23 International 1967 6378160 6356774.71919530

24 Krassowsky 1940 6378245 6356863.01877305

25 NWL 9D 6378145 6356759.76948868

26 NWL 10D 6378135 6356750.52001609

27 Plessis 1817 6376523 6355862.93325557

28 Struve 1860 6378297 6356655.84708038

29 War Office 6378300.583 6356752.27021959

30 WGS 84 6378137 6356752.31398972

31 GEM 10C 6378137 6356752.31398972

32 OSU86F 6378136.2 6356751.51667196

33 OSU91A 6378136.3 6356751.61633668

34 Clarke 1880 6378249.13884613 6356514.96026256

35 Sphere 6371000 6371000

Index Projection Parameter Index Projection Parameter

0 UTM zone number 4 Scale factor at origin

0 Longitude of origin 4 Latitude of 1st parallel

1 Latitude of origin 5 Azimuth of central line

2 False Easting 5 Latitude of 2nd parallel

3 False Northing 6 Angle from rectified to skewed grid

Code Name Major Axis Minor Axis

78


5. In the Coordinate System dialogue:

a. Select the coordinate systems catalogue to which you want to add the new coordinate system.

b. Under General, enter a Name for the new coordinate system and select a Unit. In Use, you can enter commentsabout its usage. Atoll assigns the code automatically.

c. Under Category, select the Type of coordinate system. Enter the longitude and latitude for a geographiccoordinate system, or the type of projection and its set of associated parameters for a cartographic coordinatesystem (false easting and northing, and the first and second parallels).

d. Under Geo, specify the meridian and choose a Datum for the coordinate system. The associated ellipsoid isautomatically selected. You can also describe a geodetic datum by selecting "<Customised>" in the Datum list. Inthis case, you must select an Ellipsoid and enter parameters (Dx, Dy, Dz, Rx, Ry, Rz, and S) needed for thetransformation of the datum into WGS84.

6. Click OK. The new coordinate system is added to the selected coordinate system catalogue.

To create a new coordinate system based on an existing system, select a coordinate system in the Coordinate Systemsdialogue before clicking New in step 4. The new coordinate system is initialised with the values of the selected coordinatesystem.

7.2 UnitsIn the Atoll documents, you can define measurement units for reception, transmission, antenna gain, distance, height andoffset, and temperature. You can accept the default measurement units, or you can change them using the documentproperties dialogue.

Transmission and Reception Power Units

Depending on the working environment, Atoll can use either one or two measurement units for the transmission/receptionpower.

If you are working with stand‐alone documents, i.e., documents not connected to databases, there is only one measurementunit used in Atoll for display. It corresponds to the transmission/reception power unit defined in the Atoll document.

If you are working in a multi‐user environment, Atoll uses two measurement units:

• A measurement unit for display in the Atoll document. It corresponds to the transmission/reception power unitdefined in the current Atoll document. It is used for the display in the dialogues and in the tables, e.g., receptionthresholds (coverage prediction properties, microwave link properties, etc.), and received signal levels(measurements, point analysis, coverage predictions, microwave link properties, etc.).

• An internal measurement unit for the database. The internal unit is the transmission/reception power unit stored inthe database. It corresponds to the transmission/reception power unit used in the master Atoll document when thedatabase is created. Users working in documents connected to a database can modify the transmission/receptionpower unit and save this change in their documents locally, but they cannot modify the internal power unit stored inthe database. Only the administrator can modify it manually by editing the entry in the Units tables.

Antenna Gain Units

Depending on the working environment, Atoll can use either one or two measurement units for the antenna gain.

If you are working with stand‐alone documents, i.e., documents not connected to databases, there is only one measurementunit used in Atoll for display. It corresponds to the antenna gain unit defined in the Atoll document.

If you are working in a multi‐user environment, Atoll uses two measurement units:

• A measurement unit for display in the Atoll document. It corresponds to the antenna gain unit defined in the currentAtoll document and it is used for the display in the dialogues and in the tables.

• An internal measurement unit for the database. The internal unit is the antenna gain unit stored in the database. Itcorresponds to the antenna gain unit used in the master Atoll document when the database is created. Users workingin documents connected to a database can modify the antenna gain unit and save this change in their documentslocally, but they cannot modify the antenna gain unit stored in the database. Only the administrator can modify itmanually by editing the entry in the Units tables.

Distance Units

Atoll uses the distance unit defined in the current Atoll document as display unit of the distances in the dialogues, in thetables, and in the status bar.

Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected todatabases or not. The internal measurement unit is not stored in the database and cannot be changed.

79


Height and Offset Units

Atoll uses the height and offset unit defined in the current Atoll document as display unit of the heights and the offsets in thedialogues, in the tables, and in the status bar.

Metre is used as the internal measurement unit for the heights and offsets in all Atoll documents whether they are connectedto databases or not. The internal measurement unit is not stored in the database and cannot be changed.

Temperature Units

Atoll uses the temperature unit defined in the current Atoll document as display unit of the temperatures in the dialoguesand in the tables.

Degree Celsius is used as the internal measurement unit for the temperature in all Atoll documents whether they areconnected to databases or not. The internal measurement unit is not stored in the database and cannot be changed.

7.3 BSIC FormatDepending on the working environment, there can be either one or two types of BSIC formats. If you are working with stand‐alone documents, i.e., documents not connected to databases, there is only one BSIC format:

• Display BSIC format

If you are working in a multi‐user environment, Atoll uses two type of formats:

• Display BSIC format for the Atoll document• Internal BSIC format for the database

The display format is used for the display in dialogs and tables. You can set the display format for your document from theTransmitters folder’s context menu.

The internal format is the BSIC format stored in a database. The BSIC format set by the administrator in the central Atollproject is stored in the database when the database is created, and cannot be modified by users. Only the administrator canmodify the internal format manually by editing the corresponding entry in the Units tables. All Atoll documents opened froma database will have the internal format of the database as their default BSIC format.

Users working on documents connected to a database can modify the format in their documents locally, and save this changein their documents, but they cannot modify the format stored in the database.

80

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 8: Geographic Data

8 Geographic DataAtoll supports several geographic data types; DTM (Digital Terrain Model), clutter, scanned images, vector data, traffic maps,population, and custom geographic data. Atoll offers import/export filters for the most commonly used geographic dataformats.

The following table summarizes the supported formats and filters:

You can import custom geographic data types other than those listed above into Atoll. Custom maps can be taken into accountin clutter statistics and coverage prediction reports.

Custom file formats supported by Atoll are:

• BIL (8, 16, 32‐bits)• TIFF (8, 16, 32‐bits)• BMP (8, 32‐bits)• Erdas Imagine (8, 16, 32‐bits)• MIF/TAB• SHP• Vertical Mapper (GRD, GRC)• AGD

File FormatImport Export

Geographic Data Types

GeoreferencingDTM

Clutter Classes

Clutter Heights

Traffic MapsRaster Images

PopulationVector Data

Web Map Services

BIL Both8, 16, or 32‐

bit8‐bit

8, 16, or 32‐bit

User profile raster (8‐bit) User density raster (16, 32‐

bit)

1, 4, 8 or 24‐bit

8, 16, or 32‐bit

HDR files

TIFF Both 8 or 16‐bit 8‐bit 8 or 16‐bitUser profile raster (8‐bit), User density raster (16, 32‐

bit)

1, 4, 8 or 24‐bit

8, 16, or 32‐bit

Yes TFW files

Planet Both 16‐bit 16‐bit 16‐bit

User profile density

Sector traffic maps

User profile raster (16‐bit)

User density raster (16‐bit)

1, 4, 8 or 24‐bit

Yes index files

BMP Both 8‐bit 8‐bit 8‐bitUser profile raster (8‐bit) User density raster (16, 32‐

bit)1 to 24‐bit 8 or 32‐bit Yes BPW or BMW files

DXF ImportUser profile densitySector traffic maps

Yes Yes

SHP BothUser profile densitySector traffic maps

Vector Yes Yes

MapInfo(MIF, TAB)

BothUser profile densitySector traffic maps

Vector Yes Yes

Erdas Imagine(IMG)

Import8, 16, and 32‐bit

8‐bit8, 16, and 32‐bit

User profile raster (8‐bit)User density raster (16, 32‐

bit)

1, 4, 8 or 24‐bit

8, 16, or 32‐bit

Yes

ArcView Grid(TXT)

Export Text Text Text Text Text Text Embedded data

Atoll Geo Data(AGD)

BothUser profile densitiesSector traffic maps

Vector Yes Embedded data

Vertical Mapper (GRD, GRC)

Both DTMClutter Classes

Clutter Heights

User profile rasterUser density raster

Raster Images

Vector Embedded data

ECW Import 24‐bit ERS files

PNG Both All All PGW files

JPEG Both All All JGW files

• WLD files can be used for georeferencing for any type of binary raster file.• The smallest supported resolution for raster files is 1 m. There is no restriction on the

resolution of images.• DTM, clutter classes, and clutter height maps must have an integer resolution.• All the raster maps you want to import in an ATL document must be represented in

the same projection system.

81

Atoll 3.2.1 Administrator ManualChapter 8: Geographic Data © Forsk 2014

8.1 Geographic Header File FormatsHeader files are used to describe how data is organised within a data file. This section covers the following topics:

• "HDR Header File for BIL Files" on page 82• "TFW Header File for TIFF Files" on page 83• "BPW/BMW Header Files for BMP Files" on page 84• "PGW Header File for PNG Files" on page 84• "JGW Header File for JPG Files" on page 84• "Generic Raster Header File" on page 85

8.1.1 HDR Header File for BIL FilesThe HDR file is a text file that contains meta‐data describing the organisation of the BIL file. The header file is made of rows,each row having the following format:

where ‘keyword’ corresponds to an attribute type, and ‘value’ defines the attribute value.

Keywords required by Atoll are described below. Other keywords are ignored.

Four additional keywords can optionally be managed.

This can be:

In some cases, this keyword can be replaced by datatype defined as follows:

This can be:

keyword value

ulxmap x coordinate of the centre of the upper-left pixel.

ulymap y coordinate of the centre of the upper-left pixel.

xdim x size in metre of a pixel.

ydim y size in metre of a pixel.

ncols Number of columns in the image.

nrows Number of rows in the image.

nbits Number of bits per pixel per band; 8 or 16 for DTMs or Clutter heights(altitude in metres), 8 for clutter classes file (clutter code), 16 forpath loss matrices (path loss in dB, field value in dBm, dBµV and DBµV/m).

nbands Number of spectral bands in the image, (1 for DTM and 8 bit pictures).

byteorder Byte order in which image pixel values are stored. Accepted values are M(Motorola byte order) or I (Intel byte order).

layout Must be ‘bil’.

bandrowbytes Number of bytes per band per row.

totalrowbytes Total number of bytes of data per row.

skipbytes Byte to be skipped in the image file in order to reach the beginning ofthe image data. Default value is 0.

pixeltype Type of data read (in addition to the length)

UNSIGNDINT Undefined 8, 16, 24 or 32 bits

SIGNEDINT Integer 16 or 32 bits

FLOAT Real 32 or 64 bits

datatype Type of data read (in addition to the length)

82


The other optional keywords are: valueoffset, valuescale, and nodatavalue.

By default, integer data types are chosen with respect to the pixel length (nbits).

So, we have

DTM Sample

Here, the data is 20 m.

Clutter Classes Sample

8.1.2 TFW Header File for TIFF FilesTFW files contain the spatial reference data of associated TIFF files. The TFW file structure is simple; it is an ASCII text file thatcontains six lines. You can open a TFW file using any ASCII text editor. The TFW file structure is as follows:

Un Undefined n bits (8, 16, 24 or 32 bits)

In Integer n bits (16 or 32 bits)

Rn Real n bits (32 or 64 bits)

RGB24 Integer 3 colour components on 24 bits

valueoffset Real value to be added to the read value (Vread)

valuescale Scaling factor to be applied to the read value

nodatavalue Value corresponding to “NO DATA”

nrows 1500

ncols 1500

nbands 1

nbits 8 or 16

byteorder M

layout bil

skipbytes 0

ulxmap 975000

ulymap 1891000

xdim 20.00

ydim 20.00

nrows 1500

ncols 1500

nbands 1

nbits 8

byteorder M

layout bil

skipbytes 0

ulxmap 975000

ulymap 1891000

xdim 20.00

ydim 20.00

V Vread valuescale valueoffset+=

Line Description

1 x dimension of a pixel in map units

2a amount of translation

3 amount of rotation

4 negative of the y dimension of a pixel in map units

83



8.1.3 BPW/BMW Header Files for BMP FilesThe header file is a text file that describes how organised in the BMP file. The header file is made of rows, each row havingthe following description:

Atoll supports BPW and BMW header file extensions for Import, but exports headers with BPW file extensions.


8.1.4 PGW Header File for PNG FilesA PNG world file (PGW file) is a plain text file used by geographic information systems (GIS) to provide georeferencinginformation for raster map images in PNG format. The world file parameters are:

8.1.5 JGW Header File for JPG FilesA JPEG world file (JGW file) is a plain text file used by geographic information systems (GIS) to provide georeferencinginformation for raster map images in JPEG format. The world file parameters are:

5 x‐axis map coordinate of the centre of the upper‐left pixel

6 y‐axis map coordinate of the centre of the upper‐left pixel

a. Atoll does not use the lines 2 and 3 when importing a TIFF format geographic file.

100.00

0.00

0.00

-100.00

60000.00

2679900.00

Line Description

Line Description


2 amount of translation





100.00

0.00

0.00

-100.00

60000.00

2679900.00

Line Description







84


8.1.6 Generic Raster Header FileWLD is a header format for Atoll that can be used for any raster data file for georeferencing. At the time of import of any rasterdata file, Atoll can use the corresponding WLD file to read the georeferencing information related to the raster data file. TheWLD file contains the spatial reference data of any associated raster data file. The WLD file structure is simple; it is an ASCIItext file containing six lines. You can open a WLD file using any ASCII text editor.

The WLD file is a text file that describes how organised in the associated raster data file. The header file is made of rows, eachrow having the following description:

Clutter Classes File Sample

Line Description







Line Description







100.00

0.00

0.00

-100.00

60000.00

2679900.00

85


86

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 9: Radio Data Formats

9 Radio Data FormatsRadio network data in Atoll includes the following, depending on the technology used in the network being planned:

• Site: The geographic location of transmitters (sectors, installed antennas, other equipment). A site can have one ormore transmitters.

• Antenna: The radiation patterns and gains for antennas installed at transmitters.• Transmitter: A group of radio devices installed at a site with there transmission/reception characteristics (antennas,

feeders, TMAs, other equipment). A transmitter can have one or more cells or subcells.• Cell: An RF carrier available at a transmitter in UMTS, CDMA2000, TD‐SCDMA, LTE, WiMAX, and Wi‐Fi networks. A cell

is fully defined by the "transmitter‐carrier" pair. Each cell in these networks is independent, i.e., has its own identifier,power levels, performance characteristics.

• TRX: An RF carrier available at a transmitter in GSM networks. A transceiver (TRX) can carry one ARFCN which cancorrespond to the BCCH (7 traffic timeslots) or TCH (8 traffic timeslots).

• Subcell: A subcell is a group of TRXs with the same radio characteristics. A subcell is fully defined by the "transmitter‐TRX type" pair.

• Base station: This is the generic name for a cell site ("site‐transmitter‐cell" or "site‐transmitter‐subcells"). Technology‐specific names can be BTS, Node‐B, eNode‐B, etc.

• RF repeater: An RF repeater receives, amplifies, and retransmits RF carriers both in downlink and uplink. The repeaterreceives signals from a donor transmitter which it retransmits using a coverage‐side antenna with amplification.

• Remote antenna: Transmitter antennas located at a remote location with respect to the transmitter’s site.• Microwave link: A point‐to‐point link using microwave frequencies used for backhaul in radio access networks or for

fixed wireless access.• PMP microwave link: A group of microwave links originating from a common node to serve more than one location. • Passive microwave repeater: A passive microwave repeater receives and retransmits microwave signals without

amplification. Passive repeaters do not have power sources of their own. Active repeaters, on the other hand, amplifythe received signal. Reflectors are examples of passive repeaters.

9.1 XML Import/Export FormatAll the data tables in an Atoll document can be exported to XML files. Atoll creates the following files when data tables areexported to XML files:

• An index.xml file which contains the mapping between the data tables in Atoll and the XML file created for each table.• One XML file per data table which contains the data table format (schema) and the data.

When XML files are imported to a document, the table and field definitions are not modified, i.e., the Networks andCustomFields tables are exported to XML file but are not imported.

The following sections describe the structures of the XML files created at export.

9.1.1 Index.xml File FormatThe index.xml file stores the system (GSM, UMTS, etc.) and the technology (TDMA, CDMA, etc.) of the document, and theversion of Atoll used for exporting the data tables to XML files. It also contains the mapping between the data tables in theAtoll document and the XML file corresponding to each data table.

The root tag <Atoll_XML_Config...> of the index.xml file contains the following attributes:

The index file also contains the mapping between the tables exported from Atoll and the XML files corresponding to eachtable. This list is sorted in the order in which tables must be imported in Atoll.

The list is composed of <XML_Table.../> tags with the following attributes:

A sample extract of the index.xml is given below:

Attribute Description

Atoll_File_System Corresponds to the SYSTEM_ field of the Networks table of the exported document

Atoll_File_Technology Corresponds to the TECHNOLOGY field of the Networks table of the exported document

Atoll_File_Version Corresponds to the Atoll version

Attribute Description

XML_File Corresponds to the exported XML file name (e.g., "Sites.xml")

Atoll_Table Corresponds to the exported Atoll table name (e.g., "Sites")

87

Atoll 3.2.1 Administrator ManualChapter 9: Radio Data Formats © Forsk 2014

Note that no closing tag </XML_Table> is required.

9.1.2 XML File FormatAtoll creates an XML file per exported data table. This XML file has two sections, one for storing the description of the tablestructure, and the second for the data itself. The XML file uses the standard XML rowset schema (schema included in the XMLfile between <s:Schema id=‘RowsetSchema’> and </s:Schema> tags).

Rowset Schema

The XML root tag for XML files using the rowset schema is the following:

The schema definition follows the root tag and is enclosed between the following tags:

In the rowset schema, after the schema description, the data are enclosed between <rs:data> and </rs:data>.

Between these tags, each record is handled by a <z:row … /> tag having its attributes set to the record field values since in therowset schema, values are handled by attributes. Note that no closing tag </z:row> is required.

A sample extract of a Sites.xml file containing the Sites table with only one site is given below:

<Atoll_XML_Config Atoll_File_System="UMTS" Atoll_File_Technology="CDMA" Atoll_File_Version="3.x.x build xxxx">

<XML_Table XML_File="CustomFields.xml" Atoll_Table="CustomFields" />

<XML_Table XML_File="CoordSys.xml" Atoll_Table="CoordSys" />

...

</Atoll_XML_Config>

<xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'

xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'

xmlns:rs='urn:schemas-microsoft-com:rowset'

xmlns:z='#RowsetSchema'>

<s:Schema id=‘RowsetSchema’>

<!-Schema is defined here, using <s:ElementType> and <s:AttributeType> tags ->

</s:Schema>

<xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'

xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'

xmlns:rs='urn:schemas-microsoft-com:rowset'

xmlns:z='#RowsetSchema'>

<s:Schema id='RowsetSchema'>

<s:ElementType name='row' content='eltOnly' rs:updatable='true'>

<s:AttributeType name='NAME' rs:number='1' rs:maydefer='true'rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='NAME'rs:keycolumn='true'>

<s:datatype dt:type='string' dt:maxLength='50'/>

</s:AttributeType>

<s:AttributeType name='LONGITUDE' rs:number='2' rs:maydefer='true'rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='LONGITUDE'>

<s:datatype dt:type='float' dt:maxLength='8' rs:precision='15'rs:fixedlength='true'/>

</s:AttributeType>

<s:AttributeType name='LATITUDE' rs:number='3' rs:maydefer='true'rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='LATITUDE'>

<s:datatype dt:type='float' dt:maxLength='8' rs:precision='15' rs:fixedlength='true'/>

</s:AttributeType>

88


9.2 RF 2D Antenna Pattern FormatThis section describes the format of the DIAGRAM field of the Antennas table. This field stores the antenna diagrams in a 2D(angle vs. attenuation) format. This is the format of the contents of the DIAGRAM field of the Antennas table when it is copiedfrom, pasted to, imported to (from TXT or CSV files), and exported from (from TXT, CSV, or XLS files) the Antennas table.

Antenna patterns can also be imported in Planet 2D‐format antenna files and 3D antenna files. The file format required for3D antenna file import is described in "Import Format of 3D Antenna Pattern Text Files" on page 91.

The format of 2D antenna patterns containing co‐polar diagrams only can be understood from Figure 9.1 on page 89.

The contents of the DIAGRAM field are formatted as follows:

• Pattern Descriptor 1: Space‐separated list of parameters.• First entry: The number of co‐polar diagrams. For example, 2.• Second entry: First co‐polar diagram type = 0 for azimuth (horizontal) diagram.• Third entry: The elevation angle of the azimuth diagram.• Fourth entry: The number of angle‐attenuation pairs in the first co‐polar diagram. For example, 360.

• Co‐polar Horizontal Diagram: Horizontal co‐polar diagram (the second entry in the preceding descriptor is 0). Theformat is space‐separated angle attenuation pairs. For example, 0 0 1 0 2 0.1....

• Pattern Descriptor 2: Space‐separated list of parameters.• First entry: Second co‐polar diagram type = 1 for elevation (vertical) diagram.• Second entry: The azimuth angle of the elevation diagram.• Third entry: The number of angle‐attenuation pairs in the second co‐polar diagram. For example, 360.

• Co‐polar Vertical Diagram: Vertical co‐polar diagram (the first entry in the preceding descriptor is 1). The format isspace‐separated angle attenuation pairs. For example, 0 0 1 0.1....

• End: The number cross‐polar diagrams = 0.

The format of 2D antenna patterns containing co‐polar and cross‐polar diagrams can be understood from Figure 9.2 onpage 90.

<s:AttributeType name='ALTITUDE' rs:number='4' rs:nullable='true' rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='ALTITUDE'>

<s:datatype dt:type='r4' dt:maxLength='4' rs:precision='7' rs:fixedlength='true'/>

</s:AttributeType>

<s:AttributeType name='COMMENT_' rs:number='5' rs:nullable='true' rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='COMMENT_'>

<s:datatype dt:type='string' dt:maxLength='255'/>

</s:AttributeType>

<s:extends type='rs:rowbase'/>

</s:ElementType>

</s:Schema>

<rs:data>

<rs:insert>

<z:row NAME='Site0' LONGITUDE='8301' LATITUDE='-9756'/>

</rs:insert>

</rs:data>

</xml>

Figure 9.1: 2D RF Antenna Pattern Format Containing Co‐polar Diagrams Only

Pattern EndCo-polar Horizontal Diagram Co-polar Vertical Diagram

2 0 0 360 0 0 1 0 2 0.1 … 1 0 360 0 0 1 0.1 … 0Discriptor 1

PatternDiscriptor 2

89


The contents of the DIAGRAM field are formatted as follows:

• Pattern Descriptor 1: Space‐separated list of parameters.• First entry: The number of co‐polar diagrams. For example, 2.• Second entry: First co‐polar diagram type = 0 for azimuth (horizontal) diagram.• Third entry: The elevation angle of the azimuth diagram.• Fourth entry: The number of angle‐attenuation pairs in the first co‐polar diagram. For example, 360.

• Co‐polar Horizontal Diagram: Horizontal co‐polar diagram (the second entry in the preceding descriptor is 0). Theformat is space‐separated angle attenuation pairs. For example, 0 0 1 0 2 0.1....

• Pattern Descriptor 2: Space‐separated list of parameters.• First entry: Second co‐polar diagram type = 1 for elevation (vertical) diagram.• Second entry: The azimuth angle of the elevation diagram.• Third entry: The number of angle‐attenuation pairs in the second co‐polar diagram. For example, 360.

• Co‐polar Vertical Diagram: Vertical co‐polar diagram (the first entry in the preceding descriptor is 1). The format isspace‐separated angle attenuation pairs. For example, 0 0 1 0.1....

• Pattern Descriptor 3: Space‐separated list of parameters.• First entry: The number of cross‐polar diagrams. For example, 2.• Second entry: First cross‐polar diagram type = 0 for azimuth (horizontal) diagram.• Third entry: The elevation angle of the azimuth diagram.• Fourth entry: The number of angle‐attenuation pairs in the first cross‐polar diagram. For example, 360.

• Cross‐polar Horizontal Diagram: Horizontal cross‐polar diagram (the second entry in the preceding descriptor is 0).The format is space‐separated angle attenuation pairs. For example, 0 0 1 0 2 0.1....

• Pattern Descriptor 4: Space‐separated list of parameters.• First entry: Second cross‐polar diagram type = 1 for elevation (vertical) diagram.• Second entry: The azimuth angle of the elevation diagram.• Third entry: The number of angle‐attenuation pairs in the second cross‐polar diagram. For example, 360.

• Cross‐polar Vertical Diagram: Vertical cross‐polar diagram (the first entry in the preceding descriptor is 1). The formatis space‐separated angle attenuation pairs. For example, 0 0 1 0.1....

You can use a 3rd party software or develop a tool to convert the contents of the DIAGRAM field into binary. In binary, eachantenna is described by a header and a list of value pairs.

The header is defined as follows:

• flag: (Integer, 32 bits) ‐1 for omni diagrams, 0 for directional• num: (Short integer, 16 bits) Number of diagrams (0, 1, 2, 3, 4)• siz0: (Short integer, 16 bits) Size of the first diagram (horizontal co‐polar section, elevation = 0°)• siz1: (Short integer, 16 bits) Size of the second diagram (vertical co‐polar section, azimuth = 0°)• siz2: (Short integer, 16 bits) Size of the third diagram (horizontal cross‐polar)• siz3: (Short integer, 16 bits) Size of the fourth diagram (vertical cross‐polar)• prec: (Short integer, 16 bits) Precision of the following angle values (100)

Then follows the content of each of the defined diagrams, i.e., the diagrams whose sizes (siz0, siz1, siz2, siz3) are not zero.Each diagram consists of a list of value pairs. The number of value pairs in a list depends on the value of the siz0, siz1, siz2,and siz3 parameters. For example, siz2 = 5 means there are five value pairs in the third diagram.

The value pairs in each list are:

• ang: (Short integer, 16 bits) The first component of the value pair is the angle in degrees multiplied by 100. Forexample, 577 means 5.77 degrees.

• loss: (Short integer, 16 bits) The second component of the value pair is the loss in dB for the given angle ang.

All the lists of value pairs are concatenated without a separator.

Figure 9.2: 2D RF Antenna Pattern Format Containing Co‐polar and Cross‐polar Diagrams

Pattern Co-polar Horizontal Diagram Co-polar Vertical Diagram

2 0 0 360 0 0 1 0 2 0.1 … 1 0 360 0 0 1 0.1 …

Discriptor 1Pattern

Discriptor 2

Pattern Cross-polar Horizontal Diagram Cross-polar Vertical DiagramDiscriptor 3Pattern

Discriptor 4

2 0 0 360 0 0 1 0 2 0.1 … 1 0 360 0 0 1 0.1 …

90


9.3 Import Format of 3D Antenna Pattern Text FilesText files containing 3D antenna patterns that can be imported in Atoll must have the following format:

• Header: The text file can contain a header with additional information. When you import the antenna pattern you canindicate the row number in the file where the header ends and the antenna pattern begins.

• Antenna Pattern: Each row contains three values to describe the 3D antenna pattern. The columns containing thevalues can be in any order:• Azimuth: Allowed range of values is from 0° to 360°. The smallest increment allowed is 1°.• Tilt: Allowed range of values is from ‐90° to 90° or from 0° to 180°. The smallest increment allowed is 1°.• Attenuation: The attenuation in dB.

9.4 Microwave 2D Antenna Pattern FormatThis section describes the format of the PATTERN field of the MW Antennas table. This field stores the antenna diagrams in a2D (angle vs. attenuation) format. This is the format of the contents of the PATTERN field of the MW Antennas table when itis copied from, pasted to, imported to (from TXT or CSV files), and exported from (from TXT, CSV, or XLS files) the MWAntennas table.

Antenna patterns can also be imported in Planet 2D‐format antenna files and 3D antenna files. The file format required for3D antenna file import is described in "Import Format of 3D Antenna Pattern Text Files" on page 91.

The format of 2D antenna patterns can be understood from Figure 9.3 on page 91.

The contents of the PATTERN field are formatted as follows:

• Pattern Descriptor 1: Space‐separated list of parameters.• First entry: The number of H_polarisation diagrams. For example, 4.• Second and third entries: First diagram type = 0 1, for co‐polar H‐V diagram ("EL HH" in Atoll).• Fourth entry: The elevation angle of the azimuth diagram.• Fifth entry: The number of angle‐attenuation pairs in the first co‐polar diagram. For example, 360.

• Co‐polar H‐V Diagram: Co‐polar H‐V diagram (the second and third entries in the preceding descriptor are 0 1). The format is space‐separated angle attenuation pairs. For example, 0 0 1 0.5....

• Pattern Descriptor 2: Space‐separated list of parameters.• First and second entries: Second diagram type = 0 0, for co‐polar H‐H diagram ("HH" in Atoll).• Third entry: The azimuth angle of the elevation diagram.

Figure 9.3: 2D Microwave Antenna Pattern Format

Pattern Co-polar H-V Diagram Co-polar H-H DiagramDiscriptor 1Pattern

Discriptor 2

Pattern Cross-polar H-V Diagram Cross-polar H-H DiagramDiscriptor 3Pattern

Discriptor 4

Pattern Co-polar V-V Diagram Co-polar V-H DiagramDiscriptor 5Pattern

Discriptor 6

Pattern Cross-polar V-V Diagram Cross-polar V-H DiagramDiscriptor 7Pattern

Discriptor 8

4 0 1 0 360 0 0 1 0.5 ... 0 0 0 360 0 0 1 0.5 ...

1 1 0 360 0 0 1 0.5 ... 1 0 0 360 0 0 1 0.5 ...

4 0 1 0 360 0 0 1 0.5 ... 0 0 0 360 0 0 1 0.5 ...

1 1 0 360 0 0 1 0.5 ... 1 0 0 360 0 0 1 0.5 ...

91


• Fourth entry: The number of angle‐attenuation pairs in the second co‐polar diagram. For example, 360.

• Co‐polar H‐H Diagram: Co‐polar H‐H diagram (the first and second entries in the preceding descriptor are 0 0). The format is space‐separated angle attenuation pairs. For example, 0 0 1 0.5....

• Pattern Descriptor 3: Space‐separated list of parameters.• First and second entries: Third diagram type = 1 1, for cross‐polar H‐V diagram ("EL VH" in Atoll).• Third entry: The elevation angle of the azimuth diagram.• Fourth entry: The number of angle‐attenuation pairs in the third co‐polar diagram. For example, 360.

• Cross‐polar H‐V Diagram: Cross‐polar H‐V diagram (the second and third entries in the preceding descriptor are 0 1).The format is space‐separated angle attenuation pairs. For example, 0 0 1 0.5....

• Pattern Descriptor 4: Space‐separated list of parameters.• First and second entries: Fourth diagram type = 1 0, for cross‐polar H‐H diagram ("VH" in Atoll).• Third entry: The azimuth angle of the elevation diagram.• Fourth entry: The number of angle‐attenuation pairs in the fourth co‐polar diagram. For example, 360.

• Cross‐polar H‐H Diagram: Cross‐polar H‐H diagram (the first and second entries in the preceding descriptor are 0 0).The format is space‐separated angle attenuation pairs. For example, 0 0 1 0.5....

• Pattern Descriptor 5: Space‐separated list of parameters.• First entry: The number of V_polarisation cross‐polar diagrams. For example, 4.• Second and third entries: First diagram type = 0 1, for co‐polar V‐V diagram ("EL VV" in Atoll).• Fourth entry: The elevation angle of the azimuth diagram.• Fifth entry: The number of angle‐attenuation pairs in the first cross‐polar diagram. For example, 360.

• Co‐polar V‐V Diagram: Co‐polar V‐V diagram (the first and second entries in the preceding descriptor are 1 1). The format is space‐separated angle attenuation pairs. For example, 0 0 1 0.5....

• Pattern Descriptor 6: Space‐separated list of parameters.• First and second entries: Second diagram type = 0 0, for co‐polar V‐H diagram ("VV" in Atoll).• Third entry: The azimuth angle of the elevation diagram.• Fourth entry: The number of angle‐attenuation pairs in the second cross‐polar diagram. For example, 360.

• Co‐polar V‐H Diagram: Co‐polar V‐H diagram (the first and second entries in the preceding descriptor are 1 0). The format is space‐separated angle attenuation pairs. For example, 0 0 1 0.5....

• Pattern Descriptor 7: Space‐separated list of parameters.• First and second entries: Third diagram type = 1 1, for cross‐polar V‐V diagram ("EL HV" in Atoll).• Third entry: The elevation angle of the azimuth diagram.• Fourth entry: The number of angle‐attenuation pairs in the third cross‐polar diagram. For example, 360.

• Cross‐polar V‐V Diagram: Cross‐polar V‐V diagram (the first and second entries in the preceding descriptor are 1 1).The format is space‐separated angle attenuation pairs. For example, 0 0 1 0.5....

• Pattern Descriptor 8: Space‐separated list of parameters.• First and second entries: Fourth diagram type = 1 0, for cross‐polar V‐H diagram ("HV" in Atoll).• Third entry: The azimuth angle of the elevation diagram.• Fourth entry: The number of angle‐attenuation pairs in the fourth cross‐polar diagram. For example, 360.

• Cross‐polar V‐H Diagram: Cross‐polar V‐H diagram (the first and second entries in the preceding descriptor are 1 0).The format is space‐separated angle attenuation pairs. For example, 0 0 1 0.5....

9.5 Path Loss Matrix File FormatWhen path loss matrices are stored externally, i.e., outside the ATL file, the path loss matrices folder contains a ‘pathloss.dbf’file containing the calculation parameters of the transmitters and one LOS (path loss results) file per calculated transmitter.The path loss matrices folder also contains a LowRes folder with another pathloss.dbf file and one LOS (path loss results) fileper transmitter that has an extended path loss matrix.

The formats of the pathloss.dbf and LOS files are described here.

9.5.1 Pathloss.dbf File FormatThe pathloss.dbf file has a standard DBF (dBase III) format. The file can be opened in Microsoft Access, but it should not bemodified without consulting the Forsk customer support.

For general information, the format of DBF files in any Xbase language is as follows:

Notations used in the following tables: FS = FlagShip; D3 = dBaseIII+; Fb = FoxBase; D4 =dBaseIV; Fp = FoxPro; D5 = dBaseV; CL = Clipper

92


DBF Structure

DBF Header

The DBF header size is variable and depends on the field count.

Field descriptor array in the DBF header (32 bytes for each field):

Byte Description Remarks

0...n DBF header (see next part for size, byte 8)

n+11st record of fixed length (see next parts); 2nd record (see next part for size, byte10) …; last

recordIf .dbf is not empty

last optional: 0x1a (eof byte)

Byte Size Contents Description Applies to

00 1 0x03 plain .dbf FS, D3, D4, D5, Fb, Fp, CL

0x04 plain .dbf D4, D5 (FS)

0x05 plain .dbf D5, Fp (FS)

0x43 with .dbv memo var size FS

0xB3 with .dbv and .dbt memo FS

0x83 with .dbt memo FS, D3, D4, D5, Fb, Fp, CL

0x8B with .dbt memo in D4 format D4, D5

0x8E with SQL table D4, D5

0xF5 with .fmp memo Fp

01 3 YYMMDD Last update digits All

04 4 ulong Number of records in file All

08 2 ushort Header size in bytes All

10 2 ushort Record size in bytes All

12 2 0,0 Reserved All

14 1 0x01 Begin transaction D4, D5

0x00 End Transaction D4, D5

0x00 ignored FS, D3, Fb, Fp, CL

15 1 0x01 Encrypted D4, D5

0x00 normal visible All

16 12 0 (1) multi‐user environment use D4,D5

28 1 0x01 production index exists Fp, D4, D5

0x00 index upon demand All

29 1 n language driver ID D4, D5

0x01 codepage437 DOS USA Fp

0x02 codepage850 DOS Multi ling Fp

0x03 codepage1251 Windows ANSI Fp

0xC8 codepage1250 Windows EE Fp


30 2 0,0 reserved All

32 n*32 Field Descriptor (see next paragraph) all

+1 1 0x0D Header Record Terminator all


0 11 ASCI field name, 0x00 termin all

11 1 ASCI field type (see next paragraph) all

12 4 n,n,n,n Fld address in memory D3

93


Field type and size in the DBF header, field descriptor (1 byte):

Each DBF record (fixed length):

n,n,0,0 offset from record begin Fp

0,0,0,0 ignored FS, D4, D5, Fb, CL

16 1 byte Field length, bin (see next paragraph) all \ FS,CL: for C field type

17 1 byte decimal count, bin all / both used for fld lng

18 2 0,0 reserved all

20 1 byte Work area ID D4, D5

0x00 unused FS, D3, Fb, Fp, CL

21 2 n,n multi‐user dBase D3, D4, D5

0,0 ignored FS, Fb, Fp, CL

23 1 0x01 Set Fields D3, D4, D5

0x00 ignored FS, Fb, Fp, CL

24 7 0...0 reserved all

31 1 0x01 Field is in .mdx index D4, D5


Size Type Description/Storage Applies to

C 1...n CharASCII (OEM code page chars)rest= space, not \0 term.

all

n = 1...64kb (using deci count) FS

n = 1...32kb (using deci count) Fp, CL

n = 1...254 all

D 8 Date 8 ASCII digits (0...9) in the YYYYMMDD format all

F 1...n NumericASCII digits (‐.0123456789)variable pos. of float.point

n = 1...20FS, D4, D5, Fp

N 1...n NumericASCII digits (‐.0123456789)fix posit/no float.point

all

n = 1...20 FS, Fp, CL

n = 1...18 D3, D4, D5, Fb

L 1 Logical ASCII chars (YyNnTtFf space) FS, D3, Fb, Fp, CL

ASCII chars (YyNnTtFf?) D4, D5 (FS)

M 10 Memo10 digits repres. the start block posit. in .dbt file, or 10

spaces if no entry in memoall

V 10 Variable

Variable, bin/asc data in .dbv4bytes bin= start pos in memo

4bytes bin= block size1byte = subtype

1byte = reserved (0x1a)10 spaces if no entry in .dbv

FS

P 10 Picturebinary data in .ftpstructure like M

Fp

B 10 Binarybinary data in .dbtstructure like M

D5

G 10 GeneralOLE objects

structure like MD5, Fp

2 2 short int binary int max +/‐ 32767 FS

4 4 long int binary int max +/‐ 2147483647 FS

8 8 double binary signed double IEEE FS


94


9.5.2 Pathloss.dbf File ContentsThe DBF file provides information that is needed to check validity of each path loss matrix.

Byte Size Description Applies to

0 1 deleted flag "*" or not deleted " " All

1…n 1…x‐times contents of fields, fixed length, unterminated.

For n, see (2) byte 10…11All


TX_NAME Text Name of the transmitter

FILE_NAME Text Name (and optionally, path) of .los file

MODEL_NAME Text Name of propagation model used to calculate path loss

MODEL_SIG Text

Signature (identity number) of model used in calculations. You can check it in the propagation model properties (General tab).

The Model_SIG is used for the purpose of validity. A unique Model_SIG is assigned to each propagation model. When model parameters are modified, the associated model ID changes. This enables Atoll to detect path loss matrix invalidity. In the same way, two

identical propagation models in different projects do not have the same model IDa.

ULXMAP Float X‐coordinate of the top‐left corner of the path loss matrix upper‐left pixel

ULYMAP Float Y‐coordinate of the top‐left corner of the path loss matrix upper‐left pixel

RESOLUTION Float Resolution of path loss matrix in metre

NROWS Float Number of rows in path loss matrix

NCOLS Float Number of columns in path loss matrix

FREQUENCY Float Frequency band

TILT Float Transmitter antenna mechanical tilt

AZIMUTH Float Transmitter antenna azimuth

TX_HEIGHT Float Transmitter height in metre

TX_POSX Float X‐coordinate of the transmitter

TX_POSY Float Y‐coordinate of the transmitter

ALTITUDE Float Ground height above sea level at the transmitter in metre

RX_HEIGHT Float Receiver height in metre

ANTENNA_SI FloatLogical number referring to antenna pattern. Antennas with the same pattern will have

the same number.

MAX_LOS FloatMaximum path loss stated in 1/16 dB. This information is used, when no calculation

radius is set, to check the matrix validity.

CAREA_XMIN Float Lowest x‐coordinate of centre pixel located on the calculation radiusb

CAREA_XMAX Float Highest x‐coordinate of centre pixel located on the calculation radius

CAREA_YMIN Float Lowest y‐coordinate of centre pixel located on the calculation radius

CAREA_YMAX Float Highest y‐coordinate of centre pixel located on the calculation radius

WAREA_XMIN Float Lowest x‐coordinate of centre pixel located in the computation zonec

WAREA_XMAX Float Highest x‐coordinate of centre pixel located in the computation zone

WAREA_YMIN Float Lowest y‐coordinate of centre pixel located in the computation zone

WAREA_YMAX Float Highest y‐coordinate of centre pixel located in the computation zone

LOCKED BooleanLocking status

0: path loss matrix is not locked1: path loss matrix is locked.

INC_ANT Boolean

Atoll indicates if losses due to the antenna pattern are taken into account in the path loss matrix.

0: antenna losses not taken into account1: antenna losses included

95


9.5.3 LOS File FormatThe LOS (path loss results) files are binary files with a standard row‐column structure. Data are stored starting from thesouthwest to the northeast corner of the area. The file contains 16‐bit signed integer values in the range [‐32768; +32767]with a 1/16 dB precision. "No data" values are represented by +32767.

9.6 Path Loss Tuning File FormatAtoll can tune path losses calculated by propagation models using CW measurements or drive test Data. Path losses are tunedby merging measurement data with propagation results on pixels corresponding to the measurement points and the pixels inthe vicinity. Path losses surrounding the measurement points are smoothed for homogeneity.

Measuremment paths that are used for path loss tuning are stored as a catalogue in a folder containing a pathloss.dbf file andone PTS (path loss tuning) file per transmitter. A tuning file can contain several measurement paths.

For more information on the path loss tuning algorithm, see the Technical Reference Guide.

9.6.1 Pathloss.dbf File FormatSee "Pathloss.dbf File Format" on page 92.

9.6.2 Pathloss.dbf File ContentsThe DBF file provides information about the measured transmitters involved in the tuning.

9.6.3 PTS File FormatThe PTS (path loss tuning) files contain a header and the list of measurement points.

Header:

• 4 bytes: version• 4 bytes: flag (can be used to manage flags like active flag)• 50 bytes: GUID• 4 bytes: number of points• 255 bytes: original measurement name (with prefix "Num" for drive test data and "CW" for CW measurements)• 256 bytes: comments• 4 bytes: X_RADIUS• 4 bytes: Y_RADIUS• 4 bytes: gain = measurement gain ‐ losses• 4 bytes: global error• 4 bytes: rx height• 4 bytes: frequency• 8 bytes: tx Position

List of measurement points:

• 4 bytes: X

a. In order to benefit from the calculation sharing feature, users must retrieve the propagation models from the samecentral database. This can be done using the Open from database command for a new document or the Refreshcommand for an existing one. Otherwise, Atoll generates different model_ID (even if same parameters are applied onthe same kind of model) and calculation sharing become unavailable due to inconsistency.

b. These coordinates enable Atoll to determine the area of calculation for each transmitter.c. These coordinates enable Atoll to determine the rectangle including the computation zone.



FILE_NAME Text Name (and optionally, path) of .pts file

AREA_XMIN Float Not used

AREA_XMAX Float Not used

AREA_YMIN Float Not used

AREA_YMAX Float Not used

96


• 4 bytes: Y• 4 bytes: measurement value• 4 bytes: incidence angle.

9.7 Interference Matrix File FormatsInterference matrices are used by GSM, LTE, and WiMAX AFPs (automatic frequency planning tools). Interference matricescan be imported and exported using the following formats:

• GSM: CLC, IM0, IM1, IM2• LTE and WiMAX: IM2, TXT, CSV

Interference matrix files must contain interference probability values between 0 and 1, and not in precentage (between 0 and100%). When interference matrix files are imported, Atoll does not check their validity and imports interference probabilityvalues for loaded transmitters only.

In the following format descriptions and samples, lines starting with the "#" are considered as comments.

9.7.1 CLC Format (One Value per Line)The CLC format uses wo ASCII text files: a CLC file and a DCT file. Interference matrices are imported by selecting the CLC fileto import. Atoll looks for the associated DCT file in the same directory and uses it to decode transmitter identifiers. If no DCTfile is available, Atoll assumes that the transmitter identifiers are the transmitter names, and the columns 1 and 2 of the CLCfile must contain the names of the interfered and interfering transmitters instead of their identification numbers.

9.7.1.1 CLC File Format

The CLC file consists of two parts. The first part is a header used for format identification. It must start with and contain thefollowing lines:

The second part details interference histogram of each interfered subcell‐interfering subcell pair. The lines after the headerare considered as comments if they start with "#". If not, they must have the following format:

The 5 tab‐separated columns are defined in the table below:

In GSM interference matrices:

• The interferer TRX type is not specified and is always considered to be BCCH.Subcells have different powers defined as offsets with respect to the BCCH. Forsubcells other than the BCCH, if the power offset of a subcell is X dB, then itsinterference histogram will be shifted by X dB with respect to the BCCH interferencehistogram.

• If no power offset is defined on the interfered TRX type, it is possible to set "All".• For each interfered subcell‐interferer subcell pair, Atoll saves probabilities for

several C/I values (6 to 24 values), including five fixed ones: –9, 1, 8, 14, and 22 dB.Between two fixed C/I value, there can be up to three additional values (this numberdepends on the probability variation between the fixed values). The C/I values have0.5 dB accuracy and probability values are calculated and stored with an accuracy of0.002 for probabilities between 1 and 0.05, and with an accuracy of 0.0001 forprobabilities lower than 0.05.

# Calculation Results Data File.

# Version 1.1, Tab separated format. Commented lines start with #.

<Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>

Column Name Description

Column1 Interfered transmitterIdentification number of the interfered transmitter. If the column is empty,

its value is identical to the one of the line above.

Column2 Interfering transmitterIdentification number of the interferer transmitter. If the column is null, its

value is identical to the one of the line above.

Column3 Interfered TRX typeInterfered subcell. If the column is null, its value is identical to the one of the line above. In order to save storage, all subcells with no power offset are not

duplicated (e.g. BCCH, TCH).

97


The columns 1, 2, and 3 must be defined only in the first line of each histogram.

Sample

9.7.1.2 DCT File Format

The .dct file is divided into two parts. The first part is a header used for format identification. It must start with and containthe following lines:

Column4 C/I threshold C/I value. This column cannot be null.

Column5 Probability C/I > ThresholdProbability to have C/I the value specified in column 4 (C/I threshold). This

field must not be empty.



# Remark: C/I results do not incorporate power offset values.

# Fields are:

##------------#------------#------------#-----------#------------------#

#| Interfered | Interfering| Interfered | C/I | Probability |

#| Transmitter| Transmitter| Trx type | Threshold | C/I >= Threshold |

##------------#------------#------------#-----------#------------------#

#

# Warning, The parameter settings of this header can be wrong if

# the "export" is performed following an "import". They

# are correct when the "export" follows a "calculate".

#

# Service Zone Type is "Best signal level of the highest priority HCS layer".

# Margin is 5.

# Cell edge coverage probability 75%.

# Traffic spreading was Uniform

##---------------------------------------------------------------------#

1 2 TCH_INNER 8 1

9 0.944

10 0.904

11 0.892

14 0.844

15 0.832

16 0.812

17 0.752

22 0.316

25 0.292

1 2 BCCH,TCHa 8 1

a. If the TCH and BCCH histograms are the same, they are not repeated. A single record indicates that the histogramsbelong to TCH and BCCH both.

9 0.944

10 .904

13 0.872

14 0.84

17 0.772


# Calculation Results Dictionary File.

98


The second part provides information about transmitters taken into account in AFP. The lines after the header are consideredas comments if they start with "#". If not, they must have the following format:

The last four columns describe the interference matrix scope. One transmitter per line is described separated with a tabcharacter.

Sample

9.7.2 IM0 Format (One Histogram per Line)This file contains one histogram per line for each interfered/interfering subcell pair. The histogram is a list of C/I values withassociated probabilities.

The .im0 file consists of two parts. The first part is a header used for format identification. It must start with and contain thefollowing lines:


<Column1><tab><Column2><newline>

Column Name Type Description

Column1 Transmitter name Text Name of the transmitter

Column2 Transmitter Identifier Integer Identification number of the transmitter

Column3 BCCH during calculation Integer BCCH used in calculations

Column4 BSIC during calculation Integer BSIC used in calculations

Column5 % of vic’ coverage Float Percentage of overlap of the victim service area

Column6 % of int’ coverage Float Percentage of overlap of the interferer service area

# Calculation Results Dictionary File.


# Fields are:

##-----------#-----------#-----------#-----------#---------#---------#

#|Transmitter|Transmitter|BCCH during|BSIC during|% of vic'|% of int'|

#|Name |Identifier |calculation|calculation|coverage |coverage |

##-----------#-----------#-----------#-----------#---------#---------#

#




#

# Service Zone Type is "Best signal level per HCS layer".

# Margin is 5.

# Cell edge coverage probability is 75%.

# Traffic spreading was Uniform (percentage of interfered area)

##---------------------------#

Site0_0 1 -1 -1 100 100

Site0_1 2 -1 -1 100 100

Site0_2 3 -1 -1 100 100

Site1_0 4 -1 -1 100 100

Site1_1 5 -1 -1 100 100

Site1_2 6 -1 -1 100 100

Site2_0 7 -1 -1 100 100

Site2_1 8 -1 -1 100 100


99


The second part details interference histogram of each interfered subcell‐interferer subcell pair. The lines after the headerare considered as comments if they start with "#". If not, they must have the following format:


Sample

9.7.3 IM1 Format (One Value per Line, TX Name Repeated)This file contains one C/I threshold and probability pair value per line for each interfered/interfering subcell pair. Thehistogram is a list of C/I values with associated probabilities.


<Column1><tab><Column2><tab><Column3><tab><Column4><newline>


Column1 Interfered transmitter Name of the interfered transmitter.

Column2 Interfering transmitter Name of the interferer transmitter.

Column3 Interfered TRX typeInterfered subcell. In order to save storage, all subcells with no power offset

are not duplicated (e.g. BCCH, TCH).

Column4 C/I probability C/I value and the probability associated to this value separated by a space

character. This entry cannot be null.




# Fields are:

#------------------------------------------------------------------------

#Transmitter Interferer TRX type {C/I Probability} values

#------------------------------------------------------------------------

#




#


# Margin is 5.



##---------------------------------------------------------------------#

#

Site0_2 Site0_1 BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.964 -1 0.936

0 0.932 1 0.924 4 0.896 7 0.864 8 0.848

9 0.832 10 0.824 11 0.804 14 0.712 17 0.66

Site0_2 Site0_3 BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.972 -1 0.948

0 0.94 1 0.928 4 0.896 7 0.856 8 0.84

11 0.772 13 0.688 14 0.636 15 0.608 18 0.556

Site0_3 Site0_1 BCCH,TCH-10 1 -9 0.996 -6 0.98 -3 0.948 0 0.932

1 0.924 4 0.892 7 0.852 8 0.832 9 0.816

10 0.784 11 0.764 14 0.644 15 0.616 18 0.564

Site0_3 Site0_2 BCCH,TCH-9 1 -6 0.972 -3 0.964 -2 0.96 0 0.94

1 0.932 4 0.904 7 0.876 8 0.86 9 0.844

11 0.804 13 0.744 14 0.716 15 0.692 18 0.644

100


The .im1 file consists of two parts. The first part is a header used for format identification. It must start with and contain thefollowing lines:

The second part details interference histogram of each interfered subcell‐interferer subcell pair. The lines after the headerare considered as comments if they start with "#". If not, they must have the following format:


Sample



<Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>


Column1 Interfered transmitter Name of the interfered transmitter.

Column2 Interfering transmitter Name of the interferer transmitter.

Column3 Interfered TRX typeInterfered subcell. In order to save storage, all subcells with no power offset

are not duplicated (e.g. BCCH, TCH).

Column4 C/I threshold C/I value. This column cannot be null.

Column5 Probability C/I > ThresholdProbability to have C/I the value specified in column 4 (C/I threshold). This

field must not be empty.




# Fields are:

#------------------------------------------------------------------------

#Transmitter Interferer TRX type C/I Probability

#------------------------------------------------------------------------

#




#


# Margin is 5.



##---------------------------------------------------------------------#

Site0_2 Site0_1 BCCH,TCH -10 1

Site0_2 Site0_1 BCCH,TCH -9 0.996




Site0_2 Site0_1 BCCH,TCH 0 0.932







...

101


9.7.4 IM2 Format (Co‐ and Adjacent‐channel Probabilities)IM2 files contain co‐channel and adjacent‐channel interference probabilities for each interfered transmitter – interferingtransmitter pair. In GSM, there is only one set of values for all the subcells of the interfered transmitter. Each line must havethe following format:

Where the separator (<SEP>) can either be a tab or a semicolon.

The four columns are defined in the table below:

Sample

The columns in the sample above are separated with a tab. These columns can also be separated with a semilcolon:

9.8 "Per Transmitter" Prediction File FormatWhen a coverage prediction is calculated by value intervals it is stored externally, i.e., outside the ATL file. A corresponding’<doc_name>\{<GUID>}’ folder is actually created where the ATL document is located, as soon as the latter is saved.

<Column1><SEP><Column2><SEP><Column3><SEP><Column4><newline>


Column1 Interfered transmitter Name of the interfered transmitter

Column2 Interfering transmitter Name of the interferer transmitter

Column3 Co‐channel probability Co‐channel interference probability

Column4 Adjacent‐channel probability Adjacent channel interference probability




# Fields are:

#------------------------------------------------------------------------

#Transmitter Interferer Co-channel Adjacent channel

#------------------------------------------------------------------------

#




#


# Margin is 5.



##---------------------------------------------------------------------#

Site0_2 Site0_1 0.226667 0.024

Site0_2 Site0_3 0.27 0.024

Site0_3 Site0_1 0.276 0.02

Site0_3 Site0_2 0.226 0.028

Site0_2;Site0_1;0.226667;0.024

Site0_2;Site0_3;0.27;0.024

Site0_3;Site0_1;0.276;0.02

Site0_3;Site0_2;0.226;0.028

102


The calculation of the coverage prediction is either global or "per transmitter".

• When the calculation is global, the results are stored in two files for the entire prediction: one HDR file and one BILfile (both identified by the prediction name).

• When a calculation is "per transmitter", one HDR file and one BIL file are created for each transmitter in the prediction(both identified by the transmitter’s name). In some "per transmitter" predictions, an additional DBF file is created forthe entire prediction (identified by the prediction name). The DBF file contains information on each transmitter and a

pointer to each transmitter’s specific HDR and BIL files.

In LTE, when a Cell Identifier Collision Zones (DL) prediction is calculated by value intervals with the display type set"No. of interferers per cell", the HDR file and the BIL file are created for each cell in the prediction (both identified bythe cell’s name).

The format and the content of the DBF file is described here.

9.8.1 <per_transmitter_prediction>.dbf File FormatThe format of ‘<per_transmitter_prediction>.dbf’ files is identical to the format described in "Pathloss.dbf File Format" onpage 92.

9.8.2 <per_transmitter_prediction>.dbf File ContentsThe ‘<per_transmitter_prediction>.dbf’ files generated in specific ’{<GUID>}’ folders provide information that is needed tocheck the validity of each "per transmitter" prediction> calculated by value intervals.

In both cases, an XML file describing the prediction is also created in the corresponding’<doc_name>\{<GUID>}’ folder.



FILE_NAME Text Name of the transmitter’s BIL result file

RESOLUTION Float Resolution of the calculation, same as ’xdim’ and ’ydim’ in the HDR file

AREA_XMIN Float Same as ’ulxmap’ in the HDR file

AREA_XMAX Float Same as ’ulxmap’ + ’xdim’ * ’ncols’ in the HDR file

AREA_YMIN Float Same as ’ulymap’ in the HDR file

AREA_YMAX Float Same as ’ulymap’ + ’ydim’ * ’nrows’ in the HDR file

NBITS Float Same as ’nbits’ in the HDR file

NBANDS Float Same as ’nbands’ in the HDR file

BYTE_ORDER Float Same as ’byteorder’ in the HDR file

BAND_ROW_BYTES Float Same as ’bandrowbytes’ in the HDR file

TOTAL_ROW_BYTES Float Same as ’totalrowbytes’ in the HDR file

SKIP_BYTES Float Same as ’skipbytes’ in the HDR file

DATA_TYPE Text Same as ’datatype’ in the HDR file

NO_DATA_VALUE Same as ’nodatavalue’ in the HDR file

103


104

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 10: Administration and Usage Recommendations

10 Administration and Usage RecommendationsThis chapter lists various technical recommendations for optimising your work with Atoll.

10.1 Geographic Data

Location of the Geographic Data

• In multi‐user environments, it is recommended to place all the geographic data on a file server accessible to all theusers. This approach avoids the need to replicate the geographic data on all the workstations.

• Geographic data should either be located on each server or accessible through a fast network connection, e.g., 1 Gbps.• You can restrict access to the geographic data locations by assigning read/write access rights to administrators and

read‐only rights to end‐users.

Link or Embed

• Only embed geographic data in ATL files if you wish to make a portable document. In all other cases, it isrecommended to link geographic data files to the Atoll documents.

• It is recommended to set the paths to linked geographic data files using the Universal Naming Convention (UNC).

Following the UNC, an absolute path, such as "C:\Program Files\Forsk\Geo Data\...", is represented as"\\Computer\C\Program Files\Forsk\Geo Data\...", where "Computer" is the computer name, and "C" is the sharename of disk C.

Example:

If you define paths to geographic data files using the UNC, Atoll will be able to keep track of the linked files even if theAtoll document is moved to another computer.

Size of Tiles

• Some network planning tools require geographic data to be available in small tiles in order to work more efficiently.For a country‐wide project, this can lead to hundreds of files describing the geographic data. Atoll is designed tooptimise memory consumption, which enables it to perform efficiently with regional tiles (1 tile/file per region). InAtoll, Merging small tiles to build a regional tile can improve performance greatly.

• To note as well:

• Recommended file size: 100 to 200 MB• Erdas Imagine Pyramids files can be bigger.• ECW files can be of any size (no limitations).

Recommended Formats

• In order to improve performance, it is recommended to use uncompressed DTM and clutter files, for example, BILfiles. Using compressed geographic data files, for example, compressed TIF or Erdas Imagine, can cause performancereduction due to decompression of these files in real time. If you are using compressed geographic data files, it isstrongly recommended to:

• Either, hide the status bar that displays geographic data information in real time. You can hide the status bar fromthe View menu.

• Or, disable the display of some of the information contained in the status bar, such as altitude, clutter class, andclutter height using an option in the Atoll.ini file, see "Hiding Information Displayed in the Status Bar" on page 160.

• The following table shows the recommended file formats for different geographic data:

Absolute Path C:\Program Files\Forsk\Geo Data\...

Relative Path \Program Files\Forsk\Geo Data\...

UNC Path \\Computer\C\Program Files\Forsk\Geo Data\...

Geographic data type Recommended file format

Scanned maps ECW

Vectors SHP

105

Atoll 3.2.1 Administrator ManualChapter 10: Administration and Usage Recommendations © Forsk 2014

10.2 Path Loss Matrices

Shared Path Loss Matrices

• Shared path loss matrices should be accessible through a fast network connection, e.g., 1 Gbps. These results areaccessed by Atoll during calculations, and should be available to the users through a fast network connection, i.e.,30 Mbps at least per user.

• You can restrict access to the shared path loss matrices folder by assigning read/write access rights to administratorsand read‐only rights to end‐users.

Private Path Loss Matrices

• Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices areinvalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matricesand uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whosecorresponding shared path loss matrices are valid. This can be useful for disk space management. For moreinformation, see "Synchronising Private and Shared Path Loss Matrices" on page 155.

Link or Embed

• Only embed path loss matrices in ATL files if you wish to make a portable document. In all other cases, it isrecommended to link path loss matrices to the Atoll documents.

Externalising path loss matrices to shared or private path loss folders will keep the ATL file size reasonable, which willresult in less fragmentation. Externalising path loss matrices does not reduce the performance of display andcalculations in Atoll.

• It is recommended to set the paths to the private and shared path loss matrices folders using the Universal NamingConvention (UNC).

Following the UNC, an absolute path, such as "C:\Program Files\Forsk\PathLosses\...", is represented as"\\Computer\C\Program Files\Forsk\PathLosses\...", where "Computer" is the computer name, and "C" is the sharename of disk C.

Example:

If you define paths to the private and shared path loss matrices folders using the UNC, Atoll will be able to keep trackof the linked files even if the Atoll document is moved to another computer.

Calculating Path Loss Matrices in Multi‐RAT Documents

• When the path loss matrices in multi‐RAT documents using the RunPathloss API function, the path loss matrices ofeach technology are calculated simultaneously using the same number of threads. For example, if 4 threads are usedto calculate path loss matrices, and there are 3 technologies (GSM, UMTS, and LTE), a total of 12 threads will be usedto calculate the path loss matrices at the same time. This can lead to the following problems:

• Insufficient CPU resources• Insufficient memory• Insufficient licences if external propagation models are used.

• To avoid these problems when using the RunPathloss API function to calculate path loss matrices in multi‐RATdocuments, use the following work‐arounds:

• Use the Distributed Calculation Server, even locally.• In your script or macro, deactivate the transmitters of the technologies for which you do not want to calculate the

path loss matrices and reactivate them afterwards. Repeat it for all technologies.• Lower the number of threads using the NumberOfThreadsPathloss option in RemoteCalculation section in

Atoll.ini. For example, you can set the option to 2 to use a maximum of 6 threads (3*2) during path loss calculationusing the RunPathloss function.

Absolute Path C:\Program Files\Forsk\PathLosses\...

Relative Path \Program Files\Forsk\PathLosses\...

UNC Path \\Computer\C\Program Files\Forsk\PathLosses\...

• Resource saturation during the calculation of path loss matrices for multi‐RATdocuments only occurs when using the RunPathloss API function in a macro or script.When calculating path loss matrices for a multi‐RAT document using Atoll, this doesnot occur.

106


• Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices areinvalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matricesand uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whosecorresponding shared path loss matrices are valid. This can be useful for disk space management. For moreinformation, see "Synchronising Private and Shared Path Loss Matrices" on page 155.

10.3 Atoll Documents

General

• It is recommended to define a rule for making backups of your Atoll documents at regular intervals.• Do not skip a major Atoll version. For example, if you are currently using Atoll 2.8.x, you should first upgrade the

document to Atoll 3.1.x before upgrading to Atoll 3.2.x.

Upgrading your document will be simpler if you do not skip a major version. If you skip or have skipped anintermediate major version, you should upgrade your document twice in order to make it compatible with the newversion.

10.4 Databases

General

• In order to use Atoll with Oracle, you must create Oracle users and schema with names in uppercase.• Create backups of the database before upgrading.• It is recommended to define a rule for making backups of the database at regular intervals.• Do not skip a major Atoll version. For example, if you are currently using Atoll 2.7.x, you should first upgrade the

database to Atoll 2.8.x before upgrading to Atoll 3.1.x.

Upgrading your database will be simpler if you do not skip a major version. If you skip or have skipped an intermediatemajor version, you must upgrade your database twice in order to make it compatible with the new version.

Tables and Fields

• Table and field names are case sensitive.• Table and field names should be not more than 20 characters long.

Oracle databases allow a maximum length of 30 characters for field and table names. However, for use in Atoll, youmust not create tables and fields with names longer than 20 characters. This is because Atoll adds some characters tothe table and field names for certain operations: creating associated triggers, creating project databases, etc. Limitingthe length of table and field names to 20 characters will help avoid database connection and consistency problems.

• Table and field names should only use alphanumeric characters (A‐Z, a‐z, 0‐9) and underscores (_).• Table and field names must not start with a numeric character (0‐9).• Table and field names must not contain an SQL or RDBMS‐specific keyword, such as ORDER, DATE, etc.• Table and field names must not contain spaces or special characters, such as periods (.), exclamation marks (!), colons

(:), semi‐colons (;), interrogation marks (?), parentheses (()), brackets ({}), square brackets ([]), etc.• Boolean fields, system or user‐defined, should always have default values assigned.• The CustomFields table enables you to define default values, choice lists, and read/write access for any field in any

table in Atoll, including user‐defined fields that you add to the Atoll tables. The values defined in this table havepriority over the internal predefined default values. If you define floating point default values, make sure that all theusers have the same decimal separator.

• If you wish to add custom fields in the Atoll document, you should first add the field in the database, and then updateyour Atoll document from the database.

• When setting up your database for the first time, try to anticipate user requirements in terms of custom fields in Atolltables. Some requirements of the different user groups can be satisfied if a few general‐purpose user‐defined fieldsare added in Atoll tables when setting up the database.

For example, if you add three user‐defined fields (one of type integer, float, and text (limited size)) to the Sites andTransmitters tables, users will be able to use these for sorting, filtering, grouping, or other purposes. This approachcan help the database function a long time before users require the addition of other custom fields.

• To improve performance, if your projects allow it, reduce the size of the fields corresponding to the sites andtransmitters’ names.

• To improve performance, unless absolutely necessary, do not add user‐defined fields of Text type. Rather, usenumeric field types, which allow sorting and other functions. If you must add Text fields, allocate them the appropriatesize that would suffice. For example, a 255‐character long Text type field would, for the most part, occupy disk spacefor no purpose.

• To improve performance, you should avoid adding custom fields to the neighbour management tables.

107


10.5 Calculation Server

Computation Server Stability and Resource Management

In certain conditions, as described below, Atoll users might experience a decrease in server performance and stability in amulti‐user Citrix environment. The principal difference observed might be the inability to run multiple Atoll sessions on theserver without getting error messages, general application failures, or server crashes. Such problems can occur when thenumber of Atoll sessions on the server, carrying out calculations, increases to more than four.

Causes of Instability and Loss of Performance

This general instability and low performance of the servers is due to:

• Insufficient memory resources: globally and per process (Atoll session)• Insufficient CPU resources• Network congestion

Atoll can process four simultaneous path loss matrices calculations, which means high CPU and RAM resource consumption,and as path loss calculations share the amount of memory allocated to the Atoll session, the total memory requirement canexceed the Microsoft Windows’ (32‐bit editions) limit of 2 GB per process. This is especially the case with large Atolldocuments and propagation models that require considerable memory.

Troubleshooting and Solution

As the cause of this problem is resource saturation on the server, resource consumption should be controlled in order to avoidmemory and CPU overloading as follows:

• To reduce the impact of a large number of simultaneous path loss calculations, a Distributed Calculation Server shouldbe set up. Using the Distributed Calculation Server, path loss calculations can be performed outside Atoll. Using theDistribution Calculation Server has the following advantages:• Path loss calculations are limited to four parallel instances regardless of the number of Atoll sessions running on

the server. This notably improves the memory and CPU consumption.• A queuing system, integrated in the Distributed Calculation Server, manages the calculation requests from

different Atoll sessions.• A failover mechanism automatically switches and hands over the path loss calculations back to Atoll in case a

problem occurs.• Path loss calculations are carried out by a separate process (AtollSvr), which has its own memory allocation apart

from Atoll, i.e., the amount of memory needed for calculations does not impacts the Atoll memory allocation.

This set up can introduce considerable improvements in both the number of Atoll sessions per server and the calculations. Aserver with four processors (eight threads with hyper‐threading) can accommodate four simultaneous path loss calculationsand use the other four threads for Atoll sessions. Atoll’s interface will also be more efficient and the overall processing timefor various tasks will be improved.

Apart from the above setup, you can also make some other system improvements:

• To avoid error messages caused by requesting a large number of files over the network, the following MicrosoftWindows registry parameter can be modified in order to dedicate more resources to network read/write operations:

IRQSTACKSIZE should be set to 30 instead of 11, for example.

• To avoid ‘out of memory’ problems, the Pagefile size should be increased so that the server does not run out of globalmemory when supporting more than 10 Atoll sessions simultaneously. This is different from the 2 GB per processlimit. Virtual memory can be increased from 8 GB to 16 GB, for example.

• For 32‐bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GBto 3 GB as explained in "Process Memory" on page 109.

10.6 Atoll Administration FilesThere is no specific order in which configuration and initialisation files should be created or installed on Atoll workstationsand servers. It is sufficient to have these files created and placed in the right locations before running Atoll to have thepredefined configuration of all workstations and servers.

If you have already configured these files for one server, and you are setting up another server, you can copy these files totheir respective locations on the new server to have the exact configuration and set‐up as the first. If you do not copy these

In order to prevent users from deactivating the use of the Distributed Calculation Server,and hence bypassing the resource control procedure established above, the Atoll.ini fileshould be set made read‐only for end‐users.

108


files, or create them, you will not have the same configuration of the new server, but apart from that you will be able to workwith Atoll normally. These files are optional, not obligatory.

Initialisation File (INI)

• It is highly recommended that the Atoll initialisation file be created and modified only by the administrator.• If you are using Windows 2000 Server, state the actual number of processors in the INI file.

User Configuration File (CFG)

• Use Atoll to create these files and avoid modifying these files manually as human errors can create problems.• Uncheck image visibility to avoid loading unnecessary data in the memory.• You can set up your configuration files in the following manner:

• A common configuration file that points to the geographic data, macros, and other common parameters in yourAtoll documents.

• Separate configuration files created for your 2G and 3G projects, which would store their respective coverageprediction studies parameters, traffic information, neighbour allocation parameters, and other technology‐specific parameters.

• Separate configuration files based on, and for, different groups of users. These groups of users can be, forexample, groups of users working on different regions, groups of users working on different technologies, groupsof users focusing on certain operations (i.e., performing certain types of coverage predictions, performing the AFP,etc.).

Custom Predictions File

• Coverage prediction studies can easily be duplicated within Atoll. Before creating study templates, and the XMLstudies file, make sure that this study template is aimed at serving a number of users. This means, avoid creating studytemplates unless these will be needed for a long time by a number of users. You can use the configuration files to storeyour created coverage prediction studies locally. And, you can also use the study duplicate feature to create copies ofexisting coverage prediction studies.

10.7 Process Memory

32‐bit Operating Systems

Atoll can support 3 GB address space on a properly configured 32‐bit system. For more information, please refer to thefollowing URL: http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx (/3GB section in “MemorySupport and Windows Operating Systems”).

The following link provides information on how you can setup your Windows Server 2003 systems to activate the 3 GB switchat startup: http://technet.microsoft.com/en‐us/library/bb124810.aspx.

64‐Bit Operating Systems

The 64‐bit editions of Microsoft Windows provide 4 GB of memory per process.

10.8 PrintingYou should place different layers of geographic and radio data in a definite order when printing a project or a section of theproject. The following order should be followed:

1. Visible objects of the Data tab

All the visible objects of the Data tab are displayed above those in the Geo tab. However, it is strongly recommendedto place vector layers on the top of coverage prediction plots. You can do this by transferring these vector layers tothe Data tab using the context menu. For performance reasons, it is advised to place vector layers on top of rasterlayers before printing a project. Sites and Transmitters must be on the very top, above all other layers. You shouldplace sites and sectors on the top, then vector layers, and then raster layers.

2. Unidimensional vectors (points)

3. Open polygonal vectors (lines, i.e., roads and other linear items, etc.)

4. Closed polygonal vectors (surfaces, i.e., zones and areas, etc.)

5. Multi‐format maps (vector or raster maps, i.e., population, rain, generic maps, traffic, etc.)

6. Transparent raster maps (clutter class maps, etc.)

7. Non‐transparent maps (images, DTM, clutter height maps, etc.)

109

http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx

http://technet.microsoft.com/en-us/library/bb124810.aspx


10.9 Coverage Prediction Calculations• If you do not want Atoll to calculate the shadowing margin during a coverage prediction, it is advised to clear the

Shadowing taken into account check box. This approach is more efficient in terms of performance than selecting thisoption and setting the Cell edge coverage probability to 50%.

• To improve memory consumption and optimise the calculation times, you should set the display resolutions ofcoverage predictions according to the precision required. The following table lists the levels of precision that areusually sufficient:

10.10 CW Measurements and Drive Test Data• It is recommended to use Fast Display in order to increase display speed. This option is available in the Display tab of

the Properties dialogues for CW Measurements and Drive Test Data folders. Although this approach only displaysmeasurement points as small squares, it can have a significant impact on performance depending on the number ofmeasurement points in the Atoll document.

• When performing a CW measurements drive test campaign, please follow the recommended procedure described inthe Measurements and Model Calibration Guide.

10.11 Antenna Patterns and Import• Antenna names used in some tools, such as NetAct, can be different from those used in their corresponding antenna

files. To solve this issue, you can create a new file, named "Index", containing the list of antenna names, which wouldin fact be the pattern (antenna file) names. You should place this file at the same location as the antenna patterns(files). This will replace the antenna names with the new antenna names.

• Some Kathrein antenna pattern files might have names different from the antenna pattern names present inside thefile. You will have to replace the name of the pattern inside the file by the name of the pattern file itself, in order toimport these antennas correctly.

• A Planet Index file contains the path to and the name of each antenna file available. Creating such an Index file whenthere are hundreds of antenna patterns available can be a difficult task. You can easily create the index file from theMicrosoft Windows command prompt. You can open the Command Prompt window by selecting Start > Run, entering"cmd" and pressing ENTER. In the Command Prompt window, navigate to the directory containing the antennapattern files, enter the following command and press ENTER:dir /b > Index

This will create a file called "Index" in the same directory as the antenna patter files containing a list of all the antennapattern file names, with one name per line. The file will also contain a line with its own name, so, before importingthis file into Atoll, you should use a text editor to remove the line containing the file name "Index."

• The electrical tilt, which can be defined in the antenna properties dialogues in Atoll, is an additional electrical downtilt.It might be redundant to define an additional electrical downtilt for antennas whose patterns already includeelectrical tilt. Users should verify whether the antenna patterns of the antennas in their projects, do not alreadyinclude the effect of an electrical tilt.

10.12 Traffic Maps• User profile environment‐based traffic maps should only be used for a precision on traffic that is of the same level as

the statistical clutter available in a project.• For higher precision on traffic data, you should use sector traffic maps or user density traffic maps. User density traffic

maps provide you with a means to define a density for each set of service, terminal type, and mobility type.• Sector traffic maps are best suited for traffic data issued by the OMC.

Size of the coverage prediction Display resolution

City Center 5 m

City 20 m

County 50 m

State 100 m

Country According to the size

110


10.13 Atoll APICorrect functioning of Atoll when using Atoll through the API is guaranteed during interactive user sessions only. Atoll is anapplication that requires creating tool bars, creating menus, reading user profile options from the Windows’ registry,accessing printers, etc., even when it is accessed through the API. The same is true for add‐ins working with Atoll.

Even though it is possible to load and use Atoll when there is no user session open on a computer, its correct functioning isnot guaranteed. Unexpected errors can occur. Particularly, creating objects through CreateObject or CoCreateInstance mightfail.

Therefore, the correct functioning of Atoll requires an open user session on the computer.

10.14 Performance and Memory

Memory Refresh

• You can avoid memory fragmentation while working with Atoll documents by saving the Atoll document from time totime, closing and restarting Atoll, and reopening the document.

This advice is applicable to any application running under Microsoft Windows because many common DLL files areaccessed by applications, and unloading and reloading these DLL files refreshes the memory allocation.

• If you are working in a Citrix XenApp environment, you should restart your Citrix server every week or fortnight. Theexact time should be determined by the administrator depending on the state of the network (LAN).

• In certain cases, it might be more appropriate to start working on a completely fresh ATL file. If you have been workingon your existing ATL file for a long time, it might become unnecessarily large and might contain some useless remainsfrom your earlier operations, e.g., traces of records that no longer exist in the database, etc. You can completelyrefresh your project by following these steps:

a. Open the existing ATL file in Atoll that you want to replace.

b. Create a CFG file from your existing ATL file with all the required information, e.g., geographic data set, coverageprediction parameters, neighbour allocation parameters, etc. For more information, refer to "Configuration Files"on page 117.

c. Close the old ATL file.

d. Create a new ATL from the database to create a fresh ATL file.

e. Import the CFG file in the new ATL file.

You now have a clean ATL file to work with, which has all the same information as the old ATL file, and takes up lessspace on the hard disk, has less fragmented data, and improved performance.

Memory Allocation

• If you have to open several large ATL files simultaneously on the same computer, it is better to open each in a separateAtoll session rather than to open them all in the same Atoll window. Each Atoll session on the same computer has itsown memory space allocated by the operating system. Each computer consumes a single licence token independentof the number of Atoll sessions opened simultaneously.

• For 32‐bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GBto 3 GB as explained in "Process Memory" on page 109.

File Size

• Coverage predictions calculated over large areas require more memory. If you are working on an Atoll documentcovering a large area, with coverage predictions calculated over the entire network, this document will require morememory for loading all the coverage predictions. You can reduce memory consumption by making copies of your Atolldocument, and keeping a few coverage predictions in each copy. These ATL files will be faster to load and work withcompared to a single ATL file with all the coverage predictions.

Large coverage predictions can take up a considerable amount of memory even if they are not displayed on the map.

• Externalise DTM, clutter, path loss matrices, and any other data that can be externalised, so that the ATL file size doesnot become unnecessarily large.

Path Loss Calculation

• Before starting path loss calculation, verify that the calculation radii and resolutions assigned to the different types oftransmitters are consistent. For example, calculating path loss matrices of picocells over large calculation radii wouldonly waste memory and disk space.

111


• For calculating path loss matrices over large areas, you should use the dual resolution feature in Atoll. Define shortcalculation radii and fine resolutions for the main path loss matrices, and large calculation radii and low resolutionsfor extended path loss matrices. This approach decreases the calculation time significantly compared to calculatingjust one matrix per transmitter using a fine resolution. The main path loss matrices should be calculated using thesame resolution as the resolution of the geographic data available. The extended path loss matrices can be calculatedusing a lower resolution, e.g., twice the resolution of the geographic data.

Regionalisation

• Use database regionalisation or site lists if you are working on smaller parts of a large network. Atoll loads only thedata necessary for your working area. If you load a large network, Atoll will load a lot of data that might not benecessary all the time, such as the neighbour relation data.

Performance and Memory Issues in Large GSM Projects

Memory problems might be experienced in the C/I coverage prediction studies, interference matrices calculations, and theAFP while working on large GSM networks. Large network projects are more susceptible to these problems. If the network islarge but homogeneous, these problems might only appear if the number of transmitters is over 15,000 or so. But, if there arelarge city centres involved, with each pixel having many overlapping path loss matrices, then this size limit might decrease toaround 5,000 transmitters or so.

Also, if the Atoll session has been open for a long time, memory problems can even appear while working on smallernetworks. This is because the process memory space (memory space allocated to Atoll by the operating system) becomesfragmented.

Following is a list of advice which you can follow in order to avoid such problems:

• Use regionalisation or site lists: If you load a large network, Atoll will be required to load a lot of data that might notbe necessary all of the time. For example, in a typical large GSM network, you might have around 10,000 transmitterrecords, 20,000 subcell records, 50,000 TRX records, and up to 150,000 neighbour records.

• Externalise embedded interference matrices: You can store interference matrices listed in the Interference Matricesfolder in external files. Atoll loads interference matrices from the external files to the memory only when needed. Youwill also reduce the ATL file size by externalising the interference matrices.

• Adapt calculation radii to the cell type and the EIRP: Before calculating path loss matrices, take care to correctlyassociate calculation radii and resolutions to different types of cells. If you calculate path loss matrices for all types ofcells over a large calculation radius, it will unnecessarily burden the C/I and interference matrices computations.

• Properly configure the interference thresholds: These thresholds indicate the level after which an interferer can beignored. The default value for this threshold (‐130 dBm), defined in the Predictions tab of the Predictions folder’sProperties dialogue, means that the computations will take into account all the interferers. However, if you set it toohigh, you might lose important interference information. The proper value for this threshold depends on theReception Thresholds and the C/I Thresholds defined in the Subcells table. The optimum value would be

. Which means the minimum value of the factor computed for all

subcells, i. Where, RTi is the reception threshold of the subcell i, CITi the C/I threshold of this subcell, and M is a safety

margin.

Since this interference threshold is used both in interference matrices calculation and in interference predictions, it isimportant to have at least a 3‐dB margin for the interference energy aggregation in C/I studies. We recommend asafety margin of 5 dB, which can be reduced if any problem is encountered.

• Do not define very high C/I quality thresholds (Default values: 12 dB for BCCH and 9 dB for TCH). If you want a certainTRX type to carry GPRS/EDGE traffic, you can add 1 or 2 dB to this value for that TRX type, and use the option of safetymargin in the AFP module’s Cost tab. The 12 dB and 9 dB default values already include safety margins. If youincrement these values too much, it will unnecessarily load the interference matrix generation and the AFP.

• Do not start an AFP session if the interference matrices report indicates problems: All the transmitters should haveinterferers and very few of them (not more than 20%) should have more than 70 interferers. If there are too many ortoo few entries in your interference matrices, the AFP plan will not be optimal.

• If the memory‐critical task is interference matrices generation: You can generate interference matrices in a piecewisemanner.

This means that you can generate nation‐wide interference matrices with low resolutions based on the percentage ofinterfered area (to improve computation time), with a cell edge coverage probability of 50% (which means no accessto clutter for reading standard deviation values), and an interference threshold of ‐112 dBm. This will provide roughglobal interference matrices which can be locally improved. These interference matrices will be less memory‐consuming.

Then, use polygon or site list filters to focus on each important location, and calculate local interference matrices withhigher resolutions and reliabilities. Make sure that the computation zone in your project completely encompasses thefiltering zones that you define.

• If the memory‐critical task is the AFP session: Try to make the document lighter, e.g., remove coverage predictionstudies, exit and restart Atoll, and try to generate interference matrices with fewer entries.

MinAllSubcells RTi CITi– M– RTi CITi– M–

112


• If the memory‐critical task is the traffic capture: You can use traffic load field of the Subcells table to provide trafficloads directly to the AFP, and possibly skip this step.

Performance and Memory Issues in UMTS/CDMA Simulations

• In order to optimise memory usage during simulations, you can set the "Information to retain" option to "Only theAverage Simulation and Statistics". With this option Atoll uses much less memory because it only keeps limitedinformation in memory during the simulation process. Simulation results are detailed enough to be used in generatingcoverage prediction studies.

Performance and Memory Issues in Co‐planning Projects

Co‐planning with Atoll requires that both technology documents be open in the same Atoll window at the same time.However, loading, for example, a GSM and a UMTS document can cause memory saturation especially if the documentscontain large, country‐wide networks. To decrease the amount of memory used by Atoll in such cases, you can:

• Load vector layers in main document only. Loading vectors in the linked document is not necessary and only consumesmore memory.

• Avoid loading neighbours and custom fields which are not required. This can be performed by creating views in thedatabase. For more information, see "Appendix 2: Setting Up Databases for Co‐planning" on page 60.

10.15 Appendix: Memory RequirementsThis part gives some aspects of memory requirements (both RAM and hard disk space) for Atoll depending on the network tobe planned.

Atoll is capable of performing computations in pixel sizes different from those of the raster maps in a project. It isrecommended to perform detailed planning with smaller pixel sizes in high density areas, and country‐wide (or region‐wide,depending on the size) coverage predictions and other calculations using larger pixel sizes. This approach will provide overallsatisfactory results, and will considerably improve the disk space requirements, RAM allocation and calculation time.

Please note that the figures mentioned in the following sections are approximate, and though actual figures can vary, theirdeviation from the approximate values will be negligible. These approximate values are computed through simplifiedformulas. These formulas do not consider all the input parameters, but only the input parameters that have a considerableimpact on memory requirements.

10.15.1 Disk Space RequirementsThe amount of disk space required for data varies from project to project. It depends mainly on the size of the planning area,the pixel size, and the number of cells. In networks with only a few cells, the amount of disk space required is chieflydetermined by the size of the planning area. In networks with a large number of sites, transmitters and cells, it is the numberof these network entities that governs this requirement. Pixel size plays an equally important role in all cases.

Network‐Wide Input

The file sizes for raster maps (DTM, clutter heights, clutter classes, traffic density or environments, images, etc.) does notdepend on the number of cells, but only on the size of the planning area in pixels.

The following information can provide you with an estimate of disk usage for different geographic data:

• Clutter class maps require 1 byte per pixel (2 bytes for Planet format).• Background images require from 1 to 3 bytes per pixel.• Traffic maps require 1 byte per pixel (2 bytes for Planet format).• DTM or clutter height maps require 2 bytes per pixel.• Population maps or other generic maps require from 1 to 4 bytes per pixel.

For one clutter map, one DTM map, one traffic map, and one background image, you can estimate 6 bytes per pixel of theinput area. This data can be shared between different planning alternatives of the same network.

Cell‐Specific Results

For a project with a large number of cells, it is important to consider the disk space required by the propagation predictionresults of each cell. Here, the cell calculation area and the calculation resolution are important factors.

If an embedded geographic data file is deleted from the project, Atoll automaticallycompresses the ATL file to avoid file fragmentation.

113


Cell‐specific results require 2 bytes per pixel. For example, the propagation results for a sector with a calculation area of 1024x 1024 pixels will require 2 MB disk space.

If there are different ATL files for planning the same part of the network in different ways, each ATL file will require the sameamount of disk space.

The same rule applies to extended path loss matrices as well.

Network‐Wide Output

Network‐wide output (raster results) mainly depends on:

• The size of the planning area• The pixel size• The number of coverage predictions• The types of coverage predictions

Coverage predictions can have a number of layers depending on the calculation criteria. There can be a single layer for theentire network or a layer per transmitter, sector, or subcell. The resulting size depends on the number of layers and thenumber of colours and thresholds. Therefore, Atoll coverage predictions can require between 1 bit and 2 bytes per pixel ofthe calculation area.

Temporary Disk Space

Atoll requires some disk space to temporarily store intermediate results during calculations. A file is created in the system’stemporary directory whose size depends on the calculations. This file is described in the section on RAM requirements.Likewise, a temporary file is created when using the "Save As" command. These files are erased after the calculations or oncethe storage has finished.

Other Disk Space Requirements

Other objects in a ATL file that require disk space can easily be neglected in real‐life scenarios since the required disk spacedepending on the size of the planning area and the number of transmitters is much higher.

ATL files store database tables and calculation results. An empty ATL file requires around 500 KB. Each additional site requiresbetween 1 and 2 KB, which is negligible compared to the size of the propagation results.

Furthermore, the size of vector files is negligible compared to that of other geographic data, as their size is usually muchsmaller than the DTM, clutter height, and clutter class maps.

10.15.2 RAM RequirementsUsually, 512 MB of RAM in a workstation is sufficient for all operations with Atoll, provided that there are no otherapplications being used in parallel that consume large amounts of memory.

Starting Atoll without loading a project requires around 20 MB of RAM (as monitored with the Windows Task Manager).Loading a project with 500 sites, a few predictions, and some simulations can increase the consumed memory to around 50to 100 MB.

Monte Carlo Simulations

UMTS Monte‐Carlo simulations are calculations that consume large amounts of memory. The memory requirement of thesecalculations is a function of the following:

• The number of sites involved

If embedded path loss matrices are externalised, Atoll automatically compresses the ATLfile to avoid file fragmentation.

• Atoll can compress the coverage prediction results when saving a ATL file to avoid filefragmentation.

• You can consider 14 bytes per pixel as a rough estimate to determine the disk spacerequired for each individual ATL file.

When saving an ATL file, Atoll estimates the size of unused spaces in the file due tofragmentation. If the amount of unused spaces is more than half of the useful space,Atoll proposes compressing the file.

114


• The number of transmitters involved• The number of cells involved• The number of mobiles generated by the UMTS simulation• The number of transmitters covering a pixel• The number of services simulated• The number of neighbours per cell• The "Detailed Results" and "Limit Active Set to Neighbours" flags• The number of links per mobile• The number of channel elements per site

Most of these parameters have minor influences and the actual requirements are mostly governed by the number of cells andthe number of mobiles generated.

Assuming that there are three carriers used and the number of transmitters and mobiles is high enough so that the other inputcan be ignored, the required memory can be roughly approximated by:

for normal simulations

using the "detailed results" option

with R: peak RAM requirement in KBytes t: number of transmitters affecting the computation zone m: number of mobiles generated by the UMTS simulation

Example: To calculate for 500 sites (or 1500 transmitters) and 2400 mobiles, around 28 MB of RAM are required for a normalsimulation and 30 MB if detailed results are to be stored as well.

Coverage Predictions

RAM required during coverage prediction calculations (network‐wide raster result) is the same as the required additional diskspace, i.e., between 1 bit and 2 bytes per pixel of the calculation area. Apart from this, temporary memory is required forcalculations like "Coverage by transmitter" and "Coverage by signal level". For these, Atoll temporarily allocates an averageof 4 bytes more per pixel (8 bytes, if the best server margin is not zero) of the calculation area.

Example: The Paris region has a size of around 10 x 13 km. For a calculation resolution of 25 m, this equals 5.2 million pixels.If a coverage prediction calculates the signal strength of the UMTS pilot in less than 16 colours, it would require a memory of4 bits per pixel, or a total of 2.6 MB. During the calculation, Atoll would also require 4 more bytes per pixel, which equals20.8 MB more apart from the 2.6 MB.

• Please note that this is the peak requirement. Less memory will be required once thecalculations are terminated.

• This approximation also considers effects due to the operating system, such asmemory over‐allocation due to fragmentation. It is a conservative approximation andin most cases the actual RAM requirement will be below these calculated figures.

• A more accurate estimation of the used and required memory for UMTS simulations isavailable in the Source Traffic tab of the new simulation group dialogue. To activatethe memory estimation feature, you must add an option in the Atoll.ini file. For moreinformation, see "Estimating Required and Used Memory Size for UMTS Simulations"on page 172.

For large networks, to avoid loading the entire computation zone in memory, Atolldivides the coverage prediction computations into smaller tiles, and carries out thecomputations on them successively. This subdivision is invisible to the user.

R 14.0 t 3.25 m+=

R 14.0 t 4.3 m+=

115


116

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 11: Configuration Files

11 Configuration FilesConfiguration files can be used to store parameter and display settings. These files are optional, not required for working withAtoll, but are useful means for making work easier.

This chapter describes the formats of these files in detail:

• User configuration files (UTF‐8 encoded XML‐format GEO or CFG files)

A user configuration file containing only the geographic data settings can be saved with a GEO extension. A userconfiguration file containing the geographic data settings and other parameter settings can be saved with a CFGextension.

User configuration files must be created using Atoll to ensure correct syntax and structure. It is possible to edit thecontents of these files in an XML editor and make changes if required (for example, to update the paths to geographicdata files). For more information on how to create and load user configuration files in Atoll, see the User Manual.

These files can store:

• Geographic data settings• Filtering, focus, computation, printing, and geographic export zones• Map centre and zoom level• Folder configurations• List of coverage predictions in the Predictions folder and their settings• Automatic neighbour allocation parameters• Automatic frequency planning parameters (GSM GPRS EDGE documents)• Automatic scrambling code allocation parameters (UMTS HSPA and TD‐SCDMA documents)• Automatic PN offset allocation parameters (CDMA2000 documents)• Automatic OFDM resource allocation parameters (LTE, WiMAX, Wi‐Fi)• Microwave link parameters• Full paths to macro files

For more information on the contents of user configuration files, see "Contents of User Configuration Files" onpage 118.

A user configuration file can be automatically loaded when Atoll is run if:

a. The file is identified in the command line parameter ‐Cfg "cfgfilename" (see "Atoll Command Line Parameters" onpage 24 for more information), or

b. The file is named "Atoll.cfg" and is located in the Atoll installation folder. This file will be ignored if a userconfiguration file is loaded through the command line parameter.

• Additional configuration files (UTF‐8 encoded XML‐format CFG files or plain text INI files)

The following parameter settings can be stored in additional configuration files with a CFG extension:

• Print setup configuration• Table import/export configuration• Coverage prediction report configuration

The following parameter settings can be stored in specific INI files:

• CW measurement import configuration• Drive test data import configuration

For more information on the contents of additional configuration files, see "Contents of Additional ConfigurationFiles" on page 141.

• Custom predictions file (UTF‐8 encoded XML files)

This file (one for all customised predictions) contains the list and parameter settings of customised coveragepredictions. By default, this file is named "Studies.xml" and is located in the Atoll installation folder.

The custom predictions file must be created using Atoll to ensure correct syntax and structure. It is possible to editthe contents of this file in an XML editor and make changes if required. For more information on working withcustomised predictions in Atoll, see the User Manual.

• Projection and display coordinate systems are stored in the database, not in userconfiguration files.

• Simulation settings are not stored in user configuration files.

117

Atoll 3.2.1 Administrator ManualChapter 11: Configuration Files © Forsk 2014

For more information on the contents of the custom predictions file, see "Content of the Custom Predictions File" onpage 145.

• Predictions files calculated by Value Intervals (UTF‐8 encoded XML files)

These files (one per prediction) contain the parameter settings of the coverage predictions calculated with the displaytype (on the General tab of the Properties dialog box) set to "Value intervals". By default, these files are named"<prediction_name>.XML" and are located in "C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}".

11.1 Contents of User Configuration FilesThe descriptions and examples provided below for each parameter set can help understand the format and function of theuser configuration files. The following details are available:

• "Geographic Data Set" on page 118• "Map Centre and Zoom Level" on page 122• "Zones" on page 121• "Folder Configuration" on page 122• "Coverage Predictions" on page 129• "Automatic Neighbour Allocation Parameters" on page 131• "Automatic Frequency Planning Parameters" on page 133• "Automatic Scrambling Code Allocation Parameters" on page 134• "Automatic PN Offset Allocation Parameters" on page 136• "Microwave Radio Links Parameters" on page 138• "Macros" on page 141.

11.1.1 Geographic Data SetThe following parameters are saved for various geographic data types:

• <DegreeFormat>: Format used to display degrees, minutes, and seconds for geographic coordinate systems

• Population, geoclimatic parameters, vector traffic maps, and other vector layers:• <Name>: Name of the folder• <Display>: (Different combinations of the following parameters exist in different display settings.)

• Display type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (sameas <FieldSelector>) and <FieldTitle>, visibility flag <visible>, and visibility range between <minZoom> and<maxZoom>

• <SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, backgroundcolour <BackColor>, and font style <Style>

• <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,label font background colour <BackColor>, and label font style <Style>

• <Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>,<SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle>

• <AddToLegend>: Add to legend option checked or not• <Type>: Data type properties, such as <Name>, <Formats>, <Type>, and <Integrable>• <File>: Contains the file format, path, coordinate system information.

• <Format> of and <Path> to linked files, if any• Coordinate system information for vector format data including: <CoordinateSystemName>,

<CoordinateSystemCode>, <EllipsoidCode>, <EllipsoidMajorRadius>, <EllipsoidMinorRadius>, <DatumCode>,<DatumShiftX>, <DatumShiftY>, <DatumShiftZ>, <DatumRotationX>, <DatumRotationY>, <DatumRotationZ>,<DatumScaleFactor>, <ProjectionMethod>, <ProjectionZone>, <ProjectionLongitudeOrigin>,<ProjectionLatitudeOrigin>, <ProjectionFalseEasting>, <ProjectionFalseNorthing>, <ProjectionScaleFactor>,<ProjectionFirstParallel>, <ProjectionSecondParallel>, and <ProjectionAngle>

• Clutter Classes:• <Name>: Name of the folder• <Display>: (Different combinations of the following parameters exist in different display settings.)

• Displate type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (sameas <FieldSelector>) and <FieldTitle>, transparency level <Opacity>, visibility flag <visible>, and visibility rangebetween <minZoom> and <maxZoom>


• <AddToLegend>: Add to legend option checked or not• <Attributes>, such as: <records> and <fields>, which are,

• Common: CODE, COLOR, NAME, HEIGHT, INDOOR• Under <GSM>: STDDEV, COVERI_STDDEV, TX_DIV_GAIN, ANT_HOP_GAIN

118


• Under <UMTS>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, ALPHA, FORTHO,SM_GAIN_FACTOR, STTD_GAIN_OFFSET

• Under <LTE>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, DIV_GAIN_OFFSET_DL,DIV_GAIN_OFFSET_UL

• Under <1XRTT>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, ALPHA, FORTHO• Under <TD‐SCDMA>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, FORTHO_UL,

FORTHO_DL, ANGULAR_SPREAD• Under <IEEE_802.16e>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, STTD_OFFSET_DL,

STTD_OFFSET_UL• Under <Wi‐Fi>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, STTD_OFFSET_DL, STTD_OFFSET_UL

• <DefaultValues>, for the fields stated above.

• Clutter Heights and Digital Terrain Models:• <Name>: Name of the folder• <Display>: (Different combinations of the following parameters exist in different display settings.)

• Displate type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (sameas <FieldSelector>) and <FieldTitle>, transparency level <opacity>, visibility flag <visible>, and visibility rangebetween <minZoom> and <maxZoom>


• <AddToLegend>: Add to legend option checked or not• <File>: <Format> and <Path> to linked files, if any

Sample

Sample with display set to value intervals.

<?xml version="1.0" encoding="UTF-8"?>

<Atoll>

<Geodataset version="2">

<DegreeFormat>0</DegreeFormat>

<Population> // or <GeoClimaticParams> or <Vectors>

<Name>Population</Name> // or <Name>Geoclimatic Parameters</Name>or <Name>Vectors</Name>

<Display>

<minZoom>500</minZoom>

<maxZoom>20000000</maxZoom>

<visible>Yes</visible>

<Type>ByIntervals</Type>

<FieldSelector>80000001</FieldSelector>

<FieldDesc>

<FieldId>80000001</FieldId>

<FieldTitle>Population (inhab./km²)</FieldTitle>

</FieldDesc>

<SymbolFont>

<Name>Wingdings</Name>

<Size>-120</Size>

<Color>0 0 0</Color>

<BackColor>255 255 255</BackColor>

<Style>0</Style>

</SymbolFont>

<LabelFont>

<Name>MS Shell Dlg</Name>

<Size>-83</Size>



<Style>0</Style>

119


</LabelFont>

<Items>

<Item>

<Min>900.</Min>

<Max>1000.</Max>

<Legend>900 <=Population(Density) <1 000</Legend>

<MainColor>255 96 0</MainColor>

<SecondaryColor>255 0 0</SecondaryColor>

</Item>

</Items>

</Display>

<AddToLegend>0</AddToLegend>

<Type>

<Name>Population</Name>

<Formats>15</Formats>

<Type>800</Type>

<Integrable>1</Integrable>

</Type>

<Files/>

</Population> // or </GeoClimaticParams> or </Vectors>

<ClassifiedClutter UseOnlyDefault="0">

<Display>



<FieldDesc>


<FieldTitle>Height (m)</FieldTitle>

</FieldDesc>

<Opacity>50</Opacity>

<Items>

<Item>

<Min>54.</Min>

<Max>56.</Max>

<Legend>54 <=Height (m) <56</Legend>



<LineStyle>5</LineStyle>

<LineWidth>10</LineWidth>

<FillStyle>1</FillStyle>

</Item>

</Items>




</Display>

<Attributes>

<fields>

<field length="1" type="uint" name="CODE"/>

<field length="4" type="int" name="COLOR"/>

120


11.1.2 ZonesThe user configuration files store the coordinates of the vertices of the filtering, focus, computation, printing, and geographicexport zone polygons, i.e., the points forming these polygons. The first and the last points have the same coordinates.

Sample

The following sample has rectangular computation and focus zones of the same size.

<field length="50" type="text" name="NAME"/>

<field length="4" type="real" name="HEIGHT"/>

<field length="2147483647" type="text" name="INDOOR"/>

</fields>

<records/>

</Attributes>

<Name>Clutter Classes</Name>


<DefaultValues>

</DefaultValues>

</ClassifiedClutter>

<Altitudes> // or <BuildingHeights>

<Name>Digital Terrain Model</Name> // or <Name>Clutter Heights</Name>

<Display>






<FieldDesc>


<FieldTitle>Altitude</FieldTitle>

</FieldDesc>


<Items>

<Item>

<Min>900.</Min>

<Max>1000.</Max>

<Legend>900 <=Altitude <1 000</Legend>






</Item>

</Items>

</Display>


</Altitudes> // or </BuildingHeights>

</Geodataset>

</Atoll>

121


11.1.3 Map Centre and Zoom LevelThe following parameters are saved:

• <MapPosition>: X and Y coordinates of the centre of the map window and the zoom level.

Sample

11.1.4 Folder ConfigurationThe following parameters are saved for the following folders:

• Sites folder:• <Name>: Name of the folder• <Display>:

• Displate type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (sameas <FieldSelector>) <FieldTitle> and <FieldDBName>, visibility flag <Visible>, and visibility range between<MinZoom> and <MaxZoom>

• <SymbolFont> properties, such as font name <Name>, font size <Size>, font colour <Color>, backgroundcolour <BackColor>, and font style <Style>

• <LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour <Color>, labelfont background colour <BackColor>, and label font style <Style>

• <Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>, <Symbol>,and <SymbolSize>

• <DataTips>: List of <items> displayed in tip texts• <Labels>: List of <items> displayed in labels

• <AddToLegend>: Add to legend option checked or not• <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration

<Filter>, <Groups>, and <Sort> criteria• <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the

<Filter>, <Groups>, and <Sort> criteria

• Antennas folder:• <Name>: Name of the folder• <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration



<Atoll>

<CalculationZone>

<Point>35950.000000 -15445.000000</Point>

<Point>33.000000 -15445.000000</Point>

<Point>33.000000 -33.000000</Point>

<Point>35950.000000 -33.000000</Point>

<Point>35950.000000 -15445.000000</Point>

</CalculationZone>

<FocusZone>

<Point>35950.000000 -15445.000000</Point>

<Point>33.000000 -15445.000000</Point>

<Point>33.000000 -33.000000</Point>

<Point>35950.000000 -33.000000</Point>

<Point>35950.000000 -15445.000000</Point>

</FocusZone>

<Atoll>


<Atoll>

<MapPosition CenterX="609433" CenterY="5632019" Scale="250000"/>

</Atoll>

122


• <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the<Filter>, <Groups>, and <Sort> criteria

• Transmitters, Multi‐Hops, and Point to Multipoint folders:• <Name>: Name of the folder• <Display>:

• Displate type <Type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (sameas <FieldSelector>) <FieldTitle> and <FieldDBName>, visibility flag <Visible>, and visibility range between<MinZoom> and <MaxZoom>

• <LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour <Color>, labelfont background colour <BackColor>, and label font style <Style>

• <Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>, <Symbol>,and <SymbolSize>

• <DataTips>: List of <items> displayed in tip texts• <Labels>: List of <items> displayed in labels

• <AddToLegend>: Add to legend option checked or not• <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration

<Filter>, <Groups>, and <Sort> criteria• <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the

<Filter>, <Groups>, and <Sort> criteria• <OFDM_AFP>: LTE, WiMAX, and Wi‐Fi frequency allocation constraint weights:

• <Techno>: Name of the technology• <NeighbourWeight>: Weight of the first order neighbour relation• <InterNeighbourWeight>: Weight of the relation between two neighbours of a common cell• <IMWeight>:Weight of the interference matrices relation• <DistanceWeight>: Weight of the distance‐based relation

• <PCI_Alloc>: LTE physical cell ID allocation constraint weights:• <NeighbourWeight>: Weight of the first order neighbour relation• <SecondNeighbourWeight>: Weight of the second order neighbour relation• <InterNeighbourWeight>: Weight of the relation between two neighbours of a common cell• <IMWeight>:Weight of the interference matrices relation• <DistanceWeight>: Weight of the distance‐based relation• <IDWeight>: Weight of the physical cell ID constraint• <PSSWeight>: Weight of the PSS ID constraint• <SSSWeight>: Weight of the same SSS ID per site constraint• <ULDMRSSGWeight>: Weight of the UL DMRS (PCI Mod 30) collision constraint• <DLRSSCaWeight>: Weight of the single antenna port DL CRS (PCI Mod 6) collision constraint• <PCFICHREGWeight>: Weight of the PCFICH REG (PCI Mod (N_RB/2)) collision constraint

• <PI_Alloc>: WiMAX preamble index allocation constraint weights:• <NeighbourWeight>: Weight of the first order neighbour relation• <SecondNeighbourWeight>: Weight of the second order neighbour relation• <InterNeighbourWeight>: Weight of the relation between two neighbours of a common cell• <IMWeight>:Weight of the interference matrices relation• <DistanceWeight>: Weight of the distance‐based relation• <IndexWeight>: Weight of the preamble index constraint• <SegmentWeight>: Weight of the segment constraint• <PermBaseWeight>: Weight of the same cell permbase per site constraint

• Links folder:• <Name>: Name of the folder• <Display>: Contains visibility flag <visible>, and visibility range between <minZoom> and <maxZoom>• <AddToLegend>: Add to legend option checked or not• <DefaultConfiguration>: The default configuration for the folder• <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>, label

font background colour <BackColor>, and label font style <Style>• <SiteDisplay> properties, such as:


• <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,label font background colour <BackColor>, and label font style <Style>

• <Symbol>: Symbol used for microwave links• <ShowText>: Caption for microwave links shown or not• <RepeaterDisplay> properties, such as:


• CW Measurements folder:• <DefaultConfiguration>: The default configuration for the folder

• <Distance>: The minimum <Min> and maximum <Max> distance for measurement filtering

123


• <DistanceUnit>: The distance unit• <Measure>: The minimum <Min> and maximum <Max> measured level for filtering• <MeasureUnit>: The measurement unit• <Angle>: The minimum <Min> and maximum <Max> angle for measurement filtering• <Relative>: Whether the angle is relative to each transmitter’s azimuth or an absolute value• <Clutter>: For each <Class>, its <Code> and whether it is in the <Filter> or not• <Advanced>: Any advanced filter used for filtering

• <PathLosses>: Path loss tuing parameters, i.e., <ParallelAxisRadius>, <PerpendicularAxisRadius>, <GlobalMargin>,<LocalMargin>, and <Threshold>

• <Display>:• Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between

<MinZoom> and <MaxZoom>• <SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background

colour <BackColor>, and font style <Style>• <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,

label font background colour <BackColor>, and label font style <Style>• <Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and

<SymbolSize>• <DataTips>: List of <items> displayed in tip texts• <Labels>: List of <items> displayed in labels

• <AddToLegend>: Add to legend option checked or not

• Drive Test Data folder:• <Techno>: Name of the technology (if exported from a 3GPP Multi‐RAT document.• <DefaultConfiguration>: The default configuration for the folder

• <Clutter>: For each <Class>, its <Code> and whether it is in the <Filter> or not• <Advanced>: Any advanced filter used for filtering

• <PathLosses>: Path loss tuing parameters, i.e., <ParallelAxisRadius>, <PerpendicularAxisRadius>, <GlobalMargin>,<LocalMargin>, and <Threshold>

• <Display>:• Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between

<MinZoom> and <MaxZoom>• <SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background

colour <BackColor>, and font style <Style>• <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,

label font background colour <BackColor>, and label font style <Style>• <Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and

<SymbolSize>• <DataTips>: List of <items> displayed in tip texts• <Labels>: List of <items> displayed in labels

• <AddToLegend>: Add to legend option checked or not

• Propagation Models and Smart Antenna Models folders:• <Name>: Name of the folder• <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration


Sample


<Atoll>

<FoldersConfigurations>

<Sites>

<Name>Sites</Name>

<Display>




<Type>ByValues</Type>


<FieldDesc>


<FieldTitle>Vendor</FieldTitle>

124


</FieldDesc>

<SymbolFont>


<Size>-120</Size>



<Style>32</Style>

</SymbolFont>

<LabelFont>


<Size>-80</Size>



<Style>33</Style>

</LabelFont>

<Items>

<Item>

<Value>Vendor</Value>

<Legend>Vendor</Legend>



<Symbol>164</Symbol>

<SymbolSize>120</SymbolSize>

</Item>

</Items>

<DataTips>

<Item>0</Item>

</DataTips>

<Labels>

<Item>0</Item>

</Labels>

</Display>


<DefaultConfiguration>

<Groups>Type</Groups>

</DefaultConfiguration>

</Sites>

<Antennas>

<Name>Antennas</Name>


<Filter>([CONSTRUCTOR]= Kathrein)</Filter>


<Configuration>

<Name>Conf</Name>

<Filter>([CONSTRUCTOR]= Kathrein)</Filter>

</Configuration>

</Antennas>

<Transmitters> // or <MWMultiHops> // or <MWHubs>

125


<Name>Transmitters</Name> // or <Name>Multi-Hops</Name> //or <Name>Point to Multipoint</Name>

<Display>




<Type>ByValues</Type>


<FieldDesc>


<FieldTitle>Automatic</FieldTitle>

</FieldDesc>

<Items>

</Items>

<DataTips>

<Item>0</Item>

</DataTips>

</Display>


<DefaultConfiguration/>

</Transmitters> // or </MWMultiHops> // or </MWHubs>

<MWLinks>

<Name>Links</Name>

<Display>




</Display>



<LabelFont>


<Size>-83</Size>



<Style>0</Style>

</LabelFont>

<SiteDisplay>

<SymbolFont>


<Size>80</Size>



<Style>0</Style>

</SymbolFont>

<LabelFont>


<Size>-80</Size>


126



<Style>0</Style>

</LabelFont>

</SiteDisplay>


<ShowText>0</ShowText>

<RepeaterDisplay>

<SymbolFont>


<Size>80</Size>



<Style>0</Style>

</SymbolFont>

</RepeaterDisplay>

</MWLinks>

<CWMeasurements>


<Distance>

<Min>0.</Min>

<Max>1000.</Max>

</Distance>

<DistanceUnit>0</DistanceUnit>

<Measure>

<Min>-105.</Min>

<Max>-90.</Max>

</Measure>

<MeasureUnit>0</MeasureUnit>

<Angle>

<Min>-180.</Min>

<Max>180.</Max>

</Angle>

<Relative>Yes</Relative>

<Clutter>

<Class>

<Code>1</Code>

<Filter>Yes</Filter>

</Class>

</Clutter>

<Advanced>([DIST]> 500)</Advanced>


<PathLosses>

<ParallelAxisRadius>200.</ParallelAxisRadius>

<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>

<GlobalMargin>30.</GlobalMargin>

<LocalMargin>30.</LocalMargin>

<Threshold>-130.</Threshold>

</PathLosses>

<Display>

127



<FieldSelector>Error (P-M) (dB)</FieldSelector>

<SymbolFont>


<Size>-120</Size>



<Style>0</Style>

</SymbolFont>

<LabelFont>


<Size>-83</Size>



<Style>0</Style>

</LabelFont>

<Items>

<Item>

<Min>-20.</Min>

<Legend>Error (P-M) (dB) >=-20</Legend>





</Item>

</Items>

<DataTips>

<Item>M (dBm)</Item>

</DataTips>

<Labels>

<Item>M (dBm)</Item>

</Labels>

</Display>

</CWMeasurements>

<TestMobileData>

<Techno>GSM</Techno>


<Clutter>

<Class>

<Code>1</Code>

<Filter>Yes</Filter>

</Class>

</Clutter>

<Advanced></Advanced>


<PathLosses>

<ParallelAxisRadius>200.</ParallelAxisRadius>

<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>

<GlobalMargin>30.</GlobalMargin>

128


11.1.5 Coverage PredictionsThe list of coverage predictions available in the Predictions folder and the following parameters are saved:

• General tab:• <Techno>: Name of the technology• <Name>: Name of the folder• <Resolution>: Prediction resolution• <Configuration>: <Filter>, <Groups>, and <Sort> criteria for the prediction• <LockedStudy>: Locked or not

• Conditions tab: Depend on technologies and prediction types.• <Reliability>: Cell edge coverage probability• <Indoor>: Indoor coverage checked or not• <WithShadowing>: Shadowing margin taken into account or not

<LocalMargin>30.</LocalMargin>

<Threshold>-130.</Threshold>

</PathLosses>

<Display>


<FieldSelector>Ec_I0</FieldSelector>

<SymbolFont>


<Size>-120</Size>



<Style>0</Style>

</SymbolFont>

<LabelFont>


<Size>-83</Size>



<Style>0</Style>

</LabelFont>

<Items>

<Item>

<Min>-60.</Min>

<Legend>Ec_I0 >=-60</Legend>





</Item>

</Items>

</Display>

</TestMobileData>

<PropagationModels> // or <SmartAntennasModels>

<Name>Propagation Models</Name> // or <Name>Smart Antenna Models</Name>


</PropagationModels> // or </SmartAntennasModels>

</FoldersConfigurations>

</Atoll>

129


• ...• Display tab:

• <Display>: (Different combinations of the following parameters exist in different display settings.)• Display type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (same

as <FieldSelector>) and <FieldTitle>, visibility flag <visible>, opacity <Opacity>, and visibility range between<minZoom> and <maxZoom>


• <AddToLegend>: Add to legend option checked or not• <DataTips>: List of <items> displayed in tip texts

Sample

GSM coverage by signal level


<Atoll>

<Studies>

<CoverageTRXStudy>

<Techno>GSM</Techno>

<Name>GSM: Coverage by Signal Level 0</Name>

<Display>







<Items>

<Item>

<Min>-75.</Min>

<Legend>Best Signal Level (dBm) >=-75</Legend>






</Item>

<Item>

<Min>-85.</Min>







</Item>

<Item>

<Min>-95.</Min>





130


11.1.6 Automatic Neighbour Allocation ParametersThe following parameters are saved for intra‐technology (intra‐carrier and inter‐carrier) and inter‐technology automaticneighbour allocations:

• <ANP_options>: Intra‐technology (intra‐carrier) neighbour allocation parameters• <ANP_IL_options>: Intra‐technology inter‐carrier neighbour allocation parameters (UMTS HSPA and CDMA2000

documents)• <ANP_IT_options>: Inter‐technology neighbour allocation parameters

A <Techno></Techno> tag is also present if the user configuration is exported from a 3GPP Multi‐RAT document. Thistag contains the name of the technology to which the parameters belong.



</Item>

<Item>

<Min>-105.</Min>







</Item>

</Items>

<DataTips>

<Item>c0000000</Item>

<Item>c0000001</Item>

</DataTips>

</Display>


<Resolution>50</Resolution>

<GUID>{52D66F26-5710-4F4B-A327-6DAFF337AB21}</GUID>

<LockedStudy>0</LockedStudy>

<ComputeHisto>1</ComputeHisto>

<HistoPerTx>0</HistoPerTx>

<HistoLabel></HistoLabel>

<Conditions>

<FieldDbm>

<Min>-105.</Min>

</FieldDbm>

<Reliability>0.75</Reliability>

<TRXType>BCCH</TRXType>

<DefTrgThreshold>1</DefTrgThreshold>

<Indoor>0</Indoor>

<WithShadowing>0</WithShadowing>

</Conditions>

</CoverageTRXStudy>

</Studies>

</Atoll>

131


The following parameters are saved:

• Parameters common to all technologies:• <numMax>: Maximum number of neighbours to allocate• <useCoSite>: Force co‐site transmitters/cells as neighbours or not• <useAdjacent>: Force adjacent transmitters/cells as neighbours or not• <symetric>: Force symmetry between neighbours or not• <keepNeighbs>: Reset existing neighbours or keep them• <MaxDist>: Maximum distance between sites• <PercentCoverage>: Coverage conditions: Minimum percentage of covered area• <UseShadowing>: Coverage conditions: Take shadowing into account or not• <reliability>: Coverage conditions: Cell edge coverage probability• <applyConstraints>: Force exceptional pairs as neighbours or not• <covBased>: Not implemented yet• <minCov>: Neighbour importance: minimum factor for coverage• <maxCov>: Neighbour importance: maximum factor for coverage• <minAdj>: Neighbour importance: minimum factor for adjacency• <maxAdj>: Neighbour importance: maximum factor for adjacency• <minCos>: Neighbour importance: minimum factor for co‐site• <maxCos>: Neighbour importance: maximum factor for co‐site• <minDistImportance>: Neighbour importance: minimum factor for distance• <maxDistImportance>: Neighbour importance: maximum factor for distance• <resolution>: Resolution used for coverage calculation for overlapping (‐1 means the default resolution defined in

the properties of the Predictions folder is used)• <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not• <UseGlobalThreshold>: Coverage conditions for WiMAX and LTE: Whether to use a global minimum preamble C/

N or RSRP, or per‐cell values

• Parameters specific to GSM GPRS EDGE:• <minField>: Coverage conditions: Minimum BCCH signal level• <margin>: Coverage conditions: Margin for the minimum signal level (Handover start)• <traffic>: Coverage conditions: Take traffic into account or not• <deltaMax>: Coverage conditions: Handover end

• Parameters specific to UMTS HSPA, TD‐SCDMA, and CDMA2000 1xRTT 1xEV‐DO:• <minField>: Coverage conditions: Minimum pilot signal level• <margin>: Coverage conditions: Margin for the minimum signal level (Ec/I0 margin)

• <traffic>: Coverage conditions: Take traffic into account or not• <deltaMax>: Coverage conditions: Handover end• <EcIoMin>: Coverage conditions: Minimum Ec/I0• <usePmax>: Coverage conditions: Use maximum power or not• <PerCentMaxPower>: Coverage conditions: Percentage of maximum power to consider in calculations• <EcIoMax>: Coverage conditions: Maximum Ec/I0• <useEcIoMax>: Coverage conditions: Use maximum Ec/I0 or not

• <TDrop>: TDrop value (TD‐SCDMA documents, intra‐technology neighbour allocation only)

• Parameters specific to WiMAX 802.16e and LTE:• <HOStart>: The handover start margin (intra‐technology neighbour allocation only)• <HOEnd>: The handover end margin (intra‐technology neighbour allocation only)• <BSmargin>: RSRP margin from the best server (inter‐technology neighbour allocation only)

Sample

UMTS HSPA inter‐technology, intra‐carrier neighbour allocation parameters:


<Atoll>

<ANP_options>

<Techno>UMTS</Techno>

<numMax>16</numMax>

<resolution>-1</resolution>

<minField>-10500</minField>

<margin>500</margin>

<useCoSite>1</useCoSite>

<useAdjacent>1</useAdjacent>

132


11.1.7 Automatic Frequency Planning ParametersThe following parameters are saved for automatic frequency planning (GSM GPRS EDGE documents):

• <defSeparations__CONF_CO_SITE_BB>: Default co‐site separation rule for two BCCH type TRXs.• <defSeparations__CONF_CO_CELL_BB>: Default co‐transmitter separation rule for two BCCH type TRXs.• <defSeparations__CONF_NEIGH_BOUR_BB>: Default neighbour separation rule for two BCCH type TRXs.• <defSeparations__CONF_CO_SITE_BT>: Default co‐site separation rule for a BCCH and a TCH type TRX.• <defSeparations__CONF_CO_CELL_BT>: Default co‐transmitter separation rule for a BCCH and a TCH type TRX.• <defSeparations__CONF_NEIGH_BOUR_BT>: Default neighbour separation rule a for BCCH and a TCH type TRX.• <defSeparations__CONF_CO_SITE_TT>: Default co‐site separation rule for two TCH type TRXs.• <defSeparations__CONF_CO_CELL_TT>: Default co‐transmitter separation rule for two TCH type TRXs.• <defSeparations__CONF_NEIGH_BOUR_TT>: Default neighbour separation rule for two TCH type TRXs.• <freezeState>: Last minute resource freezing options available in the AFP launch wizard• <numMinutes>: Target time alloted to the AFP• <useDTX>: Consider the effect of discontinuous transmission or not• <dtxVocalFactor>: Voice activity factor for discontinuous transmission• <AfpBasedOnInterference>: Load all potential interferers or not• <AfpBasedOnSeparations>: Load all the subcells potentially involved in separation constraints or not• <IM_calculate__WithTraffic>: Whether traffic spreading is uniform or based on the maps used in the default traffic

capture (for interference matrices calculation)• <IM_calculate__BestServerZoneMargin>: Margin in case of Best signal level per HCS layer (for interference matrices

calculation)• <IM_calculate__ServiceZoneType>: All or Best signal level per HCS layer (for interference matrices calculation)• <IM_calculate__reliability_X_10000>: Cell edge coverage probability (for interference matrices calculation)• <TakeTfFromCapt>: Whether traffic loads are read from the default traffic capture or from the Subcells table• <preferedSenario>: Scenario type, i.e., modification of existing TRXs allowed or not

<traffic>0</traffic>

<symetric>0</symetric>

<keepNeighbs>0</keepNeighbs>

<MaxDist>10000</MaxDist>

<PercentCoverage>1000</PercentCoverage>

<UseShadowing>0</UseShadowing>

<reliability>7500</reliability>

<UseIndoor>0</UseIndoor>

<deltaMax>1200</deltaMax>

<applyConstraints>0</applyConstraints>

<covBased>1</covBased>

<minDistImportance>100</minDistImportance>

<maxDistImportance>1000</maxDistImportance>

<minCov>1000</minCov>

<maxCov>3000</maxCov>

<minAdj>3000</minAdj>

<maxAdj>6000</maxAdj>

<minCos>6000</minCos>

<maxCos>10000</maxCos>

<UseGlobalThreshold>0</UseGlobalThreshold>

<EcIoMin>-1400</EcIoMin>

<usePmax>0</usePmax>

<PerCentMaxPower>5000</PerCentMaxPower>

<EcIoMax>-700</EcIoMax>

<useEcIoMax>0</useEcIoMax>

</ANP_options>

</Atoll>

133


Sample

11.1.8 Automatic Scrambling Code Allocation ParametersThe following parameters are saved for automatic scrambling code allocation (UMTS HSPA and TD‐SCDMA documents):

• <MinEcI0>: Minimum Ec/I0 constraint (not used in TD‐SCDMA)

• <margin>: Ec/I0 margin (not used in TD‐SCDMA)

• <reliability>: Cell edge coverage probability (not used in TD‐SCDMA)• <DistanceMin>: Default re‐use distance• <Strategy0>: Clustered strategy available or not• <Strategy1>: Distributed per Cell strategy available or not• <Strategy2>: One Cluster/SYNC_DL Code per Site strategy available or not• <Strategy3>: Distributed per Site strategy available or not• <Strategy>: Scrambling code allocation strategy• <FromScratch>: Reset all already allocated codes or not• <UseCurrentNghbs>: Use existing first‐order neighbours or not• <NghbOrder>: The order of neigbours to take into account, i.e., 1st, 2nd, or 3rd• <ComputeNghbs>: Calculate neighbours using the addition Ec/I0 conditions or not

• <UseMaxCodes>: Use a maximum of codes or not• <UseShadowing>: Shadowing taken into account or not (not used in TD‐SCDMA)• <SameCodeForCarriers>: Allocate carriers identically or not• <NbClusterPerSite>: Number of transmitters per site among which a cluster should be distributed• <ClustNghbs>: Additional constraint of taking into account the first‐order neighbours in other clusters• <Clust2ndNghbs>: Additional constraint of taking into account the second‐order neighbours in other clusters• <NbCodesPerCluster>: The number of scrambling codes in one cluster/SYNC_DL• <UseDistance>: Take the minimum reuse distance into account or not• <UseExcepPairs>: Take exceptional pairs into account or not• <minField>: Minimum pilot signal level constraint (not used in TD‐SCDMA)• <usePmax>: Use the maximum downlink transmission power or not (not used in TD‐SCDMA)


<Atoll>

<AFP_options>

<defSeparations__CONF_CO_SITE_BB>2</defSeparations__CONF_CO_SITE_BB>

<defSeparations__CONF_CO_CELL_BB>3</defSeparations__CONF_CO_CELL_BB>

<defSeparations__CONF_NEIGH_BOUR_BB>2</defSeparations__CONF_NEIGH_BOUR_BB>

<defSeparations__CONF_CO_SITE_BT>2</defSeparations__CONF_CO_SITE_BT>

<defSeparations__CONF_CO_CELL_BT>3</defSeparations__CONF_CO_CELL_BT>

<defSeparations__CONF_NEIGH_BOUR_BT>1</defSeparations__CONF_NEIGH_BOUR_BT>

<defSeparations__CONF_CO_SITE_TT>1</defSeparations__CONF_CO_SITE_TT>

<defSeparations__CONF_CO_CELL_TT>2</defSeparations__CONF_CO_CELL_TT>

<defSeparations__CONF_NEIGH_BOUR_TT>1</defSeparations__CONF_NEIGH_BOUR_TT>

<freezeState>0</freezeState>

<numMinutes>1000</numMinutes>

<useDTX>0</useDTX>

<dtxVocalFactor>70</dtxVocalFactor>

<AfpBasedOnInterference>1</AfpBasedOnInterference>

<AfpBasedOnSeparations>1</AfpBasedOnSeparations>

<IM_calculate__WithTraffic>0</IM_calculate__WithTraffic>

<IM_calculate__BestServerZoneMargin>5</IM_calculate__BestServerZoneMargin>

<IM_calculate__ServiceZoneType>1</IM_calculate__ServiceZoneType>

<IM_calculate__reliability_X_10000>7500</IM_calculate__reliability_X_10000>

<TakeTfFromCapt>1</TakeTfFromCapt>

<preferedSenario></preferedSenario>

</AFP_options>

</Atoll>

134


• <PerCentMaxPower>: The percentage of the maximum downlink power is <usePmax> is set to 0 (not used in TD‐SCDMA)

• <Max1stNghbCost>: The maximum cost of 1st order neighbours• <Max2ndNghbCost>: The maximum cost of 2nd order neighbours• <Max3rdNghbCost>: The maximum cost of 3rd order neighbours• <CoplanCost>: The cost for inter‐technology neighbours• <MaxCoClusterCost>: The maximum cost for same‐cluster/SYNC_DL neighbours• <MaxDistCost>: The maximum cost for a minimum reuse distance constraint violation• <ExcepPairCost>: The cost for exceptional pair constraint violation• <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not• <UseCloseNghbs>: Take the Close Neighbours constraint into account or not (TD‐SCDMA only)• <CloseDistance>: Maximum distance within which close neighbours are located (TD‐SCDMA only)• <CloseImportance>: Minimum importance value of close neighbour (TD‐SCDMA only)• <MaxCloseCost>: Maximum cost of a close neighbour relation (TD‐SCDMA only)

Sample


<Atoll>

<SCP_options>

<MinEcI0>-1500.</MinEcI0>

<margin>500.</margin>

<reliability>5000.</reliability>

<DistanceMin>200000.</DistanceMin>

<Strategy0>1</Strategy0>




<Strategy>0</Strategy>

<FromScratch>1</FromScratch>

<UseCurrentNghbs>1</UseCurrentNghbs>

<NghbOrder>1</NghbOrder>

<ComputeNghbs>0</ComputeNghbs>

<UseMaxCodes>1</UseMaxCodes>


<SameCodeForCarriers>0</SameCodeForCarriers>

<NbClusterPerSite>3</NbClusterPerSite>

<ClustNghbs>0</ClustNghbs>

<Clust2ndNghbs>0</Clust2ndNghbs>

<NbCodesPerCluster>8</NbCodesPerCluster>

<UseDistance>1</UseDistance>

<UseExcepPairs>1</UseExcepPairs>




<Max1stNghbCost>100</Max1stNghbCost>

<Max2ndNghbCost>50</Max2ndNghbCost>

<Max3rdNghbCost>5</Max3rdNghbCost>

<CoplanCost>100</CoplanCost>

<MaxCoClusterCost>50</MaxCoClusterCost>

<MaxDistCost>100</MaxDistCost>

<ExcepPairCost>100</ExcepPairCost>


135


11.1.9 Automatic PN Offset Allocation ParametersThe following parameters are saved for automatic PN offset allocation (CDMA2000 documents):

• <MinEcI0>: Minimum Ec/I0 constraint

• <TDrop>: Value for the TDrop• <reliability>: Cell edge coverage probability• <DistanceMin>: Default re‐use distance• <Strategy0>: PN Offset per Cell strategy available or not• <Strategy1>: Adjacent PN‐Cluster per Site strategy available or not• <Strategy2>: Distributed PN‐Cluster per Site strategy available or not• <Strategy>: PN offset allocation strategy• <FromScratch>: Reset all already allocated codes or not• <UseCurrentNghbs>: Use existing neighbours or not• <NghbOrder>: The order of neigbours to take into account, i.e., 1st, 2nd, or 3rd• <ComputeNghbs>: Calculate neighbours using the addition Ec/I0 conditions or not

• <UseShadowing>: Shadowing taken into account or not• <SameCodeForCarriers>: Allocate same PN offset to cells of the same transmitter or not• <PilotIncr>: Value for the PILOT_INC• <PNClusterSize>: Number of PN offsets per cluster• <UseDistance>: Take the minimum reuse distance into account or not• <UseExcepPairs>: Take exceptional pairs into account or not• <UseMaxCodes>: Use a maximum of codes or not• <minField>: Minimum pilot signal level constraint• <usePmax>: Use the maximum downlink transmission power or not• <PerCentMaxPower>: The percentage of the maximum downlink power is <usePmax> is set to 0• <Max1stNghbCost>: The maximum cost of 1st order neighbours• <Max2ndNghbCost>: The maximum cost of 2nd order neighbours• <Max3rdNghbCost>: The maximum cost of 3rd order neighbours• <CoplanCost>: The cost for inter‐technology neighbours• <MaxDistCost>: The maximum cost for a minimum reuse distance constraint violation• <ExcepPairCost>: The cost for exceptional pair constraint violation• <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not

Sample

<UseCloseNghbs>1</UseCloseNghbs>

<CloseDistance>80000.</CloseDistance>

<CloseImportance>3000.</CloseImportance>

<MaxCloseCost>100</MaxCloseCost>

</SCP_options>

</Atoll>


<Atoll>

<PNO_options>

<DistanceMin>200000.</DistanceMin>




<Strategy>2</Strategy>

<FromScratch>1</FromScratch>

<UseCurrentNghbs>1</UseCurrentNghbs>

<NghbOrder>1</NghbOrder>

<ComputeNghbs>1</ComputeNghbs>

<SameCodeForCarriers>0</SameCodeForCarriers>

<PilotIncr>4</PilotIncr>

<PNClusterSize>3</PNClusterSize>

136


11.1.10 Automatic OFDM Resource Allocation ParametersThe following parameters are saved for automatic allocation of resources in OFDM networks:

• <UseNeighbs>: Neighbours taken into account or not• <UseDistance>: Distance taken into account or not• <UseIM>: Interference matrices taken into account or not• <BasedOnFrqPlan>: Frequency plan taken into account or not• <SameSegPerTx>: Allocate the same segment to co‐transmitter cells or not• <MinDistance>: Minimum global reuse distance• <SiteStrategy>: Per‐site or free allocation for SSS ID (LTE) and cell permbase (WiMAX)• <UniformIDDistribution>: Uniform physical cell ID or preamble index distribution active or not• <RangeType>: Physical cell ID, preamble index, or zone permbase allocation domain (restricted = 0, entire = 1, custom

= 2, or per‐cell = 3)• <ExcludedPis>: List of excluded physical cell IDs, preamble indexes, or zone permbases for custom allocation domain

type

Automatically allocated resources in OFDM networks include:

• LTE: Frequency and physical cell ID allocation parameters• WiMAX: Frequency, preamble index, and zone permbase allocation parameters• Wi‐Fi: Frequency allocation parameters

Sample


<UseExcepPairs>1</UseExcepPairs>

<UseMaxCodes>1</UseMaxCodes>

<MinEcI0>-1600.</MinEcI0>

<TDrop>-1800.</TDrop>

<reliability>6000.</reliability>





<Max1stNghbCost>100</Max1stNghbCost>

<Max2ndNghbCost>50</Max2ndNghbCost>

<Max3rdNghbCost>5</Max3rdNghbCost>

<CoplanCost>100</CoplanCost>

<MaxDistCost>100</MaxDistCost>

<ExcepPairCost>100</ExcepPairCost>


</PNO_options>

</Atoll>


<Atoll>

<OFDM_AFP_options>

<UseNeighbs>1</UseNeighbs>


<UseIM>1</UseIM>

<BasedOnFrqPlan>1</BasedOnFrqPlan>

<SameSegPerTx>0</SameSegPerTx>

<MinDistance>100.</MinDistance>

<SiteStrategy>1</SiteStrategy>

<UniformIDDistribution>1</UniformIDDistribution>

137


11.1.11 Microwave Radio Links ParametersThe following parameters are saved for microwave radio links:

• <QualityModel>: Quality model used for calculations• <QualityObjective0>, <QualityObjective1>, <QualityObjective2>, <QualityObjective3>: Quality objectives• <AvailabilityObjective0>, <AvailabilityObjective1>, <AvailabilityObjective2>, <AvailabilityObjective3>: Availability

objectives• <RainModel>: Rain model used• <RBER>: Residual BER• <ALFA1>: Value of alpha 1• <ALFA2>: Value of alpha 2• <RefDelayM>: Reference delay for minimum phase• <refDelayNM>: Reference delay for non‐minimum phase• <EquipPercent>: Availability objectives ratio for equipment• <RainPercent>: Availability objectives ratio for rain• <kMoy>: Average value of k• <kMin>: Minimum value of k• <UseAtpc>: Use automatic power control or not• <P0Method>: Multi‐path occurence method• <IgnoreXPD>: Ignore cross‐polar discrimination• <IgnorePR>: Ignore passive repeaters• <WhichBER>: BER to calculate• <BER1>: Value of BER 1• <BER2>: Value of BER 2• <Rec838>: Rain model recommendations version• <UseK1Global>: Use the global value for k1• <UseK2Global>: Use the global value for k2• <CALC_LINK_PORTS>: Calculate for given link ports• <MultilineShared>: Shared multi‐channel frequency diversity• <NoAcm>: Signal enhancements• <InterferenceDistanceMax>: Maximum distance for interference filtering• <InterferenceDropMin>: Local min threshold degradation• <InterferenceDropMinGlobal>: Global min threshold degradation• <InterferenceCalcGo>: Interference calculation in the direction from site A to site B• <InterferenceCalcReturn>: Interference calculation in the direction from site B to site A• <InterferenceCalcUplink>: Interference calculation in the uplink• <InterferenceCalcDownlink>: Interference calculation in the downlink• <InterferenceRainSurfCorrelation>: Interference correlation surface area• <InterferenceAutoWeight>: Automatic interference weighting• <InterferenceUseAtpc>: Power control for interference calculation• <InterferenceWidth>: Interfered wanted bandwidth• <InterferenceOverShoot>: Interference over shoot calculation• <CochannelOnly>: Interfered bandwidth co‐channel only• <IgnoreIntraLinkInterference>: Ignore interference between channels of the same link• <Resolution>: Interfering profile calculation step• <INTERF_DETAIL>: Calculation details (none, uplink, downlink, both)• <ClutterCategory0> through <ClutterCategory36>: Bitsets for clutter category properties• <ClutterDryCategory0> through <ClutterDryCategory36>: Soil type

Sample

<RangeType>2</RangeType>

<ExcludedPis></ExcludedPis>

</OFDM_AFP_options>

</Atoll>


<Atoll>

<Microwave>

<QualityModel>6</QualityModel>

<QualityObjective0>3</QualityObjective0>


138




<AvailabilityObjective0>3</AvailabilityObjective0>



<RainModel>5</RainModel>

<RBER>1.e-012</RBER>

<ALFA1>10</ALFA1>

<ALFA2>1</ALFA2>

<RefDelayM>6.30000019</RefDelayM>

<refDelayNM>6.30000019</refDelayNM>

<EquipPercent>33.</EquipPercent>

<RainPercent>33.</RainPercent>

<kMoy>1.33</kMoy>

<kMin>0.88</kMin>

<UseAtpc>0</UseAtpc>

<P0Method>1</P0Method>

<IgnoreXPD>1</IgnoreXPD>

<IgnorePR>0</IgnorePR>

<WhichBER>5</WhichBER>

<BER1>1.e-003</BER1>

<BER2>1.e-006</BER2>

<Rec838>1</Rec838>

<UseK1Global>1</UseK1Global>

<UseK2Global>1</UseK2Global>

<CALC_LINK_PORTS>selected</CALC_LINK_PORTS>

<MultilineShared>0</MultilineShared>

<NoAcm>1</NoAcm>

<InterferenceDistanceMax>50000.</InterferenceDistanceMax>

<InterferenceDropMin>1.</InterferenceDropMin>

<InterferenceDropMinGlobal>3.</InterferenceDropMinGlobal>

<InterferenceCalcGo>1</InterferenceCalcGo>

<InterferenceCalcReturn>1</InterferenceCalcReturn>

<InterferenceCalcUplink>0</InterferenceCalcUplink>

<InterferenceCalcDownlink>0</InterferenceCalcDownlink>

<InterferenceRainSurfCorrelation>100.</InterferenceRainSurfCorrelation>

<InterferenceAutoWeight>0</InterferenceAutoWeight>

<InterferenceUseAtpc>0</InterferenceUseAtpc>

<InterferenceWidth>250</InterferenceWidth>

<InterferenceOverShoot>0</InterferenceOverShoot>

<CochannelOnly>0</CochannelOnly>

<IgnoreIntraLinkInterference>1</IgnoreIntraLinkInterference>

<Resolution>50</Resolution>

<INTERF_DETAIL>both</INTERF_DETAIL>

<ClutterCategory0>0</ClutterCategory0>

<ClutterDryCategory0>B</ClutterDryCategory0>




139




























<ClutterDryCategory15>E</ClutterDryCategory15>






















<ClutterDryCategory26>A</ClutterDryCategory26>

140


11.1.12 MacrosThe following parameters are saved for macros:

• <Path>: Full path to the macro file• <Language>: Language in which the macro is written• <Timeout>: The target time allocated to macro execution

Sample

11.2 Contents of Additional Configuration FilesComplete descriptions of the different additional configuration files are provided below.

11.2.1 Print Setup ConfigurationThe following parameters are saved for print setup:

• Page tab <Page>:





















</Microwave>

</Atoll>


<Atoll>

<Macros>

<File>

<Path>C:\TestsAddin\testEvents.vbs</Path>

<Language>VBScript</Language>

<Timeout>3600</Timeout>

</File>

</Macros>

</Atoll>

141


• Paper size and orientation <Paper size="" orientation=""/>, margins <Margins right="" left="" bottom="" top="">,scaling with the fit to page option <Scale fitToPage="">

• Components tab:• Rulers and area inside focus zone only <Map>: <Map insideFZonly="" rulers=""/>• Legend <Legend>: Legend flag, outer and inner position, and inside map flag <LegendPos enable="" majorPos=""

minorPos="" insideMap=""/>• Comments <Comments>: Comments flag, vertical and horizontal position, and the inside map flag <Position

vPos="" enable="" hPos="" insideMap=""/>, comment text <text>, and font details <font height="" weight=""charset="" face="" italic=""/>

• Header/Footer tab:• Header logo <Logo>: Logo flag, vertical and horizontal position, and the inside map flag <Position vPos=""

enable="" hPos="" insideMap=""/>, logo image <bitmap>, and logo width and height in pixels <Dimensionswidth="" height=""/>

• Header title <Title>: Header flag, vertical and horizontal position, and the inside map flag <Position vPos=""enable="" hPos="" insideMap=""/>, title text <text>, and font details <font height="" weight="" charset="" face=""italic=""/>

• Footer logo <LogoBottom>: Logo flag, vertical and horizontal position, and the inside map flag <Position vPos=""enable="" hPos="" insideMap=""/>, logo image <bitmap>, and logo width and height in pixels <Dimensionswidth="" height=""/>

• Footer text <Footer>: Footer flag, vertical and horizontal position, and the inside map flag <Position vPos=""enable="" hPos="" insideMap=""/>, footer text <text>, and font details <font height="" weight="" charset=""face="" italic=""/>

Sample


<PrintConfiguration version="1">

<Page>

<Paper size="" orientation="1"/>

<Margins right="2000" left="2000" bottom="2000" top="2000"/>

<Scale fitToPage="1">12 495</Scale>

</Page>

<Map insideFZonly="1" rulers="1"/>

<Legend>

<LegendPos enable="0" majorPos="3" minorPos="0" insideMap="0"/>

</Legend>

<Comments>

<Position vPos="1" enable="0" hPos="1" insideMap="0"/>

<text></text>

<font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/>

</Comments>

<Logo>


<bitmap></bitmap>

<Dimensions width="46" height="18"/>

</Logo>

<Title>


<text></text>


</Title>

<LogoBottom>


<bitmap></bitmap>

<Dimensions width="46" height="18"/>

</LogoBottom>

142


11.2.2 Table Import/Export ConfigurationThe following parameters are saved for table import/export:

• Header flag <TITRE>• Field separator <FLD_SEPARATOR>• Decimal symbol <DEC_SEPARATOR>• Fields available in the table (field legends) <FIELDS>• Fields selected for import/export (field legends) <CHOOSEN_FIELDS>

Sample

11.2.3 Coverage Prediction Report ConfigurationThe following parameters are saved for coverage prediction reports:

• Columns selected in the Columns to be displayed dialogue <SelectedFields> including the field titles <Field> <Title>

Sample

<Footer>


<text></text>


</Footer>

</PrintConfiguration>


<TITRE>1</TITRE>

<FLD_SEPARATOR><tab></FLD_SEPARATOR>

<DEC_SEPARATOR>.</DEC_SEPARATOR>

<FIELDS>

Site

Transmitter

...

</FIELDS>

<CHOOSEN_FIELDS>

Site

Transmitter

...

</CHOOSEN_FIELDS>


<ReportConfiguration>

<SelectedFields>

<Field>

<Title>Surface (km²)</Title>

</Field>

<Field>

<Title>% of Covered Area</Title>

</Field>

...

</SelectedFields>

</ReportConfiguration>

143


11.2.4 CW Measurement Import ConfigurationMore than one CW measurement import configurations can be saved in a single CWMeasurementsImport.ini file.

The following parameters are saved in the CWMeasurementsImport.ini files:

• Configuration name in square brackets• First measurement row (Header)• Separator (Separator)• Decimal symbol (DecimalSeparator)• Type of files for which the configuration has been defined (Pattern)• Column containing the X coordinates (Xindex)• Column containing the Y coordinates (Yindex)• Column containing the measurement values (MeasIndex)• Unit of the measurement values (Unit)• Frequency of the measurements (Frequency)• Height of the receiver used for measurements (Height)• Gain of the receiver used for measurements (Gain)• Losses of the receiver used for measurements (Losses)• Total number of columns in measurement files (NbCol)• Column types (Col0 to ColNbCol)

The column type indexes are as follows:

Sample

11.2.5 Drive Test Data Import ConfigurationMore than one drive test data import configurations can be saved in a single DriveTestDataImport.ini file.

The following parameters are saved in the DriveTestDataImport.ini files:

• Configuration name in square brackets• First measurement row (Header)

Type Index

Text 0

Integer 1

Real 2

Date 3

<Ignore> 4

[ConfigurationName]

Header=2

Separator=tab

DecimalSeparator=.

Pattern=*.txt

Xindex=1

Yindex=2

MeasIndex=4

Unit=0

Frequency=2110

Height=1.5

Gain=0

Losses=0

NbCol=23

Col0=1

Col3=4

Col5=0

...

144


• Separator (Separator)• Decimal symbol (DecimalSeparator)• Type of files for which the configuration has been defined (Pattern)• Column containing the X coordinates (Xindex)• Column containing the Y coordinates (Yindex)• Unit of the measurement values (Unit)• Height of the receiver used for measurements (Height)• Gain of the receiver used for measurements (Gain)• Losses of the receiver used for measurements (Losses)• First identifier (GenericNameIdOne)• Second identifier (GenericNameIdTwo)• Format of the second identifier (IdFormat)• Wireless technology (Techno)• Total number of columns in measurement files (NbCol)• Column types (Col0 to ColNbCol)

The column type indexes are as follows:

Sample

11.3 Content of the Custom Predictions FileThe content of the custom predictions file (by default, studies.XML in the installation folder) is identical to the content foundbetween the <Studies> and </Studies> tags in the configuration file. For more information, see "Coverage Predictions" onpage 129.

Type Index

Text 0

Integer 1

Long Integer 2

Single 3

Double 4

Date 5

<Ignore> 6

[ConfigurationName]

Header=2

Separator=tab

DecimalSeparator=.

Pattern=*.*

Xindex=1

Yindex=2

Unit=0

Height=1.5

Gain=0

Losses=0

GenericNameIdOne=

GenericNameIdTwo=BSID

IdFormat=Decimal

Techno=IEEE 802.16e

NbCol=21

Col0=1

Col3=1

Col4=4

...

145


11.4 Content of the "Value Intervals" Predictions FilesThe content of the XML files for coverage predictions calculated by value intervals (by default, prediction_name>.XML in theC:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>} folder) is identical to the content found between the <Studies> and </Studies> tags in the configuration file. For more information, see "Coverage Predictions" on page 129.

146

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Chapter 12: Initialisation Files

12 Initialisation FilesInitialisation files can be used to store operational and working environment settings. These files are optional, not requiredfor working with Atoll, but are useful means for selecting required calculation methods and other settings.

This chapter describes the formats of these files in detail:

• Atoll initialisation file (Atoll.ini)

This file contains conventions, calculation settings, and other options for Atoll. For more information on these options,see "Atoll Initialisation File" on page 147.

Atoll.ini can be automatically loaded when Atoll is run when it is:

a. Identified in the command line parameter ‐Ini "inifilename" (see "Atoll Command Line Parameters" on page 24 formore information), or

b. Located in the Atoll installation folder. This file will be ignored if an initialisation file is loaded through thecommand line parameter.

• ACP initialisation file (ACP.ini)

This file contains calculation settings and other options for the Atoll ACP module. For more information on theseoptions, see "ACP Initialisation File" on page 194.

12.1 Atoll Initialisation FileThe following main groups of options are available:

• "General Options" on page 147• "GUI Options" on page 159• "Distributed Calculation Server Options" on page 163• "Licence Management Options" on page 164• "Database Options" on page 165• "Common Calculation Options" on page 168• "GSM GPRS EDGE Options" on page 175• "UMTS HSPA, CDMA2000, and TD‐SCDMA Options" on page 180• "LTE, WiMAX, and Wi‐Fi Options" on page 185• "3GPP Multi‐RAT Options" on page 190• "Microwave Radio Links Options" on page 191• "Measurement Options" on page 193• "ACP Options" on page 194

12.1.1 General Options

12.1.1.1 Modifying the Default Formats of Site and Transmitter Names

Through the Atoll.ini file, it is possible to specify prefixes to be used for naming sites and transmitters.

In case of sites, you must add these lines:

Each new site will then be named “newprefixN” instead of “SiteN”, where N is the site number or index.

• You can open the Atoll.ini file in the Atoll installation folder for editing by pressingCTRL+SHIFT+i. If no Atoll.ini file exists, a blank Atoll.ini file is created.

• You must restart Atoll in order to take into account modifications made in Atoll.ini.• A given Atoll.ini section, e.g. [GUIUserRights] or [LTE], must occur only once in the file,

with all options pertaining to that section listed under it. If you enter the same sectiontwice, only the first occurrence of the section will be read and loaded by Atoll.

The Atoll initialisation file is a powerful tool. You should not modify any option until andunless you are absolutely sure of what you are doing.

[Site]

Prefix = "newprefix"

147

Atoll 3.2.1 Administrator ManualChapter 12: Initialisation Files © Forsk 2014

For transmitters, you can define a prefix by adding these lines:

Each new transmitter will be named “newprefixN” instead of Sitename_X (Sitename is the name of the site where thetransmitter is located and X is the transmitter sector number on this site). Not adding the above lines, or setting the prefix to<Auto> (Prefix = "<AUTO>"), will instruct Atoll to keep the conventional naming method, i.e., each transmitter will be namedSitename_X.

Furthermore, it is also possible to remove the underscore character "_" from the transmitter’s name, i.e., the transmitter canbe named SitenameX instead of Sitename_X. To do this, add the following line in the [Transmitter] section of the Atoll.ini file:

Setting this value to 0 means the underscore character will not be used when naming transmitters. The default value is 1. Youcan also define whether the suffix X in the transmitter’s name should be a number or a letter. The following two lines definethis option in the Atoll.ini file:

When SuffixIsNum = 1, the default, the suffix X in the transmitter name Sitename_X will be a number. When it is set to 0, thissuffix will be a letter. The starting suffix in this case will be A by default but can be changed to any other character throughthe second line.

If you are using number suffixes, you can also initialise the number suffix at any other number than 1. To do this, you can addthe following lines under the [Transmitter] section of the Atoll.ini file:

Where, X is a number.

12.1.1.2 Disabling Automatic Renaming of Transmitters and Cells

When the name of any site is modified, Atoll automatically renames the transmitters and cells related to the site according tothe new site name. Similarly, renaming a transmitter renames the corresponding cells automatically. Automatic renamingaccording to site names is enabled by default. However, it can be disabled by adding the following lines in the Atoll.ini file:

• "Transmitters" refers to transmitter renaming when the site name is changed.• "3Gcells" refers to cell renaming when the transmitter name is changed.

12.1.1.3 Setting the TIFF Colour Convention

In the default palette, the first colour indexes represent the useful information and the remaining colour indexes representthe background. You can export TIFF files with a palette containing the background colour at index 0 along with other colourindices representing the foreground. This can be helpful when working on TIFF files exported by Atoll in other tools. To do so,the Atoll.ini file must contain these lines:

12.1.1.4 Creating an Event Viewer Log File

You can define a log file path and file name in Atoll.ini in order to save all the warning, error, and information messagesdisplayed in the Event Viewer window to a log file. To do this, add the following lines to Atoll.ini:

[Transmitter]

Prefix = "newprefix"

[Transmitter]

Underscore = 0 or 1

[Transmitter]

SuffixIsNum = 0 or 1

FirstCharSuffix = "A"

[Transmitter]

First = X

[AutoRename]

Transmitters = 0

3GCells = 0

[TiffExport]

PaletteConvention = Gis

148


The path should be the full path to the log file, which can be, for example, "\\Server\Drive\Root\Folder\Atoll\" or "C:\ProgramFiles\Forsk\Atoll\" (without quotation marks). "LogFile.log" will be created by Atoll as an ASCII text file, and can have any filename and extension. Atoll will overwrite any already existing log file with the same name. If Atoll is unable to overwrite theexisting log file, it will not create any log.

You can also start Atoll, specifying a log file, by starting it with "Atoll.exe ‐log LogFile.log", either from the command line, orby modifying the shortcut parameters. If you have a log file defined in the Atoll.ini file, and run Atoll with the ‐log option inthe command line, the command line log file will have priority over the one mentioned in the Atoll.ini file.

The option available in Atoll.ini is more suitable for running Atoll using macros. Apart from these options, you also have thepossibility to save the messages in the Event Viewer to a log file during an Atoll session (through the Event Viewer contextmenu).

12.1.1.5 Displaying Insufficient Permission Messages in the Event Viewer

If a user attempts to load an add‐in for which he does not have the necessary permissions, by default, a message will bedisplayed in the Event Viewer. By defining an option in the Atoll.ini file, messages regarding insufficient permission will not bedisplayed.

12.1.1.6 Increasing the Maximum Printing Resolution

By default, Atoll limits the printing resolution to 150 dpi (dots per inch) to improve performance and consume less memorywhen printing. If you want Atoll to print your maps in a higher resolution than 150 dpi, you can add the following lines to theAtoll.ini file:

300 dpi is given as an example only.

12.1.1.7 Duplicating Linked Path Loss Matrices on Save As

When you save an Atoll document with linked path loss matrices as another document using Save As, Atoll creates the thelinked path loss matrices folder corresponding to the created file and copies the existing linked path loss matrices from thepath loss matrices folder of the original document. There can be a large number of LOS files, and copying these files can takea long time and use a lot of disk space. If you want Atoll not to make copies of the linked path loss matrices, you can add thefollowing lines to the Atoll.ini file:

StoreExternPrivLosFilesOnCopy is set to 1 by default, which means that Atoll makes copies of the linked path loss matrices onSave As. If you set StoreExternPrivLosFilesOnCopy to 0, Atoll does not create the linked path loss matrices foldercorresponding to the created file, and the linked path loss matrices of the original Atoll document are used for the new Atolldocument as well.

A file open in Atoll has exclusive access rights to its private path loss matrices. If two files point to the same linked path lossmatrices folder, the file open first will have access to the the path loss matrices. You will be able to open the second file, butit will no longer point to any private path loss matrices folder. Therefore, if you have more than one file that points to thesame private path loss matrices folder, you should not open them at the same time.

When StoreExternPrivLosFilesOnCopy is set to 1, you can add another option in the Atoll.ini file to make Atoll ask the whetherthe user wants Atoll to make copies the linked path loss matrices or not. To add this confirmation step on Save As, add thefollowing lines in the Atoll.ini file:

ConfirmStoreExternPrivLosFilesOnCopy is set to 0 by default. This option is ignored when Atoll is run in non‐interactive mode,for example using the API.

[EventsObserver]

LogPath = FullPath\LogFile.log

[EventsObserver]

ShowAddinAccessDeniedMsg=0 # 1 by default; insufficient permission messages are shown

[Print]

MaxDPI = 300

[Perfos]

StoreExternPrivLosFilesOnCopy = 0

[Perfos]

ConfirmStoreExternPrivLosFilesOnCopy = 1

149


12.1.1.8 Disabling External Storage of Numerical Results Files for Predictions

The numerical results of coverage predictions calculated by value intervals are stored externally files. This avoids recalculatinga coverage prediction when the legend is modified and provides a numerical difference feature between basic predictions.

However, the storage of numerical results may require additional disk space when your document contains several coveragepredictions and transmitters, and/or high resolutions are used. if you have limited disk space, you can disable this feature byadding the following lines in the Atoll.ini file:

NumericalResults is set to 1 by default, which means that Atoll will generate external results files and require more disk space.

12.1.1.9 Restricting the List of Predictions for Creating Sector Traffic Maps

When you create a sector traffic map, i.e., traffic map based on cell coverage areas, Atoll uses an existing best server coverageprediction in order to be able to distribute the live traffic data geographically. Atoll lets you select the best server coverageprediction on which the traffic map will be based. In the list of available best server coverage predictions, Atoll lists all the bestserver coverage prediction available in the Predictions folder, whether they were created using a margin or without.

If you want Atoll to list only the best server coverage predictions that were created without a margin, i.e., with 0 dB margin,you can add the following lines to the Atoll.ini file:

SelectNullMarginOnly is set to 0 by default, which means that Atoll lists all the best server coverage predictions available.

12.1.1.10 Displaying Path Loss Calculation Details in the Event Viewer

During path loss calculations, Atoll displays details about these calculations in the Tasks tab of the Event Viewer. These detailscannot be copied or saved. If you want access to these details, or to a summary of these details, once the calculations havefinished, you can add the following lines in the Atoll.ini file:

Setting the DisplayInvalidityCause option to 1 will display the cause for which path losses were calculated for each transmitter,setting DisplayIndividualSuccessOrFailure to 1 will display whether the path loss calculation succeeded or failed for eachtransmitter, and setting DisplayOverallSuccessOrFailure to 1 will display the total number of path loss matrices calculated, thenumber of path loss matrices calculated successfully, and the number of calculations that failed.

These details are listed in the Events tab of the Event Viewer.

12.1.1.11 Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files

It is now possible to define a mapping between the coordinate systems in Atoll and the coordinate systems defined in theheader files of MapInfo (MIF) and ESRI (PRJ) vector files that you want to import. You can define a mapping between the twocoordinate systems by adding the following lines in the Atoll.ini file:

In this way, Atoll is able to exactly detect the coordinate system used by the vector file being imported. In MIF files, theCoordSys clause defines the coordinate systems, datum, unit, and other information. The coordinate system definition isdifferent in the PRJ files. The syntax used in Atoll.ini follows the syntax of the CoordSys clause in MIF files. Using the samesyntax for MIF and PRJ files, Atoll is able to read the detect the coordinate systems for both MapInfo and ESRI vector files.

[Studies]

NumericalResults = 0

Memory space is not impacted when NumericalResults is set to 1.

[Studies]

SelectNullMarginOnly = 1

[Pathlosses]

DisplayInvalidityCause = 1

DisplayIndividualSuccessOrFailure = 1

DisplayOverallSuccessOrFailure = 1

[MITAB]

Coordinate system definition in the header file = Coordinate system code in Atoll

150


The coordinate system codes in Atoll are stored in the CS files in the coordsystems folder. To access the coordinate systemcodes through Atoll:

1. Select Tools > Options. The Options dialogue opens.

2. On the Coordinates tab, click the browse button (...) to the left of the Projection field. The Coordinate Systemsdialogue opens.

3. Select a coordinate system in the pane.

4. Click the Properties button. The Coordinate System properties dialogue opens.

The coordinate system code is available in the properties dialogue.

A few examples of such mapping are given below.

12.1.1.12 Exporting Coverage Prediction Polygons in Text Format

You can export coverage predictions in the form of polygons to text format files.

You can enable this feature by adding the following lines in the Atoll.ini file:

Setting EnableLBS to 1 adds a new coverage prediction export format "LBS Polygon Files (*.txt)" to Atoll. The polygons areexported in a comma separated values format.

12.1.1.13 Defining Web Map Services Servers

Web Map Services allow you to directly import geographic data from specialised servers into Atoll. The list of WMS serverscan be defined in the Atoll.ini file as follows:

You can define any number of servers by incrementing the index N. These servers will be available in the WMS data importdialogue in Atoll.

[MITAB]

; NTF

Earth Projection 1, 107 = 4275

; Tokyo

Earth Projection 1, 97 = 4301

; WGS 84 / UTM zone 31N

Earth Projection 8, 104, "m", 3, 0, 1, 500000, 0 = 32631


Earth Projection 8, 104, "m", 135, 0, 0.9996, 500000, 0 = 32653


Earth Projection 8, 104, "m", 141, 0, 0.9996, 500000, 0 = 32654

; NTF (Paris) / France II étendue

Earth Projection 3, 1002, "m", 0, 46.8, 45.8989188889, 47.69601444, 600000, 2200000= 27595

Enabling this option influences the export feature for all exportable vector fomats (MIF,TAB, AGD, SHP, TXT). When this option is enabled, only the largest polygon is exportedfor coverage layers having more than one polygon.

[Studies]

EnableLBS = 1

[WMS]

S1 = Server1

S2 = Server2

...

SN = ServerN

151


12.1.1.14 Improving Point Analysis Performance

You can improve the performance, i.e., calculation speed, of the Point Analysis tool by restricting the number of transmittersfor which the received signal levels are calculated. To restrict the number of transmitters considered in the Point Analysis tool,add the following lines in the Atoll.ini file:

The option PtAnalysisNbServersMax lets to define the maximum number of transmitters (servers) to consider for thecalculation of the received signal levels. X is the maximum number of transmitters.

The option PtAnalysisMargin lets you define the margin with respect to the best server signal level. Atoll calculates the signallevels from all the transmitters within Y dB margin from the best server signal level. The default value for PtAnalysisMargin is30 dB.

In addition to the above, you can also set the number of transmitters for which arrows are displayed from the pointer locationin the map window. For setting this number, add the following lines in the Atoll.ini file:

Z is the number of transmitters for which arrows generated from the pointer location will be displayed in the map window.

12.1.1.15 Loading Vector Files Dynamically

Vector geo data from files imported in an Atoll document are loaded in the memory when the document is open. Atoll candynamically load the data from SHP and TAB vector files when the following option is set in the Atoll.ini file:

LoadVectors is set to 0 by default, which means that the data from imported vector files are loaded in memory. When you setLoadVectors to 1, Atoll reads the data from the vector files directly.

From the point of view of performance, this option is only advisable when working with large vector data files.

12.1.1.16 Excluding Vectors from Imported KML/KMZ Files

By default, when a KML or KMZ file is imported in an Atoll document, the placemarks and vectors are both imported. Bydefining the following option in the Atoll.ini file, you can import KML and KMZ files without vectors:

LoadKMLVectors is set to 1 by default, which means that vectors are imported along with placemarks.

12.1.1.17 Setting the Precision for the Antenna Pattern Verification at Import

Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns arecorrectly aligned when:

• the horizontal pattern attenuation at 0° is the same as the vertical pattern attenuation at the pattern electrical tiltangle, and

• the horizontal pattern attenuation at 180° is the same as the vertical pattern attenuation at the 180° less the patternelectrical tilt angle.

By default, the option is inactive, i.e., the pattern attenuations are considered the same if they differ less than 100 dB. If youwant to change this default precision, add the following lines in the Atoll.ini file:

Where X is the required precision in dB multiplied by 10. For example, if you want to set the precision to 0.5 dB, X will be

.

[Perfos]

PtAnalysisNbServersMax = X

PtAnalysisMargin = Y

[ReceptionTab]

NumberOfTransmitterDisplayed = Z

[Import]

LoadVectors = 1

[Import]

LoadKMLVectors = 0

[Antenna]

PrecisionTimes10 = X

0.5 10 5=

152


12.1.1.18 Opening Exported XLS Files Automatically in MS Excel

When you export an entire data table, or selected columns, to an MS Excel file, Atoll can automatically run MS Excel once theexport is complete and open the XLS file created by the export in MS Excel. To enable this feature, add the following optionin the Atoll.ini file:

AutoOpenWithExcel is set to 0 by default.

12.1.1.19 Disabling Creation of New Documents from Templates

You can disable the creation of new Atoll documents from templates by adding the following lines in the Atoll.ini file:

EnableNewDocFromTemplate is set to 1 by default.

12.1.1.20 Blocking Access to Macros and Add‐ins

You can block access to the Add‐ins and Macros dialogue by adding the following lines in the Atoll.ini file:

EnableMacrosAddins is set to 1 by default.

12.1.1.21 Disabling Saving and Opening ZIP Files

You can block access to the File > Save to Zip and File > Open From Zip menus by adding the following lines in the Atoll.ini file:

EnableZip is set to 1 by default.

12.1.1.22 Enabling Notification for Donor Transmitter Parameter Modifications

Atoll can notify you whenever a donor transmitter parameter, which has an impact on a repeater, is modified. To activate thenotification, add the following lines in the Atoll.ini file:

CheckImpactOnRepeaters is set to 0 by default, which means that no notifications are displayed.

12.1.1.23 Setting the Display Precision of Floating Point Values

Most floating point values in Atoll are formatted for displaying two digits after the decimal point. Such formatted floatingpoint values include thresholds and power values in dBm. However, in case of documents connected to databases (other thanMS Access), some non‐formatted floating point values can be displayed with too many digits after the decimal point.

You can set the display precision for non‐formatted floating point values in Atoll dialogues and tables. For example, in orderto display two digits after the decimal point, you can add the following lines in the Atoll.ini file:

This option applies to all non‐formatted floating point parameters in Atoll, i.e., excluding geographic coordinates andformatted floating point values.

NbDecimals is set to ‐1 by default. This corresponds to maximum precision, i.e., all the digits after the decimal point availablein the database are displayed.

[Export]

AutoOpenWithExcel = 1

[GUIUserRights]

EnableNewDocFromTemplate = 0

[GUIUserRights]

EnableMacrosAddins = 0

[GUIUserRights]

EnableZip = 0

[Transmitter]

CheckImpactOnRepeaters = 1

[Grids]

NbDecimals = 2

153


12.1.1.24 Changing the Path to Linked Geo Data Files

You can change the path to a linked geographic data file by clicking the Find button in the Properties dialogue of the file. Bydefault, the Find button in the Properties dialogue is available only for missing geographic data files, i.e., the linked files thatAtoll is unable to locate and load. However, you can enable the Find button even for available geographic data files by addingthe following lines in the Atoll.ini file:

FindGeoButtonAlwaysActive is set to 0 by default. This option can be useful when you have changed the location of ageographic data file, and you wish to change the path to the new location.

12.1.1.25 Exporting/Importing Vector Data with a Display Configuration File

When you export vector data from an Atoll document, you can simultaneously export the corresponding display configurationfile (CFG) of the edited vector layer by adding the following lines in the Atoll.ini file. The exported display configuration file willhave the same file name and will be saved in the same directory as the exported vector‐format file.

VectorDisplayConfigurationCompanionFile is set to 1 by default. When you import vector data in an Atoll document, the sameoption enables you to simultaneously import the corresponding display configuration file (CFG). The display configuration filewill 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.

12.1.1.26 Using Only Visible Geo Data in Prediction Reports

By default, Atoll takes into account all the geographic data when generating prediction reports, whether the geographic datais visible on the map or not. You can change the default behaviour for population, traffic, and generic geographic data byadding the following lines in the Atoll.ini file:

ReportObeysVisibility is set to 0 by default.

12.1.1.27 Exporting BMP, TIF, and PNG Files with a TAB Reference File

When exporting BMP, TIF, and PNG files, Atoll can export the georeference information in a TAB file instead of the defaultrespective World files (BPW or BMW for BMP, TFW for TIF, and PGW for PNG). If you want Atoll to export the georeferenceinformation in a TAB file when you export in BMP, TIF, and PNG formats, add the following lines in the Atoll.ini file:

GeorefWithTAB is set to 0 by default.

12.1.1.28 Co‐Planning: Linking the Sites Folder

You can link the Sites folder, in addition to the Transmitters and Predictions folders, of a document to another (main)document using the File > Link With command by adding the following lines in the Atoll.ini file:

LinkSites is set to 0 by default.

[Geo]

FindGeoButtonAlwaysActive = 1

When changing the path to a linked geographic data file, you must provide the new pathto the same file. This option does not allow linking to another file instead. In order to linkto another file, you must follow the normal file import procedure.

[Geo]

VectorDisplayConfigurationCompanionFile = 1

[Geo]

ReportObeysVisibility = 1

[RasterExport]

GeorefWithTAB = 1

[CoPlanning]

LinkSites = 1

154


12.1.1.29 Disabling Normalisation of MIF/TAB Vector Files

When importing vector files, Atoll normalises all the vectors in the files based on the convention that a vector whose verticescoordinates are defined clockwise creates a filled polygon, and a vector whose vertices coordinates are defined counter‐clockwise creates a hole. MapInfo vectors do not follow the same convention, and hence their normalisation at the time ofimport can take a long time. If you want to disable this normalisation when importing MIF and TAB vector files, add thefollowing lines in the Atoll.ini file:

DisableNormalization is set to 0 by default.

12.1.1.30 Adding the Duplicate Site to the Original Site’s Site List

When you duplicate a site, you can choose to add the duplicate site to the site list (if any) of the original site by adding thefollowing lines in the Atoll.ini file:

AddToSiteListOnDuplicate is set to 0 by default.

12.1.1.31 Using Only Visible Clutter Classes in Interference Prediction Reports

By default, Atoll takes into account all the clutter classes when generating reports on interference‐based coveragepredictions, whether the clutter classes are visible on the map or not. You can change the default behaviour by adding thefollowing lines in the Atoll.ini file:

OnlyVisibleClassesInInterferenceReport is set to 0 by default. The visibility of clutter classes on the map can be managedthrough the Display tab of the Properties dialogue of the Clutter Classes folder. Using this option, you can exclude clutterclasses which are not relevant in interference prediction reports, for example, water.

12.1.1.32 Displaying % of Covered Clutter Classes w. r. t. the Focus Zone in Reports

In coverage prediction reports, Atoll displays the percentages of covered clutter classes with respect to the total surface areaof all the clutter classes covered by the prediction. If you want Atoll to display the percentages of covered clutter classes withrespect to the total surface area of all the clutter classes within the Focus Zone, add the following lines in the Atoll.ini file:

PerClassPercentagesRelativeToCoverageInReport is set to 1 by default.

12.1.1.33 Displaying % of Covered Traffic Classes w. r. t. the Focus Zone in Reports

In coverage prediction reports, Atoll displays the percentages of covered environment traffic classes with respect to the totalsurface area of all the environment traffic classes covered by the prediction. If you want Atoll to display the percentages ofcovered environment traffic classes with respect to the total surface area of all the environment traffic classes within theFocus Zone, add the following lines in the Atoll.ini file:

PerClassPercentagesRelativeToCoverageInReport is set to 1 by default.

12.1.1.34 Synchronising Private and Shared Path Loss Matrices

When calculations are run, Atoll verifies whether the shared and private path loss matrices are valid. If the shared path lossmatrices are valid,

• Atoll deletes any corresponding invalid private path loss matrices and uses the valid shared ones for calculations ifAtoll.ini contains the following lines:

[MITAB]

DisableNormalization = 1

[Site]

AddToSiteListOnDuplicate = 1

[Clutter]

OnlyVisibleClassesInInterferenceReport = 1

[Clutter]

PerClassPercentagesRelativeToCoverageInReport = 0

[Traffic]

PerClassPercentagesRelativeToCoverageInReport = 0

155


• Atoll deletes any corresponding valid and invalid private path loss matrices and uses the valid shared ones forcalculations if Atoll.ini contains the following lines:

If you have private path loss matrices tuned using measurement data, setting FullResyncPrivShared to 1 will makeAtoll automatically delete them when calculations are run. You should set FullResyncPrivShared to 0 when workingwith tuned private path loss matrices.

FullResyncPrivShared is set to 1 by default.

12.1.1.35 Selecting the Logo 2 Check Box by Default in Print Setup

Print setup parameters are stored in the Atoll documents, and you can save the print setup parameters in CFG files (see "PrintSetup Configuration" on page 141). If you wish to have the Logo 2 check box selected by default for any new Atoll document,add the following lines to the Atoll.ini file:

LogoFooterChecked is set to 0 by default.

12.1.1.36 Filtering Predictions by Technology When Reading the XML Studies File

In the XML studies file, some common CDMA coverage predictions can be available for both CDMA2000 and UMTS, or somecommon OFDMA coverage predictions can be available for both WiMAX and LTE. If you wish to filter the customisedpredictions stored in the XML studies file by their technology, e.g., separate the WiMAX and LTE coverage predictions, andonly load the predictions specific to the technology of the current active Atoll document, add the following lines in the Atoll.inifile:

CustomStudiesFilteredByTechno is set to 0 by default. This option is only relevant for reading the XML studies file. Atoll alwayswrites the technology type in the XML studies file when customised coverage predictions are saved in it.

12.1.1.37 Enabling Event Viewer Messages for MapInfo File Import/Export

You can enable the display of Event Viewer information, warning, or error messages related to MapInfo files by adding thefollowing lines in the Atoll.ini file:

EnableMessages is set to 0 by default, and Atoll does not display any messages related to MapInfo file import and export.

12.1.1.38 Setting the Resolution of Population Maps in Coverage Prediction Reports

Atoll uses the default resolution, defined in the Predictions folder’s Properties dialogue, for rasterisation of the populationmaps. In order to use a different resolution for higher or lower precision, you can add the following lines in the Atoll.ini file:

Where X is the resolution for the conversion of population map vectors into raster.

[Pathlosses]

FullResyncPrivShared = 0

[Pathlosses]

FullResyncPrivShared = 1

[Print]

LogoFooterChecked = 1

[Studies]

CustomStudiesFilteredByTechno = 1

[MITAB]

EnableMessages = 1

[Population]

ReportResolution = X

If you set ReportResolution to a very precise (low) value, the performance (calculationspeed) can be considerably decreased depending on the size of the population maps inthe document. It is recommended to set this parameter to an optimum value, i.e., justprecise enough to get the required accuracy.

156


12.1.1.39 Setting the Precision in Coverage Prediction Reports

You can set the precision of the floating point values displayed in the absolute value columns of coverage prediction reportsby adding the following lines in the Atoll.ini file:

Where X is the number of digits following the decimal.

You can set the precision of the floating point values displayed in the percentage value columns of coverage prediction reportsby adding the the following lines in the Atoll.ini file:

Where X is the number of digits following the decimal.

12.1.1.40 Including Pixel‐free Ranges in Coverage Prediction Reports

By default, the ranges which do not contain any pixels do not appear in the coverage prediction reports. You can include theseranges in coverage prediction reports by adding the following lines in the Atoll.ini file.

12.1.1.41 Changing Hot Spot Reference Surface in Prediction Reports

In a coverage prediction report, Atoll displays the percentage of hot spots covered by each coverage layer (display thresholds)with as reference the hot spot surface area covered by the whole prediction. If you want Atoll to display the percentage ofhot spots covered by each coverage layer (display thresholds) with as reference the hot spot surface area, add the followinglines in the Atoll.ini file:

12.1.1.42 Exporting Only Visible Value Interval Layers of Coverage Predictions

By default, Atoll exports all the layers (levels) of a coverage prediction being exported. For some coverage predictions(coverage predictions displayed by value intervals and not by discrete values, excluding GSM coverage predictions by codingschemes, throughput, and CQI), you can export only the visible levels by adding the following lines in the Atoll.ini file:

ExportOnlyVisibleLevels is set to 0 by default, which means that when any coverage prediction is exported, Atoll exports allits levels, visible or not.

12.1.1.43 Avoiding Overlapping Pixels in Best Server Coverage Prediction

In best server coverage predictions, i.e., Coverage by Transmitter with option "Best server" and a margin of 0 dB, some pixelscan be covered by more than one transmitter if the received signal level from two or more transmitters is exactly the same.To avoid this, add the following lines in the Atoll.ini file:

By default, NoOverlapOnBestServer is set to 0. When NoOverlapOnBestServer is set to 1, Atoll arbitrarily selects one of thebest servers on such pixels. This option can be useful, for example, when calculating population statistics based on a best

[Studies]

ReportDecimalPlacesAbsolute = X

[Studies]

ReportDecimalPlacesPercent = X

[Studies]

ShowIntervalsWithNoCoverageInReport = 1 # (Default=0)

[Studies]

UseFullHotSpotSurfaceOnReport = 1 # "1" = activated (Default)

[Studies]

ExportOnlyVisibleLevels = 1

Atoll exports only visible coverage predictions. If a coverage prediction consists of onlyone level, the visibility check box of that level also controls the visibility check box of theprediction itself. This means that if the visibility check box of the only level of such aprediction is cleared, the prediction will itself be hidden and will not be exported.

[Studies]

NoOverlapOnBestServer = 1

157


server coverage prediction. When a pixel is covered by more than one best server, the population belonging to that pixel iscounted as many times as the number of best servers, which can give erroneous percentages of covered population.

12.1.1.44 Setting the Minimum ATL File Size Requiring Compression

You can set the file size above which Atoll should compress data in ATL files by adding the following lines in the Atoll.ini file:

Where X is the file size in MB. Atoll will compress the ATL file if it is larger than X. By default, StartSizeInMB is set to 800.

12.1.1.45 Loading, Activating, and Setting Add‐ins as Visible

Installed add‐ins are automatically loaded by Atoll and appear in the Add‐ins and Macros dialogue. You can change thisdefault behaviour for each individual add‐in as follows:

• If you want an add‐in neither to be loaded (i.e., deactivated) nor be available in the Add‐ins and Macros dialogue, addthe following lines in the Atoll.ini file:

• If you want an add‐in to be loaded, activated, and accessible in the Add‐ins and Macros dialogue for activation/deactivation, add the following lines in the Atoll.ini file:

• If you want an add‐in to be loaded and activated, but only shown in the Add‐ins and Macros dialogue for information(impossible to deactivate), add the following lines in the Atoll.ini file:

• If you want to set an add‐in to be mandatory for Atoll, add the following lines in the Atoll.ini file:

Any add‐in set to option 3 will be loaded and activated, but only shown in the Add‐ins and Macros dialogue forinformation (impossible to deactivate). Atoll will not run if it is unable to load this add‐in.

Add‐in Name is the name of the add‐in as it appears in the Add‐ins and Macros dialogue in Atoll. Atoll fails to start if for somereason it is unable to load an add‐in whose status is set to 3. The default status for add‐ins is 1.

12.1.1.46 Defining Online Map URLs

Online maps allow you to display map data from the Internet in Atoll. You can define a list of online map URLs in the Atoll.inifile as follows:

You can define any number of online map URLs by incrementing the index N. These URLs will be available in the online mapimport dialogue in Atoll.

[Compression]

StartSizeInMB = X

[Add-ins]

Add-in Name = 0

[Add-ins]

Add-in Name = 1

[Add-ins]

Add-in Name = 2

[Add-ins]

Add-in Name = 3

[OnlineMaps]

Name1 = City1

URL1 = http://...

Name2 = City2

URL2 = http://...

...

NameN = CityN

URLN = http://...

158


12.1.1.47 Changing the Default Cache Location for the Loaded Map Tiles

The map tiles that you load into Atoll are stored in a specific cache directory named after the corresponding tile server. Bydefault, the location of this cache is "%TEMP%\OnlineMaps". You can change this location by adding the following lines in theAtoll.ini file:

12.1.1.48 Managing Carriage Returns in Imported TXT/CSV Files

By default when you export the content of a table to a TXT/CSV format, the carriage returns are replaced by spaces in the textfields. You can avoid this by adding the following lines in the Atoll.ini file:

When NewLineEscapeSequence is set to "\n", the carriage returns are replaced by "\n" in the exported files and each "\n" isreplaced by a carriage return when the files are imported.

If you want to go back to the previous behaviour, set NewLineEscapeSequence to " " (space). In this case, the carriage returnsare not replaced by a space when a file is imported.

12.1.1.49 Deleting the Filtering Zone on Removing Filters From Tables

By default, when you remove filters applied to tables, Atoll keeps the filters applied on through the map using the filteringzone. If you wish to remove the filtering zone as well when removing filters from tables, add the following lines in the Atoll.inifile:

KeepFilterZoneOnRemoveFilter is set to 1 by default.

12.1.2 GUI Options

12.1.2.1 Defining the Parameters for the Default Sites Symbol

You can define the parameters of the default symbol used for displaying sites on the map through the Atoll.ini file. You candefine the parameters as follows:

The default sites symbol is used when a new document is created in Atoll. To know the name of the font to use, and to set thesymbol, you can use the Windows’ Character Map tool. You can use the copy/paste features to set the symbol in the Atoll.inifile.

Example:

12.1.2.2 Using a Unique Symbol for Remote Antennas

By default, remote antennas are displayed using the same symbol on the map as transmitters. You can use a unique, non‐modifiable symbol for remote antennas on the map by adding the following lines in the Atoll.ini file:

[OnlineMaps]

TilesCachePath = <new path>

[Export]

NewLineEscapeSequence = "\n"

[Settings]

KeepFilterZoneOnRemoveFilter = 0

[SitesSymbol]

FontName = Name of the font

Symbol = Character used for the site symbol from the character set of the font

Size = Character size in number of pts

Color = Colour of the symbol

[SitesSymbol]

FontName = Wingdings

Symbol = ¤

Size = 12

Color = 0

159


FrozenSymbol is set to 0 by default. When you set FrozenSymbol to 1, the remote antenna symbol will be fixed and no longerlinked with the transmitter symbol.

12.1.2.3 Keeping Transmitter Symbols From Changing on Search

When using the Search Tool, all the transmitters that do not fulfil the search criteria are displayed as grey lines on the map. Ifyou want these transmitters to keep their original symbols, add the following lines in the Atoll.ini file:

ChangeSymbolOnSearch is set to 1 by default.

12.1.2.4 Displaying Filled Symbols for Inactive Transmitters on the Map

By default, Atoll empties the symbols of inactive trasnmitters, repeaters, and remote antennas on the map. If you wish todisplay filled symbols for inactive transmitters, repeaters, and remote antennas on the map, add the following lines in theAtoll.ini file:

EmptySymbolWhenInactive is set to 1 by default.

12.1.2.5 Refreshing the Display Automatically When a New Station is Dropped

You can have Atoll refresh the display automatically each time a new station or a group of stations is dropped on the map byadding the following lines in the Atoll.ini file:

AutoSynchronizeDisplay is set to 0 by default.

12.1.2.6 Hiding Information Displayed in the Status Bar

Using compressed geo data formats (TIFF, Erdas Imagine, ECW) can cause performance loss due to real‐time decompression.Performance can be improved by either hiding the Status Bar or by hiding some of the information displayed in the Status Bar(altitude, clutter class, or clutter height). To hide information in the Status Bar, add the following lines to the Atoll.ini:

DisplayZ, DisplayClutterClass and DisplayClutterHeight respectively refer to the display of altitude, clutter class, and clutterheight.

12.1.2.7 Displaying Date and Time in the Event Viewer

You can instruct Atoll to display the date, and time with milliseconds in the Event viewer. To display this information, add thefollowing lines to the Atoll.ini file:

[RemoteAntennas]

FrozenSymbol = 1

[Transmitter]

ChangeSymbolOnSearch = 0

[Transmitter]

EmptySymbolWhenInactive = 0

[Transmitter]

AutoSynchronizeDisplay = 1

[StatusBar]

DisplayZ = 0

DisplayClutterClass = 0

DisplayClutterHeight = 0

[EventsObserver]

milliseconds = 1

date = 1

160


12.1.2.8 Setting the Maximum Number of Lines in Coverage Prediction Tool Tips

If you have more than one coverage prediction displayed on the map, the tool tips display the tip text for all the coveragepredictions available at a pixel up to 30 lines by default. You can change this default number of tool tip text lines through thefollowing option in the Atoll.ini file:

X is the number of lines to display in the tool tips. By default, MultiplePlotsTipTextLines is set to 30. If you set it to a very largevalue, however, the tool tip might not display correctly.

12.1.2.9 Changing the Display for Downlink Smart Antenna Results

The downlink smart antenna simulation results, i.e, the angular distributions of downlink transmitted power density,calculated during Monte Carlo simulations using the Optimum Beamformer and Conventional Beamformer can be displayedin two different ways. By default, these diagrams represent the average array correlation matrices and are symmetric aboutthe x‐axis (same on the front and back). If you want to display these diagrams taking into account the antenna pattern of thesingle antenna element, add the following option in the Atoll.ini file:

DrawSingleElementPattern is set to 0 by default, in which case the displayed diagram is . When you set

DrawSingleElementPattern to 1, the diagram displayed will represent .

12.1.2.10 Adding Exposure Analysis to the List of Multi‐RAT Coverage Predictions (Hidden en 3.2.0.02, ces infos sont dans TN013)

The maximum permissible exposure (MPE) to electromagnetic fields (EMF) can be analysed in single‐RAT and multi‐RAT docu‐ments. A multi‐RAT exposure analysis is a combination of the corresponding single‐RAT exposure analyses.

You can include "Exposure Analysis" in the list of coverage predictions available in single‐RAT and multi‐RAT documents byadding the following lines in the Atoll.ini file:

When Exposure Analysis predictions are enabled, "Exposure Analysis" appears in the list of predictions in all types of single‐RAT (except TD‐SCDMA and Wi‐Fi) and multi‐RAT (including 3GPP2) documents.

12.1.2.11 Displaying Coverage Prediction Comments in the Legend Window

You can display the contents of the Comments box of coverage prediction properties in the Legend window by adding thefollowing lines in the Atoll.ini file:

The comments are displayed between the name of the coverage prediction and the thresholds. CommentsInLegend is set to0 by default.

12.1.2.12 Displaying Leading Zeros in the CELL_IDENTITY Field

By default, Atoll does not display leading zeros in the CELL_IDENTITY field of the Transmitters table in GSM and the Cells tablesin UMTS, CDMA2000, and TD‐SCDMA. For example, cell identity "00678" is displayed as "678". If you want Atoll to displayleading zeros, you must set the minimun number of digits the CELL_IDENTITY field should contain by adding the following linesin the Atoll.ini file:

Where X is the number of digits that the CELL_IDENTITY field should contain. For example, CellIDNbDigits = 5 means that Atollwill display at least five digits in the CELL_IDENTITY field by adding leading zeros where required. This means that Atoll willdisplay "00678" in the above example. However, if the CELL_IDENTITY field contains a number that has more than X digits, all

[Studies]

MultiplePlotsTipTextLines = X

[SAModel]

DrawSingleElementPattern = 1

SH

RAvg S

gn SH

RAvg S

[Studies]

ExposureStudy = 1

[Studies]

CommentsInLegend = 1

[Display]

CellIDNbDigits = X

161


the digits will still be displayed. For example, all seven digits in "9376562" will still be displayed even if CellIDNbDigits is set to5.

12.1.2.13 Making the Antenna Additional Electrical Downtilt Accessible

By default, Atoll does not allow modification of the Additional Electrical Downtilt for transmitters, station templates,repeaters, and remote antennas. To make this parameter accessible in the GUI, add the following lines in the Atoll.ini file:

REDTDisplay is set to 0 by default.

12.1.2.14 Increasing the Width of the Clutter Description Pane in the Status Bar

You can increase the width of the clutter description pane in the Status bar (bottom right), to display the descriptions ofclutter classes with long names, by adding the following lines in the Atoll.ini file:

ClutterPaneWidth is set to 100 by default, which means 100% of its default width. To increase the width to, for example, twicethe original width, set ClutterPaneWidth to 200.

12.1.2.15 Hiding the Technology Name in the Title Bar

The names of the technologies corresponding to the current active document are displayed in the title bar. You can hide thetechnology names by adding the following lines in the Atoll.ini file:

UseTechnoName is set to 1 by default.

12.1.2.16 Displaying Objects’ Discrete Values with User‐defined Colours

When objects are displayed by discrete values, Atoll applies colours automatically on 36‐colour cycles. As opposed to shading,this is particularly useful to distinguish neighbouring zones which have very close colour values. By setting some options in theAtoll.ini file, you can configure Atoll to loop on as many user‐defined colours as you want.

For instance if you insert the following lines in the Atoll.ini file, Atoll will loop on 12 colour values (PaletteColor0 throughPaletteColor11) the next time you display objects by discrete values.

You can also override user‐defined colours, if any, and force shading (from red to blue) by setting the following option in theAtoll.ini file.

[Antenna]

REDTDisplay = 1

[StatusBar]

ClutterPaneWidth = X

[DocTitle]

UseTechnoName = 0

[Display]

PaletteColor0=141 211 199












[Display]

DiscreteValueColoring=Shading

162


12.1.2.17 Displaying Vertical Beamwidth in Profile Analysis

You can configure Atoll to display the vertical beamwidth (‐3 dB upper and lower limits in the vertical plane) as well as theactual tilt in the geographic profile view of the Profile Analysis tool. You can configure this display mode by adding thefollowing lines in the Atoll.ini file:

The geographic profile displays clutter classes and the Fresnel ellipsoid by default. When this option is enabled, threeadditional lines are added to the diagram:

• Thick yellow and green lines: These lines indicate the upper and lower ‐3 dB beamwidth limit in the vertical plane.• Thick blue line: This line indicates the axis of minimal loss, which coincides with the actual tilt axis of the antenna

(combining the physical and electrical tilt).

The vertical beamwidth is widest in the azimut axis of the antenna. If you move the position of the Point Analysis tool off ofthe antenna azimut axis, the vertical beamwidth diminishes and disappears when the vertical beamwidth loss exceeds ‐3 dB.

12.1.3 Distributed Calculation Server Options

12.1.3.1 Detecting and Listing Distributed Calculation Servers

You can use Atoll to detect distributed calculation servers and list them in the Atoll.ini file. A computer, serving as a distributedcalculation server, can run up to 10 instances of Atollsvr, the distributed calculation application. The distributed calculationserver names can be listed in the Atoll.ini file in the following format:

Here Server1Name and Server2Name refer to the names of the computers being used as calculation servers, and N is a numberfrom 0 to 9. This means, for example, that Server1 can run up to 10 instances of the distributed calculation application, andall these instances can be listed in the NumberedServers option (Server1Name0; Server1Name1; Server1Name2; ...). Usingthis option, you can assign distributed calculation servers to different groups of users working with two different Atoll.ini files.For example, user group 1 can use Server1Name0 to Server1Name4, and group 2 can use Server1Name5 to Server1Name9.

If an error occurs on any of the distributed calculation servers, Atoll transfers the calculations back to the local computer.However, to avoid memory saturation, Atoll uses one thread on the local computer and calculates the path loss matrices oneby one. It does not attempt creating more than one thread.

12.1.3.2 Setting the Distributed Calculation Server Priority

By default, the Atoll distributed calculation server (AtollSvr.exe) runs with a normal process priority. However, it is possibleto modify its priority, in both service and application modes, and set it higher or lower. You can do this by adding the followinglines in the Atoll.ini file:

You can choose between 4 possible priority levels:

• ‐1: Below Normal priority• 0: Normal priority• 1: Above Normal priority• 2: High priority

This option works for both, application and service, modes of the distributed calculation server.

12.1.3.3 Modifying the Default Detection Time‐out

The default time‐out (2 seconds) for locating calculation servers within the network might be too short in certain cases. Youcan increase this time‐out by adding the following lines to the Atoll.ini file:

[GeoProfileDisplay]

Beamwidth=1

[RemoteCalculation]

NumberedServers = Server1NameN; Server2NameN; ...

[RemoteCalculation]

AtollSvrPriority = -1, 0, 1 or 2

• The distributed calculation server (AtollSvr.exe) must be restarted in order to takeinto account the new value for the AtollSvrPriority option.

• The Realtime priority mode has not been implemented for reasons of stability.

163


In this example, the detection time‐out is set to 5000 ms.

12.1.4 Licence Management Options

12.1.4.1 Setting an Alarm for the Licence End Date

You can set a warning message about the licence end date to appear a certain number of days before this date. The Atoll.inifile should contain the following lines:

X is the number of days prior to the temporary licence end date you want Atoll to warn you. When no information is given inthe Atoll.ini file, Atoll warns the user 30 days before the licence end.

12.1.4.2 Blocking Access to Technology Modules

This option is useful when working with a floating licence management system where a floating licence server manages anddistributes tokens between several Atoll users. This option can also be useful in setting different licence rights to users.

To block access to the different technology modules, add the corresponding lines in the [License] section of the Atoll.ini file:

You can also block access to GSM, UMTS, or LTE radio access technologies in 3GPP Multi‐RAT documents using these options.

12.1.4.3 Blocking Access to ACP and AFP Modules

You can block access to the ACP and AFP licences for users or user groups. To block access to ACP or AFP modules, add thecorresponding lines in the [License] section of the Atoll.ini file:

In order to carry out a combined GSM and UMTS optimisation using the ACP module, you must have access to both ACPmodule licences, i.e., ACP_GSM and ACP_UMTS must both not be set to 0.

In order to carry out a Wi‐Fi optimisation using the ACP module, you must have access to the WiMAX ACP module licence, i.e.,ACP_WiMAX must not be set to 0.

In order to carry out a Wi‐Fi frequency planning using the AFP module, you must have access to the WiMAX AFP modulelicence, i.e., WiMAX_AFP must not be set to 0.

[RemoteCalculation]

DetectTimeOut = 5000

[License]

TimeBombNotice = X

To block access to Add

GSM GPRS EDGE GSM = 0

UMTS HSPA UMTS = 0

CDMA2000 CDMA = 0

TD‐SCDMA TD‐SCDMA = 0

WiMAX and Wi‐Fi WiMAX = 0

LTE LTE = 0

Microwave Radio Links MW = 0

Backhaul BH = 0

Measurements Measures = 0

[License]

ACP_GSM = 0

ACP_UMTS = 0

ACP_LTE = 0

ACP_WiMAX = 0

GSM_AFP = 0

LTE_AFP = 0

WiMAX_AFP = 0

164


12.1.4.4 Changing the NetHASP Licence Manager Idle Time Setting

The floating licence manager has an idle time parameter with 10 minutes as default value. Atoll sessions consuming floatinglicences from a licence manager server reset this idle time parameter to its initial value every minute. If you are performingtime‐consuming calculations on Atoll connected to a floating licence server, and consuming a licence, it might occur that Atolldoes not get the chance to reset the idle time value to its initial value. In this case, a new Atoll session can steal the licenceactually allocated to an already running session. This might cause problems in the case where all the licences are used, theAtoll session performing heavy calculations does not get the chance to initialise the idle time parameter for its licence, and anew Atoll session is launched on another computer. In such a situation, the floating licence manager considers that thealready running session has been inactive or closed, and the licence allocated to the already running Atoll session is allocatedto the new session.

You can modify the default idle time parameter value to a higher value to avoid this effect. To set a different default value forthe idle time parameter, add the following lines to the Atoll.ini file:

Where X is the time in minutes. The idle time can be set to infinity by defining IdleTime = 0.

12.1.5 Database Options

12.1.5.1 Checking Data Integrity After Database Upgrade and Data Refresh

Atoll asks you to perform a database integrity check when you open an Atoll document connected to a database that wasrecently upgraded to a new version, or when you refresh data in an Atoll document from the database. It is recommeded toperform the proposed data integrity check.

However, if you do not wish to check the data integrity, add the following lines in the Atoll.ini file:

ControlIntegrity is set to 1 by default.

12.1.5.2 Automatically Running a Database Integrity Check at Open or Refresh

This option automatically performs a data integrity check when opening a document from a database or refreshing data froma database. To turn this feature on, you have to add the following lines in the Atoll.ini file:

If this option is set to 1, Atoll performs SELECT filters in the database to guarantee data integrity. This feature enables selectiondirectly in the database in order to avoid integrity problems in the future.

12.1.5.3 Allowing Null Entries in Non‐nullable Custom Fields

By default, to prevent from archival issues and crashes, Atoll does not support null entries in non‐nullable custom fields ofconnected documents. Failing to fill a non‐nullable custom field when you add a new record via a record template, a fileimport, or table edition, will return a message in the form "’NameOfField’ column cannot be null". To avoid this, you can definethe custom field as nullable in the database, use a default value in the field definition, or create the field and fill it in therelevant template.

As a last resort, you can force the previous behaviour of Atoll by adding the following lines in the Atoll.ini file:

12.1.5.4 Automatically Running GSM Subcell Audit at Open or Refresh

The following options automatically perform subcell audit when opening a GSM document from a database or refreshing datafrom a database.

To automatically audit the consistency of redundant values in the transmitters, subcells, and TRXs tables without fixing anyproblems found, add the following lines in the Atoll.ini file:

[License]

IdleTime = X

[Refresh]

ControlIntegrity = 0

[Database]

IntegrityChecker = 1

[Database]

AllowNullRecordsForNonNullableCustomFields = 1 #default=0

165


To automatically audit the consistency of redundant values in the transmitters, subcells, and TRXs tables and fix any problemsfound, add the following lines in the Atoll.ini file:

To automatically audit the compatibility of the main subcell values without fixing any problems found, add the following linesin the Atoll.ini file:

To automatically audit the compatibility of the main subcell values and fixi any problems found, add the following lines in theAtoll.ini file:

SubCellAuditConsistency and SubCellAuditMainValues are set to 0 by default.

12.1.5.5 Modifying the Default Database Connection Time‐out

The ODBC driver has a default command timeout value which could be too short in some cases, such as slow networks. Youcan change this default timeout value and set a higher value if you encounter problems, during execution of commands onthe database, which might be related to timeout. To change the value of the command timeout parameter of the ODBC driver,add the following lines in the Atoll.ini file:

Where X is the timeout value in an integer number of seconds. After X seconds, the command is considered too long toexecute. If you set CommandTimeout = 0, there will be no time limit for the execution of the command.

12.1.5.6 Making Atoll Case‐Sensitive for Database Import From Planet

The network data import from a Planet database into Atoll is not case sensitive by default. You can set this import to casesensitive by adding the following lines in the Atoll.ini file:

Case sensitive means that "Site0" will be considered different from "site0" during import.

12.1.5.7 Setting the Sign for KClutter When Importing Data From Planet EV

Planet EV uses the opposite sign for the Kclutter parameter with respect to Planet DMS. If you are importing data from Planet

EV, you might have to change the sign of this parameter. You can instruct Atoll to change the sign for Kclutter when importing

data from Planet EV by adding the following lines to the Atoll.ini file:

ChangeKclutterSign is set to 0 by default.

12.1.5.8 Enabling/Disabling Password Prompt at Archive

You can instruct Atoll to prompt the user for password before archiving data in a database. If you want Atoll to ask the userto enter the username and password once per Atoll session, add the following lines in the Atoll.ini file:

[Database]

SubCellAuditConsistency = 1

[Database]

SubCellAuditConsistency = 2

[Database]

SubCellAuditMainValues = 1

[Database]

SubCellAuditMainValues = 2

[Database]

CommandTimeout = X

[PlanetImport]

SensitiveCase = 1

[PlanetImport]

ChangeKclutterSign = 1

[Database]

PromptOnArchive = 1

166


PromptOnArchive = 1 is the default setting used if this option is not provided in the Atoll.ini file. The user will be prompted forpassword when he tries to archive data in the database for the first time during an Atoll session.

If you want Atoll to ask the user to enter the username and password for every refresh and archive, set:

If you want to disable the prompt for password, set:

12.1.5.9 Archiving Data to Databases Using Transactions

Atoll supports transactions for archiving data to databases. This approach ensures that users always get consistent data whenrefreshing their documents with data from the database, even when another user is archiving his modifications at the sametime. By default, Atoll uses transactions for archiving data, however you can disable the transaction mode for Atoll by addingthe following lines to the Atoll.ini file:

UseTransaction is set to 1 by default.

12.1.5.10 Keeping Separate Work and Master Path Loss Directories

When synchronising a master project with a work project, the shared path loss directory is also updated. This can cause thework and master projects to overwrite each other’s shared folder. From an operational standpoint, it is often preferable tokeep two different path loss directories: one for the master project and a second for the work project.

When the [OverwriteSharedFolderPath] option is set to "0", Atoll does not overwrite the shared path loss directory.

12.1.5.11 Enabling Partial Refresh from Recently Upgraded Databases

When you open an Atoll 2.8.x document connected to a database that has been upgraded to Atoll 3.1.0, Atoll automaticallyperforms a full refresh, i.e., loads all the data from the database, when upgrading the document to the new version. If youwish to enable partial refresh of data from the upgraded database (not recommended as it can cause data integrity problems),add the following lines in the Atoll.ini file:

EnablePartialRefreshInMigration is set to 0 by default.

12.1.5.12 Setting the Type of Database Being Used

You can set the type of database being used by adding the following lines in the Atoll.ini file:

Where providername can be "Access", "SQLServer", or "Oracle". When this option is set, Atoll uses the defined database typeand does not display the database selection dialogue that appears when creating a new document from an existing databaseor when exporting a document to create a new database.

PromptOnArchive = 2

PromptOnArchive = 0

• Username and password are stored in the ATL file in an encrypted form.• This option is only appropriate if the database connection string contains a password.

[Database]

UseTransaction = 0

Before modifying this option, make sure that the database server is correctly configuredfor transactions.

[Database]

OverwriteSharedFolderPath = 0 # "1" is default: path loss directory is overwritten

[MajorVersionChange]

EnablePartialRefreshInMigration = 1

[Database]

ExclusiveProvider = providername

167


12.1.6 Common Calculation Options

12.1.6.1 Setting the Antenna Patterns Modelling Method

In order to set the modelling method for antenna patterns, the Atoll.ini file can contain the following information:

AngleCalculation values of 2000 and 3000 are only valid for the Forsk’s propagation model library, i.e., the propagation modelsavailable with Atoll by default. Setting AngleCalculation = 2000 makes the propagation models calculate "unmasked" pathlosses, i.e., path losses without considering the transmitter antenna patterns. Setting AngleCalculation = 3000 makes thepropagation models calculate the angles of incidence to each pixel instead of path loss.

Catalog Vertical Diagram Orientation is a display option. It enables rotating the antenna’s vertical diagram to a user‐definedangle. By default, Catalog Vertical Diagram Orientation is set to 90 meaning that the vertical diagram is displayed pointing tothe right. Setting it to 0, for example, will show the vertical diagram pointing to the top.

InterpolatePatternEvenIfOnlyOneDiagram can be used to change the way Atoll interpolates antenna pattern attenuationdiagrammes for antennas with only one diagramme available, vertical or horizontal. WithInterpolatePatternEvenIfOnlyOneDiagram = 0 (default, new method), Atoll uses the only diagramme available for bothvertical and horizontal planes. With InterpolatePatternEvenIfOnlyOneDiagram = 1 (previous method), Atoll uses thediagramme available for the plane to which it corresponds, vertical or horizontal, and an isotropic diagramme (a 0 dB circularattenuation pattern) for the plane for which no diagramme is available.

InterpolatePatternIndB sets the unit used by Atoll when it performs linear interpolations on antenna pattern attenuation.When InterpolatePatternIndB = 0 (default), interpolations are calculated in Watts. When InterpolatePatternIndB = 1 (or anyvalue other than 0), interpolations are calculated in dB leading to stronger antenna pattern attenuation.

12.1.6.2 Disabling Automatic Locking of Coverage Predictions

By default, Atoll automatically locks a coverage prediction study once it is calculated. To instruct Atoll not to lock predictionstudies automatically, these lines have to be included in the Atoll.ini file:

AutoLock is to 1 by default.

12.1.6.3 Enabling Shadowing Margin in Calculations

An average value of shadowing margin is calculated by Atoll and applied to the signal level and interference levels duringcoverage predictions and other calculations such as point analysis, automatic neighbour allocation, automatic scramblingcode and PN offset allocation, and interference matrices calculation. This average value depends on the cell edge coverageprobability that you define for the calculation and the standard deviations defined per clutter class.

In the dialogues of all the above‐mentioned calculations, the Shadowing taken into account check box is not selected bydefault. Not selecting this check box implies that the shadowing margin is neither calculated nor used in the calculations.

If you want to select the Shadowing taken into account check box by default in all the above‐mentioned dialogues, you haveto enter the following lines in the Atoll.ini file:

UseShadowing is set to 0 by default.

[Antenna]

AngleCalculation = 2000 or 3000

Catalog Vertical Diagram Orientation = 90 or angle value

InterpolatePatternEvenIfOnlyOneDiagram = 0 or 1

InterpolatePatternIndB = 0 or 1

[Studies]

AutoLock = 0

[Shadowing]

UseShadowing = 1

This option does not affect the shadowing margin calculation during Monte Carlosimulations. Monte Carlo simulations do not use an average value of the shadowingmargin depending on the cell edge coverage probability. During Monte Carlo simulations,random shadowing margin values are calculated based only on the standard deviationsdefined per clutter class.

168


In UMTS HSPA and CDMA2000 documents, you can also deactivate the calculation and use of macro‐diversity gains. For moreinformation, see "Disabling Macro‐diversity (SHO) Gains in Calculations" on page 180.

12.1.6.4 Setting a Default Value for the Cell Edge Coverage Probability

The default value of the cell edge coverage probability can be configured in the Atoll.ini file. If you enter the following lines inthe Atoll.ini file, Atoll will consider the value of the cell edge coverage probability defined in the Atoll.ini file as the defaultvalue, and will take it into account when performing point analysis, in the shadowing margins calculator, and will propose itas the default value for coverage prediction studies.

Reliability = 60 means 60 % cell edge coverage probability.

12.1.6.5 Enabling Indoor Coverage in Calculations

Indoor losses are taken into account in calculations when the Indoor Coverage check box is selected. This check box is notselected by default. If you want to select the check box by default in the properties dialogues of all the calculations, you haveto enter the following lines in the Atoll.ini file:

IndoorActivity is set to 0 by default.

12.1.6.6 Modifying the Resolution for the LOS Area Calculation Around a Site

The calculation of line of sight area around a given site uses the resolution of the geographic data as the default calculationresolution. These calculations can be time‐consuming if the geographic data is available with a very high resolution. You canset the calculation resolution to a multiple of the resolution of the geographic data by adding the following lines in the Atoll.inifile:

Where X is an integer. Therefore, setting ResolutionMultFactor to 2 will double the calculation resolution and decrease thetime required for the calculation by half.

12.1.6.7 Embedding Path Losses in New Documents

If you calculate path loss matrices for a new document that has not been saved yet, Atoll asks if you would like to save thedocument and externalise the path loss matrices or if you would like to keep the path loss matrices embedded in thedocument and save it later. You can suppress this message by adding the following lines in the Atoll.ini file:

EmbeddedByDefault is set to 0 by default.

12.1.6.8 Stopping Calculations on Error

If a problem occurs in calculating one or more path loss matrices while calculating a coverage prediction, Atoll continuesperforming the remaining calculations, and provides results even if they are not complete. If you want Atoll to stop thecalculations if there is an error, you can add the following lines in the Atoll.ini file:

ContinueOnError = 1 by default. This means that by default Atoll does not stop the calculations on error.

[Shadowing]

Reliability = 60

The value of cell edge coverage probability used for automatic neighbour allocation andinterference matrices calculation is stored in user configuration files (CFG).

[ClutterParams]

IndoorActivity = 1

[LOSArea]

ResolutionMultFactor = X

[Pathlosses]

EmbeddedByDefault = 1

[Studies]

ContinueOnError = 0

169


12.1.6.9 Warning About Prediction Validity When Display Options are Modified

Coverage predictions have to be recalculated if you modify their display options. Atoll displays a warning message when youmodify the display options for coverage predictions. To deactivate this warning message, add the following lines in the Atoll.inifile:

RecomputationWarning is set to 1 by default.

12.1.6.10 Reading Exact Altitudes From the DTM

Atoll uses either the user‐defined site altitudes from the Sites table or, if they are not defined, the site altitudes read from theDTM for the site coordinates defined in the Sites table. However, transmitters can be located at certain distances from thesite coordinates. You can set these distances of transmitters from their sites in the Transmitters table under DX and DY.

If you want Atoll to consider the exact transmitter coordinates, i.e., including DX and DY, during calculations for determiningthe transmitter height, which will be read from the DTM at the exact transmitter coordinates, you must add the following linesin the Atoll.ini file:

UseSiteAltitude is set to 1 by default, which means that the altitude used in calculations will be the one which is either readfrom the Sites table or from the DTM at the site’s coordinates, if the user‐defined altitude is not available in the Sites table.

Setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exactcoordinates of each transmitter considering the values entered for the DX and DY parameters.

The above option is also valid for microwave links. In this case, setting UseSiteAltitude to 0 means that, during calculations,Atoll will read the altitudes from the DTM at the exact coordinates of each microwave link considering the values entered forthe DX_A, DY_A, DX_B, and DY_B parameters.

12.1.6.11 Setting a Common Display Resolution For All Coverage Predictions

You can set a display resolution for each coverage prediction individually as well as a default display resolution for all coveragepredictions that you create, in the Predictions tab of the Predictions folder’s Properties dialogue. If you create a new coverageprediction, Atoll reads the default resolution from the Predictions folder’s Properties dialogue and sets that as the displayresolution for the new coverage prediction. Then, if you delete this resolution from the coverage prediction properties, anddo not enter any resolution, Atoll resets the resolution to the default value. In this way, each coverage prediction has a displayresolution defined. However, it is possible to manage a common display resolution for all coverage predictions, new orexisting, that do not have a resolution defined for them. You can switch to this option by adding the following lines in theAtoll.ini file:

Once SpecifyResolutionAfterComputation is set to 0, Atoll no longer resets the resolution to the default value for coveragepredictions that do not have a resolution defined. Atoll allows you to leave the field empty in the coverage predictionproperties, and directly reads the default resolution defined in the Predictions folder’s Properties dialogue. In this way, whenyou create coverage predictions without defining resolutions for them, you can modify the default resolution of thePredictions folder’s Properties dialogue and, therefore, change the display resolution for all the coverage predictions, new orexisting.

To return to the normal working, you can either remove the lines from the Atoll.ini file, or setSpecifyResolutionAfterComputation to 1.

12.1.6.12 Setting the Priorities for GUI and Calculations

You can set the priorities for user interface and calculations through the following option in the Atoll.ini file:

[Studies]

RecomputationWarning = 0

[Calculations]

UseSiteAltitude = 0

With UseSiteAltitude = 0, if DX and DY are 0, i.e., for transmitters and microwave linkslocated at the site coordinates, Atoll will still use the altitudes defined per site, if any, orthe altitudes from the DTM otherwise

[Studies]

SpecifyResolutionAfterComputation = 0

[RemoteCalculation]

170


Priority enables you to set the priority between calculations and user interface.

• 0: User interface has the highest priority.• 1 (default): User interface has a higher priority than calculations.• 2: User interface and calculations have the same priority.

12.1.6.13 Setting the Number of Parallel Processors and Threads

You can manage the number of processors and threads through the Atoll.ini file. The file should contain the following options:

Maximum number of processors:

• NumberOfProcessors is the maximum number of processors that can be used for calculations. If you set this option to0, Atoll will use actual number of available processors.

Maximum number of calculation threads:

• NumberOfThreadsPathloss is the maximum number of threads that can be used for path loss calculations (4 bydefault, 8 maximum)

• NumberOfThreadsSimulation is the maximum number of threads that can be used for Monte Carlo simulationcalculations (4 by default, 8 maximum)

• NumberOfThreadsStudy is the maximum number of threads that can be used for the calculation of coveragepredictions (4 by default, 8 maximum)

• NumberOfThreadsStudyTile is the maximum number of threads that can be used per coverage prediction calculation(0 by default, 8 maximum). If you set this option to 0 or 1 (recommended), Atoll will use one thread for the calculation.

• NumberOfThreadsNeighbour is the maximum number of threads that can be used for automatic neighbour allocation(4 by default, 8 maximum)

• NumberOfThreadsMicrowave is the maximum number of threads that can be used for microwave link calculations (4by default, 8 maximum)

All these options are upper limits per computer. Atoll supports a maximum of 64 parallel threads.

12.1.6.14 Disabling Parallel Calculation of Monte Carlo Simulations

For UMTS HSPA and CDMA2000 1xRTT 1xEV‐DO documents, Atoll can perform multi‐thread calculations of Monte Carlosimulations. If you want to disable the parallel calculation, add the following lines to the Atoll.ini file:

ParallelSimulations is set to 1 by default.

The parallel calculation of Monte Carlo simulations in TD‐SCDMA, WiMAX, LTE, and Wi‐Fi documents is disabled by default. Itshoud not be enabled in TD‐SCDMA documents.

12.1.6.15 Performing Calculations in Read‐Only Documents

By default, when you open a read‐only Atoll document, it is not possible to run calculations in it. If you want to run calculationsin read‐only documents, add the following lines in the Atoll.ini file:

Priority = 0, 1, or 2

[RemoteCalculation]

NumberOfProcessors = X

NumberOfThreadsPathloss = 1, 2, ..., or 8

NumberOfThreadsSimulation = 1, 2, ..., or 8

NumberOfThreadsStudy = 1, 2, ..., or 8

NumberOfThreadsStudyTile = 0, 1, 2, ..., or 8

NumberOfThreadsNeighbour = 1, 2, ..., or 8

NumberOfThreadsMicrowave = 1, 2, ..., or 8

[CDMA]

ParallelSimulations = 0

The Generator Initialisation must be set to 0 in order for the simulations to be calculatedin parallel.

[Studies]

171


If you open a document that is already open in another Atoll session, Atoll lets you open the document as read‐only.

12.1.6.16 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas

In GSM, UMTS, CDMA2000, LTE, and WiMAX documents, you can create a "Coverage by Aerial" prediction providing separatecoverage areas of transmitters, repeaters, and remote antennas.

In order to make this coverage prediction available in Atoll, add the following lines in the Atoll.ini file:

12.1.6.17 Changing the Rounding Method Used for Profile Extraction

Before Atoll2.8.0, real values for altitudes read from the DTM files were rounded down to their integer values. However, fromAtoll2.8.0 onwards, real values are rounded up or down to their nearest integer values. For example, using the previousmethod, 98.8 m was rounded to 98 m, but with the new method, it is rounded to 99 m. If you want to switch back to theprevious method, add the following lines in the Atoll.ini file:

RoundAltitudes is set to 1 by default.

12.1.6.18 Estimating Required and Used Memory Size for UMTS Simulations

Atoll can estimate the required and used memory sizes for UMTS simulations and display the estimates in the Source Traffictab of the new simulation group dialogue. Estimated memory size within the green region means low consumption, withinthe yellow region means medium consumption, within the orange region means high consumption, and within the red regionmeans very high consumption, in which case the simulations might generate an out of memory error and not complete.

To activate the memory estimation feature, add the following lines in the Atoll.ini file:

PredictSimuMemorySize is set to 0 by default which means the feature is not active.

12.1.6.19 Disabling Calculations Over NoData Values for DTM and Clutter Classes

If you don’t want Atoll to calculate path losses on the pixels located over nodata values defined in the DTM and clutter classesfiles, add the following lines in the Atoll.ini file:

By default, OptimOnNoData is set to 0. This option only works with the propagation models available with Atoll by default.

12.1.6.20 Co‐planning: Calculating Predictions in the Current Document Only

Atoll calculates all the unlocked coverage predictions in the Predictions folder of the current document and the unlockedcoverage predictions in the linked Predictions folder from another document when you click the Calculate button, press F7,or select the command from a context menu in the current document. If you want Atoll to calculate only the unlockedcoverage predictions in the Predictions folder of the current document, and not in the linked Predictions folder from anotherdocument, add the following lines in the Atoll.ini file:

ComputeLinkedPredictions is set to 1 by default.

ComputeEvenIfReadOnly = 1

[Studies]

AerialStudy = 1

[Calculations]

RoundAltitudes = 0

[CDMA]

PredictSimuMemorySize = 1

[FskPropagModels]

OptimOnNoData = 1

[CoPlanning]

ComputeLinkedPredictions = 0

172


12.1.6.21 Co‐planning: Calculating Predictions in Serial or in Parallel

If you want Atoll to calculate in parallel the invalid or unavailable path loss matrices and unlocked coverage predictions in thePredictions folder of the current document and the linked Predictions folder from another document, add the following linesin the Atoll.ini file:

LinkedPredictionsComputationMode is set to Serialized by default, which means the path loss matrices and unlockedcoverage predictions in the current and linked documents are calculated in serial.

If you set LinkedPredictionsComputationMode to any other value, the calculations are performed in parallel but without beingmanaged by a task list.

Calculations are carried out starting with the current document in the order of the coverage predictions in the Predictionsfolder.

12.1.6.22 Forcing Neighbour Symmetry Only Inside Focus Zone

Atoll carries out automatic neighbour allocation on transmitters located inside the Focus Zone (or the Computation Zone ifthe Focus Zone does not exist). When you run an automatic neighbour allocation with the Force Symmetry option selected,Atoll makes calculated neighbour relations symmetrical even if one of the transmitter in the neighbour relation is locatedoutside the Focus Zone. If you want Atoll to make only those neighbour relations symmetrical for which both transmitters inthe neighbour relation are located inside the Focus Zone, add the following lines in the Atoll.ini file:

ForceSymmetryInFocusZone is set to 0 by default.

12.1.6.23 Using Poisson Distribution in Monte Carlo Simulations

By default, mobiles are generated in each simulation following a Poisson distribution. This means that there are smallvariations in the number of randomly distributed mobiles from one simulation to another. To disable this type of distribution,i.e., to have the same number of mobiles generated in each simulation of a group, add the following lines in the Atoll.ini file:

By default, RandomTotalUsers is set to 1.

12.1.6.24 Calculating EIRP from Max Power in Signal Level Predictions

Atoll calculates the EIRP from the pilot power in UMTS and CDMA2000, and reference signal power in LTE. If you wish tocalculate the EIRP from the Max Power values when calculating signal level‐based coverage predictions, add the followinglines in the Atoll.ini file:

By default, EIRPfromMaxPower is set to 0.

This option applies to Coverage by Transmitter, Coverage by Signal Level, and Overlapping Zones predictions in UMTS,CDMA2000, and LTE.

12.1.6.25 Excluding Filtered Transmitters from the List of Neighbours

By default, Atoll includes filtered transmitters in the list of neighbours. If you wish to exclude filtered transmitters from thelist of neighbours, add the following lines in the Atoll.ini file:

By default, ExcludeFilteredCellsFromNeighbourLists is set to 0.

[CoPlanning]

LinkedPredictionsComputationMode = Parallelized

[Neighbours]

ForceSymmetryInFocusZone = 1

[Simulation]

RandomTotalUsers = 0

[Studies]

EIRPfromMaxPower = 1

[Neighbours]

ExcludeFilteredCellsFromNeighbourLists = 0 (default)

173


12.1.6.26 Changing the Weighting Factor of the Effective Inter‐transmitter Distance

By default, the weighting factor of the effective inter‐transmitter distance is set 0.3. To change this weighting factor, add thefollowing lines in the Atoll.ini file:

12.1.6.27 Extending the Maximum Inter‐site Distance to Repeaters and Remote Antennas

The maximum inter‐site distance used in automatic neighbour allocation and neighbour importance evaluation considers thedonor sites only. If you want it to also consider repeaters and remote antennas, then add the following lines in the Atoll.ini file:

12.1.6.28 Forcing the Real Inter‐site Distance Threshold

By default, the automatic neighbour allocation compares the defined Max inter‐site distance with the effective inter‐transmitter distance. As a consequence, there can be cases where the real distance between assigned neighbours is higherthan the Max inter‐site distance, because the effective distance is smaller.

To force Atoll to compare the defined Max inter‐site distance with the real inter‐site distance, add the following lines in theAtoll.ini file:

12.1.6.29 Prioritising Individual Inter‐site Distances in Neighbour Importance Calculation

By default, the neighbour importance calculated with respect to distance is based on the global Max inter‐site distance settingfor all neighbour candidates. As a consequence, there can be cases where the calculated importance is different when theglobal Max inter‐site distance is modified.

You can avoid that by forcing Atoll to prioritise individual distances between reference transmitters/cells and their respectiveneighbour candidates. To do that, add the following lines in the Atoll.ini file:

12.1.6.30 Keeping the Assigned Neighbours which are not Symmetrised with the Reference Transmitter

By default, when the Force Symmetry option is selected and the neighbour list of a transmitter is full, the referencetransmitter is not added as a neighbour and that transmitter is removed from the reference transmitter’s neighbours list.

To force Atoll to keep that transmitter in the reference transmitter’s neighbours list, add the following lines in the Atoll.ini file:

12.1.6.31 Enabling and Disabling Per‐site Path Loss Matrix Calculations

Atoll calculates path loss matrices of co‐located co‐site transmitters in a single step, i.e., per site, instead of calculating eachtransmitter’s matrix separately. You can disable per‐site calculation of path loss matrices by adding the following lines in theAtoll.ini file:

[Neighbours]

DistanceAzimutWeightingPercent = 0.3 (default)

If the value you set is too high (e.g. 0.7), the resulting inter‐transmitter distance can benegative. In such a case, nothing will be displayed in the corresponding table cell.

[Neighbours]

RepeaterInterSiteDistanceInAlloc = 1 #(default = 0)

[Neighbours]

RealInterSiteDistanceCondition = 1 #(default = 0)

[Neighbours]

CandidatesMaxDistanceInImportanceCalculation = 1 #(default = 0)

[Neighbours]

DoNotDeleteSymmetrics = 1 #(default = 0)

[RemoteCalculation]

174


DisablePathlossPerSiteCalculation is set to 0 by default for Atoll 64‐bit and to 1 for Atoll 32‐bit.

12.1.6.32 Defining a Global Maximum Path Loss Calculation Radius

You can set a maximum path loss calculation radius, applicable to both main and extended matrices, by adding the followinglines in the Atoll.ini file:

Where X is the maximum calculation radius in metres. By default, there is no limit for the path loss calculation radii. The limityou set here is applied to values entered by the user in the Transmitters table or properties dialog box.

12.1.7 GSM GPRS EDGE Options

12.1.7.1 Considering Inter‐technology Interference

In GSM "Coverage by C/I Level (DL)" predictions and in point analysis ("Interference" and "Details" views), inter‐technologyinterference is taken into account by default. By adding the following option in the Atoll.ini file, you can add an Inter‐technology check box to the list of Interference Sources on the Conditions tab of "Coverage by C/I Level (DL)" predictions’Properties dialog boxes and in point analyses’ "Interference" and "Details" views, which will allow to consider or not inter‐technology interference.

ExternalIncluded is set to 1 by default, i.e. inter‐technology interference is taken into account by default in GSM "Coverage byC/I Level (DL)" predictions (the Inter‐technology check box does not appear in the list of Interference Sources) and in pointanalyses’ "Interference" and "Details" views.

12.1.7.2 Considering Overlapping Zones for IM Calculation Based on Traffic

When calculating interference matrices based on traffic, overlapping between coverage areas of different transmitters istaken into account when the option "Best Server" is selected and a positive margin is defined. For interference matricescalculation based on "All" the servers (not Best Server), Atoll does not consider the overlapping to improve performance.However, you can instruct Atoll to consider the overlapping during these calculations as well by adding the following lines inthe Atoll.ini file:

12.1.7.3 Setting the Default BSIC Format

You can set the default BSIC format to be used by Atoll by adding these lines in the Atoll.ini file:

DefaultValue enables you to change the default BSIC format (Octal by default) when you create a new Atoll document.

12.1.7.4 Checking Database Consistency Automatically

If you want Atoll to automatically perform a basic data consistency check to avoid incompatibility between redundant fieldsin GSM GPRS EDGE documents, add the following lines to the Atoll.ini file:

By default, this option is considered to be set to 0, which improves Atoll’s performance.

If this option is set to 1, Atoll updates the values of the fields "Number of TRXs" and "Channels" in the Table tab of theTransmitters folder’s Properties dialogue with the values from the TRGs and the TRXs tables respectively, when a documentis opened from a database or refreshed.

DisablePathlossPerSiteCalculation = 1

[Transmitter]

MaximumCalculationRadius = X

[GSM]

ExternalIncluded = 0

[Features]

IM_TRAFFIC_OVERLAP = 1

[BsicFormat]

DefaultValue = 1 for Octal or 0 for Decimal format

[Refresh]

TRXIntegrity = 1

175


12.1.7.5 Disabling the Maximum Range Parameter

The maximum cell range parameter (System frame in the Network Settings folder’s Properties dialogue) in GSM GPRS EDGEdocuments is used by default and set to 35 km. You can disable this option by adding the following lines in the Atoll.ini file:

If you set this option to anything other than "No", Atoll will use the maximum range parameter and set it to the default valueof 35 km.

12.1.7.6 Enabling the Support for Multi‐band Transmitters

Atoll is capable of modelling transmitters with subcells (TRX groups) belonging to different frequency domains. To turn on themulti‐band modelling feature, add the following lines in the Atoll.ini file:

MultiBandManagement is set to 0 by default. Enabling multi‐band management allows the users to access the multi‐bandmanagement features through the Frequency Band Propagation button under the Subcells section of the TRXs tab of atransmitter’s Properties dialogue, and through the Subcells > Multi‐Band Propagation Parameters command in the contextmenu of the Transmitters folder.

In the Multi‐Band Propagation Parameters table and in the database, Atoll uses the "@" character to identify the multi‐bandtransmitters. Therefore, if you are working on a document with multi‐band transmitters, and you have the "@" character inthe names of repeaters, remote antennas, or subcells without a donor/main transmitter, Atoll deletes these records whenopening the document from a database. If you do not want Atoll to automatically delete such records when opening thedocument from a database, you have to sett the following option in the Atoll.ini file:

RemoveBadMultiCells is set to 1 by default.

If you are not working with multi‐band transmitters, i.e., MultiBandManagement is set to 0, Atoll does not automaticallydelete such records. If you want Atoll to automatically delete such records when opening the document from a database, youhave to sett the following option in the Atoll.ini file:

CleanMultiCellManagement is set to 0 by default.

12.1.7.7 Setting the Best Server Calculation Method in Same Priority HCS Layers

Atoll can calculate serving transmitters according to HCS layer priorities in coverage predictions. The signal level received from

the serving transmitter must be higher than the minimum reception threshold ( ) for its HSC layer.

If there are two HCS layers with different priorities:

• The serving transmitter is the one that belongs to the HCS layer with the highest priority.

If there are two HCS layers with the same priority:

• 1st strategy: The serving transmitter is the one for which the difference between the received signal level and

is the highest. Where, is the minimum reception threshold for the HSC layer of each respective transmitter.

• 2nd strategy: The serving transmitter is the one which has the highest received signal level.

The default strategy is the 1st one. You can use the 2nd strategy by adding the following lines in the Atoll.ini file:

UseThresholdForSameLayerPriorities is set to 1 by default.

[Perfos]

MaxRangeApplied = No

[Studies]

MultiBandManagement = 1

[Studies]

RemoveBadMultiCells = 0

[Studies]

CleanMultiCellManagement = 1

[Studies]

UseThresholdForSameLayerPriorities = 0

TRecHCS

TRecHCS

TRecHCS

176


12.1.7.8 Hiding Advanced AFP Parameters

You can hide the advanced parameters from the Atoll AFP Properties dialogue by adding the following lines in the Atoll.ini file:

SimpleUserGUI is set to 0 by default. Setting SimpleUserGUI to 1 hides the Interference Matrices, MAIO, and Advanced tabs.

12.1.7.9 Modifying the Thresholds for Important Violations in AFP

By default, AFP allocation results are displayed in red when a resource has been modified and there is an important separationconstraint violation. You can modify the thresholds above which the important violations will be highlighted by adding thefollowing lines in the Atoll.ini file:

CoRedColorThreshPercent (for co‐channels) and AdjRedColorThreshPercent (for adjacent channels) are set to 12 and 15 bydefault. You can modify these thresholds to any value ranging from 0 to 999.

Setting CoRedColorThreshPercent and/or AdjRedColorThreshPercent to 0 will force the behaviour of previous releases whereimportant and less important violations were both highlighted.

12.1.7.10 Hiding Violations Between Low Importance GSM Neighbours in AFP Results

By default, each neighbour pair has an importance value which defines the quality (and the rank) of the neighbour link. Thisimportance can be evaluated during the automatic neighbour allocation, a specific calculation process or manually populatedin the neighbour tables. In the Allocation tab of the AFP results dialogue, no difference is made between high and lowimportance neighbours in term of violation display. In other words, whatever the importance value is, any neighbour link in aseparation violation is systematically displayed in a specific colour. You can avoid displaying separation violations betweenlow importance neighbours in a specific colour by adding the following lines in the Atoll.ini file:

Where XX is the minimum importance for a neighbour pair to be considered as potentially violated.

12.1.7.11 Hiding Violations Between Non‐synchronised MALs‐MAIOs in AFP Results

In SFH, one can call synchronised MALs‐MAIOs the case where, assuming the synchronisation site and the HSN can beidentified over the entire duration of a GSM frame. As an example, when the synchronisation site, the HSN and the MAL lengthof 2 MALs‐MAIOs are identical, it is always possible to identify if these are or not in separation violation. In case thesynchronisation site, the HSN and/or the MAL lengths or 2 MALs‐MAIOs are different, a certain probability of collision (andconsequently a separation violation) may occur.

You can avoid displaying separation violations between non‐synchronised MALs‐MAIOs in a specific colour by adding thefollowing lines in the Atoll.ini file:

ShowNonSynchSFHViolationsInAFPResults is set to 1 by default. Setting ShowNonSynchSFHViolationsInAFPResults to 0 doesnot show non‐synchronised (MALs‐MAIOs) possibly in a separation violation case.

12.1.7.12 Selecting the Interference Matrices Used During the AFP

All active interference matrices are taken into account during an AFP session according to the method defined in the Atoll.inifile:

[AFP]

SimpleUserGUI = 1

[GSM]

CoRedColorThreshPercent = 12

AdjRedColorThreshPercent = 15

[GSM]

MinNeighbourImportanceInAFPResults = XX

The value in the Atoll.ini file has to be between 0 and 100 whereas the importance valuein the neighbours tables is between 0 and 1.

[GSM]

ShowNonSynchSFHViolationsInAFPResults = 0

177


This option is valid for Forsk’s AFP.

1 refers to the default method, which is the worst case one. Setting this value to 0 will instruct the AFP to use the secondmethod.

• Worst Case Method: For each interference matrix relationship, the worst case value in all the active interferencematrices is taken into consideration.

• First Value Method: For each interference matrix relationship, the first value found in any active interference matrixis taken into consideration. The order in which the interference matrices are scanned to find the first value is the orderof the interference matrices in the Interference Matrices folder in the Network tab, i.e. the first IM is the one at thetop.

The First Value method was the default method in earlier versions of Atoll which allowed multiple interference matrix import.

12.1.7.13 Defining the Maximum Number of Transmitters for Reuse Distance

When using the reuse distance with the AFP, you can limit the number of relations based on distance taken into considerationfor each transmitter in order to ensure that performance is not degraded. In this example, the number is limited to 70:

12.1.7.14 Making Redundant Fields in the Transmitters Table Read‐only

Some of the fields in the Transmitters table are redundant with other fields in the Subcells table. Modifying values in one tablemight cause inconsistencies between the two tables in some cases. You can make these redundant fields uneditable in theTransmitters table by adding the following lines in the Atoll.ini file:

The redundant fields in the Transmitters table are the BCCH and the Number of TRXs fields.

CanEditTRXInfoAtTXLevel is set to 1 by default, which means that the fields are editable.

12.1.7.15 Setting the Transmission Diversity Gain

If a subcell is using transmission diversity, the air‐combining gain of 3 dB is applied to all the received signal levels, wanted (C)as well as interfering (I), during calculations. You can modify the default value of 3 dB by adding the following lines in theAtoll.ini file:

Where X is the value of the air‐combining gain in dB.

MT/YR 24/10/13: Option Grouped HCS Servers supprimée du UM, texte ci‐dessous caché au cas où on fait marche arrière

12.1.7.16 Adding Grouped HCS Servers Option in Calculations

By default, the Grouped HCS Servers option is not available in the list of choices for Server in coverage predictions, trafficcapture, and interference matrix calculations. To make this option available, add the following lines in the Atoll.ini file:

12.1.7.17 Deactivating Frequency Band Filtering in IM Calculation

When calculating interference matrices, Atoll filters potential interferers based on the frequency bands used by the interferedand interfering subcells. For example, if the interfered subcell uses the GSM900 band and a potential interferer uses theGSM1800 band, and the two bands do not overlap, then this potential interferer is ignored. This filtering helps improve thecalculation performance by ignoring the interfered‐interferer pairs that would have eventually resulted in no IM entry afterthe calculation. Any interferer whose assigned frequency band overlaps with the frequency band assigned to the interferedsubcell is not filtered.

You can deactivate this filtering by adding the following lines in the Atoll.ini file:

[AFP]

WorstCaseIM_FskAfp = 0 or 1

[AFP]

GlobalDistanceMatrixDegreeUB = 70

[GSM]

CanEditTRXInfoAtTXLevel = 0

[Studies]

2GTxDiversityGain = X

[TMP]

ExtraServZone = 1

178


FilterByFrequencyBands is set to 1 by default.

12.1.7.18 Starting TRX Indexes at 1

By default, TRXs are indexed by Atoll starting at index 0. If you wish to start the indexing at 1, add the following lines in theAtoll.ini file:

FirstTRXIndex is set to 0 by default. Setting FirstTRXIndex to any other value has the same effect as setting it to 1.

12.1.7.19 Hiding the TRX Index

If you wish to hide the TRX index column, add the following lines in the Atoll.ini file:

TRXIndexHidden is set to 0 by default.

12.1.7.20 Extending the Allowed Value Range for C/I and Reception Thresholds

Currently the subcell C/I threshold allows values from 0 to 24 dB and the reception threshold allows values from ‐116 to ‐50 dBm. If you wish to extend this range to 30 dB and ‐134 dBm for the C/I and reception thresholds respectively, add thefollowing lines in the Atoll.ini file:

WideRangeSubcellThresholds is set to 0 by default, which corresponds to the default value ranges.

12.1.7.21 Automatically Correcting Out‐of‐range Subcell Values

When out‐of‐range subcell values are found in the GSM network, Atoll fixes them by default as follows:

If you wish to modify this default behaviour, add the following lines in the Atoll.ini file:

SubcellValueFixMethod is set to 0 by default, which corresponds to the default behaviour described above.

[IM]

FilterByFrequencyBands = 0

[GSM]

FirstTRXIndex = 1

[GSM]

TRXIndexHidden = 1

[GSM]

WideRangeSubcellThresholds = 1

Subcell Value If it is... ...then it is replaced by:

Number of required TRXs <1 or >62 1

Number of required BCCHs not 1 1

Traffic load <0 or >1 1

Reception threshold < ‐116 dBm or > ‐50 dBm ‐102 dBm

Minimum C/I > 25 dB 12 dB

Half‐rate traffic ratio <0% or >100% 40%

Mean power control gain <0 dB or >32 dB 4 dB

DL power reduction <0 dB or >25 dB 0 dB

AFP weight <0 or >100 1

Target rate of traffic overflow <0% or >100% 0%

Maximum percentage of interference <1% or >100% 1%

Maximum MAL size >62 62

[GSM]

SubcellValueFixMethod = 1

179


If you set this parameter to 1, the values currently out‐of‐range are shifted to the closest boundary of the authorised range.For example if the reception threshold is less than ‐116 dBm, it will be replaced by ‐116 dBm instead of ‐102 dBm as in thedefault behaviour. Likewise, if it is greater than ‐50 dBm, it will be replaced by ‐50 dBm instead of ‐102 dBm.

If you set this parameter to 2, the values which are currently out of the permitted ranges will not modified.

12.1.8 UMTS HSPA, CDMA2000, and TD‐SCDMA Options

12.1.8.1 Suppressing Cell Name Carrier Suffixes

It is only possible to suppress the carrier suffix in a 3G cell name in the case of a single carrier scenario, i.e., the first carrier isalso the last carrier in the global parameters. To do this, add the following lines in the Atoll.ini file:

This is set to 0 by default, which means that cell names will follow the normal convention of Atoll, SiteN_X(C). If there is onlyone carrier, meaning that C is unique, then this option can be set to 1. This will result in cell names which will be same as thetransmitter names, SiteN_X.

12.1.8.2 Disabling Macro‐diversity (SHO) Gains in Calculations

In UMTS HSPA and CDMA2000 documents, macro‐diversity gains are calculated for pilot Ec/Io, and DL and UL Eb/Nt based onthe respective standard deviations. You can deactivate the calculation and use of macro‐diversity gains in all the calculationsby adding the following lines in the Atoll.ini file:

WithSHOGain is set to 1 by default.

If you wish, you can deactivate the macro‐diversity gain calculation for the pilot Ec/Io only by adding the following lines in theAtoll.ini file:

AddPilotSHOGain is set to 1 by default.

12.1.8.3 Calculating and Displaying Peak or Instantaneous HSDPA Throughput

In UMTS HSPA documents, you can choose to display and work with either peak values or instantaneous values of the HSDPAthroughputs per mobile, cell, and site in simulation results. To do this, you can add the following lines in the Atoll.ini file:

• 0: Instantaneous throughput (Default)• 1: Peak throughput

If you choose to display the instantaneous HSDPA throughputs, Atoll will:

• Display the number of simultaneous HSDPA users in the simulation results.• Place a certain part of HSDPA users in a waiting queue during simulations.• Display the instantaneous gross and instantaneous application level throughputs per mobile and per cell in the

simulation results.• Display the instantaneous throughput per site in the Sites tab of the simulation results.

If you choose to display the peak HSDPA throughputs, Atoll will:

• Not display the number of simultaneous HSDPA users in the simulation results.• Display the peak gross and peak application level throughputs per mobile and per cell in the simulation results.• Display the MUG table in the cell properties. Input from this are used to calculate the peak gross throughput per cell

when the scheduling algorithm is "Proportional Fair".• Display the average HSDPA throughput per user in the Cells tab of the simulation results.

HSDPA resource scheduling will not be carried out. The HSDPA throughput for each user will be calculated by taking intoaccount the MUG corresponding to the current number of connected HSDPA users.

[3GCells]

NoSuffixIfUniqueCarrier = 0 or 1

[Shadowing]

WithSHOGain = 0

[CDMA]

AddPilotSHOGain = 0

[CDMA]

HSDPAThroughputPeak = 0 or 1

180


In Average Simulation results, the average HSDPA throughput per user can be calculated excluding the simulations where noHSDPA users were served. To do this, enter the following lines in the Atoll.ini file:

HSDPAAvgSimuResults = 0 by default.

12.1.8.4 Setting the Power to Use for Intra‐cell Interference in HSDPA

In HSDPA prediction studies, you can choose whether to perform intra‐cell interference calculations based on total cell power(Ptot) or maximum cell power (Pmax). By default, Atoll performs this calculation based on the total power. You can instructAtoll to use maximum power in stead by adding the following lines in the Atoll.ini file:

• 0: Intra‐cell interference calculation based on total power (Default)• 1: Intra‐cell interference calculation based on maximum power

12.1.8.5 Enabling Coverage Predictions of Connection Probabilities

You can perform coverage prediction studies for connection probabilities in UMTS HSPA documents by adding the followinglines in the Atoll.ini file:

This coverage prediction study is available in the list of prediction studies if UseStudyCnxProba is set to 1. Otherwise, it willnot be available. MinUsersPerBin is the minimum number of users per pixel required for that pixel to be taken into accountin the coverage prediction.

12.1.8.6 Setting the Calculation Method for HS‐PDSCH CQI

If you choose the “CQI based on CPICH quality” option in Global Parameters, you can select the formula used for calculatingHS‐PDSCH CQI in Atoll by adding the following lines in the file:

CQIDeltaWithPower is set to 1 by default. In this case, the HS‐PDSCH CQI is calculated using the formula:

If you set CQIDeltaWithPower to 0, the HS‐PDSCH CQI will be calculated using the formula:

Note that the default configuration (CQIDeltaWithPower set to 1) is relevant only when is calculated using the "Total

Noise" option.

The above equations are in dB. Refer to the Technical Reference Guide for more details.

12.1.8.7 Enabling Orthogonality Factor in Pilot EC/NT Calculation in HSDPA

%Pilot Finger and the Orthogonality Factor model two different effects on the CPICH quality. %Pilot Finger is related to theCPICH physical channel only and models the loss of energy in the CPICH signal due to multipath. The Orthogonality Factor isrelated to the correlation between the CPICH physical channel and other intra‐cell physical channels.

You can instruct Atoll to use the Orthogonality Factor in the calculation of pilot EC/NT in HSDPA instead of %Pilot Finger by

adding the following lines in the Atoll.ini file:

[CDMA]

HSDPAAvgSimuResults = 1

[CDMA]

PmaxInIntraItf = 1

[CDMA]

UseStudyCnxProba = 1

MinUsersPerBin = X

[CDMA]

CQIDeltaWithPower = 0 or 1

CQI HS PDSCH– CQI pilot Ppilot– PHS PDSCH–+=

CQI HS PDSCH– CQI pilot

EC

NT-------

pilot–

EC

NT-------

HS PDSCH–+=

NT

[CDMA]

OrthoInCPICH = 1

181


12.1.8.8 Setting the Maximum Number of Rejections for Mobiles

You can define a maximum number of rejections for mobiles during simulations by adding the following lines in the Atoll.inifile:

If a mobile is rejected X number of times, it will no longer be considered in the next iterations.

12.1.8.9 Setting the Maximum Number of Rejections for HSDPA Mobiles

You can set the number of times an HSDPA mobile should be rejected (or placed in a queue) before it is consideredpermanently rejected (or permanently placed in the queue). The default value of this option is 5. To modify the default value,enter the following lines in the Atoll.ini file:

Where X is the number of times an HSDPA mobile should be rejected to be considered permanently rejected for thesimulation.

12.1.8.10 Defining an Offset With Respect to The Thermal Noise

You can define an offset with respect to the thermal noise by adding the following lines in the Atoll.ini file:

Where, X is the offset value in dBs. During Monte Carlo simulations, calculations performed on each mobile only take intoaccount the cells whose received power, at the mobile location, is greater than the thermal noise minus this offset. You shouldset CutOffSimu to 20 dB for optimum performance without losing a lot of interference.

12.1.8.11 Setting Precision of the Rasterisation Process

During Monte Carlo simulations, Atoll internally converts vector traffic maps to raster traffic maps in order to perform adistribution of users according to the traffic densities and the connection probabilities. The accuracy of this conversion fromvectors to raster is high enough for most, nearly all, cases. However, this accuracy might not be enough for highly precisevector polygons defining traffic hotspots.

The figure below depicts this effect for a vector polygon which is just slightly larger than 1 raster pixel. The vector polygon andthe raster bin have the same traffic density in the following figure.

The primitive libraries, which perform the conversion from vector to raster, deal in terms of float values for the x and ycoordinates of the vector polygons. Since these are float values, you will have to create vector polygons with the exact(accurate to all the decimal places) size of a pixel (or multiples of a pixel) in order to get raster pixels with the exact samesurface area as the vector polygons. If the coordinates of the vector polygons are not accurate, it is possible that the rasterpixel found from the vector polygon will be shifted 1 bin to the right or to the left.

Such a rasterisation means that the number of users in the vector remains correct, but the density might be different sincethe surface area has changed (Number of users = User Density x Area).

If you want Atoll to increase the precision of the rasterisation process for hotspots in your network. You can add the followinglines in the Atoll.ini file:

[CDMA]

MaxRejections = X

[CDMA]

HSDPAMaxRejections = X

[CDMA]

CutOffSimu = X

Figure 12.1: Rasterisation Process

182


The options are:

• Improve = 1 (by default) means that Atoll will use the accurate rasterisation method for small polygons. Improve = 0means that the normal rasterisation method will be used for all polygons. Setting this option to 1 implies that thisalgorithm will not be used globally for all polygons, but only for small polygons which are defined by the options“SurfRatio” or “MaximumSurf”.

• Precision = 1 (by default) means that the rasterisation resolution (step) used by the algorithm for small polygons is 1metre. You can set it to a higher value if you observe performance degradation. The step of rasterisation means thesize of the bin used to approximate the vector shape with bins.

• SurfRatio = 20 (by default) means that the accurate algorithm will be used only for polygons whose size is smaller than20 times the size of the normal raster bin. The normal raster bin size in an Atoll document is the finest resolutionamong the geographic data available in the document.

• MaximumSurf = 2500 (by default) means that a polygon will be considered small only if its surface area is less than orequal to 2500 sq. m.

So, a polygon will be considered small, and will be rasterised using the accurate algorithm, if either the ratio of its surface areato the surface area of the normal raster bin is equal to or less than SurfRatio, or if its surface area is less than MaximumSurf.If you want to use just the MaximumSurf option, you can set the SurfRatio to 0.

12.1.8.12 Defining the Number of Iterations Before Downgrading

You can set the number of iterations that Atoll should carry out before starting the downgrading. The default value of thisoption is 30. To modify the default value, enter the following lines in the Atoll.ini file:

Where X is the integer number of iterations.

12.1.8.13 Adjusting the Working of the Proportional Fair Scheduler

In UMTS HSPA documents, you can adjust how the proportional fair scheduler functions by adding the following lines in theAtoll.ini file:

Where X is a number between 0 and 100, which represents the proportional fair scheduler weight. PFSchedulerCQIFactor =50 by default. If you set PFSchedulerCQIFactor = 0, the proportional fair scheduler functions like the Round Robin scheduler.If you set PFSchedulerCQIFactor = 100, the proportional fair scheduler functions like the Max C/I scheduler.

12.1.8.14 Displaying Ec/I0 of Rejected Mobiles in Simulation Results

In UMTS and CDMA simulation results, the Ec/I0 AS1 column in the Mobiles tab can list the Ec/I0 values from the best serverfor all the mobiles, connected or rejected. To display the Ec/I0 from the best server for the rejected mobiles, add the followinglines in the Atoll.ini file:

[Rasterization]

Improve = 0 or 1

Precision = 1

SurfRatio = 20

MaximumSurf = 2500

If you set Precision = 1, the performance (calculation speed) can be considerablydecreased depending on the size of your network. It is recommended to set a highervalue for the Precision option.

If your Atoll document contains two geographic data files, one with a 20 m resolution andthe other with a 5 m resolution, and you remove the 5 m one from your document, Atollwill still keep 5 m as the normal raster bin size.

[CDMA]

IterBeforeDown = X

[CDMA]

PFSchedulerCQIFactor = X

183


DisplayEcIoOfRejected is set to 0 by default.

12.1.8.15 Switching Back to the Old Best Server Determination Method

Before Atoll 2.8.0, best server determination in UMTS and CDMA networks used to be performed by selecting the best carrierwithin transmitters according to the selected method (site equipment) and then the best transmitter using the best carrier.To switch back to this best server determination method, add the following lines in the Atoll.ini file:

MultiBandSimu is set to 1 by default.

12.1.8.16 Displaying Automatic Allocation Cost Values

You can display the cost values calculated by Atoll for different relations when allocating scrambling codes and PN offsets. Todisplay cost values, add the following lines in the Atoll.ini file:

DisplayCostValues is set to 0 by default.

12.1.8.17 Selecting SC and PN Offset Allocation Strategies Available in the GUI

In the Atoll.ini file, you can select the scrambling code (UMTS and TD‐SCDMA) and PN offset (CDMA2000) allocation strategiesthat will be available to the user in the automatic allocation dialogue. To select the allocation strategies, add the followinglines in the Atoll.ini file:

The allocation strategies 1, 2, 3, and 4 correspond to the following:

• In UMTS:• 1: Clustered• 2: Distributed per Cell• 3: One Cluster per Site• 4: Distributed per Site

• In TD‐SCDMA:• 1: Clustered• 2: Distributed per Cell• 3: One SYNC_DL Code per Site• 4: Distributed per Site

• In CDMA2000:• 1: PN Offset per Cell• 2: Adjacent PN‐Clusters per Site• 3: Distributed PN‐Clusters per Site

12.1.8.18 Defining a Fixed Interval Between Scrambling Codes

You can define a fixed interval between scrambling codes assigned to cells on a same site when the allocation is based on adistributed strategy (Distributed per Cell or Distributed per Site). To apply the defined interval, add the following lines in theAtoll.ini file:

ConstantStep is set to 0 by default.

[CDMA]

DisplayEcIoOfRejected = 1

[CDMA]

MultiBandSimu = 0

[PSC]

DisplayCostValues = 1

[CDMA]

CodeStrategies = 1, 2, 3, 4

[PSC]

ConstantStep = 1

184


12.1.8.19 Compressed Mode: Restricting Inter‐carrier and Inter‐technology Neighbour Allocation

You can prevent Atoll from allocating inter‐carrier and inter‐technology neighbours to cells located on sites whose equipmentdoes not support compressed mode, by adding the following lines in the Atoll.ini file:

CompressModeEval is set to 0 by default.

12.1.8.20 Setting the Maximum AS Size for SC Interference Prediction

You can set the maximum active set size to a fixed number of transmitters for the scrambling code interference coverageprediction by adding the following lines in the Atoll.ini file:

Where X is the maximum number of transmitters in the active set. If you set SCActivesetMaxSize = 10, you will get the sameresults in the coverage prediction as the SC Interference tab in the point analysis.

12.1.8.21 Displaying Uplink Total Losses in Coverage by Signal Level

In UMTS and CDMA documents, you can activate the Uplink Total Losses and Minimum Uplink Total Losses display options inthe Coverage by Signal Level prediction by adding the following lines in the Atoll.ini file:

UplinkLosses is set to 0 by default. Uplink total losses are calculated from the downlink total losses by replacing the downlinktransmitter losses by uplink transmitter losses.

12.1.8.22 Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise Estimation

In UMTS HSPA simulations, Atoll assumes a constant uplink reuse factor for estimating the maximum available noise rise perHSUPA user. This can cause unnecessary rejection of some HSUPA users in very low traffic cases. You can set an upper limitfor the uplink reuse factor by adding the following lines in the Atoll.ini file:

MaxReuseFactor is set to 5 by default.

12.1.9 LTE, WiMAX, and Wi‐Fi Options

12.1.9.1 Blocking Access to IEEE Parameters in WiMAX

You can disallow modification of the parameters that come from the IEEE specifications, and are not supposed to be changed,by adding the following lines in the Atoll.ini file:

By default, ModifiableIEEEParams is set to 1, which means that all the parameters are modifiable. When you setModifiableIEEEParams to 0, it means that the following parameters will be unmodifiable in the GUI:

• In the Permutation Zones table: Number of Used Subcarriers, Number of Data Subcarriers, and Number ofSubchannels per Channel.

• In the Permutation Zones table: Subchannel Groups (Segment 0), Subchannel Groups (Segment 1), and SubchannelGroups (Segment 2) for FFT sizes < 1000.

[Neighbours]

CompressModeEval = 1

[Studies]

SCActivesetMaxSize = X

[Studies]

UplinkLosses = 1

[UMTSSimus]

MaxReuseFactor = X

[WiMAX]

ModifiableIEEEParams = 0

185


• In the Frame Configurations table and in the General tab of the frame configurations Properties dialogue: Number of Preamble Subcarriers.

12.1.9.2 Using Only Bearers Common Between the Terminal’s and Cell’s Equipment

If you want Atoll to perform an intersection over the bearers supported by the cell equipment and by the terminal equipment,add the following lines in the Atoll.ini file:

UseCommonBearersOnly is set to 0 by default. When UseCommonBearersOnly is set to 1, Atoll only uses the bearers forwhich selection thresholds are defined in both the terminal’s and the cell’s equipment for both downlink and uplink bearerselection.

12.1.9.3 Enabling Display of Signals per Subcarrier Point Analysis in LTE

By default a point analysis in LTE displays RS per channel, SS & PBCH per channel, PDCCH & PDSCH per channel, and RS persubcarrier. If desired, you can also use a point analysis to display SS & PBCH per subcarrier and PDCCH & PDSCH per subcarrierby adding the following lines in the Atoll.ini file:

DisplaySignalsPerSCInPtA is set to 0 by default. When the DisplaySignalsPerSCInPtA option is set to "0" or is absent, SS & PBCHper subcarrier and PDCCH & PDSCH per subcarrier are not available options in a point analysis.

12.1.9.4 Including Cyclic Prefix Energy in LTE Signal Level Calculation

The useful signal level calculation takes into account the useful symbol energy (Es), i.e., excluding the energy correspondingto the cyclic prefix part of the total symbol duration. However, you can include the cyclic prefix energy in the useful signal levelcalculation by adding the following lines in the Atoll.ini file:

ExcludeCPFromUsefulPower is set to 1 by default.

Independant of the option, interference levels are calculated for the total symbol durations, including the energy usefulsymbol duration and the cyclic prefix energy.

12.1.9.5 Excluding Cyclic Prefix Energy in WiMAX and Wi‐Fi Signal Level Calculation

The useful signal level calculation can exclude the energy corresponding to the cyclic prefix part of the total symbol duration,hence taking into account only the energy belonging to the useful symbol duration. In order to do so, you must add thefollowing lines in the Atoll.ini file:

ExcludeCPFromUsefulPower is set to 0 by default.

Independant of the option, interference levels are calculated for the total symbol durations, including the energy usefulsymbol duration and the cyclic prefix energy.

In the Permutation Zones table, the first DL PUSC permutation zone cannot bedeactivated.

In the Frames Configurations table, the cells under Total Number of Subcarriers changeinto combo boxes with the following five values: 128, 256, 512, 1024, 2048.

[OFDM]

UseCommonBearersOnly = 1

[LTE]

DisplaySignalsPerSCInPtA = 1

[LTE]

ExcludeCPFromUsefulPower = 0

[WiMAX]

ExcludeCPFromUsefulPower = 1

186


12.1.9.6 Ignoring Inter‐Neighbour Preamble Index Collision in WiMAX

The automatic preamble index allocation algorithm in Atoll takes into account the possible collision of preamble indexesassigned to neighbours of a cell. This means that Atoll tries to not allocate the same preamble index to two neighbours of acell. If you want to disable this constraint, i.e., allow Atoll to allocate the same preamble index to two neighbours of a cell,add the following lines in the Atoll.ini file:

InterNeighbourPICollisions is set to 1 by default.

The preamble index audit based on neighbours also takes this option into account. With InterNeighbourPICollisions = 1, theaudit lists the cell pairs that are neighbours of a cell and are allocated the same preamble index. WhenInterNeighbourPICollisions = 0, the preamble index collision is not verified between neighbours of a cell.

12.1.9.7 Ignoring Inter‐Neighbour Physical Cell ID Collision in LTE

The automatic physical cell ID allocation algorithm in Atoll takes into account the possible collision of physical cell IDs assignedto neighbours of a cell. This means that Atoll tries to not allocate the same physical cell ID to two neighbours of a cell. If youwant to disable this constraint, i.e., allow Atoll to allocate the same physical cell ID to two neighbours of a cell, add thefollowing lines in the Atoll.ini file:

InterNeighbourIDCollisions is set to 1 by default.

The physical cell ID audit based on neighbours also takes this option into account. With InterNeighbourIDCollisions = 1, theaudit lists the cell pairs that are neighbours of a cell and are allocated the same physical cell ID. WhenInterNeighbourIDCollisions = 0, the physical cell ID collision is not verified between neighbours of a cell.

12.1.9.8 Applying Transmit Diversity Gains to Reference Signals

For more than one transmission antenna port, antenna ports 0 and 1 transmit reference signals using different subcarriersduring the same OFDM symbol. If you want to include the subcarriers transmitted simultaneously on both antenna ports whencalculating the received reference signal level, add the following lines in the Atoll.ini file:

If you wish to make Atoll apply the same transmit diversity gains on reference signals as used for PDSCH, add the followinglines in the Atoll.ini file:

UseDivGainOnRS is set to 0 by default. This corresponds to the equation present in the Technical Reference Guide.

12.1.9.9 Renaming OPUSC Zone to PUSC UL in WiMAX

If you wish to work with two PUSC UL permutation zones, you can rename the OPUSC permutation zone to PUSC UL by addingthe following lines in the Atoll.ini file:

ReplaceOPUSCwithPUSCUL is set to 0 by default.

12.1.9.10 Deactivating Uniform Distribution of Resources

By default, the basic automatic allocation of physical cell IDs and preamble indexes distributes the allocated resourcesuniformly. If you wish to deactivate the uniform distribution of resources, add the following lines in the Atoll.ini file:

[WiMAX]

InterNeighbourPICollisions = 0

[LTE]

InterNeighbourIDCollisions = 0

[LTE]

UseDivGainOnRS = 1

[LTE]

UseDivGainOnRS = 2

[WiMAX]

ReplaceOPUSCwithPUSCUL = 1

[OFDM]

UniformIDDistribution = 0

187


UniformIDDistribution is set to 1 by default.

12.1.9.11 Taking Second Order Neighbours into Account in the AFP

The LTE AFP takes first order neighbours into account when allocating physical cell IDs. The WiMAX AFP takes first orderneighbours into account when allocating preamble indexes and downlink and uplink zone permbases. If you want the AFP totake both first and second order neighbours into account, add the following lines in the Atoll.ini file:

SecondNeighbours is set to 0 by default.

12.1.9.12 Excluding the Adjacent Channel Overlap from the AFP Cost Functions

The LTE, WiMAX, and Wi‐Fi AFPs take the adjacent channel overlap into account for allocation frequencies, physical cell IDs,preamble indexes, and other resources. If you wish to take only the co‐channel overlap into account and exclude the effect ofadjacent channel overlap in resource allocation, add the following lines in the Atoll.ini file:

AdjacentProtection is set to 1 by default.

12.1.9.13 Switching Between Synchronised and Unsynchronised Interference Calculation Methods

Two downlink interference calculation methods exist in Atoll:

• Method 1: Synchronised Transmission and Reception (default)

Atoll calculates the interference between two cells using this method when:

• The frequency channels assigned to the interfered and interfering cells have the same centre frequency, and• The interfered and interfering cells both have an even number of frequency blocks or both have an odd number

of frequency blocks, and• The following option is set in the Atoll.ini file (default value):

Synchronised transmission and reception means that the OFDM symbols of the interfered and interfering framesoverlap and match each other in time.

• Method 2: Non‐synchronised Transmission and Reception

Atoll calculates the interference between two cells using this method when:

• The frequency channels assigned to the interfered and interfering cells do not have the same centre frequency, or• The interfered and interfering cells do not both have an even number of frequency blocks or do not both have an

odd number of frequency blocks, or• The following option is set in the Atoll.ini file:

This method is also used for calculating the interference received from LTE cells of an external network in co‐planningmode, i.e., inter‐technology interference received from LTE cells calculated using the inter‐technology IRFs.

For more information, see the Technical Reference Guide.

12.1.9.14 Setting PDCCH to 100% Loaded in LTE Interference Calculations

By default, the downlink interference calculated from PDSCH and PDCCH is weighted by the downlink traffic loads of theinterfering cells. If you wish to set the PDCCH to 100% loaded, i.e., only weight the interference from PDSCH by the downlinktraffic load and not the interference from the PDCCH, add the following lines in the Atoll.ini file:

[OFDM]

SecondNeighbours = 1

[OFDM_AFP]

AdjacentProtection = 0

[LTE]

SameItf_PDSCH_RS_PDCCH = 0

[LTE]


[LTE]


ApplyDLLoadOnPDCCHInterf = 0

188


ApplyDLLoadOnPDCCHInterf is set to 1 by default. This option is only relevant when SameItf_PDSCH_RS_PDCCH is set to 1.

12.1.9.15 Calculating EIRP from RS EPRE in LTE Signal Level Predictions

Atoll calculates the EIRP from the reference signal power in LTE. In signal level‐based coverage predictions, if you wish tocalculate the EIRP from the Reference Signal EPRE instead, add the following lines in the Atoll.ini file:

EIRPfromRSEPRE is set to 0 by default. This option applies to Coverage by Transmitter, Coverage by Signal Level, andOverlapping Zones predictions in LTE.

12.1.9.16 Averaging the Uplink Noise Rise in dB

The average simulation results provide the linear average of uplink noise rise values displayed in dB. If you want Atoll tocalculate the average by directly using the noise rise values in dB, add the following lines in the Atoll.ini file:

MeanNRInDB is set to 0 by default.

12.1.9.17 Deactivating Service Max Throughput Demand Downgrading in LTE

Service maximum throughput demand downgrading is active by default in LTE Monte Carlo simulations. If you wish todeactivate this downgrading, add the following lines in the Atoll.ini file:

ServiceMBRDowngrading is set to 1 by default.

12.1.9.18 Displaying Pixels with Zero Throughput in Coverage Predictions

In throughput coverage predictions, pixels are coloured according to the defined throughput threshold colours if there arebearers available on those pixels. If you wish to have other pixels, i.e., those with no available bearer hence zero throughput,to be coloured as well, add the following lines in the Atoll.ini file:

DisplayThroughputZero is set to 0 by default.

12.1.9.19 Setting Uplink Noise Rise Control Parameters in LTE

The default method of uplink noise rise control is the best effort method. This means that uplink noise rise control is not partof the simulation convergence criteria. For best effort noise rise control, you can modify the noise rise control margin throughAtoll.ini file by adding the following lines:

Positive values of NR_CONTROL_MARGIN_MIN are considered as negative margins. For example, X is interpreted by Atoll as‐X dB. NR_CONTROL_MARGIN_MIN is set to 1 by default, interpreted as ‐1 dB.

If you wish to include the uplink noise rise control in the simulation convergence criteria, you can change the uplink noise risecontrol method from best effort to strict by setting the following option in the Atoll.ini file:

ULNRControlMethod is set to 0 by default.

For the strict noise rise control method, you can modify the noise rise control precision level through the Atoll.ini file by addingthe following lines:

[LTE]

EIRPfromRSEPRE = 1

[OFDM_SIMU]

MeanNRInDB = 1

[LTE]

ServiceMBRDowngrading = 0

[OFDM]

DisplayThroughputZero = 1

[LTE]

NR_CONTROL_MARGIN_MIN = X

[LTE]

ULNRControlMethod = 1

189


Integer values of ULNRControlPrecision are considered as tenths of dB. For example, X is interpreted by Atoll as 0.X dB.ULNRControlPrecision is set to 5 by default, interpreted as 0.5 dB.

12.1.9.20 Using the ABS Patterns Throughout a Cell in LTE

By default, ABS patterns are used only on the cell‐edges. This means that all subframes are considered non‐ABS subframes inthe cell centre. This method enables you to include the cell‐edge traffic ratio in the calculation of interference. If you wish toapply the ABS patterns throughout the cell, irrespective of the cell‐edge area and the cell‐edge traffic ratio, you can do so byadding the following lines in the Atoll.ini file:

By default, UseABSonCellEdgeOnly is set to 1.

12.1.9.21 Applying the ABS Collision Probability on Interference from RS

Almost blank subframes do not contain any traffic data. They, however, contain transmitted reference signals that generatecertain amount of interference. The 3GPP defines further enhanced ICIC (FeICIC) as the possibility for some advancedreceivers to eliminate interference from reference signals on the ABS. If you wish to eliminate interference from referencesignals transmitted on the ABS, add the following lines in the Atoll.ini file:

By default, eICICOnRS is set to 0.

12.1.9.22 Enabling Multi‐eNode‐B Carrier Aggregation

By default, Atoll supports intra‐eNode‐B carrier aggregation. This means that, Atoll only selects secondary serving cells fromwithin the same eNode‐B (belonging to the same site) as the selected primary serving cell of an LTE‐A user. If you wish toswitch to multi‐eNode‐B carrier aggregation, you can do so by adding the following lines in the Atoll.ini file:

CAWithinENB is set to 1 by default.

12.1.9.23 Switching Between Carrier Aggregation Scheduling Methods

For their maximum throughput demands, LTE‐A users are scheduled separately on each of their serving cells, primary andsecondary. Each user’s remaining throughput demand (maximum – minimum) is distributed over each of its serving cellsproportionally to the resources available on each serving cell and to the user’s downlink effective RLC channel throughput oruplink effective RLC allocated bandwidth throughput on each of its serving cell. Within each serving cell, resource allocationfor the maximum throughput demands is carried out according to the scheduler used by that particular cell.

If you wish to have each user’s remaining throughput demand (maximum – minimum) distributed over each of its serving cellsproportionally only to the resources available on each serving cell, add the following lines in the Atoll.ini file:

CASchedulingMethod is set to 0 by default.

12.1.10 3GPP Multi‐RAT Options

12.1.10.1 BSIC, SC, and PCI Allocation with Inter‐technology Neighbour Constraints

The automatic allocations of BSIC (using the GSM AFP), scrambling codes (in UMTS), and physical cell IDs (using the LTE AFP)take inter‐technology neighbour constraints into account. For example, different physical cell IDs are assigned to two LTE cellsthat are neighbours of the same GSM transmitter or UMTS cell. If you wish to disable the inter‐technology neighbourconstraints in the automatic allocations of BSIC, SC, and PCI, add the following lines in the Atoll.ini file:

[LTE]

ULNRControlPrecision = X

[LTE]

UseABSonCellEdgeOnly = 0

[LTE]

eICICOnRS = 1

[LTE]

CAWithinENB = 0

[LTE]

CASchedulingMethod = 1

190


AllCodesAllocWithInterRATNeighbours is set to 1 by default.

12.1.11 Microwave Radio Links Options

12.1.11.1 Updating A>>B and B>>A Profiles in Real‐time

In the MW Analysis window’s Profile view, when a change is made on the A>>B link, it is not automatically taken into accountin the B>>A direction in real time. This produces inconsistent results in the 2 directions. If you want to make the profile updatereal‐time in both directions, i.e., changes in one direction automatically updated in the other direction, add the following linesin the Atoll.ini file:

UpdateOppositeHop is set to 1 by default.

12.1.11.2 Disabling Shielding Factor on Wanted Signal at Receiver

If you want to disable the use of the shielding factor on the wanted signal at the receiver during interference calculations, addthe following lines in the Atoll.ini file:

ShieldingFactorOnWantedSignal is set to 1 by default, which means that the shielding factor is taken into account at thereceiver when calculating interference. On the transmitter side, the shielding factor is always taken into account whencalculating interference.

12.1.11.3 Making the ITU‐R P.530‐5 Method Available

The Rec. ITU‐R P.530‐5 method is hidden by default on the Models tab of the Microwave Radio Links Properties dialogue.You can make this method available for availability and quality calculations by adding the following lines in the Atoll.ini file:

HIDE_REC‐5 is set to 1 by default. If the method was selected in a document saved in a previous Atoll version, it will beavailable even if HIDE_REC‐5 is set to 1 in the Atoll.ini file.

12.1.11.4 Decreasing Calculation Time of Path Profiles

When you calculate a link budget or interference for a microwave link:

• The path profile is calculated twice (A>>B and B>>A) and up to 3 separate extractions can be used: one for DTM, onefor clutter heights, and one for clutter classes.

• A new directory, C:\<path_to_doc>\<doc_name>.profiles, is created. It contains the external files (which include allthe calculated path profiles) that will be used the next time link budgets or interferences need to be recalculated.

You can disable this feature by setting the following option in the Atoll.ini file:

[MultiRAT]

AllCodesAllocWithInterRATNeighbours = 0

[MWCalculations]

UpdateOppositeHop = 1

[MWCalculations]

ShieldingFactorOnWantedSignal = 0

[MWCalculations]

HIDE_REC530_5 = 0

[MWCalculations]

UseProfilesFiles = 0 # (default=1)

• Keep the ATL file on your machine instead of a server to significantly decrease thecalculation time of path profiles.

• This feature is more efficient when the DTM resolution is low, provided that thecalculation resolution is greater than or equal to the geo data resolution.

• Profile files are not created for links with at least one remote antenna. They will notbe used either if they were created before an antenna has become remote.

191


12.1.11.5 Using Old Min C/I Values

If you wish to use Min C/I values defined or calculated in old versions of Atoll, add the following lines in the Atoll.ini file:

MWEquipment_CIMIN is set to 0 by default.

12.1.11.6 Solving Alignment Issue in Generated Reports

If you encounter an alignment issue in the Microwave report or in the Reflection Analysis report, you can solve it by increasingthe tab value. To do that, add the following lines in the Atoll.ini file:

12.1.11.7 Using Default Method for Calculating Unavailability

When generating an Analysis Report, Atoll calculates the availability (average over a year) using the Crane or the ITUrecommendations: ITU‐R P.530‐5, ITU‐R P.530‐8, ITU‐R P.530‐10, ITU‐R P.530‐11, ITU‐R P.530‐12 and ITU‐R P.530‐13. UnderUnavailability due to rain, however, the values are extrapolated to give a more accurate result.

The default for option "RainBelow0001" is "1" which uses the same extrapolation method as Pathloss. If desired, the option"RainBelow0001" can be set to "2" in order to follow the Atoll extrapolation (as before) or to "0", to use no extrapolation whencalculating unavailability due to rain.

12.1.11.8 Defining Default Configuration Files for Link Budgets Reports

You can define a default configuration file for each link budget report by specifying an absolute or UNC path in the Atoll.ini file:

Where each of the above options corresponds to a specific Report Configuration dialogue:

• DesignSummaryCfg: corresponds to the Report Configuration dialogue displayed after clicking the Configure Report

button ( ) from the Design Summary view (MW Analysis window).• LinkAnalysisCfg: corresponds to the Report Configuration dialogue displayed after clicking the Configure Report

button from the Analysis Report view (MW Analysis window).• LinkInterferenceCfg: corresponds to the Report Configuration dialogue displayed after clicking the Configure Report

button from the Interference Report view (MW Analysis window).• RequiredMarginCfg: corresponds to the Report Configuration dialogue displayed after clicking the Configure Report

button from the Required Margin view (MW Analysis window).• LinksBudgetCfg: corresponds to the Report Configuration dialogue displayed after selecting Microwave Radio Links

> Links > Link Budgets > Configuration Report from the Network explorer.• LinksInterferenceCfg: corresponds to the Report Configuration dialogue displayed after selecting Microwave Radio

Links > Links > Interference > Configuration Report from the Network explorer.• MultihopAnalysisCfg: corresponds to the Report Configuration dialogue displayed after selecting Microwave Radio

Links > Multi‐Hops > [Multi‐Hop X] > Analysis from the Network explorer.• ReflectionAnalysisCfg: corresponds to the Report Configuration dialogue displayed after:

• right‐clicking in the Profile Analysis view (MW Analysis window) and selecting Reflection and Diversity Analysis,• then clicking the Configure Report button from the Analysis Report view (MW Reflection/Diversity window).

[Compatibility]

MWEquipment_CIMIN = 1

[MWReport]

tab = 2000 # Default value is 500

[MWReport]

RainBelow0001 = 1 # Default; the same extrapolation method as Pathloss

[MWReport]

DesignSummaryCfg = path to the report’s default configuration file

LinkAnalysisCfg = path to the report’s default configuration file

LinkInterferenceCfg = path to the report’s default configuration file

RequiredMarginCfg = path to the report’s default configuration file

LinksBudgetCfg = path to the report’s default configuration file

LinksInterferenceCfg = path to the report’s default configuration file

MultihopAnalysisCfg = path to the report’s default configuration file

ReflectionAnalysisCfg = path to the report’s default configuration file

192


12.1.11.9 Defining a Default Configuration File for the Channel Arrangement Display

You can define a default configuration file for the channel arrangement display by specifying an absolute or UNC path in theAtoll.ini file:

Where the above option corresponds to the Channel Arrangement dialogue displayed after selecting Microwave Radio Links> Interference > Channel Arrangement > Display on Map from the Network explorer.

12.1.11.10 Defining a Default Template for Microwave Links Custom Reports

You can define a default template for microwave links custom reports by specifying an absolute or UNC path in the Atoll.inifile:

12.1.12 Measurement Options

12.1.12.1 Displaying Additional Information in Drive Test Data

It is possible to display the following additional information in the columns of serving and neighbour cells:

• BCCH ‐ BSIC pair (GSM GPRS EDGE documents)• Scrambling Code ‐ Scrambling Code Group pair (UMTS HSPA documents)• PN Offset ‐ PN Offset Group pair (CDMA2000 1xRTT 1xEV‐DO documents)

You have to add the following lines in the Atoll.ini file to display this information:

Setting ShowCoupleInfo to 0 hides this information.

12.1.12.2 Setting the Number of Transmitters per Drive Test Data Path

By default, Atoll can import information about one serving transmitter (or cell in CDMA documents) and six neighbourtransmitters (or cells in CDMA documents) for drive test data paths. You can change the number of transmitters per drive testdata path by adding the following lines in the Atoll.ini file:

Where X is the number of transmitters per drive test data path. The default value of NumberOfTestMobileTransmitters is 7.

12.1.12.3 Recalculating Distances of Points From There Serving Cells at Import

If you want Atoll to calculate the distance of each measurement point from its nearest serving cell, you can add the followinglines in the Atoll.ini file:

The default value of RecalcDist is 1, which means that Atoll will calculate the distance for each measurement point. Thenearest serving cell is the one closest to the measurement point which has the same (Scrambling Code, SC Group), (BSIC,BCCH), or (PN Offset, PN Offset Group) pair as the point.

12.1.12.4 Defining the BCCH and BSIC Columns for FMT Import

The .fmt files generated by the TEMS Investigation GSM tool contain a number of columns. To define which of these columnsshould be imported as the BCCH column and which one as the BSIC column in Atoll, you can add the following lines in theAtoll.ini file:

[MWChannelArrangement]

DefaultConfiguration = path to the channel arrangement default configuration file

[MWReport]

DefaultTemplate = path to the default template for microwave links custom reports

[TestMobileData]

ShowCoupleInfo = 1

[TestMobileData]

NumberOfTestMobileTransmitters = X

[TestMobileData]

RecalcDist = 1 or 0

193


Where, Column1 and Column2 are the titles of the two columns in the .fmt file corresponding to the BCCH and the BSICcolumns respectively.

12.1.12.5 Importing Drive Test Data with Scrambling Codes as Integers

You can force the conversion of scrambling codes to integer values when importing drive test data by adding the followingoption in the Atoll.ini file:

FloatingPointScramblingCodeSupport is set to 0 by default, and the scrambling codes are imported according to the numericdata type selected for the scrambling code column in the import dialogue.

12.1.12.6 Importing Drive Test Data for Active and Filtered Transmitters Only

When you import drive test data in Atoll, it assigns servers and neighbours to each measurement point based on the cellidentification method defined for the import. By default, Atoll takes all the transmitters and cells of the document intoaccount, whether they are active or inactive and filtered or not. If you want Atoll to take only active and filtered transmittersand cells into account for drive test data import, add the following option in the Atoll.ini file:

ImportForFilteredTransmittersOnly is set to 0 by default.

12.1.13 ACP OptionsFor the most part, you can configure the ACP with its own initialisation file: the acp.ini. However, there are a few options thatyou can set in the Atoll.ini to configure the ACP.

12.1.13.1 Specifying the Location of the Acp.ini File

By default, Atoll ACP uses the global acp.ini file, located in the installation directory of Atoll. You can set an option in theAtoll.ini file to define a different location for the acp.ini file. This option is useful for assigning a different ACP initialisation fora different group of users.

To use another location, add the following line to the Atoll.ini file:

12.2 ACP Initialisation FileThe ACP initialisation file is used to inform Atoll of the preferred settings when the ACP is used for automatic cell planningduring Atoll sessions. It can be used to adjust the behaviour of the ACP.

You can comment out any option in the acp.ini by preceding the line with a semi‐colon (";") or with a hash mark ("#").

In order for the ACP initialisation file to be used by Atoll, you should place the acp.ini file in the Atoll installation directory.

You can define a different location for the acp.ini file as shown in "Specifying the Location of the Acp.ini File" on page 194:

[TestMobileDataImportFmt]

BCCHColumn = Column1

BSICColumn = Column2

[TestMobileData]

FloatingPointScramblingCodeSupport = 1

[TestMobileData]

ImportForFilteredTransmittersOnly = 1

[ACP]

iniFile = /path/to/the/ACP.ini

The ACP initialisation file is a powerful tool. You should not modify any option in theacp.ini file until and unless you are absolutely sure of what you are doing.

194


12.2.1 Managing PreferencesSome of the settings provided in the acp.ini file can be modified directly using the ACP ‐ Automatic Cell Planning Propertiesdialogue, under ACP Automatic Cell Planning on the Setup Template tab. ACP either embeds these settings directly in the ATLdocument or in a user‐defined acp.ini file. These settings are referred as "local settings." Local settings are the settings foundin sections using the "Tpl" keyword, such as [ACPTplGeneralPage].

12.2.2 GUI OptionsIn this section are the settings defining default values and defining certain aspects of the GUI configuration. These settings arelocal and are usually defined using Setup Template tab of the ACP ‐ Automatic Cell Planning Properties dialogue, and storedeither in the Atoll project or a local acp.ini file.

12.2.2.1 Default Values on the Optimisation Tab

In the [ACPTplGeneralPage] section, you can find the options used to set default values for the Optimisation tab.

The following options can be used to set default values for the number of iterations and resolution:

Other options can be used to define the default values for calculating cost:

• The local settings, defined using the ACP ‐ Automatic Cell Planning Propertiesdialogue, take precedence over the same settings defined in the global acp.inifile. The settings in the acp.ini file are read when you start a new project toinitialise the settings of the ACP.

• When using the acp.ini file to define options, instead of using the ACP ‐Automatic Cell Planning Properties dialogue, you can also define any othersettings even if they can not be set using the ACP ‐ Automatic Cell PlanningProperties dialogue. These settings redefined locally have precedence over theglobal settings.

[ACPTplGeneralPage]

nbIteration=100

resolution=50

cost.type=0 # 0=off, 1=limt_to_max, 2=apply_cost_to_change_plan

;cost.unit= # here define the optional 'unit' for cost: $, 'yen', etc. Less than 4 characters

cost.tradeoffLevel=1 # 0=low, 1=normal, 2=strong

cost.maxCost=50

cost.azimuth.cost=1

cost.azimuth.isSiteVisit=true

cost.tilt.cost=1

cost.tilt.isSiteVisit=true

cost.antenna.cost=1

cost.antenna.isSiteVisit=true

cost.etilt.cost=0.1

cost.etilt.isSiteVisit=false

cost.height.cost=1

cost.height.isSiteVisit=true

cost.power.cost=0.1

cost.power.isSiteVisit=false

cost.siteVisitCost=2

cost.upgradeSiteCost=5

cost.newSiteCost=10

cost.removeSiteCost=-5

195


12.2.2.2 Displaying Advanced Cost Options

In the [ACPGeneralPage] section, you can define an option to display advanced cost options which enable the user to definethe maximum number of changes to be made (either as a value or a ratio) and to change the ranking of the order of cost inthe final implementation plan: changes with the lowest cost are performed first and changes with the highest cost areperformed last.

In the [ACPTplGeneralPage] section, you can define default values for advanced cost control. The "cost.planCostWeighting"option enables you to define the importance of cost in the implementation plan:

The "cost.planLimitType" option enables you to limit the number of changes in the implementation plan:

If the "cost.planLimitType" option is set to "1" (i.e., an absolute value), then the "cost.planChangeMax" option must be set todefine the number of changes in the implementation plan:

If the "cost.planLimitType" option is set to "2" (i.e., a percentage of the total antennas in the computation zone), then the"cost.planChangePercent" option must be set to define the number of changes in the implementation plan as a percentageof the number of antennas:

If the "cost.planLimitType" option is set to "2" (i.e., a percentage of the total antennas), the user can then use the focus zoneinstead of the computation zone as the reference zone by setting the "cost.planChangRefZone" option in the[ACPGeneralPage]:

12.2.2.3 Automatically Creating Custom Zones on the Optimisation Tab

In the [ACPTplGeneralPage] section, you can find the options used to automatically create custom zones that will appear onthe Optimisation tab when you create a new ACP setup.

The following option can be used to automatically create ACP custom zones from the hotspots in the Atoll project:

The following options can be used to automatically create ACP custom zones from one or more clutter classes or from a SHPfile:

[ACPGeneralPage]

enableAdvancedCost=0 # "1" to display (default); "0" to hide

[ACPTplGeneralPage]

cost.planCostWeighting=0 # "0"=low, "1"=medium (default), "2"=high

[ACPTplGeneralPage]

cost.planLimitType=0 # "0"=no limit (default) "1"=absolute value# "2"=percent of total antennas in the computation zone

[ACPTplGeneralPage]

cost.planLimitType=1

cost.planChangeMax=10 # In this example, the maximum no. of changes is "10."

[ACPTplGeneralPage]

cost.planLimitType=1

cost.planChangePercent=10 # In this example, the maximum no. of changes is "10%"# of the total number of antennas in the computation zone

[ACPGeneralPage]

cost.planChangRefZone=1 # Ration computed against computation zone # (0:Default) or focus zone (1)

[ACPGeneralPage]

zone.autobuildHotspot=1 # automatically build hotspot from Atoll hotspot (default)

[ACPGeneralPage]

zone.count=2 # The number of zones to be created.

zone.0.name=MyClutterZone1 # The name of the zone (in this case from clutter)

zone.0.clutter=10,11,12 # The clutter classes that will constitute this zone

zone.1.name=MyVectorZone2 # The name of the zone (in this case from SHP)

196


12.2.2.4 Default Values on the Objectives Tab

In the [ACPTplObjectivePage] section are the settings defining default values for the Objectives tab.

The following option is used to define the default value for traffic extraction resolution in metres:

The following options are used to define the default values for the technology quality indicators (UMTS Ec/Io, UMTS RSCP,UMTS overlap, GSM signal level, GSM overlap, WiMAX CINR, WiMAX C/N, LTE C/N, etc.):

zone.1.file=c:\path\to\file.shp # Absolute path to the SHP file.

[ACPTplObjectivePage]

traffic.extraction.resolution=50 # the traffic extraction resolution, in metres


param.gsm.overlap.autoPrediction=yes

param.gsm.overlap.margin=5

param.gsm.overlap.minRxLevel=0 # 0=use defined TRG threshold, other=defined value

param.gsm.bcch.autoPrediction=yes

param.gsm.bcch.isShadowing=no

param.gsm.bcch.cellEdgeCov=0.75

param.umts.overlap.autoPrediction=yes

param.umts.overlap.margin=10

param.umts.overlap.minRxLevel=-120

param.umts.rscp.autoPrediction=yes

param.umts.rscp.isShadowing=no

param.umts.rscp.cellEdgeCov=0.75

param.umts.ecio.autoPrediction=yes

param.umts.ecio.isShadowing=no

param.umts.ecio.cellEdgeCov=0.75

param.cdma.overlap.autoPrediction=yes

param.cdma.overlap.margin=10

param.cdma.overlap.minRxLevel=-120

param.cdma.coverage.autoPrediction=yes

param.cdma.coverage.isShadowing=no

param.cdma.coverage.cellEdgeCov=0.75

param.cdma.ecio.autoPrediction=yes

param.cdma.ecio.isShadowing=no

param.cdma.ecio.cellEdgeCov=0.75

param.wimax.overlap.autoPrediction=yes

param.wimax.overlap.margin=5

param.wimax.overlap.minRxLevel=-105

param.wimax.coverage.autoPrediction=yes

param.wimax.coverage.isShadowing=no

param.wimax.coverage.cellEdgeCov=0.75

param.wimax.cnir.autoPrediction=yes

param.wimax.cnir.isShadowing=no

param.wimax.cnir.cellEdgeCov=0.75

param.wimax.cnir.useFreqBand=1

param.wimax.cnir.useSegmentation=1

197


The following options are used to define the default threshold for each objective rule:

The following options are used to define the default objectives proposed by the ACP. All objectives defined with the option"auto=yes" are automatically created during a new setup. Others are available on the context menu used for creating newobjectives.

param.lte.overlap.autoPrediction=yes

param.lte.overlap.margin=5

param.lte.overlap.minRxLevel=-105

param.lte.coverage.autoPrediction=yes

param.lte.coverage.isShadowing=no

param.lte.coverage.cellEdgeCov=0.75

param.lte.cinr.autoPrediction=yes

param.lte.cnir.isShadowing=no

param.lte.cnir.cellEdgeCov=0.75

param.lte.cnir.useFreqBand=1

param.lte.cnir.useSegmentation=1


quality.gsm.bcch.threshold= -85

quality.gsm.overlap.threshold=4

quality.umts.rscp.threshold= -85

quality.umts.ecio.threshold= -13

quality.umts.overlap.threshold=4

quality.cdma.rscp.threshold= -85

quality.cdma.ecio.threshold= -13

quality.cdma.overlap.threshold=4

quality.wimax.coverage.threshold= -85

quality.wimax.c.threshold=-85

quality.wimax.cn.threshold=20

quality.wimax.cinr.threshold=10

quality.wimax.overlap.threshold=5

quality.lte.coverage.threshold= -85

quality.lte.c.threshold= -85

quality.lte.cn.threshold=20

quality.lte.rsrp.threshold= -105

quality.lte.cinr.threshold=10

quality.lte.rsrq.threshold= -12

quality.lte.overlap.threshold=5

For the setting "objective.X.conditions.X.operande," a value of "0" means "<" (less than)and "1" means ">" (greater than).


objective.count=14 # The total number of objectives to be defined.

objective.0.name=GSM Coverage # Name of objective "0" defined.

objective.0.conditions.count=1

objective.0.conditions.0.layer=gsm

198


objective.0.conditions.0.quality=bcch

objective.0.conditions.0.threshold=-85

objective.0.conditions.operande=OR

objective.0.auto=true

objective.0.weight=1

objective.0.targetZone=-1 # -2=compZone, -1=focusZone, or other zone idx

objective.0.target.isAbsoluteCoverage=yes

objective.0.target.absoluteCoverage=90

objective.0.filter.count=0

;; The following objective should be defined separately for each layer

objective.1.name=GSM Cell Dominance # Name of objective "1" defined.

objective.1.conditions.operande=AND



objective.1.conditions.0.quality=overlap

objective.1.conditions.0.operande=1 # "1" means ">" (greater than).

objective.1.conditions.0.threshold=0



objective.1.conditions.1.operande=0 # "0" means "<" (less than)




objective.2.name=UMTS RSCP Coverage # Name of objective "2" defined.


objective.2.conditions.0.layer=umts

objective.2.conditions.0.quality=rscp





objective.3.name=UMTS EcIo # Name of objective "3" defined.



objective.3.conditions.0.quality=ecio





objective.4.name=UMTS Pilot Pollution # Name of objective "4" defined.

objective.4.auto=false






199





objective.5.name=UMTS Soft Handover # Name of objective "5" defined.





objective.5.conditions.0.operande=1 # "1" means ">" (greater than)







objective.5.filters.count=1

objective.5.filters.0.layer=umts

objective.5.filters.0.quality=rscp

objective.5.filters.0.operande=0

objective.5.filters.0.threshold=-95

objective.6.name=WiMAX Preamble Coverage # Name of objective "6" defined.


objective.6.conditions.0.layer=wimax

objective.6.conditions.0.quality=coverage



objective.7.name=WiMAX Preamble CINR # Name of objective "7" defined.


objective.7.conditions.0.layer=wimax

objective.7.conditions.0.quality=cinr

objective.7.conditions.0.operande=1 # "1" means ">" (greater than)





objective.8.name=LTE RS Coverage # Name of objective "8" defined.


objective.8.conditions.0.layer=lte




objective.9.name=LTE RS CINR # Name of objective "9" defined.


objective.9.conditions.0.layer=lte

objective.9.conditions.0.quality=cinr

200






objective.10.name=CDMA Coverage # Name of objective "10" defined.


objective.10.conditions.0.layer=cdma




objective.11.name=CDMA EcIo # Name of objective "11" defined.



objective.11.conditions.0.quality=ecio





objective.12.name=CDMA Pilot Pollution # Name of objective "12" defined.











objective.13.name=CDMA Soft Handover # Name of objective "13" defined.









objective.13.conditions.1.operande=0 # "0" means "<" (less than



objective.13.filters.count=1

objective.13.filters.0.layer=cdma

objective.13.filters.0.quality=coverage

objective.13.filters.0.operande=0

objective.13.filters.0.threshold=-95

201


The following option enables you to use the XOR boolean expression when creating objectives.

The following option is used to remove the Capacity and Load Balancing features from the Objectives tab:

The following option is used to clear the Scale Traffic according to Zone Weighting check box on the Capacity page of theObjectives tab:

The following options are used to define a capacity traffic map, either by a BIL file or by a comma‐separated list of traffic mapnames:

The following options are used to define the default threshold for each quality (Objectives tab > Capacity page > ServicesDefinition frame):

The following options are used to define the default quality used by each technology for traffic capture condition:

[ACPObjectivePage]

combination.XOR.use=0 # disabled by default

[ACPCapacityPage]

enable=0 (default=1 => capacity and load balancing enabled)

[ACPTplCapacityPage]

useZoneWeight=0 (default=1 => zone weighting applied on capacity traffic)


traffic.file=c:\tmp\traffic.bil

traffic.maps=User density traffic map; environment map

traffic.resolution=50


quality.gsm.bcch.threshold=-85

quality.umts.rscp.threshold=-85

quality.umts.ecio.threshold=-13

quality.cdma.rscp.threshold=-85

quality.cdma.rscp.threshold=-85

quality.wimax.coverage.threshold=-85

quality.wimax.c.threshold=-85

quality.wimax.cn.threshold=20

quality.wimax.cinr.threshold=10

quality.lte.coverage.threshold=-85

quality.lte.c.threshold=-85

quality.lte.cn.threshold=20

quality.lte.rsrp.threshold=-105

quality.lte.cinr.threshold=10

quality.lte.rsrq.threshold=-12


service.gsm.condition.quality=bcch

service.umts.condition.quality=rscp

service.cdma.condition.quality=coverage

service.wimax.condition.quality=coverage

service.lte.condition.quality=coverage

service.factor=1.0

202


The following option is used to enable the load balancing feature by default:

The following option is used to specify the load balancing default target zone:

• ‐2 => computation zone• ‐1 => focus zone• 0 and above => index of custom zone

12.2.2.5 Default Values on the Reconfiguration page

In the [ACPTplReconfPage] section are the settings defining default values for the Reconfiguration page.

The following options enable you to define the default reconfiguration that will be done: power, antenna, azimuth, ormechanical tilt optimisation.

service.density=30


loadBalancing.enable=1 (default setting is 0 => load balancing feature disabled)


loadBalancing.targetZoneIdx=-2

loadBalancing.target=80

loadBalancing.weight=1

When the options in this section are set to "1", the default reconfiguration option is notselected. Instead the reconfiguration option is disabled.

[ACPTplReconfPage]

umts.disablePilotPowerOptimisation=1

umts.disableMaxPowerOptimisation=1

umts.SyncMultiCellPower=1

umts.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm# around actual value. If 0, use fixed value 37-46

cdma.1xrtt.SyncMultiCellPower=1

cdma.1xevdo.SyncMultiCellPower=1

cdma.1xrtt.disablePilotPowerOptimisation=1

cdma.1xrtt.disableMaxPowerOptimisation=1

cdma.1xevdo.disableMaxPowerOptimisation=1

cdma.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm# around actual value. If 0, use fixed value 37-46

gsm.disablePowerOptimisation=1

gsm.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm# around actual value. If 0, use fixed value 37-46

wimax.disablePreamblePowerOptimisation=1

wimax.SyncMultiCellPower=1

wimax.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm# around actual value. If 0, use fixed value 37-46

lte.disablePowerOptimisation=1

lte.SyncMultiCellPower=1

lte.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm# around actual value. If 0, use fixed value 37-46

203


The following options are used to define the default reconfiguration that will be done on transmitters and sites:

The following options are used to specify default values for the reconfiguration ranges:

The following option can be used to display an additional constraint on the Transmitters tab of the Reconfiguration tab thatwill be applied to electrical tilt changes.

When the option above is set to one, you can define the variation in the header of the new Variation +‐ column. The valueyou enter beside the Variation +‐ header defines the range of electrical tilt changes with respect to the current electrical tilt.For example, setting a variation of "4" means that the ACP can find an optimal electrical tilt that is 4 degrees more or 4 degreesless than the current electrical tilt. The possible range is displayed for each antenna.

Each cell in the electrical tilt column displays a check box enabling the user to define whether the constraint should be used,and the corresponding absolute limit for the electrical tilt. This constraint is an additional constraint on the electrical tiltconfiguration options. The final electrical tilt will be allowed within the intersection of the two range constraints.

The following option can be used to define a default value for the Variation +‐ header mentioned above:

The following option is used to automatically disable reconfiguration of all donors (possibly in cascade) of a repeater:

The possible values are:

• "0", no auto lock (the default value)• "1", the Use check boxes for transmitter reconfiguration parameters are cleared (antenna, tilt, azimuth, and height).

Only the last repeater in a series of cascading repeaters is optimised; the rest are cleared by default (but can beselected manually).

[ACPTplReconfPage]

disableAntennaOptimization=1

disableETiltOptimization=1

disableAzimuthOptimization=1

disableMechTiltOptimization=1

disableSiteSelection=1

[ACPTplReconfPage]

defaultTxAzimuthVariation=20

defaultTxAzimuthStep=5

defaultTxAzimuthMinInterSector=0

defaultTxTiltMin=0

defaultTxTiltMax=5

defaultTxTiltStep=1

defaultTxETiltMin=0

defaultTxETiltMax=10

defaultTxHeightMin=0

defaultTxHeightMax=10

defaultTxHeightStep=5

defaultTxHeightMin.feet=0

defaultTxHeightMax.feet=30

defaultTxHeightStep.feet=15

umts.disablePilotPowerOptimization=0

umts.disableMaxPowerOptimization=0

[ACPReconfPage]

tx.etilt.deltaLimitConstraint.show=1 (default=0)

[ACPTplReconfPage]

etilt.deltaLimitConstraint=4 (default=0)

[ACPTplReconfPage]

autoLockDonor=0

204


• "2", the Use check boxes for all reconfiguration parameters are cleared (antenna, tilt, azimuth, height, and power).Only the last repeater in a series of cascading repeaters is optimised; the rest are cleared by default (but can beselected manually).

• "5", the same as option "1", except that the Use check boxes can not be selected in the user interface.• "6", the same as option "2", except that the Use check boxes can not be selected in the user interface.

12.2.2.6 Default Values on Sites tab of Reconfiguration page

In the [ACPTplReconfPage] section are the settings defining default values for the Sites tab of the Reconfiguration page.

The following options enable you to define the reconfiguration options that are selected by default: site or sector removable,or antenna azimuth or height. The settings of "defaultSiteCellsRemoveable", "defaultSiteRemoveable", and"defaultSiteHeightLocked" also define the default settings for Station Template Reconfiguration dialogue.

12.2.2.7 Custom Columns on Sites tab of Reconfiguration page

The following options can be used to define the number of custom columns to display on the Sites tab of the Reconfigurationpage:

Where ’tabularDataColumn’ displays data issued from Atoll’s SITES table and identified by site.custom.1.column (columnname). Atoll column names are case sensitive.

The option below defines an optional label for a given column. If unset, the Atoll column name is used (e.g. "FOO"):

12.2.2.8 Default Values on the Transmitters Tab of the Reconfiguration Page

In the [ACPReconfPage] section are the settings defining default values for the display of mechanical and electrical tilts, andfor the display of linked transmitters.

The following options are used to display the mechanical and electrical tilts as relative values instead of absolute values. As a

result, the Min. and Max. columns will be renamed to Min. Offset. and Max. Offset.

The following option is used to display the minimum and maximum electrical tilts only once for each group of linkedtransmitters, when the Advanced mode is selected for display.

When the options in this section are set to "1", the corresponding reconfiguration optionis selected by default.

[ACPTplReconfPage]

# Specify the default values for the site selection

defaultSiteCellsRemoveable=0 # "0" means Sectors removable not selected by default.

defaultSiteRemoveable=1 # "0" means Site removable not selected by default.

defaultSiteAzimuthLocked=0 # "0" means Lock Sector/Azimuth not selected by default.

defaultSiteHeightLocked=1 # "0" means Lock Sector/height not selected by default.

# "defaultSiteHeightLocked" is forced to false ("0") for sites that have antennas# at different heights

defaultSiteReconfigurationLocked=0 # "0" means that the default value for the Disablereconfiguration option is not selected by default.

[ACPReconfPage]

site.custom.count=x

site.custom.1.type=tabularDataColumn

site.custom.1.column=FOO

site.custom.1.label=The Foo Label

[ACPReconfPage]

tx.tilt.asRelative=1 (default=0)

tx.etilt.asRelative=1 (default=0)

[ACPReconfPage]

tx.etilt.groupMinMax=1 (default=1)

205


When "tx.etilt.groupMinMax" is set to 0, the min/max electrical tilts are displayed for each transmitter.

12.2.2.9 Custom Columns on Transmitters/Remotes tabs of Reconfiguration page

The following option can be used to define the number of custom columns to display on the Transmitters tab of theReconfiguration page:

The options below allow you to specify the data you want to show under each custom column.

Where:

• ’elevation’ displays the transmitter elevation (site altitude plus transmitter height).

• ’bandwidth’ displays the cell bandwidth (only for LTE, WiMAX, and Wi‐Fi).

• ’tabularDataColumn’ displays data issued from Atoll’s TRANSMITTERS table and identified by tx.custom.x.column(column name).

Atoll column names are case sensitive:

The option below defines an optional label for a given column. If unset, the Atoll column name is used (e.g. "FOO"):

12.2.2.10 Default Values on the Patterns tab of the Antenna Tab

In the [ACPAntennaPage] section are the settings defining default values for the display of additional constraints on

mechanical and electrical tilt values. The following options are used to display these additional constraints:

12.2.2.11 Default Values for EMF Exposure

In the [ACPTplEMFPage] section are the settings defining default values for the EMF Exposure section of the Optimisation tab.

The following option is used to enable the EMF exposure module:

The option "weightLevel" enables you to define the level of importance accorded to the optimisation of EMF exposure. Threare three possible values:

• 0: Low: EMF exposure is optimised only if does not worsen coverage quality.• 1: normal: There is a tradeoff between EMF exposure and coverage quality (default).• 2: critical : EMF exposure is optimised independently of the effect it might have on coverage quality.

The following options enable you to define the default resolution in metres in the X, Y, and Z planes:

The following options define how EMF exposure will be measured in buildings: only on the facade or inside the building aswell:

[ACPReconfPage]

tx.custom.count=x

tx.custom.x.type=elevation

tx.custom.x.type=bandwidth

tx.custom.x.type=tabularDataColumn

tx.custom.x.column=FOO

tx.custom.x.label=’OptionalFooLabel’

[ACPReconfPage]

enableMTilt=1 # (default=0)

enableETilt=1 # (default=0)

[ACPTplEMFPage]

enable=1

weightLevel=1 # 0=low, 1=normal, 2=critical

resolutionXY=5

resolutionZ=3

206


The following option defines whether clutter classes and clutter heights are used to create a 3D representation of the terrainor whether just vectors are to be used. The default is "1" (yes), but, given that vectors are always given priority where theyexist, this option can be disabled if vectors are available for the entire area of interest.

The following option defines whether the 3D propagation model is using diffraction. When it is not, only positions with a directLOS to transmitters will register EMF exposure.

The following option defines whether the EMF module should use transparent mode. When transparent mode is used, noobstacle or indoor loss is accounted for.

The following option defines the calculation radius (in metres) around transmitters when calculating EMF exposure:

The following options define the default threshold and weight for the EMF exposure objective:

The following options enable you to define up to 16 propagation classes for EMF exposure. Each class is defined by a name,an indoor loss, and whether it can be edited by the user.

The following options enable you to map clutter classes to propagation classes. Each mapping is defined on two lines: the firstline defines the clutter class (by its code from the Description tab of the Clutter Classes Properties dialogue); the second linedefines the propagation class (by its ID under Propagation on the Optimisation tab of the ACP Setup dialogue). The defaultpropagation classes in the ACP are "Open" (ID "0"), "Vegetation" (ID "1"), and "Building" (ID "2"). Any additional propagationclasses will have an ID assigned when they are created.

In the [ACPEMFPage] section, you can specify whether or not users can define new propagation classes:

onlyFacade=1 # Measurement only on facade in building propagation classes.# Default = 1 (yes)

buildingDeeping=10 # if "onlyFacade" is set to 0, the depth in the building measured.

useDhmFromClutter=1 # Default is "1" (yes)

useDiffraction=0

isWorstCase=0 # Default is "0" (no)

calculationRadius=300

defaultObjThreshold=0.6defaultObjWeight=1

eclass.count=2 # The total number of propagation classes defined.

eclass.0.name=Open

eclass.0.position=0 # Distribution of measurement points:# 0=3D, i.e., distribution at all heights over area, 1=2D on top, 2=2D on bottom

eclass.0.buildingLos=0

eclass.0.linearBuildingLos=0

eclass.0.linearBuildingStart=0

eclass.0.editionFlag=0 # 0 can not be edited by user

clutterMapping.count=3

clutterMapping.0.clutterCode=10

clutterMapping.0.classCode=0







[ACPEMFPage]

isPropClassesExtendable=1 # "1" enables user to create propagation classes.

207


12.2.2.12 Controlling Antenna Pattern Smoothing

Crosswave version 4.0.4 has introduced the "AntennaLossesThreshold" option to control the smoothing performed onantenna patterns in gain calculations. A similar option has been introduced in Atoll ACP for compliance with Crosswave results.When "AntennaLossesThreshold" is specified in the Crosswave.ini file, the following lines must be included in ACP.ini:

where X is a value between 0 and 500 specified by "AntennaLossesThreshold" in Crosswave.ini to increase the specificthreshold applied by Crosswave.

12.2.2.13 Default Values on the Antennas Tab

In the [ACPAntennaPage] section are the settings defining default values for the Antennas tab.

The following options enable you to define default REGEX pattern that will is used to automatically calculating antennagroups:

By setting the following option to "1" (default), ACP will automatically apply the default antenna configuration each time anew setup is created (i.e., the configuration which have have been backed up by a user):

By setting the following option to "1", you enable the use of AEDT (additional electrical tilt) for managing different electricaltilt on each antenna pattern:

By setting the following option, you can control the internal logic that ACP uses to assign different antenna patterns todifferent frequency bands. ACP considers that an antenna pattern is allowed for a given frequency band if its base frequencyis within the allowed range (in MHz):

12.2.2.14 Defining the Antenna Masking Model

In the [ACPAntMaskModelPage] section, you can find the options used to set the choices available under Antenna MaskingMethod on the Setup Template tab of the ACP ‐ Automatic Cell Planning Properties dialogue.

You can use the "advancedUI" option to display a column called Delegate Calculation to Model. Using the DelegateCalculation to Model column, you can define whether the ACP calculates the path loss matrices or angles of incidence usedin antenna masking or whether it delegates calculation to the propagation model (providing the propagation modelimplements the appropriate methods of Atoll’s API). Delegating calculation to the propagation model provides more accurateresults but might take longer. Additionally, it will use disk space to store the calculation results.

The following option can be used to allow "Optimised" propagation models (i.e., propagation models that use the "Optimised"mode) to use "Full Path Loss" mode:

12.2.2.15 Defining Multi‐Storey Options

In the [ACPGeneralPage] section, you can define an option to display the multi‐storey module. Once displayed, the user canstill choose to not make a multi‐story optimisation; the "enable3dMode" only governs the display of the module.

[ACPGenericPM]

cw.antennaLossesThreshold = X

[ACPAntennaPage]

autoGroupPattern=(.*)_

autoGroupPattern_ant=(.*)_

autoGroupPattern_group=(.*)_

autoRestoreDefaultConfig=1

enableAedt=1

freqBandRange=99

[ACPAntMaskModelPage]

advancedUI=1 # The default is "0"; the "Delegate Calculation to Model"# feature is disabled.

nativeAllowFullPathLoss=1 # The default is "0"; the feature is disabled.

[ACPAntMaskModelPage]

enable3dMode=1 # The default is "1"; Setting the option to "0" hides the module.

208


12.2.2.16 Defining Reconfiguration Values in Custom Atoll Fields

In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields fromtables in the Atoll database. ACP will extract the values entered in the custom fields and use them as default reconfigurationvalues when a new optimisation setup is created. The values extracted can be updated in the ACP setup, but ACP will notupdate the Atoll tables with the new values.

12.2.2.16.1 Defining Reconfiguration Values for Transmitters and Repeaters Using Custom Atoll Fields

In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields fromthe Transmitters and Repeaters tables in the Atoll database. The custom columns in the Transmitters or Repeaters tablesmust match the column name defined in the acp.ini file. By default, the ACP does not extract custom fields.

If a value is undefined in a custom field for a cell, ACP will use the default value for thatparameter.

[ACPCustomFieldExtraction]

# The name of the custom column in Transmitters and Repeaters table use to # initialize the reconfiguration parameter for each transmitter or repeater.

tx.antenna.optimize=acp_ant_use # Best to define this column as a Boolean

tx.antenna.group=acp_ant_group

tx.etilt.optimize=acp_etilt_use

tx.etilt.min=acp_etilt_min

tx.etilt.max=acp_etilt_max

tx.tilt.optimize=acp_tilt_use

tx.tilt.min=acp_tilt_min

tx.tilt.max=acp_tilt_max

tx.tilt.step=acp_tilt_step

tx.azimuth.optimize=acp_azim_use # relative values from current azimuth

tx.azimuth.deltamin=acp_azim_deltamin

tx.azimuth.deltamax=acp_azim_deltamax

tx.azimuth.min=acp_azim_min # absolute value for azimuth angle

tx.azimuth.max=acp_azim_max

tx.azimuth.step=acp_azim_step

tx.azimuth.minInterSector=acp_azim_inter

tx.height.optimize=acp_height_use

tx.height.deltamin=acp_height_deltamin # relative values from current height

tx.height.deltamax=acp_height_deltamax

tx.height.min=acp_height_min # absolute value for height values

tx.height.max=acp_height_max

tx.height.step=acp_height_step

tx.gsm.power.optimize=acp_gsmpower_use

tx.gsm.power.min=acp_gsmpower_min

tx.gsm.power.max=acp_gsmpower_max

tx.gsm.power.step=acp_gsmpower_step

repeater.gain.optimize=acp_gain_use

repeater.gain.min=acp_gain_min

repeater.gain.max=acp_gain_max

repeater.gain.step=acp_gain_step

209


12.2.2.16.2 Defining Reconfiguration Values for Secondary Antennas Using Custom Atoll Fields

In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields fromthe Secondary Antennas table in the Atoll database. The custom columns in the Secondary Antennas table must match thecolumn names defined in the acp.ini file. By default, the ACP does not extract custom fields. Howeve, if the custom columnsare defined using these options and the column exists in the secondary antenna table, the reconfiguration items areautomatically configured using these values (instead of using the values defined at the transmitter level).

12.2.2.16.3 Defining Reconfiguration Values for Cells Using Custom Atoll Fields

In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields fromthe Cells table in the Atoll database. The custom columns in the Cells table must match the column names defined in acp.inifile.

The following options can be used to define the custom columns in the CdmaCells table. By default, the ACP does not extractcustom fields.

Some reconfiguration parameters such as height and azimuth can be defined either asrelative values (i.e., by defining the reconfiguration range starting from the current value)or as absolute values. You therefore only need to define the settings relevant to the valuetype (i.e., relative or absolute).


# The name of the custom column in Secondary Antenna table use to # initialize the reconfiguration parameter for each transmitter or repeater.

tx.antenna.optimise=acp_ant_use # Best to define this column as a Boolean

tx.antenna.group=acp_ant_group

tx.etilt.optimize=acp_etilt_use

tx.etilt.min=acp_etilt_min

tx.etilt.max=acp_etilt_max

tx.tilt.optimize=acp_tilt_use

tx.tilt.min=acp_tilt_min

tx.tilt.max=acp_tilt_max

tx.tilt.step=acp_tilt_step

tx.azimuth.optimize=acp_azim_use # relative values from current azimuth

tx.azimuth.deltamin=acp_azim_deltamin

tx.azimuth.deltamax=acp_azim_deltamax

tx.azimuth.min=acp_azim_min # absolute value for azimuth angle

tx.azimuth.max=acp_azim_max

tx.azimuth.step=acp_azim_step

tx.azimuth.minInterSector=acp_azim_inter

Some reconfiguration parameters such as height and azimuth can be defined either asrelative values (i.e., by defining the reconfiguration range starting from the current value)or as absolute values. You therefore only need to define the settings relevant to the valuetype (i.e., relative or absolute).


ccell.pilotPower.optimize=acp_pilotpower_use

ccell.pilotPower.min=acp_pilotpower_min

ccell.pilotPower.max=acp_pilotpower_max

ccell.pilotPower.step=acp_pilotpower_step

ccell.maxPower.optimize=acp_maxpower_use

ccell.maxPower.min=acp_maxpower_min

ccell.maxPower.max=acp_maxpower_max

ccell.maxPower.step=acp_maxpower_step

210


The following options can be used to define the custom columns in the WCells table. These will be used for defaultreconfiguration options for WiMAX cells. By default, the value of each is undefined; therefore the field will not be extracted.

The following options can be used to define the custom columns in the T4GCells table. These will be used for defaultreconfiguration options for LTE cells. By default, the value of each is undefined; therefore the field will not be extracted.

12.2.2.16.4 Defining Reconfiguration Values for Sites Using Custom Atoll Fields

In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields fromSites table in the Atoll database. The custom columns in the Sites table must match the column name defined by the settingsin the acp.ini file:

• Status of sites: By using the "site.status" option to define the name of the custom status column in the Sites table,you can extract the status (candidate or existing) of sites for site selection. All sites in the Sites table with the label setto the one defined by the "site.status.candidate" option will be automatically set as candidate sites. Any sites with alabel other than the one defined by the "site.status.candidate" option will be considered as existing sites. By default,all active sites are considered as existing sites.

The following options can be used to define custom columns in the Sites table. These will be used for default reconfigurationoptions for each site.


wcell.power.optimize=acp_power_use

wcell.power.min=acp_power_min

wcell.power.max=acp_power_max

wcell.power.step=acp_power_step


lcell.power.optimize=acp_power_use

lcell.power.min=acp_power_min

lcell.power.max=acp_power_max

lcell.power.step=acp_power_step


site.status=acp_site_status # Name of the custom column in Sites table. # Default value is 'ACP_STATUS'.

site.gsm.status=acp_site_gsm_status

site.umts.status=acp_site_umts_status

site.lte.status=acp_site_lte_status

site.status.candidate=candidate # Name used to define a candidate site.


site.disableSelection=acp_site_disableSelection

site.gsm.disableSelection=acp_site_gsm_disableSelection

site.umts.disableSelection=acp_site_umts_disableSelection

site.lte.disableSelection=acp_site_lte_disableSelection

site.removeable=acp_site_removeable

site.gsm.removeable=acp_site_gsm_removeable

site.umts.removeable=acp_site_umts_removeable

site.lte.removeable=acp_site_lte_removeable

site.sectorsRemoveable=acp_site_sectorsRemoveable

site.gsm.sectorsRemoveable=acp_gsm_site_sectorsRemoveable

site.umts.sectorsRemoveable=acp_umts_site_sectorsRemoveable

site.lte.sectorsRemoveable=acp_lte_site_sectorsRemoveable

site.azimLocked=acp_site_azimLocked

site.heightLocked=acp_site_heightLocked

211


The following option can be used to manage the ’disable reconfiguration’ attribute.

12.2.2.16.5 Defining Reconfiguration Values for Antennas Using Custom Atoll Fields

In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields fromAntennas table in the Atoll database. ACP can use the information in the custom fields to group antennas and to set defaultreconfiguration values when a new optimisation setup is created . The custom column in the Antennas table must match thecolumn names defined in the acp.ini file.

The following option can be used to name the custom column in the Antennas table to group antenna patterns into groupsof physical antennas (i.e., all patterns related to the same physical antenna) and group the physical antennas at differentfrequencies into radomes by using the "antenna.model" option. Using the "antenna.model" enables you to automaticallyform a multi‐band antenna. The antenna model is by default set to the PHYSICAL_ANTENNA column of the Antennas table.Hence by default the auto antenna grouping is always enabled if antenna patterns are correctly assigned to physical antennas.

If the physical antenna has been defined using the "antenna.model" option, the following option can be used to name thecustom column in the Antennas table that is used to define antenna groups. In the custom column in the Antennas table, allantenna patterns corresponding to physical antenna belonging to the same group are identified with a unique string. The ACPautomatically groups all physical antenna into a new group with the name given by the string used in the column.

The following options can be used to name the custom columns in the Antennas table to automatically define the mechanicaltilt options.

The following option can be used to name the custom column in the Antennas table to automatically link antenna elementsof a multi‐band physical antenna which have the same electrical tilt. In the ACP Setup dialogue, this is accomplished byselecting the check box in the Same Elec. Tilt column. The "antenna.etilt.share" option should contain a list of the space‐separated frequencies for which the corresponding physical antenna must be linked (i.e., physical antenna that always usessame electrical tilt).

The following options can be used to name the custom columns in the Antennas table to automatically define the electricaltilt options.


site.reconfLocked=acp_site_reconfLocked


antenna.model=PHYSICAL_ANTENNA


antenna.group.model=acp_group_model


# The name of the custom column in ANTENNA table of type 'bool', defining# which antenna pattern is associated with a 'mechanical tilt constraint' antenna.tilt.use=ACP_TILT_USE

# The name of the custom columns in ANTENNA table of type 'string' or numeric,# defining the mechanical tilt allowed range. Non-valid values are treated as# "forbidden"antenna.tilt.min=ACP_TILT_MINantenna.tilt.max=ACP_TILT_MAX


antenna.etilt.share=ACP_ETILT_SHARE

To optimise the electrical tilt, first set the "enableAedt" and "enableETilt" options to "1"to activate them.


# The name of the custom column in ANTENNA table of type 'bool', defining# which antenna pattern is associated with an 'electrical tilt constraint' antenna.etilt.use=ACP_ETILT_USE

212


12.2.2.17 Defining Site Class Options

You can set options in the ACP.ini file to define site classes in the ACP. You can both define site classes that automaticallyappear in the ACP Setup dialogue and set options in the ACP.ini so that the ACP applies site classes based on optional data inthe Atoll database.

12.2.2.17.1 Defining Automatic Site Classes

In the [ACPGeneralPage] section, you can find the option used to define the whether the site class feature appears.

The following option can be used to show or hide the site class feature and set the number of site classes defined:

In the [ACPTplGeneralPage] section, you can define the default values when the site class option is available. These settingsare local settings.

You can then define the site classes that will appear each time a new ACP optimisation is created along with pre‐defined costs.The name of each class as it appears in the ACP is defined by an option called "cost.classes.X.name" where "X" is a sequentialnumber. The corresponding settings for the class defined in "cost.classes.X.name" are defined using the following options:

• cost.classes.X.azimuth.cost: This key is used to define the cost of changing the antenna azimuth.• cost.classes.X.azimuth.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.• cost.classes.X.tilt.cost: This key is used to define the cost of changing the mechanical tilt of the antenna.• cost.classes.X.tilt.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.• cost.classes.X.antenna.cost: This key is used to define the cost of changing the type of the antenna.• cost.classes.X.antenna.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.• cost.classes.X.etilt.cost: This key is used to define the cost of changing the electrical tilt of the antenna.• cost.classes.X.etilt.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.• cost.classes.X.height.cost: This key is used to define the cost of changing the antenna height.• cost.classes.X.height.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.• cost.classes.X.power.cost: This key is used to define the cost of changing the power.• cost.classes.X.power.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.• cost.classes.X.siteVisitCost: This key is used to define the cost of a site visit.• cost.classes.X.upgradeSiteCost: This key is used to define the cost of upgrading an existing site.• cost.classes.X.newSiteCost: This key is used to define the cost of creating a new site.• cost.classes.X.removeSiteCost: This key is used to define the cost of removing an existing site.

The following is an example of the keys for the first site class (numbered "0") called "Planned" in this example.

# The name of the custom columns in ANTENNA table of type 'string' or numeric,# defining the AEDT and e-tilt allowed range. Non-valid values are treated as# "forbidden"antenna.etilt.min=ACP_ETILT_MINantenna.etilt.max=ACP_ETILT_MAX

[ACPGeneralPage]

cost.classes.showUI=1 # The default is "1"; the site class feature is enabled.

cost.classes.count=1 # Number of defined classes

[ACPTplGeneralPage]

cost.classes.count=1 # Number of defined classes

cost.classes.0.name=Planned

cost.classes.0.azimuth.cost=1

cost.classes.0.azimuth.isSiteVisit=true

cost.classes.0.tilt.cost=1

cost.classes.0.tilt.isSiteVisit=true

cost.classes.0.antenna.cost=1

cost.classes.0.antenna.isSiteVisit=true

cost.classes.0.etilt.cost=0.1

cost.classes.0.etilt.isSiteVisit=false

cost.classes.0.height.cost=1

cost.classes.0.height.isSiteVisit=true

cost.classes.0.power.cost=0.1

213


12.2.2.17.2 Automatic Assignment of Site Classes in the ACP

In the [ACPCustomFieldExtraction] section, you can define the custom field in the Sites table of the Atoll database thatidentifies the site class of each site.

The site class defined in the Sites table will be assigned automatically when an ACP optimisation is defined. For new candidatesites which are located on an existing site, the site class is the same as the site on which the new candidate is located. For newcandidate sites which are not co‐located on an existing site, the site class is set to "Default" and can be changed manually.

By defining the costs of each site class as explained in "Defining Automatic Site Classes" on page 213, the cost structure isautomatically defined as well.

12.2.2.18 Defining the Appearance of the Optimisation Dialog Box During a Run

In the [ACPMapDefault] and [ACPMapPage] sections are the settings you can use to define the appearance of theOptimisation dialog box during a run. Some options refer to the Quality tab and others to the Graphs tab.

12.2.2.18.1 Defining the Colours in the Analysis Maps on the Quality Tab

The following settings can be used to define the colours in the analysis maps on the Quality tab.

There are two possible formats for defining the range of colours on maps:

1. Detailed format: The detailed format enables you to set a non‐uniform range. The number of ranges is defined and,for each range, the minimum and maximum value of the range followed by its RGB color representation.

2. Uniform format description: A uniform format description using a range and step, in one of the following intervals:

• [firstBreak startcolor] [lastBreak endColor]• ‐INF [firstBreak startcolor] [lastBreak endColor]

where interval starts from minus infinite to englobe all lower values and avoid transparent pixels for lower values.

These colormap descriptions are used for default colormap and can easily be changed by the user. The settings are the samefor the various quality indicator of the various technologies, where you replace:

• <techno> with: umts, gsm, lte, wimax, cdma

cost.classes.0.power.isSiteVisit=false

cost.classes.0.siteVisitCost=2

cost.classes.0.upgradeSiteCost=5

cost.classes.0.newSiteCost=10

cost.classes.0.removeSiteCost=-5

You must first create the corresponding custom column in the Sites table of the Atolldatabase and assign a site class to each site in this column for this option to have effect.


site.costClass=[name of custom field in Site table]

[ACPMapDefault]

colormap.<techno>.<quality>.nbRange=8 # Number of ranges to be defined

colormap.<techno>.<quality>.range.0=[-99999.000000 -15.000000] RGB(0 0 255)







colormap.<techno>.<quality>.range.7=[-3.000000 99999.000000] RGB(255 0 0)

[ACPMapDefault]

colormap.<techno>.<quality>.rangeDefinition=[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5

colormap.<techno>.<qual>.rangeDefinition=-INF[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5

214


• <quality> with:• In GSM: sl, slgain, • In UMTS: ecio, ec, ecgain, eciogain, ecnt, ecntgain• In LTE: sl, slC, slCN, rsrp, cinr, rsrq, slgain, cinrgain, rssi• In WiMAX: sl, slC, slCN, cinr, slgain, cinrgain

In addition, a number of other colormaps can be defined for other types of maps:

• colormap.overlap and colormap.overlapgain for overlap maps• colormap.objective and colormap.objective.gain for objective status maps• colormap.bestcell.ttilt and colormap.change.ttilt for combined electrical/mechanical tilt maps• and a few others for change maps, emf maps, etc. The default acp.ini file installed with the ACP has a complete list

12.2.2.18.2 Other Components of the Optimisation Dialog Box

The following options can be used to define other components of the Optimisation dialog box during a run.

Below are the default colour codes for the foreground and background on the Quality tab, with the RGB code as an integer:

The RGB code for white is calculated as follows: .

The following options define the pixel size used in the maps on the Quality tab. You can let ACP automatically define the pixelsize or you can define it yourself:

The following options define the size of the map title on the Quality tab:

The following option defines the width of the margin on the Quality tab:

The following options define the appearance of the map legend on the Quality tab:

The following option defines whether or not the axis will be displayed on the Quality tab:

The following options define the appearance of the histogram on the Quality tab:

The following options define the appearance of the focus zone on the Quality tab:

[ACPMapPage]

config.foreground = 0 #default foreground colour setting (black)

config.background = 16777215 #default background colour code (white)

config.isAutoPixel=1 # Automatically calculate point size from coverage surface

config.pixelSize=1 # If autopixel is not set, use this number of pixels for each point

config.pixelCoverage=50 # If autopixel is set, calculate the pixel size of a pointto try to cover the set percentage of the used surface

config.maxPixelSize=6 # If autopixel is set, limit the pixel size to the set maximum.

config.titleHeight=16 # Title height in pixels

config.titleFontSize=16 # Size of title font in points

config.margin=2 # Margin width in pixels

config.showLegend=1 # Defines whether the legend is displayed.

config.legendWidth=40 # Defines the width of the legend in pixels.

config.legendFontSize=11 # Defines the font used in points.

config.legendForeground=0 # RGB code as integer: here black

config.showAxis=1

config.showHistogram=1 # Defines whether the histogram is displayed.

config.histogramHeight=60 # Defines the width of the histogram in pixels.

config.showFocusZone=1 # Defines whether the focus zone is displayed.

config.focusLighterPercent=30 # Defines how much lighter the area outside the focuszone is displayed.

255 255 28 255 2

16 16777215=+ +

215


12.2.2.19 Defining the Appearance of Predictions

In the [ACPMapDefault] section is the option for defining the appearance of predictions created from optimisation results.

The following option defines the transparency of predictions:

12.2.2.20 Defining New Predictions

In the [ACPNewMapDlg] section are options for displaying additional predictions that can be created from setups and fromthe optimisation results.

Setting the option "showBestServerAerialMap" enables the user to create a prediction that displays the initial and finalcoverage by antenna.

Setting the option "showObjectiveWeightMap" enables the user to create a prediction that displays the weight used for thetraffic and for each zone.

Setting the option "showBestServerTxMap" enables the user to create a prediction that displays the initial and final coverageby transmitter.

Setting the option "showchangeImprovementMap" enables the user to create a prediction that displays the improvement incoverage.

Setting the option "showSectorSelectionMap" enables the user to create a prediction that displays the added or removedsectors during site selection.

Setting the option "showTotTilt" enables the user to create a prediction that displays the total tilt (electrical and mechanical).

12.2.2.21 Defining the Functionality of the Commit Tab

In the [ACPCommitPage] section is the option for defining whether the user can only edit the set of changes to be committedon the Change Details tab (default). Setting "allowUserChangeForCommit" to "true" allows the user to edit the set of changeson the Commit tab; this setting is not recommended.

You can use the "addCandidateComment" option to create a comment in any site, transmitter, and cells automatically createdby ACP in Atoll as part of the candidate site selection. No comment is added if this option is left blank.

Trac1905: You can use the following options to transfer to Atoll the candidate pathloss computed by ACP, so as to avoid re‐computation by Atoll.

transparency=50

[ACPNewMapDlg]

showBestServerAerialMap=1 # "1" displays the option, "0" hides the option

[ACPNewMapDlg]

showObjectiveWeightMap=1 # "1" displays the option, "0" hides the option

[ACPNewMapDlg]

showBestServerTxMap=1 # "1" displays the option, "0" hides the option

[ACPNewMapDlg]

showchangeImprovementMap=1 # "1" displays the option, "0" hides the option

[ACPNewMapDlg]

showSectorSelectionMap=1 # "1" displays the option, "0" hides the option

[ACPNewMapDlg]

showTotTilt=1 # "1" (default) displays the option, "0" hides the option

[ACPCommitPage]

allowUserChangeForCommit=false

[ACPCommitPage]

addCandidateComment=Created from ACP candidate list

216


12.2.2.22 Defining the Appearance of the Overlay Window

In the [ACPOverlayDialog] section is the option for defining the opacity of the overlay window when it loses focus. A value of100 disables it.

12.2.2.23 Defining the Appearance of the Graph Tab

In the [ACPGraphPage] section is the option for enabling the display of time markers on the Graph tab of the OptimisationProperties dialogue. A value of 100 disables it.

12.2.2.24 Defining the Default Font

In the [ACPUI] section is the option for defining the default font to be used by the grid, graph component, and mapcomponent. In the example below, the font "MS UI Gothic," used in Japanese systems, is set as the default font.

12.2.2.25 Exporting Optimisation Results in XML

In the [ACPXmlReport] section are the options for defining the contents and appearance of an XML report generated from theStatistics tab of the optimisation Properties dialogue.

12.2.2.26 Changing the Colour Legend for the Optimisation Graph

In the [ACPColorsDefault] section are the options for defining the default colours in the Optimisation window (during andafter a run). These default colours can be defined in either of the following formats:

The following are the default colour codes for the graphs in the Optimisation window (on the Graphs tab during a run) and inthe Optimisation results after a run (on the Change Details and Graph tabs)

[ACPCommitPage]

transferCandidatePathlossToAtoll=0

transferCandidatePathlossToAtoll.autoRemoveHdr=1

[ACPOverlayDialog]

opacity=100

[ACPGraphPage]

showTimeMarkers=1 # add time markers on the X axis. Default is "0" (OFF)

[ACPUI]

# define the font used by grid, graph component and map componentDefaultFont=MS UI Gothic

# for grid only, define the used font size. 0 mean default sizeDefaultGridFontSize=0

enableXmlExport=1 #enable the xml report from the ResultStatPage

generateXmlSection=-1 # bit combination of following: 1=metadata, 2=setup, 4=resultSummary, 8=resultSectors, 16=resultIterations, 32=resulstChangeset, 64=resultMaps., -1=all

encoding=UTF-8

saveDefaultStylesheet=1 #save a default stylesheet if none exist

defaultStylesheetName=.acpReport.xslt # name of the default stylesheet file. set it empty to disable stylesheet processing instruction

graph.umts1 = RGB(0 0 255)orgraph.umts1 = 0000FF -> RGB hexadecimal color code as used in HTML

graph.umts1 = B34700 (same colour codes are used in CDMA)graph.umts2 = FF6600graph.umts3 = FFB380

217


The following are the default colour codes for the histogram in the Optimisation window (on the Changes tab during a run).

12.2.3 ACP Core Engine OptionsThe settings in the [ACPCore] section are used to define how the ACP engine functions.

12.2.3.1 Log File Settings

ACP enables you to set up a log file as well as create a crash report in case of an application crash.

The following option defines whether ACP generates a log file (with the name ATL_NAME_optim.log):

12.2.3.2 Calculation Thread Pool Settings

The following options define how the calculation thread pool will be managed. If "useComputationThreadPool" is set to"false," ACP uses only one thread. If "useComputationThreadPool" is set to "true," ACP uses the number of threads specifiedby the "computationThreadPoolSize" option. The default setting for "computationThreadPoolSize" is "‐1" and means that ACPwill use one thread per processor core (CPU) available.

graph.gsm1 = 660099graph.gsm2 = D580FFgraph.gsm3 = EABFFF

graph.wimax1 = 458A8A (same colour codes are used in Wi‐Fi)graph.wimax2 = 30BFBFgraph.wimax3 = 66FFFF

graph.lte1 = FFD100graph.lte2 = 999900graph.lte3 = D9CC7F

graph.obj1 = FF000D (colour codes used for multi‐technology objectives in multi‐technology optimisations)graph.obj2 = 3600FFgraph.obj3 = 18FF00graph.obj4 = FFD100

graph.cost = 00FF00 (colour code for financial cost)graph.expos = 3737A6 (colour code for EMF exposure)

graph.load = 0AFFFF (colour codes for load balance)graph.loadqi = A27901graph.traf = F9F602

change.antenna = RGB(0 0 255)change_etilt = RGB(64 224 208)change_azimuth = RGB(0 255 0)change_tilt = RGB(255 255 0)change_power = RGB(193 0 66)change_height = RGB(255 173 93)change_txRemoved = FFCDE8change_siteRemoved = FF99CCchange_siteAdded = 99CCFFchange_txAdded = 5D927Dchange_repGain = 660099

[ACPCore]

generateLogFile=0 # The default is "0"; no log file.

[ACPCore]

useComputationThreadPool=true

computationThreadPoolSize=-1

218


12.2.3.3 Number of Threads Used for Propagation Model Calculations

The following option defines how many threads the propagation model can use when calculations (for example, of height orangles of incidence) are delegated to the propagation model. This can be useful, for example, to control the number oflicences taken by the ACP, without reducing the number of threads used by regular ACP calculations. The following settingsare possible:

• ‐2: The default value means that the propagation model will use the same number of threads as that defined by the"computationThreadPoolSize" option.

• ‐1: Auto configuration; the propagation model will use one thread for each CPU core.• Other: Entering a numerical value for "pathlossThreadPoolSize" indicates the number of threads the propagation

model can use.

12.2.3.4 Memory Management Settings

The following options define how the ACP manages memory during calculations.

The ACP tries to estimate the worst‐case scenario in memory use, and indicates to the user when memory use seems too high.Using one of the following options, you can define the method ACP uses to indicate excessive memory use:

• memLimitNumPos: Memory use is determined to be excessive when the maximum number of pixels, as defined in"memLimitNumPos" is reached during a calculation. Setting "memLimitNumPos" to "‐1" deactivates this option.

• memLimitMemory: Memory use is determined to be excessive when the estimated memory use in Mb, as defined in"memLimitMemory" is reached during a calculation. Setting "memLimitMemory" to "‐1" deactivates this option.

• memLimitUseableMemory: Memory use is determined to be excessive when the estimated memory use exceeds thepercentage of the total memory available for Atoll, as defined in "memLimitUseableMemory." Setting"memLimitUseableMemory" to "‐1" deactivates this option.

If all three options are deactivated, ACP does not check excessive memory usage.

The "abortIfMemLimitReach" option defines how ACP reacts if the defined maximum memory use is reached. By default (with"abortIfMemLimitReach" set to "0"), ACP will attempt to allocate memory. If unable to successfully allocate memory, ACPdisplays a message and the calculation is stopped. When using the option "abortIfMemLimitReach", then ACP will not start ifthe message indicating excessive memory use is displayed.

By default, excessive memory use is considered an estimate of 80% of the memory available to the process; ACP is notprevented running even when 80% is exceeded.

12.2.3.5 Signal Level and Macro Diversity Gain Calculation Options

The following options determine how ACP calculates the signal level and the macro diversity gain mode.

12.2.3.5.1 Signal Level

You can define how ACP measures the signal level (UMTS RSCP, GSM BCCH Power, WiMAX Preamble Power, LTE Referencesignal Power, CDMA pilot power) using the "linkMode" option. The "linkMode" option can have one of the following values:

• 0: When "linkMode" is set to "0," ACP considers the signal level on the downlink and transmission losses are takeninto account. This is the default setting.

• 1: When "linkMode" is set to "1," ACP considers the signal level on the uplink and reception losses are taken intoaccount.

• 2: When "linkMode" is set to "2," ACP does not take reception or transmission losses into account.

[ACPCore]

pathlossThreadPoolSize=-2 # Default. Same as computationThreadPoolSize.

When ACP estimates actual memory use (i.e., using either "memLimitMemory" or"memLimitUseableMemory"), the memory estimate is only a rough estimate. Dependingon the project, actual memory usage can be quite different.

memLimitNumPos=-1 # A setting of "-1" deactivates this option.

memLimitMemory=-1 # A setting of "-1" deactivates this option.

memLimitUseableMemory=80 # A setting of "-1" deactivates this option.

abortIfMemLimitReach=0

linkMode = 0 # The default

219


12.2.3.5.2 Macro Diversity Gain (UMTS Only)

The following option defines whether ACP takes macro diversity gain into account in UMTS. "addPilotSHOGain" can have thefollowing values:

• 0: When "addPilotSHOGain" is set to "0," ACP does not take macro diversity gain into account.• 1: When "addPilotSHOGain" is set to "1," ACP takes macro diversity gain into account. This is the default value.

12.2.3.6 Determining Transmitter Altitude

The following option defines how ACP determines the transmitter altitude when no site altitude is defined in Atoll."useSiteAltitude" can have the following values:

• 0: When "useSiteAltitude" is set to "0," ACP uses the exact transmitter coordinates, including dx and dy offset.• 1: When "useSiteAltitude" is set to "1," ACP uses only the coordinates of the site. This is the default value.

12.2.3.7 Automatic Candidate Positioning Options

The following option defines the minimum distance that must be respected between an automatically created candidate andan existing site or a predefined candidate site. If Atoll can not create an automatic candidate site and respect this distance,no candidate will be created. The default value is 25% of the inter‐site distance defined in the Automatic CandidatePositioning dialogue.

The following option defines the default inter‐candidate site distance in metres.

The ACP normally places candidate sites in a strict hexagonal pattern. However, the ACP can search for a more appropriatesite within a search radius ratio according to the defined rules. The following option defines the default search radius ratio asa percentage of the defined inter‐candidate site distance.

The following option defines the default minimum increase in altitude (in metres) that the ACP must find when placing a newautomatic candidate site.

12.2.3.8 Balancing Speed, Memory Use, and Accuracy in Calculations

On the User Preferences tab of the ACP ‐ Automatic Cell Planning Properties dialogue, ACP enables you to select a mode ofoperation that balances balance speed, memory use, and accuracy. By defining the settings of the options in the acp.ini filethat each mode uses, you can fine‐tune how ACP will operate in the selected mode:

• High Speed: Using the highest speed also uses the least memory although the final results might be slightly lessaccurate.

• Default: When no changes are made to the acp.ini file, ACP uses the default settings. The default settings can beoverridden by changing the settings in this section.

• High Precision: When the settings in this section are defined to give the results of the highest precision, calculatingthe results will take the longest time and will use more memory.

Any changes you make here must match corresponding changes in the Atoll.ini file. When"addPilotSHOGain" is set to "0," the ACP results will only match the results in Atoll if thefollowing settings are made in the [CDMA] section of the Atoll.ini file: AddPilotSHOGain=0

addPilotSHOGain=1 # The default

Any change you make here must match a corresponding change in the Atoll.ini file. When"useSiteAltitude" is set to "1," the ACP results will only match the results in Atoll if thefollowing setting is made in the Atoll.ini file: useSiteAltitude=1

useSiteAltitude=1 # The default

[ACPAutoCandPosDlg]

minInterSiteDistRatio=0.25 # Default

interSiteDist=500

searchRadiusRatio=30

hpHeightThres=10

220


The options described below are those used for the default operation mode

The acp.ini options that define how the selected mode works are described below:

• maxMonitorCell: The "maxMonitorCell" defines the maximum number of cells monitored. This option affects memoryuse and accuracy. The analogous options for the high speed mode and the high precision mode are"maxMonitorCellSpeed" and "maxMonitorCellPrec", respectively.

• threshLevelMonitorCell: The "threshLevelMonitorCell" defines the best server signal threshold (dB) in order to bemonitored. This option affects memory and accuracy.

• The analogous options for the high speed mode and the high precision mode are "threshLevelMonitorCellSpeed" and"threshLevelMonitorCellPrec", respectively.

The following options define the values ACP uses for default mode:

The following options define the values ACP uses for high speed mode:

The following options define the values ACP uses for high precision mode:

Other options in the acp.ini file can be used to define additional offsets that will be used by the specific technology that ACPis optimising:

12.2.3.9 Accessing Raster Data

When working in co‐planning mode, you have several Atoll documents open and you are working with the ACP from the maindocument. ACP needs to access raster data and by default it accesses only the raster data specified in the main document. Iffor some reason different raster data is used in the secondary document, you must set the ACP to access raster data for eachdocument separately using the following option:

Atoll ACP loads raster data with block‐based processing to reduce memory usage. The maximum memory (in Mb) allowed forthis block processing in Mb is controlled with the following setting:

You can reduce this number if you experience issues with ACP failure due to memory allocation.

12.2.3.10 Accessing Path Loss Matrices

You can define how ACP accesses path loss matrices using the "pathlossAccessMode" option. This option has two possiblevalues:

• 0: If this option is set to "0," ACP will access path loss matrices through Atoll. • 1: If this option is set to "1," ACP will access path loss matrices directly. With this setting, the path loss matrices must

be stored externally; they can not be embedded.• 2: If this option is set to "2," ACP will access path loss matrices directly if they are external, otherwise through Atoll if

they are embedded. This is the default value.

maxMonitorCell=32

threshLevelMonitorCell = 35

maxMonitorCellSpeed=30

threshLevelMonitorCellSpeed = 30

maxMonitorCellPrec=35

threshLevelMonitorCellPrec = 40

threshLevelOffUmts=0

maxMonitorOffUmts=0

threshLevelOffGsm=0

maxMonitorOffGsm=0

threshLevelOffWimax=5

maxMonitorOffWimax=5

threshLevelOffLte=10

maxMonitorOffLte=10

gisDataTechnoShared=0

gisDataCacheMemMax=256

221


12.2.3.11 Filtering Clutter Class Layers

When using several layers of raster clutter classes, each with a different resolution, you can define which resolution (usuallythe lower resolution) ACP should use when defining zones by clutter class. Setting the "gisDataClutterOnlyRes" option to "0"(the default) means that clutter class layers will not be filtered out by resolution. Setting this option to any other value (forexample, "20") means that ACP will only use clutter classes with that resolution (in this calse, "20").

If you set the "gisDataClutterOnlyRes" option to filter out all clutter classes but those with the defined option, you should alsolist the clutter classes that are not to be used in the "zone.clutter.hiddenCodes" in the [ACPGeneralPage] section to ensurethat the user will not create zones based on clutter classes that are not used. When you define the clutter classes that are notused, they will not be displayed in the Zone Definition dialogue.

12.2.3.12 Preamble Segmentation (WiMAX)

You can define how ACP takes segmentation into account using the "wimaxPreambleSegmented" option. This option enablesyou to take into account the change in change in calculation methods from version 2.7.1 to version 2.8.0 of Atoll. In version2.7.1, the preamble was not considered as segmented unless the frame configuration used by the cell was flagged assegmented. In version 2.8.0, the preamble is considered by default to be segmented.

This option has the possible values:

• 0: This value is intended for versions of Atoll up to and including version 2.7.1. If this option is set to "0," ACP will onlytake preamble segmentation into account if the segmentation flag of cell frame configuration is set to ON.

• 1: This value is intended for versions of Atoll of 2.8.0 and up. If this option is set to "1," ACP always takes preamblesegmentation into account.

• 2: If this option is set to "2," ACP automatically detects the version of Atoll used. This is the default value.

12.2.3.13 Multi‐antenna Interference Calculation (LTE)


• 0: Interference independent of number of transmit antennas.• 1: Interference multiplied by number of transmit antennas.• 2: ACP automatically detects the version of Atoll used, and hence the value used by Atoll for this option. This is the

default value.

12.2.3.14 Multi‐antenna Interference Calculation (WiMAX)


• 0: Interference independent of number of transmit antennas.• 1: Interference multiplied by number of transmit antennas.• 2: ACP automatically detects the version of Atoll used, and hence the value used by Atoll for this option. This is the

default value.

12.2.3.15 Cyclic Prefix Energy in Signal Level Calculation (LTE)

Refer to "Including Cyclic Prefix Energy in LTE Signal Level Calculation" on page 186 for details.


• 0: Included.• 1: Excluded.

pathlossAccessMode=2

[ACPCore]

gisDataClutterOnlyRes=20 # ACP will only use clutter classes with this resolution

[ACPGeneralPage]

zone.clutter.hiddenCodes=0,1,2,12,13 # These clutter classes are not displayed

wimaxPreambleSegmented=2

lteMultiAntennaInterference=2

wimaxMultiAntennaInterference=2

222


• 2: ACP automatically detects the version of Atoll used, and hence the value used by Atoll for this option. This is thedefault value.

12.2.3.16 Cyclic Prefix Energy in Signal Level Calculation (WiMAX)

Refer to "Excluding Cyclic Prefix Energy in WiMAX and Wi‐Fi Signal Level Calculation" on page 186 for details.


• 0: Included.• 1: Excluded.• 2: ACP automatically detects the version of Atoll used, and hence the value used by Atoll for this option. This is the

default value.

12.2.3.17 Applying Transmit Diversity Gains to Reference Signals (LTE)

This option defines in multi‐antenna mode how the instantaneous Reference Signal power is calculated.

• 0: use the power transmitted on a single port (Default)• 1: use the power transmitted on both ports• 2: use the same transmit diversity gain as used for PDSCH (unsupported)

12.2.3.18 Fixed Ratio Between Pilot Power and Max Power (UMTS)

When optimising the maximum cell power in UMTS, the ACP forces the ratio between pilot power and maximum power tostay constant. You can remove this constraint using the following option:

12.2.3.19 Showing Initial/Final "Total Power"or "DL Load" on Sectors Tab (UMTS)

When optimising the pilot power in UMTS, you can display an additional Total Power (dBm) or DL Load (%) column on theSectors tab of the Optimisation Properties dialog box, according to the DL load setting (Absolute or % Pmax, resp.) in theNetwork Settings Properties dialog box.

Before you run an optimisation, make sure that Pilot Power is selected on the UMTS Cells tab of the Reconfiguration page(Setup Properties) and set the following option in ACP.ini:

12.2.3.20 Enabling Multi‐technology Optimisation Including WiMAX

In order to use the ACP to optimise your WiMAX network with any other technology network (GSM, UMTS, CDMA2000, andLTE), set the following option in ACP.ini:

12.2.4 EMF Exposure Core OptionsIn the [ACPEMFCore] section there are several options controlling the EMF exposure calculation engine.

lteExcludeCPFromUsefulPower=2

wimaxExcludeCPFromUsefulPower=2

lteUseDivGainOnRS=0

umtsPilotPowerRatioFixed=0

[ACPResultSectorPage]

showDlLoad=1 # (default=0)

[ACPImportProject]

importWimax=1 # (default=0)

This option is valid for co‐planning support between WiMAX and:

• Single‐RAN GSM, UMTS, CDMA2000, and LTE• Multi‐RAT 3GPP and 3GPP2

223


One set of options allows for the detection and auto correction of transmitter heights which are found to be indoors, justbelow the roof. This is usually caused by inconsistencies between the vectors imported to create the 3D representation of theterrain and Atoll database.

The other option controls the resolution used internally to rasterise input vectors, the default being 2 metres.

When the height of a transmitter is within the Digital Height Model (i.e., the combination of clutter heights and importedvectors used to create the 3D representation of the terrain) and DHM‐offset, then it is considered to be indoors, just belowthe roof. The ACP automatically detects these transmitters and displays warnings in the Event Viewer. The defaultdistancebeneath the roof is 5 metres.

The ACP can automatically adjust the height of transmitters that are below roof so that they are on top of the clutter heightusing the defined offset (in metres).

The following option defines the internal resolution in metres for terrain 3D representation when the ACP rasterises inputvectors:

The following option allows you decrease the displayed EMF level when penetration loss is increased for buildings.

flagPixelFacadeDist defines the indoor distance from façade for a pixel to be considered as "indoor". When the distance is 0,the outdoor pixels will be applied the indoor penetration loss specified in the Propagation Class Definition table (Propagationpage on the Optimisation tab).

12.2.5 Other OptionsIn the [ACPMisc] section are several additional ACP configuration options.

12.2.5.1 Validity of Coverage Predictions

You can use the following option to enable or disable the automatic verification of the validity of coverage predictions beforerunning an optimisation setup.

The following options can be used to enable other automatic verifications on the number of active transmitters, their pathlossfile size, and locked status in the Atoll document:

If "autoCheckPredictionValidity" is set to "1," thereby enabling the verification of the validity of coverage predictions, you canhave ACP automatically recalculate the invalid coverage predictions using the following option. If it is set to "0," ACP will notautomatically recalculate predictions.

[ACPEMFCore]

detectTxIndoorOffset=5

resetTxHeightWhenIndoor=0 # "0" is the default; height is not reset.

vectorRasterizationResolution=2 # "2" is the default.

flagPixelFacadeDist=0 # "0" is a distance in metres.

autoCheckPredictionValidity=1 # "1" enables the automatic verification

autoCheckPredictionFileValidity=1 # Check of path loss matrices before a run.

autoCheckTxNumber=1 # Check number of active transmitters.

manageLockedPredictionAsvalid=1 # Treat locked prediction as always valid.# Default is "1" (true)

autoPathlossRecomputation=0

224

Atoll 3.2.1 Administrator ManualAT321_AM_E1 Index of Initialisation Options

Index of Initialisation Options

Aacp.ini main options

Calculation Thread Pool Settings

computationThreadPoolSize 218useComputationThreadPool 218

Custom columns on Transmitters and Remote tabs of Reconfigu‐ration page

206tx.custom.x.column 206tx.custom.x.label 206tx.custom.x.type 206

Default Values on the Antennas Tab

enableAedt 208

Default Values on the Optimisation Tab

cost.antenna.cost 195cost.antenna.isSiteVisit 195cost.azimuth.cost 195cost.azimuth.isSiteVisit 195cost.etilt.cost 195cost.etilt.isSiteVisit 195cost.height.cost 195cost.height.isSiteVisit 195cost.newSiteCost 195cost.power.cost 195cost.power.isSiteVisit 195cost.removeSiteCost 195cost.siteVisitCost 195cost.tilt.cost 195cost.tilt.isSiteVisit 195cost.upgradeSiteCost 195

Default Values on the Patterns tab of the Antenna Tab

enableETilt 206enableMTilt 206

Default Values on the Reconfiguration Tab

defaultTxAzimuthMinInterSector 204defaultTxAzimuthStep 204defaultTxAzimuthVariation 204defaultTxETiltMax 204defaultTxETiltMin 204defaultTxHeightMax 204defaultTxHeightMax.feet 204defaultTxHeightMin 204defaultTxHeightMin.feet 204defaultTxHeightStep 204defaultTxHeightStep.feet 204defaultTxTiltMax 204defaultTxTiltMin 204defaultTxTiltStep 204tx.etilt.deltaLimitConstraint.show 204

Default Values on the Transmitters Tab of the Reconfiguration Tab

tx.tilt.asRelative 205

Defining Automatic Site Classes

cost.classes.0.antenna.cost 213cost.classes.0.antenna.isSiteVisit 213cost.classes.0.azimuth.cost 213

cost.classes.0.azimuth.isSiteVisit 213cost.classes.0.etilt.cost 213cost.classes.0.etilt.isSiteVisit 213cost.classes.0.height.cost 213cost.classes.0.height.isSiteVisit 213cost.classes.0.name 213cost.classes.0.newSiteCost 213cost.classes.0.power.cost 213cost.classes.0.power.isSiteVisit 213cost.classes.0.removeSiteCost 213cost.classes.0.siteVisitCost 213cost.classes.0.tilt.cost 213cost.classes.0.tilt.isSiteVisit 213cost.classes.0.upgradeSiteCost 213cost.classes.count 213

Defining Reconfiguration Values for Sites Using Custom Atoll Fields

site.gsm.status 211site.lte.status 211site.status 211site.status.candidate 211site.umts.status 211

Defining the Appearance of the Graph Tab

showTimeMarkers 217

Defining the Functionality of the Commit Tab

allowUserChangeForCommit 216

Number of Threads Used for Propagation Model Calculations

pathlossThreadPoolSize 219

atoll.ini options listed by INI section

3GCells, NoSuffixIfUniqueCarrier 180

ACP, iniFile 194

Add‐ins, ’Add‐in Name’ 158

AFP, GlobalDistanceMatrixDegreeUB 178

AFP, SimpleUserGUI 176

AFP, WorstCaseIM_FskAfp 177

Antenna, AngleCalculation 168

Antenna, CatalogVerticalDiagramOrientation 168

Antenna, InterpolatePatternEvenIfOnlyOneDiagram 168

Antenna, InterpolatePatternIndB 168

Antenna, PrecisionTimes10 152

Antenna, REDTDisplay 162

AutoRename, 3GCells 148

AutoRename, Transmitters 148

BsicFormat, DefaultValue 175

Calculations, RoundAltitudes 172

Calculations, UseSiteAltitude 170

CDMA, AddPilotSHOGain 180

CDMA, CodeStrategies 184

CDMA, CQIDeltaWithPower 181

CDMA, CutOffSimu 182

CDMA, DisplayEcIoOfRejected 183

CDMA, HSDPAAvgSimuResults 180

CDMA, HSDPAMaxRejections 182

225

Atoll 3.2.1 Administrator ManualIndex of Initialisation Options © Forsk

CDMA, HSDPAThroughputPeak 180

CDMA, IterBeforeDown 183

CDMA, MaxRejections 182

CDMA, MinUsersPerBin 181

CDMA, MultiBandSimu 184

CDMA, OrthoInCPICH 181

CDMA, ParallelSimulations 171

CDMA, PFSchedulerCQIFactor 183

CDMA, PmaxInIntraItf 181

CDMA, PredictSimuMemorySize 172

CDMA, UseStudyCnxProba 181

Clutter, OnlyVisibleClassesInInterferenceReport 155

Clutter, PerClassPercentagesRelativeToCoverageInReport 155

ClutterParams, IndoorActivity 169

Compatibility, MWEquipment_CIMIN 191

Compression, StartSizeInMB 158

CoPlanning, ComputeLinkedPredictions 172

CoPlanning, LinkedPredictionsComputationMode 173

CoPlanning, LinkSites 154

Database, AllowNullRecordsForNotNullableCustomFields 165

Database, CommandTimeout 166

Database, ExclusiveProvider 167

Database, IntegrityChecker 165

Database, OverwriteSharedFolderPath 167

Database, PromptOnArchive 166

Database, SubCellAuditConsistency 165

Database, SubCellAuditMainValues 166

Database, UseTransaction 167

Display, CellIDNbDigits 161

Display, DiscreteValueColoring 162

Display, PaletteColor0 162

DocTitle, UseTechnoName 162

EventsObserver, LogPath 149

EventsObserver, milliseconds 160

EventsObserver, ShowAddinAccessDeniedMsg 149

EventsObserver,date 160

Export, AutoOpenWithExcel 153

Export, NewLineEscapeSequence 159

Features, IM_TRAFFIC_OVERLAP 175

FskPropagModels, OptimOnNoData 172

Geo, FindGeoButtonAlwaysActive 154

Geo, ReportObeysVisibility 154

Geo, VectorDisplayConfigurationCompanionFile 154

Grids, NbDecimals 153

GSM, 177

GSM, CanEditTRXInfoAtTXLevel 178

GSM, ExternalIncluded 175

GSM, FirstTRXIndex 179

GSM, MinNeighbourImportanceInAFPResults 177

GSM, ShowNonSynchSFHViolationsInAFPResults 177

GSM, SubcellValueFixMethod 179

GSM, TRXIndexHidden 179

GSM, WideRangeSubcellThresholds 179

GUIUserRights, EnableMacrosAddins 153

GUIUserRights, EnableNewDocFromTemplate 153

GUIUserRights, EnableZip 153

IM, FilterByFrequencyBands 178

Import, LoadKMLVectors 152

Import, LoadVectors 152

License, ACP_GSM 164

License, ACP_LTE 164

License, ACP_UMTS 164

License, ACP_WiMAX 164

License, BH 164

License, CDMA 164

License, GSM 164

License, GSM_AFP 164

License, IdleTime 165

License, LTE 164

License, LTE_AFP 164

License, Measures 164

License, MW 164

License, TD‐SCDMA 164

License, TimeBombNotice 164

License, UMTS 164

License, WiMAX 164

License, WiMAX_AFP 164

LOSArea, ResolutionMultFactor 169

LTE, ApplyDLLoadOnPDCCHInterf 188

LTE, DisplaySignalsPerSCInPtA 186

LTE, eICIConRS 190

LTE, EIRPfromRSEPRE 189

LTE, ExcludeCPFromUsefulPower 186

LTE, InterNeighbourIDCollisions 187

LTE, NR_CONTROL_MARGIN_MIN 189

LTE, SameItf_PDSCH_RS_PDCCH 188

LTE, ServiceMBRDowngrading 189

LTE, ULNRControlMethod 189

LTE, ULNRControlPrecision 189

LTE, UseABSonCellEdgeOnly 190

LTE, UseDivGainOnRS 187

MajorVersionChange, EnablePartialRefreshInMigration 167

MITAB, ’Coordinate system definition in the header file’ 150

MITAB, DisableNormalization 155

MITAB, EnableMessages 156

MultiRAT, AllCodesAllocWithInterRATNeighbours 190

MWCalculations, HIDE_REC530_5 191

MWCalculations, ShieldingFactorOnWantedSignal 191

MWCalculations, UpdateOppositeHop 191

MWCalculations, UseProfilesFiles 191

MWReport, DefaultTemplate 193

MWReport, DesignSummaryCfg 192, 193

MWReport, LinkAnalysisCfg 192

MWReport, LinkInterferenceCfg 192

MWReport, LinksBudgetCfg 192

MWReport, LinksInterferenceCfg 192

MWReport, MultihopAnalysisCfg 192

MWReport, RainBelow0001 192

MWReport, ReflectionAnalysisCfg 192

MWReport, RequiredMarginCfg 192

MWReport, tab 192

Neighbours, CandidatesMaxDistanceInImportanceCalculation 174

Neighbours, CompressModeEval 185

226


Neighbours, DistanceAzimutWeightingPercent 174

Neighbours, DoNotDeleteSymmetrics 174

Neighbours, ExcludeFilteredCellsFromNeighbourLists 173

Neighbours, ForceSymmetryInFocusZone 173

Neighbours, RealInterSiteDistanceCondition 174

Neighbours, RepeaterInterSiteDistanceInAlloc 174

OFDM_AFP, AdjacentProtection 188

OFDM_SIMU, MeanNRInDB 189

OFDM, DisplayThroughputZero 189

OFDM, SecondNeighbours 188

OFDM, UniformIDDistribution 187

OFDM, UseCommonBearersOnly 186

OnlineMaps, Name 158

OnlineMaps, TilesCachePath 159

OnlineMaps, URL 158

Pathlosses, EmbeddedByDefault 169

Pathlosses, FullResyncPrivShared 156

Pathlosses,DisplayIndividualSuccessOrFailure 150

Pathlosses,DisplayInvalidityCause 150

Pathlosses,DisplayOverallSuccessOrFailure 150

Perfos, MaxRangeApplied 176

Perfos, PtAnalysisMargin 152

Perfos, PtAnalysisNbServersMax 152

Perfos,ConfirmStoreExternPrivLosFilesOnCopy 149

Perfos,StoreExternPrivLosFilesOnCopy 149

PlanetImport, ChangeKclutterSign 166

PlanetImport, SensitiveCase 166

Population, ReportResolution 156

Print, LogoFooterChecked 156

Print, MaxDPI 149

PSC, ConstantStep 184

PSC, DisplayCostValues 184

RasterExport, GeorefWithTAB 154

Rasterization, Improve 182

Rasterization, MaximumSurf 183

Rasterization, Precision 182

Rasterization, SurfRatio 183

ReceptionTab, NumberOfTransmitterDisplayed 152

Refresh, ControlIntegrity 165

Refresh, TRXIntegrity 175

RemoteAntennas, FrozenSymbol 159

RemoteCalculation, AtollSvrPriority 163

RemoteCalculation, DetectTimeOut 163

RemoteCalculation, DisablePathlossPerSiteCalculation 174

RemoteCalculation, NumberedServers 163

RemoteCalculation, NumberOfProcessors 171

RemoteCalculation, NumberOfThreadsMicrowave 171

RemoteCalculation, NumberOfThreadsNeighbour 171

RemoteCalculation, NumberOfThreadsPathloss 171

RemoteCalculation, NumberOfThreadsSimulation 171

RemoteCalculation, NumberOfThreadsStudy 171

RemoteCalculation, NumberOfThreadsStudyTile 171

RemoteCalculation, Priority 171

SAMModel, DrawSingleElementPattern 161

Settings, KeepFilterZoneOnRemoveFilter 159

Shadowing, Reliability 169

Shadowing, UseShadowing 168

Shadowing, WithSHOGain 180

Simulation, RandomTotalUsers 173

Site, AddToSiteListOnDuplicate 155

Site, Prefix 147

SitesSymbol, Color 159

SitesSymbol, FontName 159

SitesSymbol, Size 159

SitesSymbol, Symbol 159

StatusBar, ClutterPaneWidth 162

StatusBar, DisplayClutterClass 160

StatusBar, DisplayClutterHeight 160

StatusBar, DisplayZ 160

Studies, 150

Studies, 2GTxDiversityGain 178

Studies, AerialStudy 172

Studies, AutoLock 168

Studies, CleanMultiCellManagement 176

Studies, CommentsInLegend 161

Studies, ComputeEvenIfReadOnly 172

Studies, ContinueOnError 169

Studies, CustomStudiesFilteredByTechno 156

Studies, EIRPfromMaxPower 173

Studies, ExportOnlyVisibleLevels 157

Studies, ExposureStudy 161

Studies, MultiBandManagement 176

Studies, MultiplePlotsTipTextLines 160

Studies, NoOverlapOnBestServer 157

Studies, RecomputationWarning 170

Studies, RemoveBadMultiCells 176

Studies, ReportDecimalPlacesAbsolute 157

Studies, ReportDecimalPlacesPercent 157

Studies, SCActivesetMaxSize 185

Studies, ShowIntervalsWithNoCoverageInReport 157

Studies, SpecifyResolutionAfterComputation 170

Studies, UplinkLosses 185

Studies, UseFullHotSpotSurfaceOnReport 157

Studies, UseThresholdForSameLayerPriorities 176

Studies,SelectNullMarginOnly 150

TestMobileData, FloatingPointScramblingCodeSupport 194

TestMobileData, ImportForFilteredTransmittersOnly 194

TestMobileData, NumberOfTestMobileTransmitters 193

TestMobileData, RecalcDist 193

TestMobileData, ShowCoupleInfo 193

TestMobileDataImportFmt, BCCHColumn 193

TestMobileDataImportFmt, BSICColumn 193

TiffExport, PaletteConvention 148

TMP, ExtraServZone 178

Traffic, PerClassPercentagesRelativeToCoverageInReport 155

Transmitter, AutoSynchronizeDisplay 160

Transmitter, ChangeSymbolOnSearch 160

Transmitter, CheckImpactOnRepeaters 153

Transmitter, EmptySymbolWhenInactive 160

Transmitter, First 148

Transmitter, FirstCharSuffix 148

Transmitter, Prefix 148

Transmitter, SuffixIsNum 148

Transmitter, Underscore 148

227


UMTSSimus, MaxReuseFactor 185

WiMAX, ExcludeCPFromUsefulPower 186

WiMAX, InterNeighbourPICollisions 187

WiMAX, ModifiableIEEEParams 185

WiMAX, ReplaceOPUSCwithPUSCUL 187

atoll.ini options listed by topic

Adding Exposure Analysis to the List of Multi‐RAT Coverage Predictions

Studies, ExposureStudy 161

Adding the Duplicate Site to the Original Site’s Site List

Site, AddToSiteListOnDuplicate 155

Adjusting the Working of the Proportional Fair Scheduler

CDMA, PFSchedulerCQIFactor 183

Allowing Null Entries in Non‐nullable Custom Fields

Database, AllowNullRecordsForNotNullableCustomFields165

Applying the ABS Collision Probability on Interference from RS

LTE, eICIConRS 190

Applying Transmit Diversity Gains to Reference Signals

LTE, UseDivGainOnRS 187

Archiving Data to Databases Using Transactions

Database, UseTransaction 167

Automatically Correcting Out‐of‐range Subcell Values

GSM, SubcellValueFixMethod 179

Automatically Running a Database Integrity Check at Open or Refresh

Database, IntegrityChecker 165

Automatically Running GSM Subcell Audit at Open or Refresh

Database, SubCellAuditConsistency 165Database, SubCellAuditMainValues 166

Averaging the Uplink Noise Rise in dB

OFDM_SIMU, MeanNRInDB 189

Avoiding Overlapping Pixels in Best Server Coverage Prediction

Studies, NoOverlapOnBestServer 157

Blocking Access to ACP and AFP Modules

License, ACP_GSM 164License, ACP_LTE 164License, ACP_UMTS 164License, ACP_WiMAX 164License, GSM_AFP 164License, LTE_AFP 164License, WiMAX_AFP 164

Blocking Access to IEEE Parameters in WiMAX

WiMAX, ModifiableIEEEParams 185

Blocking Access to Macros and Add‐ins

GUIUserRights, EnableMacrosAddins 153

Blocking Access to Technology Modules

License, BH 164License, CDMA 164License, GSM 164License, LTE 164License, Measures 164License, MW 164License, TD‐SCDMA 164License, UMTS 164License, WiMAX 164

BSIC, SC, and PCI Allocation in 3GPP with Inter‐technology Neigh‐bour Constraints

MultiRAT, AllCodesAllocWithInterRATNeighbours 190

Calculating and Displaying Peak or Instantaneous HSDPA Throughput

CDMA, HSDPAAvgSimuResults 180CDMA, HSDPAThroughputPeak 180

Calculating EIRP from Max Power in Signal Level Predictions

Studies, EIRPfromMaxPower 173

Calculating EIRP from RS EPRE in LTE Signal Level Predictions

LTE, EIRPfromRSEPRE 189

Changing Hot Spot Reference Surface in Prediction Reports

Studies, UseFullHotSpotSurfaceOnReport 157

Changing the Default Cache Location for the Loaded Map Tiles

OnlineMaps, TilesCachePath 159

Changing the Display for Downlink Smart Antenna Results

SAModel, DrawSingleElementPattern 161

Changing the NetHASP Licence Manager Idle Time Setting

License, IdleTime 165

Changing the Path to Linked Geo Data Files

Geo, FindGeoButtonAlwaysActive 154

Changing the Rounding Method Used for Profile Extraction

Calculations, RoundAltitudes 172

Changing the Weighting Factor of the Effective Inter‐transmitter Distance

Neighbours, DistanceAzimutWeightingPercent 174

Checking Data Integrity After Database Upgrade and Data Refresh

Refresh, ControlIntegrity 165

Checking Database Consistency Automatically

Refresh, TRXIntegrity 175

Compressed Mode ‐ Restricting Inter‐carrier and Inter‐tech‐nology Neighbour Allocation

Neighbours, CompressModeEval 185

Considering Inter‐technology Interference in GSM

GSM, ExternalIncluded 175

Considering Overlapping Zones for IM Calculation Based on Traffic

Features, IM_TRAFFIC_OVERLAP 175

Co‐planning ‐ Calculating Predictions in Serial or in Parallel

CoPlanning, LinkedPredictionsComputationMode 173

Co‐planning ‐ Calculating Predictions in the Current Document Only

CoPlanning, ComputeLinkedPredictions 172

Creating an Event Viewer Log File

EventsObserver, LogPath 149

Deactivating Frequency Band Filtering in IM Calculation

IM, FilterByFrequencyBands 178

Deactivating Service Max Throughput Demand Downgrading in LTE

LTE, ServiceMBRDowngrading 189

Deactivating Uniform Distribution of Resources

OFDM, UniformIDDistribution 187

Decreasing Calculation Time of Path Profiles

MWCalculations, UseProfilesFiles 191

Defining a Default Template for Microwave Links Custom Reports

MWReport, DefaultTemplate 193

Defining a Fixed Interval Between Scrambling Codes

PSC, ConstantStep 184

Defining a Global Maximum Path Loss Calculation Radius

228


Transmitter, MaximumCalculationRadius 175

Defining an Offset With Respect to The Thermal Noise

CDMA, CutOffSimu 182

Defining Default Configuration Files for Link Budgets Reports

MWReport, DesignSummaryCfg 192, 193MWReport, LinkAnalysisCfg 192MWReport, LinkInterferenceCfg 192MWReport, LinksBudgetCfg 192MWReport, LinksInterferenceCfg 192MWReport, MultihopAnalysisCfg 192MWReport, ReflectionAnalysisCfg 192MWReport, RequiredMarginCfg 192

Defining Online Map URLs

OnlineMaps, Name 158OnlineMaps, URL 158

Defining the BCCH and BSIC Columns for FMT Import

TestMobileDataImportFmt, BCCHColumn 193TestMobileDataImportFmt, BSICColumn 193

Defining the Maximum Number of Transmitters for Reuse Distance in AFP

AFP, GlobalDistanceMatrixDegreeUB 178

Defining the Number of Iterations Before Downgrading

CDMA, IterBeforeDown 183

Defining the Parameters for the Default Sites Symbol

SitesSymbol, Color 159SitesSymbol, FontName 159SitesSymbol, Size 159SitesSymbol, Symbol 159

Defining Web Map Services Servers

WMS, ’Web map services servers’ 151

Deleting the Filtering Zone on Removing Filters From Tables

Settings, KeepFilterZoneOnRemoveFilter 159

Detecting and Listing Distributed Calculation Servers

RemoteCalculation, NumberedServers 163

Disabling Automatic Locking of Coverage Predictions

Studies, AutoLock 168

Disabling Automatic Renaming of Transmitters and Cells

AutoRename, 3GCells 148AutoRename, Transmitters 148

Disabling Calculations Over NoData Values for DTM and Clutter Classes

FskPropagModels, OptimOnNoData 172

Disabling External Storage of Numerical Results Files for Predic‐tions

Studies, NumericalResults 150

Disabling Macro‐diversity (SHO) Gains in Calculations

CDMA, AddPilotSHOGain 180Shadowing, WithSHOGain 180

Disabling Normalisation of MIF/TAB Vector Files

MITAB, DisableNormalization 155

Disabling Parallel Calculation of Monte Carlo Simulations

CDMA, ParallelSimulations 171

Disabling Saving and Opening ZIP Files

GUIUserRights, EnableZip 153

Disabling Shielding Factor on Wanted Signal at Receiver

MWCalculations, ShieldingFactorOnWantedSignal 191

Disabling the Maximum Range Parameter

Perfos, MaxRangeApplied 176

Disallowing Creation of New Documents from Templates

GUIUserRights, EnableNewDocFromTemplate 153

Displaying % of Covered Clutter Classes with Respect to the Focus Zone in Reports

Clutter, PerClassPercentagesRelativeToCoverageInReport155

Displaying % of Covered Traffic Classes with Respect to the Focus Zone in Reports

Traffic, PerClassPercentagesRelativeToCoverageInReport155

Displaying Additional Information in Drive Test Data

TestMobileData, ShowCoupleInfo 193

Displaying Automatic Allocation Cost Values

PSC, DisplayCostValues 184

Displaying Coverage Prediction Comments in the Legend Window

Studies, CommentsInLegend 161

Displaying Date and Time in the Event Viewer

EventsObserver, date 160EventsObserver, milliseconds 160

Displaying Ec/I0 of Rejected Mobiles in Simulation Results

CDMA, DisplayEcIoOfRejected 183

Displaying Filled Symbols for Inactive Transmitters on the Map

Transmitter, EmptySymbolWhenInactive 160

Displaying Leading Zeros in the CELL_IDENTITY Field

Display, CellIDNbDigits 161

Displaying Objects’ Discrete Values with User‐defined Colours

Display, DiscreteValueColoring 162Display, PaletteColor0 162

Displaying Path Loss Calculation Details in the Event Viewer

Pathlosses, DisplayIndividualSuccessOrFailure 150Pathlosses, DisplayInvalidityCause 150Pathlosses, DisplayOverallSuccessOrFailure 150

Displaying Pixels with Zero Throughput in Coverage Predictions

OFDM, DisplayThroughputZero 189

Displaying Uplink Total Losses in Coverage by Signal Level

Studies, UplinkLosses 185

Duplicating Linked Path Loss Matrices on Save As

Perfos, ConfirmStoreExternPrivLosFilesOnCopy 149Perfos, StoreExternPrivLosFilesOnCopy 149

Embedding Path Losses in New Documents

Pathlosses, EmbeddedByDefault 169

Enabling and Disabling Per‐site Path Loss Matrix Calculations

RemoteCalculation, DisablePathlossPerSiteCalculation 174

Enabling Coverage Predictions of Connection Probabilities

CDMA, MinUsersPerBin 181CDMA, UseStudyCnxProba 181

Enabling Display of Signals per Subcarrier Point Analysis in LTE

LTE, DisplaySignalsPerSCInPtA 186

Enabling Event Viewer Messages for MapInfo File Import/Export

MITAB, EnableMessages 156

Enabling Indoor Coverage in Calculations

ClutterParams, IndoorActivity 169

Enabling Notification for Donor Transmitter Parameter Modifica‐tions

Transmitter, CheckImpactOnRepeaters 153

Enabling Orthogonality Factor in Pilot EC/NT Calculation in HSDPA

CDMA, OrthoInCPICH 181

Enabling Partial Refresh from Recently Upgraded Databases

229


MajorVersionChange, EnablePartialRefreshInMigration167

Enabling Shadowing Margin in Calculations

Shadowing, UseShadowing 168

Enabling the Support for Multi‐band Transmitters

Studies, CleanMultiCellManagement 176Studies, MultiBandManagement 176Studies, RemoveBadMultiCells 176

Enabling/Disabling Password Prompt at Archive

Database, PromptOnArchive 166

Estimating Required and Used Memory Size for UMTS Simula‐tions

CDMA, PredictSimuMemorySize 172

EventsObserver, ShowAddinAccessDeniedMsg 149

Excluding Cyclic Prefix Energy in WiMAX and Wi‐Fi Signal Level Calculation

WiMAX, ExcludeCPFromUsefulPower 186

Excluding Filtered Transmitters from the List of Neighbours

Neighbours, ExcludeFilteredCellsFromNeighbourLists 173

Excluding the Adjacent Channel Overlap from the AFP Cost Func‐tions

OFDM_AFP, AdjacentProtection 188

Excluding Vectors from Imported KML/KMZ Files

Import, LoadKMLVectors 152

Exporting BMP, TIF, and PNG Files with a TAB Reference File

RasterExport, GeorefWithTAB 154

Exporting Coverage Prediction Polygons in Text Format

Studies, EnableLBS 151

Exporting Only Visible Value Interval Layers of Coverage Predic‐tions

Studies, ExportOnlyVisibleLevels 157

Exporting/Importing Vector Data with a Display Configuration File

Geo, VectorDisplayConfigurationCompanionFile 154

Extending the Allowed Value Range for C/I and Reception Thresholds

GSM, WideRangeSubcellThresholds 179

Extending the Maximum Inter‐site Distance to Repeaters and Remote Antennas

Neighbours, RepeaterInterSiteDistanceInAlloc 174

Filtering Predictions by Technology When Reading the XML Studies File

Studies, CustomStudiesFilteredByTechno 156

Forcing Neighbour Symmetry Only Inside Focus Zone

Neighbours, ForceSymmetryInFocusZone 173

Forcing the Real Inter‐site Distance Threshold

Neighbours, RealInterSiteDistanceCondition 174

Hiding Advanced AFP Parameters

AFP, SimpleUserGUI 176

Hiding Information Displayed in the Status Bar

StatusBar, DisplayClutterClass 160StatusBar, DisplayClutterHeight 160StatusBar, DisplayZ 160

Hiding the Rec. ITU‐R P.530‐5 Method

MWCalculations, HIDE_REC530_5 191

Hiding the Technology Name in the Title Bar

DocTitle, UseTechnoName 162

Hiding the TRX Index

GSM, TRXIndexHidden 179

Hiding Violations Between Low Importance GSM Neighbours in AFP Results

GSM, MinNeighbourImportanceInAFPResults 177

Hiding Violations Between Non‐Synchronised MALs‐MAIOs in AFP Results

GSM, ShowNonSynchSFHViolationsInAFPResults 177

Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas

Studies, AerialStudy 172

Ignoring Inter‐Neighbour Physical Cell ID Collision in LTE

LTE, InterNeighbourIDCollisions 187

Ignoring Inter‐Neighbour Preamble Index Collision in WiMAX

WiMAX, InterNeighbourPICollisions 187

Importing Drive Test Data for Active and Filtered Transmitters Only

TestMobileData, ImportForFilteredTransmittersOnly 194

Importing Drive Test Data with Scrambling Codes as Integers

TestMobileData, FloatingPointScramblingCodeSupport194

Improving Point Analysis Performance

Perfos, PtAnalysisMargin 152Perfos, PtAnalysisNbServersMax 152ReceptionTab, NumberOfTransmitterDisplayed 152

Including Cyclic Prefix Energy in LTE Signal Level Calculation

LTE, ExcludeCPFromUsefulPower 186

Including Pixel‐free Ranges in Coverage Prediction Reports

Studies, ShowIntervalsWithNoCoverageInReport 157

Increasing the Maximum Printing Resolution

Print, MaxDPI 149

Increasing the Width of the Clutter Description Pane in the Status Bar

StatusBar, ClutterPaneWidth 162

Keeping Separate Work and Master Path Loss Directories

Database, OverwriteSharedFolderPath 167

Keeping the Assigned Neighbours which are not Symmetrised with the Reference Transmitter

Neighbours, DoNotDeleteSymmetrics 174

Keeping Transmitter Symbols From Changing on Search

Transmitter, ChangeSymbolOnSearch 160

Linking the Sites Folder in Co‐planning

CoPlanning, LinkSites 154

Loading Vector Files Dynamically

Import, LoadVectors 152

Loading, Activating, and Setting Add‐ins as Visible

Add‐ins, ’Add‐in Name’ 158

Making Atoll Case‐Sensitive for Database Import From Planet

PlanetImport, SensitiveCase 166

Making Redundant Fields in the Transmitters Table Read‐only

GSM, CanEditTRXInfoAtTXLevel 178

Making the Antenna Additional Electrical Downtilt Accessible

Antenna, REDTDisplay 162

Managing Carriage Returns in Imported TXT and CSV Files

Export, NewLineEscapeSequence 159

Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files

MITAB, ’Coordinate system definition in the header file’150

Modifying the Default Database Connection Time‐out

230


Database, CommandTimeout 166

Modifying the Default Detection Time‐out

RemoteCalculation, DetectTimeOut 163

Modifying the Default Formats of Site and Transmitter Names

Site, Prefix 147Transmitter, First 148Transmitter, FirstCharSuffix 148Transmitter, Prefix 148Transmitter, SuffixIsNum 148Transmitter, Underscore 148

Modifying the Resolution for the LOS Area Calculation Around a Site

LOSArea, ResolutionMultFactor 169

Modifying the Threshold for Important Violations in AFP

GSM, AdjRedColorThreshPercent 177GSM, CoRedColorThreshPercent 177

Opening Exported XLS Files Automatically in MS Excel

Export, AutoOpenWithExcel 153

Performing Calculations in Read‐Only Documents

Studies, ComputeEvenIfReadOnly 172

Prioritising Individual Inter‐site Distances in Neighbour Impor‐tance Calculation

Neighbours, CandidatesMaxDistanceInImportanceCalcula‐tion 174

Reading Exact Altitudes From the DTM

Calculations, UseSiteAltitude 170

Recalculating Distances of Points From There Serving Cells at Import

TestMobileData, RecalcDist 193

Refreshing the Display Automatically When a New Station is Dropped

Transmitter, AutoSynchronizeDisplay 160

Renaming OPUSC Zone to PUSC UL in WiMAX

WiMAX, ReplaceOPUSCwithPUSCUL 187

Restricting the List of Predictions for Creating Sector Traffic Maps

Studies, SelectNullMarginOnly 150

Selecting SC and PN Offset Allocation Strategies Available in the GUI

CDMA, CodeStrategies 184

Selecting the Interference Matrices Used During the AFP

AFP, WorstCaseIM_FskAfp 177

Selecting the Logo 2 Check Box by Default in Print Setup

Print, LogoFooterChecked 156

Setting a Common Display Resolution For All Coverage Predic‐tions

Studies, SpecifyResolutionAfterComputation 170

Setting a Default Value for the Cell Edge Coverage Probability

Shadowing, Reliability 169

Setting an Alarm for the Licence End Date

License, TimeBombNotice 164

Setting PDCCH to 100% Loaded in LTE Interference Calculations

LTE, ApplyDLLoadOnPDCCHInterf 188

Setting Precision of the Rasterisation Process

Rasterization, Improve 182Rasterization, MaximumSurf 183Rasterization, Precision 182Rasterization, SurfRatio 183

Setting the Antenna Patterns Modelling Method

Antenna, AngleCalculation 168

Antenna, CatalogVerticalDiagramOrientation 168Antenna, InterpolatePatternEvenIfOnlyOneDiagram 168Antenna, InterpolatePatternIndB 168

Setting the Best Server Calculation Method in Same Priority HCS Layers

Studies, UseThresholdForSameLayerPriorities 176

Setting the Calculation Method for HS‐PDSCH CQI

CDMA, CQIDeltaWithPower 181

Setting the Default BSIC Format

BsicFormat, DefaultValue 175

Setting the Display Precision of Floating Point Values

Grids, NbDecimals 153

Setting the Distributed Calculation Server Priority

RemoteCalculation, AtollSvrPriority 163

Setting the Maximum AS Size for SC Interference Prediction

Studies, SCActivesetMaxSize 185

Setting the Maximum Number of Lines in Coverage Prediction Tool Tips

Studies, MultiplePlotsTipTextLines 160

Setting the Maximum Number of Rejections for HSDPA Mobiles

CDMA, HSDPAMaxRejections 182

Setting the Maximum Number of Rejections for Mobiles

CDMA, MaxRejections 182

Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise Estimation

UMTSSimus, MaxReuseFactor 185

Setting the Minimum ATL File Size Requiring Compression

Compression, StartSizeInMB 158

Setting the Number of Parallel Processors and Threads

RemoteCalculation, NumberOfProcessors 171RemoteCalculation, NumberOfThreadsMicrowave 171RemoteCalculation, NumberOfThreadsNeighbour 171RemoteCalculation, NumberOfThreadsPathloss 171RemoteCalculation, NumberOfThreadsSimulation 171RemoteCalculation, NumberOfThreadsStudy 171RemoteCalculation, NumberOfThreadsStudyTile 171

Setting the Number of Transmitters per Drive Test Data Path

TestMobileData, NumberOfTestMobileTransmitters 193

Setting the Power to Use for Intra‐cell Interference in HSDPA

CDMA, PmaxInIntraItf 181

Setting the Precision for the Antenna Pattern Verification at Import

Antenna, PrecisionTimes10 152

Setting the Precision in Coverage Prediction Reports

Studies, ReportDecimalPlacesAbsolute 157Studies, ReportDecimalPlacesPercent 157

Setting the Priorities for GUI and Calculations

RemoteCalculation, Priority 171

Setting the Resolution of Population Maps in Coverage Predic‐tion Reports

Population, ReportResolution 156

Setting the Sign for KClutter When Importing Data From Planet EV

PlanetImport, ChangeKclutterSign 166

Setting the TIFF Colour Convention

TiffExport, PaletteConvention 148

Setting the Transmission Diversity Gain

Studies, 2GTxDiversityGain 178

Setting the Type of Database Being Used

231


Database, ExclusiveProvider 167

Setting Uplink Noise Rise Control Parameters in LTE

LTE, NR_CONTROL_MARGIN_MIN 189LTE, ULNRControlMethod 189LTE, ULNRControlPrecision 189

Solving Alignment Issue in Generated Reports

MWReport, tab 192

Specifying the Location of the Acp.ini File

ACP, iniFile 194

Starting TRX Indexes at 1

GSM, FirstTRXIndex 179

Stopping Calculations on Error

Studies, ContinueOnError 169

Suppressing 3G Cell Name Carrier Suffixes

3GCells, NoSuffixIfUniqueCarrier 180

Switching Back to the Old Best Server Determination Method

CDMA, MultiBandSimu 184

Switching Between Synchronised and Unsynchronised Interfer‐ence Calculation Methods

LTE, SameItf_PDSCH_RS_PDCCH 188

Synchronising Private and Shared Path Loss Matrices

Pathlosses, FullResyncPrivShared 156

Taking Second Order Neighbours into Account in the AFP

OFDM, SecondNeighbours 188

Updating A>>B and B>>A Profiles in Real‐time

MWCalculations, UpdateOppositeHop 191

Using a Unique Symbol for Remote Antennas

RemoteAntennas, FrozenSymbol 159

Using Default Method for Calculating Unavailability

MWReport, RainBelow0001 192

Using Old Min C/I Values

Compatibility, MWEquipment_CIMIN 191

Using Only Bearers Common Between the Terminal’s and Cell’s Equipment

OFDM, UseCommonBearersOnly 186

Using Only Visible Clutter Classes in Interference Prediction Reports

Clutter, OnlyVisibleClassesInInterferenceReport 155

Using Only Visible Geo Data in Prediction Reports

Geo, ReportObeysVisibility 154

Using Poisson Distribution in Monte‐Carlo Simulations

Simulation, RandomTotalUsers 173

Using the ABS Patterns Throughout a Cell in LTE

LTE, UseABSonCellEdgeOnly 190

Warning About Prediction Validity When Display Options are Modified

Studies, RecomputationWarning 170

atoll.ini options listed INI option

Transmitter, MaximumCalculationRadius 175

232

AT321_AM_E1 Atoll 3.2.1 Administrator Manual

233

AT321_AM_E1 www.forsk.com February 2014

• Head Office7 rue des Briquetiers31700 Blagnac, FranceTel: +33 562 747 210Fax: +33 562 747 211

• US Office200 South Wacker Drive – Suite 3100Chicago, IL 60606, USATel: +1 312 674 4800Fax: +1 312 674 4847

• China OfficeSuite 302, 3/F, West Tower, Jiadu Commercial Building,No. 66 Jianzhong Road, Tianhe Hi‐Tech Industrial Zone,Guangzhou, 510665, P. R. of ChinaTel: +86 20 8553 8938 Fax: +86 20 8553 8285

http://www.forsk.com