Atoll 3.2.1 Administrator Manual

Version 3.2.
Administrator Manual
AT321_AM_E4
Atoll 3.2.1 Administrator Manual
Release: AT321_AM_E4
© 1997‐2014 Forsk. All Rights Reserved.
Published by:
Forsk
7 rue des Briquetiers
31700 Blagnac, France
Tel: +33 562 747 210
Fax: +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 products 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. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information contained
herein.
AT321_AM_E4 Table of Contents
Table of Contents
1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
1.1 Supported Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Supported Database Management Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 Supported Installation Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.5 Recommended Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.5.1 User Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.5.2 Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.3 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.4 Floating Licence Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5.5 File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.6 Recommended Computer Network Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2 Installing Atoll and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
2.1 Installing Atoll Using the Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2 Installing Atoll C++ Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3 Setup Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4 Installing and Uninstalling Add‐ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.5 Installing and Uninstalling Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.6 Atoll Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7 Troubleshooting and Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3 Setting Up Distributed Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
3.1 Setting Up Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2 Setting Up Atoll to Access the Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3 Distributed Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4 Managing Licences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
4.1 Working with Floating Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.1.1 Installing the HASP Licensing System Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.1.1.1 Installing the HASP Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.1.1.2 Installing the HASP Licence Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.1.2 nhsrv.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.1.3 nethasp.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2 Using the Atoll Licence Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.1 Licence Manager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.2 Updating Licence Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5 Managing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
5.1 Atoll Database Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.2 Customising Atoll Database Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.3 Atoll Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4 Creating New Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4.1 Creating a New Database Using the Atoll Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4.2 Creating a New Database Using Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.5 Upgrading Existing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.6 Working With a Multi‐level Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.6.1 Creating Project Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.6.2 Archiving Project Databases to Master Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.6.3 Refreshing Project Databases from Master Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.7 Setting Database Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.8 Managing Data Modifications History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.8.1 Setting Up Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.8.2 Enabling/Disabling Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.8.3 Updating After Data Structure Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.8.4 Purging Old Data Modification Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3
Table of Contents © Forsk 2014
5.8.4.1 Purging Old Data Modification Records of a Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
5.8.4.2 Purging Old Data Modification Records of a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
5.9 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
5.9.1 Appendix 1: Advanced Customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
5.9.2 Appendix 2: Setting Up Databases for Co‐planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
6 Multi‐user Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.1 Setting Up Multi‐user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
6.2 Components of Multi‐user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
6.2.1 Master Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
6.2.2 Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
6.2.3 Shared Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
6.2.4 Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
6.2.5 User Atoll Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
6.3 Managing User Accounts and Access Rights in Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
6.3.1 Defining Database and Interface Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
6.3.2 Creating and Editing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
6.3.3 Resetting User Database Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
6.4 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
6.4.1 Appendix 1: Checking Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
6.4.2 Appendix 2: Database Regionalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
6.4.3 Appendix 3: Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
6.4.4 Appendix 4: Path Loss Matrices From Different Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
7 Coordinate Systems and Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.1 Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
7.1.1 Definition of a Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
7.1.2 Types of Coordinate Systems in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
7.1.3 Coordinate Systems File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
7.1.4 Creating a Coordinate System in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
7.2 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
7.3 BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
8 Atoll File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
8.1 Geographic Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
8.1.1 HDR Header File for BIL Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
8.1.2 TFW Header File for TIFF Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
8.1.3 BPW/BMW Header Files for BMP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
8.1.4 PGW Header File for PNG Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
8.1.5 JGW Header File for JPG Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
8.1.6 Generic Raster Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
8.2 Path Loss Matrix File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
8.2.1 Pathloss.dbf File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
8.2.2 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
8.2.3 LOS File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
8.3 Path Loss Tuning File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
8.3.1 Pathloss.dbf File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
8.3.2 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
8.3.3 PTS File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
8.4 Interference Matrix File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
8.4.1 CLC Format (One Value per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
8.4.1.1 CLC File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
8.4.1.2 DCT File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
8.4.2 IM0 Format (One Histogram per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
8.4.3 IM1 Format (One Value per Line, TX Name Repeated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
8.4.4 IM2 Format (Co‐ and Adjacent‐channel Probabilities) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
8.5 "Per Transmitter" Prediction File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
8.5.1 <per_transmitter_prediction>.dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
8.5.2 <per_transmitter_prediction>.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
9 Administration and Usage Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.1 Geographic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
9.2 Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
9.3 Atoll Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
9.4 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
4
9.5 Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9.6 Atoll Administration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9.7 Process Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9.8 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9.9 Coverage Prediction Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.10 CW Measurements and Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.11 Antenna Patterns and Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.12 Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.13 Atoll API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
9.14 Performance and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
10 Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
10.1 Contents of User Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
10.1.1 Geographic Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
10.1.2 Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10.1.3 Map Centre and Zoom Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
10.1.4 Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
10.1.5 Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
10.1.6 Automatic Neighbour Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
10.1.7 Automatic Frequency Planning Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
10.1.8 Automatic Scrambling Code Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
10.1.9 Automatic PN Offset Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
10.1.10 Automatic OFDM Resource Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
10.1.11 Microwave Radio Links Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
10.1.12 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
10.2 Contents of Additional Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
10.2.1 Print Setup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
10.2.2 Table Import/Export Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
10.2.3 Coverage Prediction Report Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
10.2.4 CW Measurement Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
10.2.5 Drive Test Data Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
10.3 Content of the Custom Predictions File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
10.4 Content of the "Value Intervals" Predictions Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
11 Initialisation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
11.1 Atoll Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
11.1.1 General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
11.1.1.1 Modifying the Default Formats of Site and Transmitter Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
11.1.1.2 Disabling Automatic Renaming of Transmitters and Cells. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
11.1.1.3 Setting the TIFF Colour Convention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
11.1.1.4 Creating an Event Viewer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.1.1.5 Displaying Insufficient Permission Messages in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.1.1.6 Increasing the Maximum Printing Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.1.1.7 Duplicating Linked Path Loss Matrices on Save As. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.1.1.8 Disabling External Storage of Numerical Results Files for Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
11.1.1.9 Restricting the List of Predictions for Creating Sector Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
11.1.1.10 Displaying Path Loss Calculation Details in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
11.1.1.11 Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
11.1.1.12 Exporting Coverage Prediction Polygons in Text Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
11.1.1.13 Defining Web Map Services Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
11.1.1.14 Improving Point Analysis Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
11.1.1.15 Loading Vector Files Dynamically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
11.1.1.16 Excluding Vectors from Imported KML/KMZ Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
11.1.1.17 Setting the Precision for the Antenna Pattern Verification at Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
11.1.1.18 Opening Exported XLS Files Automatically in MS Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.1.1.19 Disabling Creation of New Documents from Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.1.1.20 Blocking Access to Macros and Add‐ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.1.1.21 Disabling Saving and Opening ZIP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.1.1.22 Enabling Notification for Donor Transmitter Parameter Modifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.1.1.23 Setting the Display Precision of Floating Point Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.1.1.24 Changing the Path to Linked Geo Data Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11.1.1.25 Exporting/Importing Vector Data with a Display Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11.1.1.26 Using Only Visible Geo Data in Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11.1.1.27 Exporting BMP, TIF, and PNG Files with a TAB Reference File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11.1.1.28 Co‐Planning: Linking the Sites Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11.1.1.29 Disabling Normalisation of MIF/TAB Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5
11.1.1.30 Customising Performance Optimisation when Exporting Vector Files in TAB Format . . . . . . . . . . . . . . . . . . . . . . . . . . 143

11.1.1.31 Adding the Duplicate Site to the Original Site’s Site List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
11.1.1.32 Real Altitude versus DTM Altitude in Sites’ Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
11.1.1.32.1 Duplicate/Moved Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
11.1.1.32.2 New Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
11.1.1.33 Using Only Visible Clutter Classes in Interference Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
11.1.1.34 Displaying % of Covered Clutter Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
11.1.1.35 Displaying % of Covered Traffic Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
11.1.1.36 Synchronising Private and Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
11.1.1.37 Selecting the Logo 2 Check Box by Default in Print Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
11.1.1.38 Filtering Predictions by Technology When Reading the XML Studies File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
11.1.1.39 Enabling Event Viewer Messages for MapInfo File Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
11.1.1.40 Setting the Resolution of Population Maps in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
11.1.1.41 Setting the Precision in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
11.1.1.42 Including Pixel‐free Ranges in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
11.1.1.43 Changing Hot Spot Reference Surface in Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
11.1.1.44 Exporting Only Visible Value Interval Layers of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
11.1.1.45 Avoiding Overlapping Pixels in Best Server Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
11.1.1.46 Setting the Minimum ATL File Size Requiring Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
11.1.1.47 Loading, Activating, and Setting Add‐ins as Visible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
11.1.1.48 Defining Online Map URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
11.1.1.49 Changing the Default Cache Location for the Loaded Map Tiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
11.1.1.50 Defining the Microsoft Bing Tile Server for Online Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
11.1.1.51 Defining the Microsoft Bing Tile Server for Online Searches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
11.1.1.52 Managing Carriage Returns in Imported TXT/CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
11.1.1.53 Deleting the Filtering Zone on Removing Filters From Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
11.1.1.54 Disabling Automatic Restart of Atoll after a Crash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
11.1.2 GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
11.1.2.1 Defining the Parameters for the Default Sites Symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
11.1.2.2 Using a Unique Symbol for Remote Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.1.2.3 Keeping Transmitter Symbols From Changing on Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.1.2.4 Displaying Filled Symbols for Inactive Transmitters on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.1.2.5 Refreshing the Display Automatically When a New Station is Dropped. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.1.2.6 Hiding Information Displayed in the Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.1.2.7 Displaying Date and Time in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.1.2.8 Setting the Maximum Number of Lines in Coverage Prediction Tool Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11.1.2.9 Changing the Display for Downlink Smart Antenna Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11.1.2.10 Displaying Coverage Prediction Comments in the Legend Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11.1.2.11 Displaying Leading Zeros in the CELL_IDENTITY Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11.1.2.12 Making the Antenna Additional Electrical Downtilt Accessible. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11.1.2.13 Increasing the Width of the Clutter Description Pane in the Status Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11.1.2.14 Hiding the Technology Name in the Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11.1.2.15 Displaying Objects’ Discrete Values with User‐defined Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11.1.2.16 Displaying Vertical Beamwidth in Profile Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11.1.2.17 Case‐insensitive Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
11.1.3 Distributed Calculation Server Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
11.1.3.1 Detecting and Listing Distributed Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
11.1.3.2 Setting the Distributed Calculation Server Priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
11.1.3.3 Modifying the Default Detection Time‐out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.1.4 Licence Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.1.4.1 Setting an Alarm for the Licence End Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.1.4.2 Blocking Access to Technology Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.1.4.3 Blocking Access to ACP and AFP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.1.4.4 Changing the NetHASP Licence Manager Idle Time Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.1.5 Database Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.1.5.1 Checking Data Integrity After Database Upgrade and Data Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.1.5.2 Automatically Running a Database Integrity Check at Open or Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.1.5.3 Displaying Database Tables in the Event Viewer at Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.1.5.4 Allowing Null Entries in Non‐nullable Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.1.5.5 Automatically Running GSM Subcell Audit at Open or Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
11.1.5.6 Modifying the Default Database Connection Time‐out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
11.1.5.7 Making Atoll Case‐Sensitive for Database Import From Planet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
11.1.5.8 Setting the Sign for KClutter When Importing Data From Planet EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
11.1.5.9 Setting the Clutter No Data Value for When Importing Data From Planet EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
11.1.5.10 Enabling/Disabling Password Prompt at Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
11.1.5.11 Archiving Data to Databases Using Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
11.1.5.12 Keeping Separate Work and Master Path Loss Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
6
11.1.5.13 Enabling Partial Refresh from Recently Upgraded Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

11.1.5.14 Setting the Type of Database Being Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.1.6 Common Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.1.6.1 Setting the Antenna Patterns Modelling Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.1.6.2 Disabling Automatic Locking of Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.1.6.3 Enabling Shadowing Margin in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.1.6.4 Setting a Default Value for the Cell Edge Coverage Probability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
11.1.6.5 Enabling Indoor Coverage in Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
11.1.6.6 Modifying the Resolution for the LOS Area Calculation Around a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
11.1.6.7 Embedding Path Losses in New Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
11.1.6.8 Stopping Calculations on Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
11.1.6.9 Warning About Prediction Validity When Display Options are Modified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
11.1.6.10 Reading Exact Altitudes From the DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
11.1.6.11 Setting a Common Display Resolution For All Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
11.1.6.12 Setting the Priorities for GUI and Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
11.1.6.13 Setting the Number of Parallel Processors and Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
11.1.6.14 Parallel Calculation of Monte Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
11.1.6.15 Performing Calculations in Read‐Only Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
11.1.6.16 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
11.1.6.17 Changing the Rounding Method Used for Profile Extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
11.1.6.18 Estimating Required and Used Memory Size for UMTS Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
11.1.6.19 Disabling Calculations Over NoData Values for DTM and Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
11.1.6.20 Co‐planning: Calculating Predictions in the Current Document Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
11.1.6.21 Co‐planning: Calculating Predictions in Serial or in Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
11.1.6.22 Forcing Neighbour Symmetry Only Inside Focus Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
11.1.6.23 Using Poisson Distribution in Monte Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
11.1.6.24 Calculating EIRP from Max Power in Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.1.6.25 Excluding Filtered Transmitters from the List of Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.1.6.26 Changing the Weighting Factor of the Effective Inter‐transmitter Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.1.6.27 Extending the Maximum Inter‐site Distance to Repeaters and Remote Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.1.6.28 Forcing the Real Inter‐site Distance Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.1.6.29 Prioritising Individual Inter‐site Distances in Neighbour Importance Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
11.1.6.30 Keeping the Assigned Neighbours which are not Symmetrised with the Reference Transmitter . . . . . . . . . . . . . . . . . . 164
11.1.6.31 Enabling and Disabling Per‐site Path Loss Matrix Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
11.1.6.32 Defining a Global Maximum Path Loss Calculation Radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
11.1.6.33 Preserving Loss and Noise Figures with no Assigned Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
11.1.7 GSM GPRS EDGE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
11.1.7.1 Considering Inter‐technology Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
11.1.7.2 Considering Overlapping Zones for IM Calculation Based on Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
11.1.7.3 Setting the Default BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
11.1.7.4 Checking Database Consistency Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
11.1.7.5 Disabling the Maximum Range Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
11.1.7.6 Enabling the Support for Multi‐band Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
11.1.7.7 Setting the Best Server Calculation Method in Same Priority HCS Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
11.1.7.8 Hiding AFP Advanced Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
11.1.7.9 Hiding AFP Hopping Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
11.1.7.10 Hiding Violations Between Low Importance GSM Neighbours in AFP Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
11.1.7.11 Hiding Violations Between Non‐synchronised MALs‐MAIOs in AFP Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
11.1.7.12 Modifying the Thresholds for Important Violations in AFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
11.1.7.13 Selecting the Interference Matrices Used During the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
11.1.7.14 Defining the Maximum Number of Transmitters for Reuse Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.1.7.15 Changing the Level of Intermodulation Products Checked by AFP in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.1.7.16 Changing the Level of Intermodulation Products Checked by AFP in TETRA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.1.7.17 Making Redundant Fields in the Transmitters Table Read‐only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.1.7.18 Setting the Transmission Diversity Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.1.7.19 Deactivating Frequency Band Filtering in IM Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.1.7.20 Starting TRX Indexes at 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
11.1.7.21 Hiding the TRX Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
11.1.7.22 Extending the Allowed Value Range for C/I and Reception Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
11.1.7.23 Automatically Correcting Out‐of‐range Subcell Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
11.1.8 UMTS HSPA, CDMA2000, and TD‐SCDMA Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
11.1.8.1 Suppressing Cell Name Carrier Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
11.1.8.2 Disabling Macro‐diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
11.1.8.3 Calculating and Displaying Peak or Instantaneous HSDPA Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
11.1.8.4 Setting the Power to Use for Intra‐cell Interference in HSDPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
11.1.8.5 Enabling Coverage Predictions of Connection Probabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
11.1.8.6 Setting the Calculation Method for HS‐PDSCH CQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
7
11.1.8.7 Enabling Orthogonality Factor in Pilot EC/NT Calculation in HSDPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

11.1.8.8 Setting the Maximum Number of Rejections for Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
11.1.8.9 Setting the Maximum Number of Rejections for HSDPA Mobiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
11.1.8.10 Defining an Offset With Respect to The Thermal Noise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
11.1.8.11 Setting Precision of the Rasterisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
11.1.8.12 Defining the Number of Iterations Before Downgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
11.1.8.13 Adjusting the Working of the Proportional Fair Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
11.1.8.14 Displaying Ec/I0 of Rejected Mobiles in Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
11.1.8.15 Switching Back to the Old Best Server Determination Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
11.1.8.16 Switching Back to the Old Radio Bearer Allocation Algorithm for Multi‐carrier EVDO Rev.B. . . . . . . . . . . . . . . . . . . . . 174
11.1.8.17 Displaying Automatic Allocation Cost Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
11.1.8.18 Selecting SC and PN Offset Allocation Strategies Available in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
11.1.8.19 Defining a Fixed Interval Between Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.1.8.20 Compressed Mode: Restricting Inter‐carrier and Inter‐technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . 175
11.1.8.21 Setting the Maximum AS Size for SC Interference Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.1.8.22 Displaying Uplink Total Losses in Coverage by Signal Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.1.8.23 Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.1.9 LTE, WiMAX, and Wi‐Fi Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.1.9.1 Blocking Access to IEEE Parameters in WiMAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.1.9.2 Using Only Bearers Common Between the Terminal’s and Cell’s Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
11.1.9.3 Enabling Display of Signals per Subcarrier Point Analysis in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
11.1.9.4 Including Cyclic Prefix Energy in LTE Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
11.1.9.5 Excluding Cyclic Prefix Energy in WiMAX and Wi‐Fi Signal Level Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
11.1.9.6 Ignoring Inter‐Neighbour Preamble Index Collision in WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
11.1.9.7 Ignoring Inter‐Neighbour Physical Cell ID Collision in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
11.1.9.8 Renaming OPUSC Zone to PUSC UL in WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
11.1.9.9 Deactivating Uniform Distribution of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
11.1.9.10 Taking Second Order Neighbours into Account in the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
11.1.9.11 Excluding the Adjacent Channel Overlap from the AFP Cost Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
11.1.9.12 Switching Between Synchronised and Unsynchronised Interference Calculation Methods. . . . . . . . . . . . . . . . . . . . . . 178
11.1.9.13 Setting PDCCH to 100% Loaded in LTE Interference Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
11.1.9.14 Calculating EIRP from RS EPRE in LTE Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
11.1.9.15 Averaging the Uplink Noise Rise in dB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
11.1.9.16 Deactivating Service Max Throughput Demand Downgrading in LTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
11.1.9.17 Displaying Pixels with Zero Throughput in Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
11.1.9.18 Setting Uplink Noise Rise Control Parameters in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
11.1.9.19 Using the ABS Patterns on Cell‐edge Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
11.1.9.20 Applying the ABS Collision Probability on Interference from RS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
11.1.9.21 Enabling Multi‐eNode‐B Carrier Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
11.1.9.22 Switching Between Carrier Aggregation Scheduling Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
11.1.9.23 Displaying Grid‐of‐Beam Patterns in Logarithmic Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
11.1.10 3GPP Multi‐RAT Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
11.1.10.1 BSIC, SC, and PCI Allocation with Inter‐technology Neighbour Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
11.1.10.2 Multi‐RAT Technology Selection Default Behaviour. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
11.1.11 Microwave Radio Links Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
11.1.11.1 Modifying the Default Format of Link Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
11.1.11.2 Updating A>>B and B>>A Profiles in Real‐time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
11.1.11.3 Disabling Shielding Factor on Wanted Signal at Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
11.1.11.4 Considering XPIF value in Interference for Dual‐Polar Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
11.1.11.5 Making the ITU‐R P.530‐5 Method Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
11.1.11.6 Decreasing Calculation Time of Path Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
11.1.11.7 Using Old Min C/I Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
11.1.11.8 Solving Alignment Issue in Generated Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
11.1.11.9 Defining Default Configuration Files for Link Budgets Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
11.1.11.10 Defining a Default Configuration File for the Channel Arrangement Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
11.1.11.11 Defining a Default Template for Microwave Links Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
11.1.12 Measurement Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
11.1.12.1 Displaying Additional Information in Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
11.1.12.2 Setting the Number of Transmitters per Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
11.1.12.3 Recalculating Distances of Points From There Serving Cells at Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
11.1.12.4 Defining the BCCH and BSIC Columns for FMT Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
11.1.12.5 Importing Drive Test Data with Scrambling Codes as Integers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
11.1.12.6 Importing Drive Test Data for Active and Filtered Transmitters Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
11.1.12.7 Specifying the Location of the ACP.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
11.2 ACP Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
11.2.1 Managing ACP Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
11.2.2 ACP GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
8
11.2.2.1 Default Settings of the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

11.2.2.2 Default Settings of the Optimisation > Cost Control Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
11.2.2.3 Default Settings of the Optimisation > Advanced Cost Control Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
11.2.2.4 Automatically Creating Custom Zones on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
11.2.2.5 Default Settings of the Objectives Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
11.2.2.6 Default Settings of the Reconfiguration page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
11.2.2.7 Default Settings of the Reconfiguration > Sites vertical tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
11.2.2.8 Custom Columns on Sites tab of Reconfiguration page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
11.2.2.9 Default Settings of the Reconfiguration > Transmitters Vertical Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
11.2.2.10 Custom Columns on the Reconfiguration > Transmitters/Remotes tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
11.2.2.11 Default Settings of the Antenna > Patterns Vertical Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
11.2.2.12 Default Settings of the Optimisation > EMF Exposure Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
11.2.2.13 Controlling Antenna Pattern Smoothing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
11.2.2.14 Default Settings of the Antenna Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
11.2.2.15 Defining the Antenna Masking Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
11.2.2.16 Defining Reconfiguration Values Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
11.2.2.16.1 Defining Reconfiguration Values for Transmitters, Repeaters, and Secondary Antennas Using Custom Atoll Fields 196
11.2.2.16.2 Defining Reconfiguration Values for Cells Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
11.2.2.16.3 Defining Reconfiguration Values for Sites Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
11.2.2.16.4 Defining Reconfiguration Values for Antennas Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
11.2.2.17 Defining Site Class Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
11.2.2.17.1 Defining Automatic Site Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
11.2.2.17.2 Automatic Assignment of Site Classes in the ACP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
11.2.2.18 Defining the Appearance of a Running Optimisation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
11.2.2.18.1 Defining the Colours in the Analysis Maps on the Quality Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
11.2.2.18.2 Other Components of the Optimisation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
11.2.2.19 Defining the Appearance of Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
11.2.2.20 Defining New Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
11.2.2.21 Defining the Functionality of the Commit Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
11.2.2.22 Defining the Appearance of the Overlay Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
11.2.2.23 Defining the Appearance of the Graph Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
11.2.2.24 Defining the Default Font. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
11.2.2.25 Exporting Optimisation Results in XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
11.2.3 ACP Core Engine Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.2.3.1 Log File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.2.3.2 Calculation Thread Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.2.3.3 Number of Threads Used for Propagation Model Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.2.3.4 Memory Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.2.3.5 Macro Diversity Gains Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.2.3.6 Transmitter Altitude Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.2.3.7 Automatic Candidate Positioning Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.2.3.8 Balancing Speed, Memory Use, and Accuracy in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
11.2.3.9 Accessing Raster Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
11.2.3.10 Filtering Clutter Class Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
11.2.3.11 Multi‐antenna Interference Calculation (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
11.2.3.12 Multi‐antenna Interference Calculation (WiMAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
11.2.3.13 Cyclic Prefix Energy in Signal Level Calculation (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.2.3.14 Cyclic Prefix Energy in Signal Level Calculation (WiMAX and Wi‐Fi). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.2.3.15 Fixed Ratio Between Pilot Power and Max Power (UMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.2.3.16 Showing Initial/Final Total Poweror DL Load on Sectors Tab (UMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.2.3.17 Enabling Multi‐technology Optimisation Including WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.2.4 EMF Exposure Core Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.2.5 Other Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
11.2.5.1 Validity of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
9
10
AT321_AM_E4 Chapter 1: Getting Started
1 Getting Started
Atoll is an open, scalable, and flexible multi‐technology network design and optimisation platform that supports wireless
operators throughout the network life cycle, from initial design to densification and optimisation. Atoll supports a wide range
of 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 in
a multi‐user environment.
In this chapter, the following are explained:
• "Supported Technologies" on page 11
• "Supported Operating Systems" on page 11
• "Supported Database Management Systems" on page 12
• "Supported Installation Configurations" on page 12
• "Recommended Hardware and Software" on page 12
• "Recommended Computer Network Architecture" on page 14.
1.1 Supported Technologies
Atoll 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 (combined
CDMA2000 and LTE). Atoll Microwave supports detailed design and analysis of microwave link networks.
1.2 Supported Operating Systems
Atoll supports the following versions of Microsoft Windows operating systems. Atoll also supports VMWare ESXi 4.x and 5.1
virtualisation 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 and 8.1 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
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
Among other Microsoft Windows components, Atoll 64‐bit uses Microsoft Access
Database Engine 64‐bit. Microsoft Access Database Engine 64‐bit is included in Microsoft
Office 64‐bit, and is also available as a free redistributable Microsoft Windows
component from the Forsk support website.
• If the computer on which you wish to install and run Atoll 64‐bit already has
Microsoft Office installed, you must upgrade it to Microsoft Office 64‐bit (version
2010 SP1 or newer).
• 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 the Forsk support website.
Note: Installing Microsoft Office 64‐bit or the Microsoft Access Database Engine 64‐bit
requires uninstalling any 32‐bit Microsoft Office components that may be installed on
the computer.
11
Chapter 1: Getting Started © Forsk 2014
1.3 Supported Database Management Systems
In a multi‐user environment, databases allow several users to share data without the risk of data inconsistency. In a multi‐user
environment, 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 database
must be installed:
Database Server Client computer
Microsoft Access No Yesa
Microsoft SQL server Yes No
Oracle Yes Yes (Oracle client)
a. It is possible to work with an Atoll document connected to a Microsoft Access database even if Microsoft Access is not
installed on the computer.
1.4 Supported Installation Configurations
Depending 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 that
allocates 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. The
floating licence management server allocates licence tokens to Atoll sessions run by the users on the servers. The
servers can be Citrix‐based, where users run Atoll sessions on the servers through the Citrix interface.
1.5 Recommended Hardware and Software
This section provides guidelines for dimensioning client computers and servers on your network for optimum performance
with Atoll. This section lists the recommended hardware and software for:
• "User Computers" on page 12
• "Database Servers" on page 13
• "Application Servers" on page 13
• "Floating Licence Servers" on page 13
• "File Servers" on page 13.
1.5.1 User Computers
The following table lists the required and recommended hardware and software for user computers (clients) intended for
running with Atoll.
Processor Core i7
RAM 8 GB or more
Storage 512 GBa (preferably SSD)
Operating system Windows 7 or Windows 8 Professional or Enterprise
a. Depends on the size of the locally stored geographic data and path loss matrices, if any.
User computers must also have a USB port available for plugging in a fixed licence key, or the nethasp.ini file providing
information 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 client
version 10.0.2.3 or later should be used.
12
AT321_AM_E4 Chapter 1: Getting Started
1.5.2 Database Servers
The following table lists the required and recommended hardware and software for an Oracle database server. The same
configuration can be considered valid for other database systems as well.
Processor Xeon E3/E5 family or equivalent
RAM 8 GB or more
Storage 2x146 GB (RAID 1) or morea
Oracle: Windows / UNIX / Linux / Solaris
Operating system
SQL Server: Microsoft Windows
Connectivity Gigabit Ethernet or better
Oracle 10g or 11g
RDBMS
Microsoft SQL Server 2005
a. Tablespace of around 100 MB per 10000 transmitters.
1.5.3 Application Servers
Application servers are intended for installing and running Atoll, defining user rights, etc. Users can work with Atoll installed
on 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 running
with Atoll.
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
Windows Server 2008 R2 SP1
Operating system
Windows Server 2012
Remote Desktop
Thin‐client configuration
Citrix XenApp 6.0 or later
Virtualisation VMWare ESXi 4.x or 5.1
The minimum bandwidth between application servers and client computers for satisfactory performance is 300 kbps per user.
1.5.4 Floating Licence Servers
The floating licence management server:
• Must be accessible to all the user computers / Citrix servers on the network in order to provide licence tokens for Atoll
sessions.
• 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 29.
• Must have the floating licence key plugged in.
• Can be one of the application servers.
1.5.5 File Servers
File servers can store geographic data, path loss matrices, Atoll configuration and initialisation files, and user projects. The
required 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 is
required 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 accessing
these data do not affect Atoll’s usage and unnecessarily slow down the GUI.
13
Chapter 1: Getting Started © Forsk 2014
1.6 Recommended Computer Network Architecture
The following network architecture recommendations are based on benchmark tests carried out on the network of an
average‐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 during
a 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 to
load all the path loss matrices in memory. When the path loss matrices are stored on a file server, as recommended, this
operation creates a considerable data transfer activity over the network. The benchmark tests have been based on this
simulated data transfer activity.
Computer Network Architecture
A centralised network architecture is the most widely used network architecture by Atoll users. The figure below shows the
recommended architecture along with a per‐user network bandwidth requirement between network components.
Figure 1.1: Recommended Network Architecture and Bandwidth Requirements
Citrix XenApp is used to centralise data and balance user loads between servers. A network based on such an architecture with
Citrix 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 is
recommended. 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. A
country‐wide project would have larger network dimensions than a project that covers a city.
Link
Recommended Bandwidth
From To
End‐user Citrix server 300 kbps per user
Citrix server File server 30 Mbps per user performing calculations
14
AT321_AM_E4 Chapter 2: Installing Atoll and Components
2 Installing Atoll and Components
The 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 Wizard
To install Atoll:
• If you work with fixed licences, you must unplug the key before the installation and wait for the installation to finish
before plugging it back in.
• Disable UAC (User Account Control) for the following versions of Microsoft Windows. If you are installing Atoll on
other versions of Microsoft Windows, proceed to step 1.
• Microsoft Windows Vista
• Microsoft Windows 7
• Microsoft Windows Server 2008 R2
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 the
computer. Microsoft Access Database Engine 64‐bit is included in Microsoft Office 64‐bit, and is also available as a free
redistributable 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 must
upgrade it to Microsoft Office 64‐bit (version 2010 SP1 or newer). This will automatically install the Microsoft Access
Database 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.
Installing Microsoft Office 64‐bit or the Microsoft Access Database Engine 64‐bit requires
uninstalling any 32‐bit Microsoft Office components that may be installed on the
computer.
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.
15
Chapter 2: Installing Atoll and Components © Forsk 2014

Figure 2.1: Select Destination Location Dialogue for Atoll
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.
Figure 2.2: Select Components Dialogue
7. Click Next.
If you selected the Distributed Calculation Server component for installation, the Logon Information dialogue
appears.
If you did not select this component, the Select Start Menu Folder dialogue appears. In which case, proceed to step 8.
Figure 2.3: Select Components Dialogue
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 of
the domain to access this service.
b. Click Next. The Select Start Menu Folder dialogue appears
8. Select the Start Menu folder for Atoll.
16
The default Start Menu folder for Atoll is Atoll. You can select a different folder by clicking Browse.
Figure 2.4: Select Start Menu Folder Dialogue
9. Click Next. The Ready to Install dialogue appears.
10. Review the installation parameters.
Figure 2.5: Ready to Install Dialogue
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. Restarting
the 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 an
administrator account and with UAC disabled when the installation is complete.
• If the following files do not already exist in the installation folder, empty ones are
created by the setup:
• [Atoll installation folder]\Atoll.ini
• [Atoll installation folder]\AntennaImport.ini
• [Atoll installation folder]\CWMeasurementsImport.ini
• [Atoll installation folder]\DriveTestDataImport.ini
• [Atoll installation folder]\coordsystems\Favourites.cs
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 accessible
to users.
To restrict access to the Atoll installation folder, you can assign read/write access rights
to this folder to administrators and read‐only rights to end‐users.
17
2.2 Installing Atoll C++ Development Kit
To 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
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:
• 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
You can select a different location by clicking Browse.

Figure 2.6: Select Destination Location Dialogue
4. Click Next. The Ready to Install dialogue appears.
5. Review the installation parameters.
18
Figure 2.7: Ready to Install Dialogue
6. Click Install. Atoll C++ Development Kit is installed on the computer.
2.3 Setup Command Line Parameters
You can also install Atoll and its components from the command line. The Atoll setup program accepts optional command line
parameters, which can be useful to administrators, and to other programs calling the setup program. For example, when
automating 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 the
installation 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 startup
prompt.
If the setup is silent and it requires to restart the computer, but the /NORESTART option is not used (see below), it will
display 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 Close
button. Useful along with /SILENT or /VERYSILENT.
• /NORESTART
Instructs the setup not to restart the computer even if necessary.
• /SAVEINF="file name"
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 be
prepared 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 the
folder name contains spaces.
• /GROUP="folder name"
Overrides the default start menu folder name displayed on the Select Start Menu Folder wizard page. Use quotes if
the 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 can
be helpful for troubleshooting. For example, if you suspect a file is not being installed as it should be, the log file will
tell you if the file was actually skipped and why. Use quotes if the filename contains spaces. If the file cannot be
created, 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
19
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 automatically
select 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.4 Installing and Uninstalling Add‐ins
Add‐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 and
register 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 it
in the list of available add‐ins. It is possible to access and work with add‐ins and macros when there is no ATL file open
in Atoll.
Installed add‐ins are automatically loaded by Atoll and appear in the Add‐ins and Macros
dialogue (Figure 2.8 on page 21). If you wish that a certain add‐in not be loaded, and
hence be unavailable for activation in this dialogue, you can do so by adding an option in
the Atoll.ini file. For more information, see "Loading, Activating, and Setting Add‐ins as
Visible" on page 146.
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.8 on page 21).
2. Select the add‐in’s check box to activate it, or clear the check box to deactivate it.
20
Figure 2.8: Add‐ins and Macros Dialogue
Add‐ins installed by the Atoll setup are uninstalled when Atoll is uninstalled. To uninstall any other add‐in by unregistering its
DLL:
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.5 Installing and Uninstalling Macros
Atoll 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. If
you 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 are
added to Atoll when the user configuration files are loaded. For more information, refer to "Contents of User Configuration
Files" on page 106.
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.
21
2.6 Atoll Command Line Parameters
Atoll supports the following optional command line parameters:
Atoll.exe [-log "logfilename"] [-Ini "inifilename"] [-Cfg "cfgfilename"]

[-Provider providername -UserId username -Password password
-DataSource server -Project projectaccount]
• ‐log "logfilename"
Instructs Atoll to create a log file containing all the messages listed in the Events tab. This can be helpful for
troubleshooting. "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 the
Atoll.ini file located in the Atoll installation folder. "inifilename" is the full path and file name of the initialisation file
inside quotes.
• ‐Cfg "cfgfilename"
Instructs Atoll to load the specified user configuration file when run. This can be used to override the default loading
of the Atoll.cfg file located in the Atoll installation folder. "cfgfilename" is the full path and file name of the user
configuration file inside quotes.
• ‐Provider providername
Instructs Atoll to use the mentioned providername to access the database server:
Provider Atoll version providername

32‐bit Microsoft.Jet.OLEDB.4.0
Microsoft Access
64‐bit Microsoft.ACE.OLEDB.12.0
SQL Server 32/64‐bit SQLOLEDB
Oracle (Oracle driver) 32/64‐bit OraOLEDB.Oracle
• ‐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.
• The keywords Provider, Password, UserId, DataSource, and Project are case sensitive.
2.7 Troubleshooting and Other Information
Read and follow carefully the instructions in "Installing Atoll Using the Setup Wizard" on page 15 for a smooth installation.
If problems occur and you are unable to resolve them with the help of the following information, contact Forsk’s customer
support.
Microsoft Windows Updates
• It is recommended to install new Windows updates. However, it is also recommended to go through the description
of each update patch to see whether it might have a negative effect on your system or network. Pay special attention
to updates and patches related to networking.
• It is also recommended to keep the Windows updates uninstall folders, named "$NtUninstall...", under the Windows
folder, in case you have to uninstall a certain patch. Some of the update patches might require uninstall folders of
older patches to be available for their own installation.
22
Fixed licence keys
• Fixed licence keys cannot be used with "Server"‐type operating systems. Therefore, you should not install the driver
for fixed licence keys on:
• 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 Atoll
installation folder if you selected the Driver for Fixed Licence Keys component during the installation. You can also
download 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 licence
keys to work.
• If you get a protection key error message, verify that the fixed licence key is correctly plugged in and that the licence
has not expired.
• In case the fixed or the floating licence key becomes unavailable, Atoll will ask the users currently accessing the key
to save their open documents before Atoll closes. If the key becomes available again, Atoll will let the users continue
working.
• 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.) by
selecting 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 contained
in 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 and
password provided to you by Forsk.
• The Atoll User Manual and other documents are available on the installation CD. More documents are available for
download on the Forsk’s support website.
• The support website also offers you:
• 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:
23
• 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.
24
AT321_AM_E4 Chapter 3: Setting Up Distributed Calculation Server
3 Setting Up Distributed Calculation Server
Distributed calculation enables you to distribute the calculation of path loss matrices over many computers in a network. The
distributed calculation service is an optional service that can be installed at the same time as Atoll. For more information on
installation, see "Installing Atoll and Components" on page 15.
A computer on which the distributed calculation service is installed and running is called a distributed calculation server. This
computer, the distributed calculation server, is visible to all the other computers on the network through Atoll. You can set
up 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. The
distributed calculation server uses the standard Atoll API to exchange data with the path loss calculator and Atoll. The
distributed 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 version
of 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" on
page 152.
3.1 Setting Up Servers
When installed, the distributed calculation service automatically starts and remains available as long as the computer is
turned on. The service does not require any active user session on the computer, i.e., the service keeps running even when
there 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 Control
Panel >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.
Figure 3.1: Atoll Server Properties
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.
25
Chapter 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 distributed
calculation 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 installation
folder. 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.
Atoll can detect a total of 10 instances of the distributed calculation service. If you run
more than 9 additional distributed calculation services, they will not be detected by Atoll
and can cause the operating system to stop responding.
Stopping and Starting the Distributed Calculation Server
To stop the distributed calculation service:
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 Atoll
installation folder.
c. Click Run.
This will remove the distributed calculation service from the computer.
3.2 Setting Up Atoll to Access the Servers
To 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 distributed
calculation 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 Process
Once distributed calculations have been set up on the calculation server and on the user sides, the path loss calculations run
by 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 on
a file server.
26
AT321_AM_E4 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 is
available, 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 messages
generated 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 local
computer. However, to avoid memory saturation, Atoll uses one thread on the local computer and calculates the path
loss 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 to
the storage location (which can also be on a file server, not necessarily on the user’s computer that requested the
calculations).
7. Atoll user can then request the path loss matrices from the file server if they are needed for coverage predictions.
27
Chapter 3: Setting Up Distributed Calculation Server © Forsk 2014
28
AT321_AM_E4 Chapter 4: Managing Licences
4 Managing Licences
Atoll 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 and
Components" on page 15.
The software for managing floating licence keys must be installed on a server accessible to the computers on which Atoll is
going to be used. For more information, see "Working with Floating Licences" on page 29.
For information on the Atoll licence management utility, see "Using the Atoll Licence Manager" on page 32.
4.1 Working with Floating Licences
A 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 available
to users through a server.
A floating licence server is a computer, accessible to other computers on a network, on which the floating licence
management software has been installed and a floating licence key plugged in. The floating licence server can be one of the
computers on which Atoll is installed.
The floating licence management software and the floating licence key control the number of potential Atoll users. A floating
licence system has a defined maximum number of tokens available. This is the maximum number of computers on which Atoll
can be run simultaneously. Each computer that runs Atoll takes one token from the floating licence key, even if more than
one Atoll session is run on the same computer. The token is released and made available for other users when all the Atoll
sessions 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 is
accessed first.
4.1.1 Installing the HASP Licensing System Files
Atoll uses a 3rd‐party floating licence management system called HASP from SafeNet. The floating licence management
system 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 (optional): 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.
The HASP device driver, the HASP licence manager, and the floating licence key must be installed on the server.
Newer versions may be available than those provided on the Atoll installation disk, therefore it is recommended to download
the latest HASP licensing products from the SafeNet web site.
HASP hardware keys are supported by Windows 2000 Server and Windows Server 2003
with HASP Licence Manager 8.20 or above.
4.1.1.1 Installing the HASP Device Driver
The HASP device driver enables communication between the hardware HASP floating license key and the License Manager
software.
The HASP device driver can be installed on a computer running Windows 2000 or later. A USB port must be available on the
server for plugging in the floating licence key.
• Do not plug the floating licence key into the server before installing the device driver.
Wait for the HASP licence manager setup to indicate when to plug in the key.
29
Chapter 4: Managing Licences © Forsk 2014
To install the HASP Device Driver:
1. Browse to the SafeNet download web site:
http://sentinelcustomer.safenet‐inc.com/sentineldownloads/
2. Locate and download the following files:
• Sentinel HASP/LDK ‐ Windows GUI Run‐time Installer ‐ version 6.64 or later.
3. Unzip the downloaded into a temporary directory.
4. Run the installer and follow the instructions provided.
5. Once the device driver is successfully installed, plug in the floating licence key.
4.1.1.2 Installing the HASP Licence Manager
The HASP licence manager controls the allocation and retrieval of licence tokens available on a floating licence key.
• If the floating licence server is protected by a firewall, port 475 must be open when
using the UDP or TCP protocols.
• In case the fixed or the floating licence key becomes unavailable, Atoll will ask the
users currently accessing the key to save their open documents before Atoll closes. If
the key becomes available again, Atoll will let the users continue working.
• The floating licence key can become unavailable and a key protection error message
appears in Atoll if the licence management server is heavily loaded. Check if there is
any application running on the server that might be causing the problem. If this is the
case, remove any such application from memory. If this is not possible, try changing
the latency associated to the HASP Licence Manager in accessing the key.
• You can optionally install the HASP Monitor on the floating licence server, or on one
or several other computers, to monitor the token allocation and retrieval activity. The
HASP Monitor displays the list of computers using tokens available on the floating
licence key.
To install the HASP License Manager:
1. Browse to the SafeNet download web site:
http://sentinelcustomer.safenet‐inc.com/sentineldownloads/
2. Locate and download the following files:
• HASP HL License Manager ‐ version 8.32 or later.
3. Unzip the downloaded into a temporary directory.
4. Run the installer and follow the instructions provided.
The installer is not compatible with Windows 8 or later. To install the HASP Device Driver
on Windows 8 or later, right‐click the installer, select Properties > Compatibility and run
the program in Windows Vista (Service Pack 2) compatibility mode.
5. When prompted, 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. You
can choose to install it as an application, but in that case you will have to run the licence manager manually every time
you log on to the server and you will have to stay logged on for the licence server to be available to the Atoll users.
6. 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 be
available in the task bar. You can access the network communication protocols by double‐clicking this icon.
When running, the HASP Licence Manager window displays a list of supported protocols which can be modified through the
Load and Remove menus. Closing this window does not stop the licence manager. The icon remains available in the taskbar
as long as the service is running.
Once the HASP licence manager has been installed, the floating licence key must always
remain plugged in.
30
To stop the HASP licence manager:
2. In the list of services, right‐click the HASP Loader service, and select Stop from the context menu.
System administrators might want to restrict access to the HASP licence manager
installation folder. To do this, you can assign read/write access rights to this folder to
administrators and read‐only rights to end‐users.
4.1.2 nhsrv.ini File
The 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 (usually
C:\Windows).
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 licence
server. Complete syntax can be found on the HASP installation CD or on the Aladdin website.
[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
4.1.3 nethasp.ini File
The nethasp.ini file enables Atoll to locate the floating licence server quickly. Without the nethasp.ini file, finding the floating
licence 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 to
store 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 than
one version of Atoll installed, and you wish to access the same floating licence server. This avoids making a copy of the file in
each 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 on
the HASP installation CD or on the Aladdin website.
[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
NH_TCPIP_METHOD = UDP ;(b)Send TCP or UDP packets
NH_USE_BROADCAST = Disabled ;Use TCP/IP broadcast - Enabled or Disabled
31
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.
b. For HASP Licence Manager 8.20 and later, Aladdin recommends UDP as the default TCP/IP method.
• Remove the NH_SESSION and NH_SEND_RCV entries from the nethasp.ini file if these
exist.
• These fields define the timeout delays depending to the network. They can be useful
in slow networks and should be set only if required.
4.2 Using the Atoll Licence Manager
Atoll Licence Manager enables you to monitor, troubleshoot, and update licence keys. You must not use the licence manager
without full instructions and details from Forsk customer support. Modifying parameters in the licence manager without
proper input from Forsk customer support can damage your fixed or floating licences and block access of Atoll users to the
licences.
4.2.1 Licence Manager Interface
To 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 32).
Figure 4.1: Atoll Licence Manager
4. Under Available licences, select a licence key in order to display the information related to it.
32
The Clear all button is reserved for Forsk use only.
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, when
requested, 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
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 stops
working. You can then choose to either purchase maintenance for the next year, and benefit from the new
features and bug fixes, or have the licence key reprogrammed without maintenance for the next year, in which
case 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 configured
through the Atoll.ini file.
• Do not attempt to modify the Time bomb settings on the fixed licence key. Contact
Forsk’s customer support.
• Do not change the computer’s date.
• Under Profile signature, the PID (profile signature or ID) is the encrypted description of the user rights available
on the key. Each key has a unique PID.
• Under Current profile summary, all of the above information is summarised.
4.2.2 Updating Licence Keys
Atoll licence manager enables administrators to update licence keys by loading new key programming data from ALIC files
provided by Forsk. To update a licence key, you must have the ALIC file sent by Forsk.
Do not attempt to reprogram a licence key without full information and support from
Forsk customer support.
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 long
as a session is running. If a licence key is updated while a session is still running, the running session will not read the
updated licence information from the key and will expire according to the old licence information.
2. Go to the Atoll installation folder.
3. Run Lic.exe. The licence manager opens (see Figure 4.1 on page 32).
4. Under Available licences, select the key to update. If the key does not appear in the available licences list, check that
it 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.
33
34
AT321_AM_E4 Chapter 5: Managing Databases
5 Managing Databases
In Atoll, you can work with standalone documents, i.e., documents without any back‐end database, or with documents
connected to databases. Standalone documents are more portable, however a back‐end database is required when working
in a multi‐user environment. In multi‐user environments, several users work on the same project and a central data storage
is 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 and
resolve 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 be
stored on the same database server using the same RDBMS (Oracle, for example).
In this chapter, the following are explained:
• "Atoll Database Templates" on page 35
• "Customising Atoll Database Structures" on page 36
• "Atoll Management Console" on page 38
• "Creating New Databases" on page 39
• "Upgrading Existing Databases" on page 41
• "Working With a Multi‐level Databases" on page 45
• "Setting Database Access Privileges" on page 49
• "Managing Data Modifications History" on page 50
5.1 Atoll Database Templates
All the technology modules available in Atoll (GSM, UMTS, LTE, CDMA2000, TD‐SCDMA, WiMAX, Wi‐Fi, and Microwave Radio
Links) are based on database templates. These templates are used for creating Atoll documents with the appropriate data
structure 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 modifications
are applied to existing Atoll documents and databases by Atoll and the Atoll Management Console, respectively. It is also
possible to upgrade an existing database manually, but due to the complex nature of the upgrade process, it is highly
recommended 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 of
tables 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"
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: = n or  1
• 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.
The following table lists the types of fields used in Atoll database templates, their sizes, and the equivalent field types and
sizes in different RDBMS:
35
Chapter 5: Managing Databases © Forsk 2014
Atoll Oracle Equivalent Microsoft SQL Server Equivalent Microsoft

Access
Field Type Length Field Type Length Field Type Length Equivalent
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
1 Variable1 Variable1
Text Variable VARCHAR2 varchar Text1
Memo Variable VARCHAR2 2000 varchar 4000 Memo
2 > 2000
CLOB
Binary Variable image 16 OLE Object
BLOB3 Variable
1. Lengths for these fields are specified in parentheses in the database structure tables.
2. CLOB: Character large object
3. BLOB: Binary large object
If you export the contents of an Atoll document, already connected to a database, to
another RDBMS (for example, if you export a document connected to an Oracle database
to SQL Server), some field types will be converted according to the above table. This
conversion does not have any impact on the document in Atoll.
For more information on the Atoll Management Console and upgrading databases, see "Atoll Management Console" on
page 38 and "Upgrading Existing Databases" on page 41, respectively.
5.2 Customising Atoll Database Structures
Atoll 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 the
CustomFields 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 be
available in all new Atoll documents created from that template. A new database created by exporting such a
document will also contain these custom fields.
• Custom fields added to an Atoll document through the Atoll user interface will not be automatically added to the
corresponding Atoll database template. However, a new database created by exporting such a document will contain
these custom fields. For more information on adding custom fields to Atoll documents through the user interface, see
the 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:
User Interface
Field Description
Caption
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)
36
User Interface
Field Description
Caption
Caption of the field as it will appear in the user interface (optional but
CAPTION Legend
recommended)
Semicolon‐separated list of the names of groups to which the field belongs
GROUP_NAME Group
(optional)
1: Custom field only accepts values listed in the choice list
CHOICE_TYPE Restricted
0: Custom field accepts values other that those listed in the choice list
1: Custom field is read‐only in the user interface
DISPLAY_TYPE Read‐only
0: 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 Properties
dialogue.
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 default
values 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 of
the following fields:
User Interface
Field Description
Caption
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 decimal
symbol.
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 choice
lists 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 of
the following fields:
User Interface
Field Description
Caption
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
For example, you can replace the default choice list available for the SUPPORT_INFO field in the Sites table with a different
list of options corresponding to the different types of towers and pylons that may exist in your network.
• You can enter one of the choice list items in the DEFAULT_VALUE in order to set a
default value for the text field.
• For custom text fields, you can set the CHOICE_TYPE to 1 if you want the custom text
field to only accept values listed in the choice list. By default, CHOICE_TYPE is
considered to be 0 meaning that users are allowed to enter values other than those
defined in the choice list.
37
5.3 Atoll Management Console
The Atoll Management Console provides the database administrator the possibility of globally managing the database with
the 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 39)
• Upgrade database structures from one major version to the next (see "Upgrading Existing Databases" on page 41)
• Work with multi‐level databases (see "Working With a Multi‐level Databases" on page 45)
• Manage data modifications history in databases (see "Managing Data Modifications History" on page 50)
• Manage user accounts and access rights (see "Managing User Accounts and Access Rights in Oracle" on page 61)
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" on
page 15. You can run the Atoll Management Console from the Windows Start menu program group or by double‐clicking
AMC.msc in the management subfolder of the Atoll installation folder. The Atoll Management Console runs using the
Microsoft Management Console environment.
When the Atoll Management Console is run for the first time, you must register your database server in order to have the
databases 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 Administration
Atoll. 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 is
Oracle or SQL Server.
Figure 5.1: Data Link Properties dialogue ‐ Provider Tab
4. Click Next. On the Connection tab, enter the server name, and the user name and password required to access the
database 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.2
on page 38). You now have access to the features offered by the Atoll Management Console.
Figure 5.2: Atoll Management Console
38
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 current
user can be the owner of one of the listed databases. The user name of the owner of a database appears in parentheses in
the title bar. One Oracle user can create and own one database. For each new database, you must create a new user owner
of 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 information
on master and project databases, see "Working With a Multi‐level Databases" on page 45.
• 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 Databases
New databases can be created using the Atoll Management Console or by directly exporting a document to a database from
Atoll. In this section, the following are explained:
• "Creating a New Database Using the Atoll Management Console" on page 39
• "Creating a New Database Using Atoll" on page 41
5.4.1 Creating a New Database Using the Atoll Management
Console
You can create new databases using the Atoll Management Console.
You must have administrator rights to the database and to the server for creating new
databases.
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 to
create a new database. The context menu appears.
2. Select New > Database. The New Database Wizard dialogue appears.
Figure 5.3: New Database Wizard
39
Figure 5.3: New Database Wizard
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 new
user and enter a Name and Password to create a new user that will be owner of the new database.
If your password must contain special characters, for example, !, ?, etc., type the
password inside double quotation marks: "mypassword!" instead of mypassword!
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 database
templates installed with Atoll.
Atoll and the Atoll Management Console must have the same version. This means that
the Atoll Management Console can create databases based on the database templates
installed with Atoll of the same version.
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 selected
database server.
A database created using the Atoll Management Console contains an ATOLL_ADMIN table with the following structure:
Field Type Description

NAME Text (50) The name of the database
Text
DESCRIPTION Description of the database
(255)
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)
40

ATOLL_TEMPLATE Text (50) Atoll database template used to create the database
DBSCHEMA Memo An image of the schema of the original database
Among other uses, the ATOLL_ADMIN table is used to speed up the database upgrade to the next version. This table stores
the 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 using
the Atoll Management Console contain a smaller ATOLL_ADMIN table, with just the NAME, ATOLL_VERSION, and
ATOLL_BUILD fields. Upgrading such databases using the Atoll Management Console can take a long time because the Atoll
Management 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 41.
All the tables in a database created using the Atoll Management Console (except the COORDSYS and UNITS tables) contain a
non‐modifiable, integer DB_RECORD_ID field. This field is used to store the ID of every record in the table. It is not added to
Microsoft Access databases.
5.4.2 Creating a New Database Using Atoll
You 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.
By setting an option in the Atoll.ini file, you can instruct Atoll to always use a defined
database type (MS Access, SQL Server, or Oracle). In this case, the Export to a Database
dialogue will be skipped and the database‐specific authentication dialogue will appear
immediately. For more information, see "Setting the Type of Database Being Used" on
page 157.
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:

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 coordinate
systems and units in the source document.
• Before creating the database, make sure that you have added any required custom
fields. 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 the
database, 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 database
when they create a new Atoll document from the database or refresh an existing one.
5.5 Upgrading Existing Databases
In each new major release, data structure changes must be made in the database in order to support the new features added
in the version. The data structures of standalone Atoll documents, i.e., documents not connected to any database are
upgraded when they are opened in the new Atoll version. You can upgrade databases using the Atoll Management Console.
41
• 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 skip
or have skipped an intermediate major version, you must upgrade your database
twice in order to make it compatible with the new version.
• If you are upgrading a database which was neither created nor already upgraded (at
least once) using the Atoll Management Console, see "Upgrading Databases for the
First Time" on page 43 first.
The Microwave Radio Links template now supports Radio Series. Similar microwave
radios 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 the
MWEquipments table.
2. Enter the radio series names in this field for each radio, i.e., group the radios of
the same series under the same radio series name in the FAMILY field.
Without this manual organisation of the microwave radios into radio series, the database
upgrade will create one radio series for each microwave radio.
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. The
context 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 be
upgraded.
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 was
created. If there is more than one template corresponding to the network, select the template to be used for the
upgrade and click Next.
The Atoll Management Console upgrades the database.
• If some of the tables in a database have been replaced by views, the Database
Upgrade Wizard asks to select the views to upgrade. Select the views that you want
the 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 of
the view. The upgraded definition will take the newly added fields into account.
• When you upgrade a 3GPP Multi‐RAT database, the Atoll Management Console adds
any missing tables to the database. For example, a database created by exporting a
3GPP Multi‐RAT document containing only GSM contains only GSM tables. When
upgraded, the Atoll Management Console will add the UMTS and LTE tables to the
database as well.
Obsolete fields in the data structure are automatically deleted from the database by the Atoll Management Console during
the upgrade.
If you use the Atoll Management Console’s history management tool, you must repair
the upgraded database in order to continue using this tool. For more information, see
"Managing Data Modifications History" on page 50.
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.
42
When users open their existing documents in the new Atoll version, they are asked whether they want to upgrade the
documents’ data structures to the new version or to disconnect the documents from the database. On selecting the
upgrade option, Atoll upgrades the document data structures to make them compatible with the new version.
Notes on Document Data Structure Upgrade
• The data structure of an Atoll document not connected to any database is
automatically upgraded to the new Atoll version when the document is opened and
saved 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 the
document in the previous Atoll version as read‐only. It is also not possible to
interact with the upgraded database (archive, refresh, etc., are not allowed). To
make the document write‐accessible in the previous Atoll version, it must be
disconnected from the upgraded database.
It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields as
required by the new version. For information on manually upgrading a database, see "Upgrading Databases Manually" on
page 44.
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 Atoll
Management Console, you must first upgrade the database to the same version as the current version of the database. This
is required so that the Atoll Management console adds the required information to the database to make it upgradable to
newer versions.
To upgrade the database:
1. Before installing the new version of Atoll, install the Atoll Management Console (if not already installed) compatible
with the existing version of Atoll.
2. Upgrade the database (as described in "Upgrading Existing Databases" on page 41) using the Atoll Management
Console 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 the
tables, as described in "Creating a New Database Using the Atoll Management Console" on page 39. Once the Atoll
Management Console has performed the necessary modifications, you can upgrade the database to the new Atoll
version.
3. Install the new version of Atoll and the Atoll Management Console.
4. Upgrade the database (as described in "Upgrading Existing Databases" on page 41), using the new version of the Atoll
Management 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 stores
the 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.dll
again, upgrade the database to the existing version, register the new Admin.dll, and upgrade the database to the new version
using the new Atoll Management Console.
For the Atoll Management Console to be able to recognise obsolete or deleted fields
from 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 Atoll
Management Console, the database administrator will have to remove the obsolete
fields manually. Once the Atoll Management Console has been used to upgrade a
database, it will be able to recognise obsolete or deleted fields in the following upgrades.
43
Upgrading Databases Manually
Due to the complex nature of the database upgrade process, it is highly recommended to use the Atoll Management Console
for upgrading existing databases. You should only proceed with a manual upgrade of your database, as described below, if
and 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 are
lost 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 make
it compatible with the new version.
3. Using the upgraded document, create a new database as explained in "Creating a New Database Using Atoll" on
page 41.
If you are upgrading your database using a script based on the data structure
modifications 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 39.
• 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 this
equipment to "Conventional Beamformer."
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 database
through 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 41.
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.
Figure 5.4: Technologies in the Multi‐RAT Database
9. Select the technology you want to add and click OK.
44
• You cannot deselect a technology already present in a multi‐RAT database.
A new record is added to the networks table for each technology added to the database.
5.6 Working With a Multi‐level Databases
Atoll Management Console allows you to set up and work with multi‐level databases using Oracle. In this optional database
architecture, the master database is not directly accessible to end‐users. Groups of end‐users work with their respective
project databases which are in turn connected to the master database. The end‐users archive data to and refresh data from
their respective project databases, and the database administrator manages the connections and data exchange between the
project 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 here
work with their local region’s project database, and would not have to unnecessarily load country‐wide data.
Figure 5.5: Working With a Single Level Database
Project databases are intermediate databases created from a common master database. A project database contains the
original 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 the
master database remains unchanged until the database administrator archives all the modifications from the project
databases to the master database.
Figure 5.6: Working With Project Databases
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 entire
master 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. This
reduces the risk of conflicts in the database as only the database administrator can archive modifications from project
databases to the master database.
For example, if a country‐wide network database is accessible to all end‐users:
45
• 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 scenario
is depicted in the figure below:
Figure 5.7: Multiple Project Databases From a Single Master Database
Multi‐level databases can be set up using the Atoll Management Console. In this section, the following are explained:
• "Creating Project Databases" on page 46
• "Archiving Project Databases to Master Databases" on page 48
• "Refreshing Project Databases from Master Databases" on page 49
5.6.1 Creating Project Databases
You can create project databases using the Atoll Management Console.
For creating a project database, you must have enough rights to be able to create new
tables in the master database schema.
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 to
create 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 select
Create a new user and enter a User name and Password to create a new user that will be owner of the new project
database.
Some versions of Oracle let you create a new user through this dialogue but the new user
is not assigned DBA rights, which makes the new user unable to create the project
database. Therefore, it is recommended to create the new user with DBA rights directly
in the database before create the project database using the Atoll Management Console
using the new user account.
6. Click Next. The Name the database page appears.
46
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 sites
included in a site list of the master database, and select a site list. This option is only available when at least one
site list exists in the master database.
• Select the sites to include using an SQL condition
that verify an SQL condition (for example, sites that have a common parameter or flag), and enter the SQL
condition.
• Include the sites contained within a polygon contained in a file
that 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 the
selected database server.
The project database will have the type PROJECT listed in the Atoll Management Console window.
Figure 5.8: New Project Database Wizard
A project database created using the Atoll Management Console contains an ATOLL_ADMIN_PRJ table, in addition to the
ATOLL_ADMIN table, with the following structure:

NAME Text (50) The name of the project database
Text
MASTER_CONNECTION Connection parameters to the master database
(255)
MASTER_DBSCHEMA Text (50) The name of the original schema of the master database
Data extraction method used to select the sites to include in the project
SEL_METHOD Short
database
47

Text
SEL_PARAM Site selection method parameters (the SQL condition, if any)
(255)
SEL_PGON Memo Site selection polygon (if used)
You can view the details stored in the ATOLL_ADMIN_PRJ table in the project database properties. To view the above details
of 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 and
Settings 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 are
prefixed with "O_". For example, the ANTENNAS table of the master database is stored in the project database under the
name O_ANTENNAS. The COORDSYS and UNITS are not copied to the project database because their contents cannot be
different 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 database
using the O_RECORD_ID of the project database and DB_RECORD_ID of the master database. The O_CHANGED field is set to
TRUE for records modified in the project database.
5.6.2 Archiving Project Databases to Master Databases
Changes made in the project databases can be archived to the master database using the Atoll Management Console. The
Archive 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 to
archive 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 the
project 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 of
the field in the master database. This can occur if the master database has been updated with changes from
another source and the project database has not yet been refreshed with data from the master database.
48
Figure 5.9: Archiving Changes in Master Databases
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 Databases
Project 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 refresh
with 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 unmodified
records from the master database. During the refresh, the Atoll Management Console will reload records from
the 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 unmodified
records 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 Privileges
You 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 access
to 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 the
users who have access to the database. Different write permissions can be granted for columns of the tables. For
example, 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 user
connection properties (log in), on external table references, or on the geographic locations of sites (e.g., through
polygons, or when using the spatial features of databases).
49
All of these permissions can be set as regular SELECT, INSERT, UPDATE, and DELETE privileges on database objects. Triggers
can 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 to
define 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 61.
5.8 Managing Data Modifications History
The Atoll Management Console allows you to keep and manage the history of modifications made in the network data by
different users. The history management tool keeps track of all the modifications made in the following Atoll tables:
Technology Tracked Tables
Sites, Transmitters, TRGs, TRXs, Repeaters, SecondaryAntennas, Neighbours,
GSM GPRS EDGE
NeighboursExt
Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours,
UMTS HSPA
NeighboursExt
Sites, Transmitters, T4GCells, Repeaters, SecondaryAntennas, Neighbours,
LTE
NeighboursExt
sites, ltransmitters, utransmitters, gtransmitters, lcells, ucells, gtrgs, gtrxs,
lrepeaters, urepeaters, grepeaters, lsecondaryantennas, usecondaryantennas,
3GPP Multi‐RAT
gsecondaryantennas, lneighbours, uneighbours, gneighbours, guneighbours,
ugneighbours, glneighbours, lgneighbours, ulneighbours, luneighbours
Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours,
CDMA2000 1xRTT 1xEV‐DO
NeighboursExt
Sites, Transmitters, WCells, Repeaters, SecondaryAntennas, Neighbours,
WiMAX
NeighboursExt
Sites, MWLinks, MWHubs, MWPMP, MWMultiHops, MWMultiHopsLinks,
Microwave Radio Links
MWRepeaters
You can, however, enable or disable history management for table as required (see "Enabling/Disabling Data Modifications
History Management" on page 51 for more information). If you want, you can also purge old data modifications history (see
"Purging Old Data Modification Records" on page 52 for more information).
The history management tool is available for Oracle databases. The following section describes how to set up the history
management tool using the Atoll Management Console.
5.8.1 Setting Up Data Modifications History Management
When you set up history management for any database, the Atoll Management Console adds new tables to the database
structure. For each tracked table, it adds a corresponding history table that has the same name as the tracked table with the
suffix "_H". Each history table has the same structure as the corresponding tracked table, but with the following four
additional fields. These fields enable the Atoll Management Console to store the modifications made by users to each tracked
table:
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
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 up
data 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.
50
The Atoll Management Console updates the database structure to make it compatible with the data modifications
history 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 52). This
dialogue lists all the tables for which the data modifications history management has been enabled, the total numbers
of 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 50 are stored in the history
tables 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 51.
5.8.2 Enabling/Disabling Data Modifications History Management
You can enable or disable data modifications history management for any table. You can enable or disable history
management 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 table
corresponding to the table. When history management is disabled for a table, the MODIFIED_BY, MODIFIED_DATE, and
HISTORY_STATUS fields are still updated with each modification, but the history of modifications is not stored in the
corresponding 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 enable
3. In the Data Modifications History Management dialogue, right‐click the table for which you want to enable data
modifications 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 History
Management 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 disable
3. In the Data Modifications History Management dialogue, right‐click the table for which you want to enable data
modifications 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 Management
dialogue is set to Deactivated for this table.
5.8.3 Updating After Data Structure Upgrade
When 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 be
updated 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 whose
history 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 to
update. The context menu appears.
3. In the Data Modifications History Management dialogue, right‐click the table that you want to update. The context
menu 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 of
the corresponding tracked table.
51
5.8.4 Purging Old Data Modification Records
History management tables store the lists of all the modifications made by all the users. These tables can therefore quickly
become very large and require a lot of disk space. You can purge old data modifications history (records) from these tables in
order to gain disk space.
In this section, the following is explained:
• "Purging Old Data Modification Records of a Table" on page 52
• "Purging Old Data Modification Records of a Database" on page 53.
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 old
data modifications history. The context menu appears.
2. In the context menu, select Manage Data Modifications History. The Data Modifications History Management
dialogue appears (see Figure 5.10 on page 52).
Figure 5.10: Data Modifications History Management Dialogue
3. In the Data Modifications History Management dialogue, right‐click the table for which you want to purge old data
modifications history. The context menu appears.
4. In the context menu, select Purge. The table record purge dialogue appears (see Figure 5.11 on page 52).
Figure 5.11: Table Record Purge Dialogue
5. Under Purge data modifications recorded before, move the slider to select from which date onwards you want to
keep the data modification history records.
All the data modification history records before this date will be deleted. Number of records shows the number of
records 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 to
creation 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 selected
date are not deleted.
52
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 old
data modifications history. The context menu appears.
2. In the context menu, select Manage Data Modifications History. The Data Modifications History Management
3. In the Data Modifications History Management dialogue, click the Scheduler button. The database record purge
Figure 5.12: Database Record Purge Dialogue
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 purge
periodicity 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 under
Conditions.
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 53).
9. Click the Close button.
53
Scheduled regular purges are programmed as a scheduled job in Oracle using the DBMS_SCHEDULER.create_job function. The
following SQL string generates scheduled job:
"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;"
Here:
Parameter Description
job_name AHMS_<schema_name>
job_type PLSQL_BLOCK
job_action Actual PL‐SQL code for the purge
start_date SYSTIMESTAMP
Frequency of the scheduled purge
repeat_interval
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
5.9 Appendices
The first appendix shows how to use SQL for Oracle database customisation and the second appendix shows how to set up
databases for co‐planning taking the example of GSM and UMTS MS Access databases.
5.9.1 Appendix 1: Advanced Customisation
You can use SQL in order to manage access to and share the Sites table (example 1), or to restrict the connection to a set of
transmitters for some users (example 2). To implement the following two examples, you must log on as the owner of the
tables 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.
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);
2. Replace the AtollADMINGSM.SITES table by an AtollADMINGSM.SITES view.
SQL > connect AtollADMINGSM/ADMINGSM@AtollDB;
SQL > drop table AtollADMINGSM.SITES;
SQL > grant delete on AtollADMIN.SITES to AtollADMINGSM with grant option;
54
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;
3. Follow the same procedure for UMTS (AtollADMIN.SITES already created).
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;
4. Commit.
SQL > 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.
SQL > alter table SITES add (POSTCODE number);
2. Rename the SITES table to be able to hide it by a view.
SQL > rename SITES to PRIVATE_SITES;
3. Create a POSTCODETABLE table to link users and postcodes (one user can be linked to several postcodes).
SQL > create table POSTCODETABLE (USERNAME varchar2(30), POSTCODE number);
You can fill this table using this instruction.
SQL > insert into POSTCODETABLE values (‘USER1’, 75);
4. Create a view owned by this user hiding the actual SITES table through these commands.
SQL > create view SITES as
select * from PRIVATE_SITES
where POSTCODE in
(select POSTCODE from POSTCODETABLE where USERNAME =USER)
with check option;
"with check option" is very important as it specifies that insert and update operations performed through the view
must 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 the
SITES view.
SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS;

SQL > create view TRANSMITTERS as
select * from PRIVATE_TRANSMITTERS
where SITE_NAME in (select NAME from SITES);
6. Commit.
SQL > commit;
55
The error message "ORA‐01402: view WITH CHECK OPTION ‐ clause violation" appears if
you try to archive a record that does not match the project.
5.9.2 Appendix 2: Setting Up Databases for Co‐planning
Two 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‐RAT
document.
• Co‐planning any two radio technologies (GSM, UMTS, LTE, CDMA2000, TD‐SCDMA, and WiMAX), with two separate
data structures, by linking Atoll documents.
In terms of database, while the first approach provides an integrated multi‐technology co‐planning environment, the second
requires setting up sharing of the Sites table between the databases of the two technologies being co‐planned. The Sites table
must be shared between the databases of the two technologies being co‐planned so that the sites where sectors of both
technologies are installed are listed only once in a common Sites table. In other words, the Sites tables in the databases of the
two 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 radio
technology 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 contain
the 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 the
same 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.
56
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 data
source 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 tables
contain 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 other
tables in the database. See the Data Structure Reference Guide for detailed information on database tables.
• The UMTS Sites table has more fields than the GSM Sites table. Therefore, you should
replace the GSM Sites table with the UMTS one.
• When you upgrade one by one the databases that share the Sites table, any triggers
that you might have set on the Sites table of the database that is upgraded first might
be overwritten by the triggers set on the Sites table of the database upgraded last. In
order to avoid the triggers being overwritten, you can rename the triggers on the
Sites table of the database upgraded first (by adding, for example, the database
technology as prefix to the trigger names) before upgrading the other database(s).
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 mechanism
against database inconsistencies. If a user archives the changes made in one document but forgets to archive the changes
made 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 or
archives one document, Atoll automatically saves or archives the other. This can be done using a macro triggered by the save
or archive operation.
57
58
AT321_AM_E4 Chapter 6: Multi‐user Environments
6 Multi‐user Environments
A 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. For
example, different user groups can work on different regions of a country‐wide network. In this chapter, the following are
explained:
• "Setting Up Multi‐user Environments" on page 59
• "Components of Multi‐user Environments" on page 59
• "Managing User Accounts and Access Rights in Oracle" on page 61
6.1 Setting Up Multi‐user Environments
The 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 59.
1. Create the master Atoll document with the required network data and geographic data. For more information, see
"Master Atoll Document" on page 60 and "Shared Geographic Data" on page 60.
2. Export the master Atoll document to a new database and keep the document connected to the new database. For
more information, see "Master Database" on page 60.
3. Create the private path loss matrices folder for the master Atoll document and calculate the private path loss
matrices. For more information, see "Shared Path Loss Matrices" on page 61.
4. Create user Atoll documents from the master database. For more information, see "User Atoll Documents" on
page 61.
5. In the user Atoll documents, add the required geographic data and set the master Atoll document’s private path loss
matrices folder as the shared path loss matrices folder of the user documents.
• 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 Atoll
document after loading modified data from the master database. For more
information, see "Appendix 1: Checking Data Integrity" on page 65.
6.2 Components of Multi‐user Environments
Figure 6.1 on page 59 shows the components of a multi‐user environment.
Figure 6.1: Components of Multi‐user Environments
59
Chapter 6: Multi‐user Environments © Forsk 2014
In this section, the following are explained:
• "Master Atoll Document" on page 60
• "Master Database" on page 60
• "Shared Geographic Data" on page 60
• "Shared Path Loss Matrices" on page 61
• "User Atoll Documents" on page 61
6.2.1 Master Atoll Document
It is the source Atoll document that contains the entire project’s network data. It is created and maintained by the Atoll
administrator. This document is initially used to create the radio network database with which all the end‐users work. The
master 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 and
keeping the path loss matrices up to date with the user modifications to the radio network data. The document also contains
the required geographic data for path loss calculations. Geographic data are usually located on file servers and linked to the
document, not embedded in the ATL file. The private path loss matrices of this document are used as shared path loss matrices
by the end‐users. The shared path loss matrices folder is usually located on a file server accessible to all the users on the
network.
For exceptionally large networks, you can also work with more than one master Atoll document (for example, one master
document per region). However, the multi‐user environment set up remains the same. Master Atoll documents should not
have redundant radio network data (same sites, for example), and should ideally cover different geographical regions. For
more information on regionalisation, see "Appendix 2: Database Regionalisation" on page 66.
If you wish to add custom fields in the Atoll document, you should first add the field in
the database, and then update your Atoll document from the database. Custom fields
added in an Atoll document connected to a Microsoft Access database are automatically
added to the database. However, this is not the case with other RDBMS, such as Oracle.
6.2.2 Master Database
The master database stores the radio network data shared by all the end‐users. It can be created by exporting the radio
network data in the master Atoll document to a database from Atoll (for more information, see "Creating a New Database
Using Atoll" on page 41). An empty database can also be created using the Atoll Management Console, and populated with
data later on (for more information, see "Creating a New Database Using the Atoll Management Console" on page 39).
Only radio network data are stored in the database, i.e., sites, transmitters, antennas, etc. Parameters related to geographic
data files, their paths, folder configurations, prediction definitions, zones, traffic maps, measurements can be stored in user
configuration files (see "Configuration Files" on page 105 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 66. For more information on database management, see "Managing
Databases" on page 35. The recommended database server configuration is provided in "Recommended Hardware and
Software" on page 12.
The same database server can be used to store one or more master databases
corresponding to different technologies. For example, a GSM database and a UMTS
database can be stored on the same database server using the same RDBMS (Oracle, for
example).
6.2.3 Shared Geographic Data
Geographic 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 105.
The administrator can set up different user configuration files (CFG) for separate user groups. User configuration files can be
created so that only the geographic data required by a user are loaded. It is possible to load a user configuration file
automatically when running Atoll. User configuration files can be shared and exchanged between users working on the same
project. For more information, see "Atoll Command Line Parameters" on page 22.
Geographic data files are usually large files, and it is recommended that these be stored externally and not embedded in Atoll
documents. The recommended file server configuration is provided in "Recommended Hardware and Software" on page 12.
60
If users modify geographic data locally, for example edit clutter or traffic in their
respective projects, they should store these modified geographic data locally so that the
modifications do not impact other users.
6.2.4 Shared Path Loss Matrices
Shared path loss matrices are usually stored on a file server accessible to and shared by all the users working on the same
project. These path losses are calculated using the master Atoll document by the Atoll administrator. The private path loss
matrices 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 path
loss 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 master
database 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 66.
Shared path loss matrices are available for use in calculations to all the end‐users. However, end‐users are not allowed to
modify the shared path loss matrices.
The shared path loss matrices must be unlocked in order for users to be able to work with
them. You can check whether path loss matrices are unlocked in the Propagation tab of
the Transmitters folder’s properties dialogue.
6.2.5 User Atoll Documents
User Atoll documents are created from the master database. These can contain the entire project network data or only a part
of it. User documents are the working documents of the Atoll end‐users connected to the master database, the geographic
data, 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 loss
matrices folder for the document. For any modifications made by end‐users in their Atoll documents that render some shared
path losses invalid, Atoll calculates the invalid path loss matrices locally for the end‐users and stores them in their private path
loss matrices location. Shared path loss matrices are only used in calculations if valid private path loss matrices are not
available. 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 66.
If you wish to add custom fields in the Atoll document, you should first add the field in
the database, and then update your Atoll document from the database. Custom fields
added in an Atoll document connected to a Microsoft Access database are automatically
added to the database. However, this is not the case with other RDBMS, such as Oracle.
6.3 Managing User Accounts and Access Rights in Oracle
The Atoll Management Console enables you to create and delete database user accounts, edit user account information, and
define 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 make
the database compatible with the user management tool. This is done automatically when the user management tool is run
on a database for the first time. The database has to be of the same version as the Atoll Management Console being used to
manage 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 62).
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:

ATOLL_USER Text (50) Name of the user account
61

RIGHTS Memo Semi‐colon separated set of interface access rights
Each user’s interface access rights are stored in a unique record in the GUIUserRights table. The contents of the RIGHTS field
have the following syntax:
RADIOPARAMS;CALCPARAMS;PROPAGMODELS;PASSWORD
The syntax is explained in detail in "Defining Database and Interface Access Rights" on page 62.
If interface access rights are not defined for a database, i.e., the GUIUserRights table does not exist, all the users have
unrestricted 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 document
connected to the database, Atoll retrieves the interface access rights for the user when he enters his user name and password
to 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’s
interface access rights are set to read‐only by default (for more information, see "Defining Database and Interface Access
Rights" on page 62). If the user is listed in the GUIUserRights table, his interface access rights are read and applied to the Atoll
interface (table grids and properties dialogues). A message is displayed in the Event Viewer window to inform the user of his
interface 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 can
work on their documents without actually being connected to the database, and still have their usual interface access rights
applied in the document.
Atoll does not ask for the user name and password when a document is opened using the
API. The interface access rights stored in the document are used.
When database connection properties are modified for a document, for example, when a different user enters his user name
and 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 Rights
For 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.
Figure 6.2: User Account and Access Rights Management Dialogue
3. Under Atoll projects, select the project for which you want to manage user accounts.
62
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 64.
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 they
are 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 table
of 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 network
data 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 other
than Oracle, you will not be able to set database access rights. You can, however, still set interface access rights as
explained 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, 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.
• Read‐only: (RADIOPARAMS = NONE) Users with read‐only access to tables and properties dialogues, i.e., users
are not allowed to modify radio network data and parameters.
• Database access rights and access rights to radio data in Atoll can be set
independently. For example, a user can have full access rights in the interface but not
be allowed to archive changes to the database.
• However, access rights in the interface should only be granted if the user has at least
read‐only access to the database.
• 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 the
Properties dialogue of the Microwave Radio Links folder).
• Standard: (CALCPARAMS = STD) Users with access to customised coverage predictions only, and allowed to
modify coverage conditions and display settings. These users do not have access to the microwave calculation
settings mentioned above.
• Customised only: (CALCPARAMS = NONE) Users with access to customised coverage predictions only, but not
allowed to modify coverage conditions and display settings. These users do not have access to the microwave
calculation 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.
63
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 Accounts
You 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 64).
b. Under Identification, enter a User name (in block letters) and Password, and select a Tablespace for the new user
account.
c. Under Advanced, select Use operating system authentication if you want to use OS authentication prefix with the
user 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 64).
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 the
user 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 64).
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.
Figure 6.3: Creating or Editing a User Account
6.3.3 Resetting User Database Permissions
The 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.
64
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 just
looks 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.
The duration of the database rebuilding process depends on the number of users and on
the database processing speed.
6.4 Appendices
The following appendices provide additional information on:
• "Appendix 1: Checking Data Integrity" on page 65
• "Appendix 2: Database Regionalisation" on page 66
• "Appendix 3: Calculating Path Loss Matrices" on page 66
• "Appendix 4: Path Loss Matrices From Different Sources" on page 67
6.4.1 Appendix 1: Checking Data Integrity
Atoll includes data consistency and integrity checking tools that allow you to check data consistency between the different
Atoll tables (Sites, Transmitters, etc.). It is recommended that the Atoll administrator runs data integrity checks regularly on
the 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. Integrity
problems occur when records refer records that do not exist. For example, transmitters located on sites that do not
exist in the Sites table, transmitters referring to an antenna that does not exist in the Antennas table, etc.). Records
with 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, and
neighbours 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 the
same 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 found
in the Event Viewer.
If you fix any problems in the Atoll document, you must archive the changes in the
database in order to fix the problems for all the users working with that database.
65
6.4.2 Appendix 2: Database Regionalisation
You 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. Static
regionalisation is carried out by creating project databases from the master database, i.e., multi‐level databases as
explained in "Working With a Multi‐level Databases" on page 45.
Static regionalisation requires manual synchronisation between the master database and the regional project
databases using the Atoll Management Console. In a multi‐level database environment, end‐users work with project
databases, refreshing and archiving data as they continue to work on their respective regions of the network. Data
archive and refresh between the project databases and the master database are performed by the administrator
alone.
• 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 the
master database, but rather lets the different users work with the master database directly while managing their
access privileges according to their user connection properties. In an Atoll multi‐user environment, you can create
such regionalisation without installing Oracle Spatial. You can implement this solution using Oracle Locator, which is
provided in the standard Oracle installation.
Specific documents explaining how to set up this regionalisation, using Oracle, in any Atoll master database are
available on demand from Forsk. These documents provide scripts for creating different types of users, e.g., the
administrator, advanced user, read‐only user, etc., and give examples of how to set up regions in the network and how
to 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 Matrices
You can calculate only the invalid path loss matrices or all the path loss matrices in Atoll or using a macro.
You should only calculate the shared path loss matrices when they are not being accessed
by users.
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 nonexistent
matrices 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.
66
You should also make regular backups of the master Atoll document. The above macro
could also create a backup ATL file of the master Atoll document on a regular basis. This
file can be overwritten daily, whenever path losses are calculated.
6.4.4 Appendix 4: Path Loss Matrices From Different Sources
Atoll calculates path loss matrices and creates path loss matrix storage files using the propagation models assigned to
transmitters. Atoll can also work with path loss matrices calculated by other tools. To use path loss matrices from different
sources, 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 82.
• 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.
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 calculated
by Atoll.
The shared path loss matrices architecture can contain path loss matrices from different sources. The Pathloss.dbf file
provides the means to manage several sources of path loss matrices. This file stores, among other information, the validity
status 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 B
wish to work with path loss matrices generated by a different tool for a part of the network and with path loss matrices
generated 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 is
C:\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 the
Path_Loss_Internal folder with the paths to the LOS files modified. For example, if the path loss matrices generated by the
other tool include Transmitter_1, the Pathloss.dbf file in the Path_Loss_Mixed folder will have all the same entries as
Pathloss.dbf file in the Path_Loss_Internal folder except for the path for the Transmitter_1 path loss matrices file. Figure 6.4
on page 67 explains this concept.
Figure 6.4: Path Loss Architecture for Multiple Source Path Loss Matrices
Once the Pathloss.dbf file in the Path_Loss_Mixed folder is updated with the correct paths corresponding to the different
transmitters, 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 path
loss matrices with the propagation models assigned to the transmitters. The external path loss matrix will no longer be used.
67
68
AT321_AM_E4 Chapter 7: Coordinate Systems and Units
7 Coordinate Systems and Units
7.1 Coordinate Systems
A map or a geo‐spatial database is a flat representation of data collected over a curved surface. Projection is a means of
producing all or part of a spheroid on a flat surface, which cannot be done without distortion. It is up to the cartographer to
choose the characteristic (distance, direction, scale, area, or shape) that he wants to produce accurately on a flat surface at
the expense of the other characteristics, or to make a compromise on several characteristics. The projected zones are
referenced 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 or
two standard parallels. This projection method is useful for representing countries or regions that have a predominant
east‐west expanse.
• The Universal Transverse Mercator (UTM) Method: A portion of the earth is projected on a cylinder tangent to a
meridian (which is transverse or crosswise to the equator). This projection method is useful for mapping large areas
that are oriented north‐south.
A geographic system is not a projection, but a representation of a location on the surface of the earth in geographic
coordinates (degree‐minute‐second, gradient) with the latitude and longitude with respect to a meridian (e.g., Paris for NTF
system and Greenwich for ED50 system). Locations in a geographic system can be converted into other projections.
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)
7.1.1 Definition of a Coordinate System
A geographic coordinate system is a latitude and longitude coordinate system. The latitude and longitude are related to an
ellipsoid, a geodetic datum, and a prime meridian. The geodetic datum provides the position and orientation of the ellipsoid
relative 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 the
transformation 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 geographic
coordinate 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 meridians
are defined by the longitude with respect to Greenwich.
69
Chapter 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 projection
methods 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. It
associates a geographic coordinate system and a projection. Atoll enables you to choose the projection coordinate system
matching your geographic data.
7.1.2 Types of Coordinate Systems in Atoll
Depending on the working environment, there can be either two or four coordinate systems used in Atoll. If you are working
with 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 the
projection coordinate system of your Atoll document so that it corresponds to the coordinate system of the available raster
geographic 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 coordinate
system. You cannot work with raster geographic data files with different coordinate systems in the same document.
If you import vector geographic data (e.g., traffic, measurements, etc.) with different
coordinate systems, it is possible to convert the coordinate systems of these data into
the projection coordinate system of your Atoll document.
The projection coordinate system is used to keep the coordinates of sites (radio network data) consistent with the geographic
data.
When you import a raster geographic data file, Atoll reads the geo‐referencing information from the file (or from its header
file, depending on the geographic data file format), i.e., its Northwest pixel, to determine the coordinates of each pixel. Atoll
does not use any coordinate system during the import process. However, the geo‐referencing information of geographic data
files 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 the
status bar, etc. The coordinates of each pixel of geographic data are converted to the display coordinate system from the
projection coordinate system for display. The display coordinate system is also used for sites (radio network data). You can
set 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 Atoll
document.
If you change the display coordinate system in a document which is not connected to a database, the coordinates of all the
sites are converted to the new display system.
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 systems
separately. By default, the two coordinate systems are the same.
70
Internal Coordinate Systems
The internal coordinate systems are the projection and the display coordinate systems stored in a database. The projection
and display coordinate systems set by the administrator in the central Atoll project are stored in the database when the
database is created, and cannot be modified by users. Only the administrator can modify the internal coordinate systems
manually by editing the entries in the CoordSys and the Units tables. All Atoll documents opened from a database will have
the 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 display
coordinate system for the database, and the currently chosen projection coordinate system becomes the internal projection
coordinate 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 system
is 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 save
these 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 the
sites 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 sites
are converted to the new coordinate system in the Atoll document locally but not in the database because the internal
coordinate systems cannot be changed.
Atoll uses the internal coordinates systems in order to keep the site coordinates consistent in the database which is usually
accessed by a large number of users in a multi‐user environment.
7.1.3 Coordinate Systems File Format
The Coordsystems folder located in the Atoll installation directory contains all the coordinate systems, both geographic and
cartographic, 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 coordinate
systems to it. Each catalogue is described by an ASCII text file with .cs extension. In a .cs file, each coordinate system is
described in one line. The line syntax for describing a coordinate system is:
Code = "Name of the system"; Unit Code; Datum Code; Projection Method Code, Projection
Parameters; "Comments"
Examples:
4230 = "ED50"; 101; 230; 1; "Europe - west"
32045 = "NAD27 / Vermont"; 2; 267; 6, -72.5, 42.5, 500000, 0, 0.9999643; "United

States - Vermont"
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 coordinate
system, 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 in
brackets. There can be 3 to 7 parameters defined in the following order: Dx, Dy, Dz, Rx, Ry, Rz, S. The syntax of the line
in the .cs file will be:
Code = "Name of the system"; Unit Code; {Ellipsoid Code, Dx, Dy, Dz, Rx, Ry, Rz, S};
Projection Method Code, Projection Parameters; "Comments"
• There can be up to seven projection parameters. These parameters must be ordered according to the parameter index
(see "Projection Parameter Indices" on page 74). Parameter with index 0 is the first one. Projection parameters are
delimited by commas.
• For UTM projections, you must provide positive UTM zone numbers for north UTM zones and negative numbers for
south 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.
71
Unit 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
Datum Codes
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
72
Code Datum Code Datum

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
NAD 1927 Guatemala/Honduras/Salvador
257 Makassar 903
(Panama Zone)
258 European Reference System 1989
Projection Method Codes
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
Ellipsoid Codes
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
73
Code Name Major Axis Minor Axis

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
Projection Parameter Indices
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
7.1.4 Creating a Coordinate System in Atoll
Atoll provides a large default catalogue of coordinate systems. However, it is possible to add new geographic and cartographic
coordinate 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.
74
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 comments
about its usage. Atoll assigns the code automatically.
c. Under Category, select the Type of coordinate system. Enter the longitude and latitude for a geographic
coordinate system, or the type of projection and its set of associated parameters for a cartographic coordinate
system (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 is
automatically selected. You can also describe a geodetic datum by selecting "<Customised>" in the Datum list. In
this case, you must select an Ellipsoid and enter parameters (Dx, Dy, Dz, Rx, Ry, Rz, and S) needed for the
transformation 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 Systems
dialogue before clicking New in step 4. The new coordinate system is initialised with the values of the selected coordinate
system.
7.2 Units
In the Atoll documents, you can define measurement units for reception, transmission, antenna gain, distance, height and
offset, and temperature. You can accept the default measurement units, or you can change them using the document
properties dialogue.
Transmission and Reception Power Units
Depending on the working environment, Atoll can use either one or two measurement units for the transmission/reception
power.
If you are working with stand‐alone documents, i.e., documents not connected to databases, there is only one measurement
unit 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 unit
defined in the current Atoll document. It is used for the display in the dialogues and in the tables, e.g., reception
thresholds (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 in
the database. It corresponds to the transmission/reception power unit used in the master Atoll document when the
database is created. Users working in documents connected to a database can modify the transmission/reception
power unit and save this change in their documents locally, but they cannot modify the internal power unit stored in
the 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 measurement
unit 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 current
Atoll 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. It
corresponds to the antenna gain unit used in the master Atoll document when the database is created. Users working
in documents connected to a database can modify the antenna gain unit and save this change in their documents
locally, but they cannot modify the antenna gain unit stored in the database. Only the administrator can modify it
manually 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 the
tables, and in the status bar.
Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected to
databases or not. The internal measurement unit is not stored in the database and cannot be changed.
75
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 the
dialogues, 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 connected
to 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 dialogues
and in the tables.
Degree Celsius is used as the internal measurement unit for the temperature in all Atoll documents whether they are
connected to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
7.3 BSIC Format
Depending 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 types 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 the
Transmitters 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 Atoll
project is stored in the database when the database is created, and cannot be modified by users. Only the administrator can
modify the internal format manually by editing the corresponding entry in the Units tables. All Atoll documents opened from
a 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 change
in their documents, but they cannot modify the format stored in the database.
Atoll expects the BSIC format in the database to be the octal format. If that is not the case,
do the following:
• In the Atoll database, update the setting of UNITS.BSIC_FORMAT to 1.
• In your ATL project (and in any ATL project created from the previous database
configuration), go to the Parameters tab, select GSM Network Settings > BSICs >
Format > Octal and save the ATL file.
76
AT321_AM_E4 Chapter 8: Atoll File Formats
8 Atoll File Formats
Radio 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 or
more 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 can
correspond 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 repeater
receives 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, amplify
the received signal. Reflectors are examples of passive repeaters.
This section covers the following file types that are used by Atoll:
• "Geographic Data Files" on page 77
• "Path Loss Matrix File Format" on page 82
• "Path Loss Tuning File Format" on page 85
• "Interference Matrix File Formats" on page 86
• ""Per Transmitter" Prediction File Format" on page 92
8.1 Geographic Data Files
Atoll supports multiple types of geographic data, including 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 data formats.
The following table summarizes the supported formats and filters:
Geographic Data Types
Import
File Format Clutter Clutter Raster Vector Web Map Georeferencing
Export DTM Traffic Maps Population
Classes Heights Images Data Services
User profile raster (8‐bit)
8, 16, or 32‐ 8, 16, or 32‐ 1, 4, 8 or 24‐ 8, 16, or 32‐
BIL Both 8‐bit User density raster (16, 32‐ HDR files
bit bit bit bit
bit)
User profile raster (8‐bit),
1, 4, 8 or 24‐ 8, 16, or 32‐
TIFF Both 8 or 16‐bit 8‐bit 8 or 16‐bit User density raster (16, 32‐ Yes TFW files
bit bit
bit)
User profile density
Sector traffic maps 1, 4, 8 or 24‐
Planet Both 16‐bit 16‐bit 16‐bit Yes index files
User profile raster (16‐bit) bit
User density raster (16‐bit)
BMP Both 8‐bit 8‐bit 8‐bit User density raster (16, 32‐ 1 to 24‐bit 8 or 32‐bit Yes BPW or BMW files
bit)
DXF Import Yes Yes
Sector traffic maps
SHP Both Vector Yes Yes
Sector traffic maps
MapInfo User profile density
Both Vector Yes Yes
(MIF, TAB) Sector traffic maps
Erdas Imagine 8, 16, and 8, 16, and 1, 4, 8 or 24‐ 8, 16, or 32‐
Import 8‐bit User density raster (16, 32‐ Yes
(IMG) 32‐bit 32‐bit bit bit
bit)
77
Chapter 8: Atoll File Formats © Forsk 2014
Geographic Data Types
Import
File Format Clutter Clutter Raster Vector Web Map Georeferencing
Export DTM Traffic Maps Population
Classes Heights Images Data Services
ArcView Grid
Export Text Text Text Text Text Text Embedded data
(TXT)
Atoll Geo Data User profile densities
Both Vector Yes Embedded data
(AGD) Sector traffic maps
Vertical Mapper Clutter Clutter User profile raster Raster
Both DTM Vector Embedded data
(GRD, GRC) Classes Heights User density raster Images
ECW Import 24‐bit ERS files
PNG Both All All PGW files
JPEG Both All All JGW files
You can import custom geographic data types other than those listed above into Atoll. Custom maps can be taken into account
in 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
• 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.
Specific header files are used to describe how data is organised within any of these geographic data file formats. This section
describes the following header file formats:
• "HDR Header File for BIL Files" on page 78
• "TFW Header File for TIFF Files" on page 80
• "BPW/BMW Header Files for BMP Files" on page 80
• "PGW Header File for PNG Files" on page 81
• "JGW Header File for JPG Files" on page 81
• "Generic Raster Header File" on page 81
8.1.1 HDR Header File for BIL Files
The 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:
keyword value
where ‘keyword’ corresponds to an attribute type, and ‘value’ defines the attribute value.
Keywords required by Atoll are described below. Other keywords are ignored.
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 for
path 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).
78
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 of
the image data. Default value is 0.
Four additional keywords can optionally be managed.
pixeltype Type of data read (in addition to the length)
This can be:
UNSIGNDINT Undefined 8, 16, 24 or 32 bits

SIGNEDINT Integer 16 or 32 bits
FLOAT Real 32 or 64 bits
In some cases, this keyword can be replaced by datatype defined as follows:
datatype Type of data read (in addition to the length)
This can be:
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
The other optional keywords are: valueoffset, valuescale, and nodatavalue.
By default, integer data types are chosen with respect to the pixel length (nbits).
valueoffset Real value to be added to the read value (Vread)
valuescale Scaling factor to be applied to the read value
So, we have V = Vread  valuescale + valueoffset
nodatavalue Value corresponding to “NO DATA”
DTM Sample
Here, the data is 20 m.
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
Clutter Classes Sample
nrows 1500
ncols 1500
79
nbands 1
nbits 8
byteorder M
layout bil
skipbytes 0
ulxmap 975000
ulymap 1891000
xdim 20.00
ydim 20.00
8.1.2 TFW Header File for TIFF Files
TFW files contain the spatial reference data of associated TIFF files. The TFW file structure is simple; it is an ASCII text file that
contains six lines. You can open a TFW file using any ASCII text editor. The TFW file structure is as follows:
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
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
8.1.3 BPW/BMW Header Files for BMP Files
The header file is a text file that describes how organised in the BMP file. The header file is made of rows, each row having
the following description:
Line Description
2 amount of translation
Atoll supports BPW and BMW header file extensions for Import, but exports headers with BPW file extensions.
100.00
0.00
0.00
-100.00
80
60000.00
2679900.00
8.1.4 PGW Header File for PNG Files
A PNG world file (PGW file) is a plain text file used by geographic information systems (GIS) to provide georeferencing
information for raster map images in PNG format. The world file parameters are:
Line Description
8.1.5 JGW Header File for JPG Files
A JPEG world file (JGW file) is a plain text file used by geographic information systems (GIS) to provide georeferencing
information for raster map images in JPEG format. The world file parameters are:
Line Description
8.1.6 Generic Raster Header File
WLD is a header format for Atoll that can be used for any raster data file for georeferencing. At the time of import of any raster
data file, Atoll can use the corresponding WLD file to read the georeferencing information related to the raster data file. The
WLD file contains the spatial reference data of any associated raster data file. The WLD file structure is simple; it is an ASCII
text 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, each
row having the following description:
Line Description
Clutter Classes File Sample
100.00
0.00
0.00
-100.00
60000.00
2679900.00
81
8.2 Path Loss Matrix File Format
When 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) file
per transmitter that has an extended path loss matrix.
The formats of the pathloss.dbf and LOS files are described here.
8.2.1 Pathloss.dbf File Format
The pathloss.dbf file has a standard DBF (dBase III) format. The file can be opened in Microsoft Access, but it should not be
modified 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
DBF Structure
Byte Description Remarks

0...n DBF header (see next part for size, byte 8)
1st record of fixed length (see next parts); 2nd record (see next part for size, byte10) …; last
n+1 If .dbf is not empty
record
last optional: 0x1a (eof byte)
DBF Header
The DBF header size is variable and depends on the field count.
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
82

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
Field descriptor array in the DBF header (32 bytes for each field):
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
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
Field type and size in the DBF header, field descriptor (1 byte):
Size Type Description/Storage Applies to
ASCII (OEM code page chars)
C 1...n Char all
rest= space, not \0 term.
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
ASCII digits (‐.0123456789)
F 1...n Numeric variable pos. of float.point FS, D4, D5, Fp
n = 1...20
ASCII digits (‐.0123456789)
N 1...n Numeric all
fix posit/no float.point
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)
10 digits repres. the start block posit. in .dbt file, or 10
M 10 Memo all
spaces if no entry in memo
83
Size Type Description/Storage Applies to

Variable, bin/asc data in .dbv
4bytes bin= start pos in memo
4bytes bin= block size
V 10 Variable FS
1byte = subtype
1byte = reserved (0x1a)
10 spaces if no entry in .dbv
binary data in .ftp
P 10 Picture Fp
structure like M
binary data in .dbt
B 10 Binary D5
structure like M
OLE objects
G 10 General D5, Fp
structure like M
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
Each DBF record (fixed length):
Byte Size Description Applies to

0 1 deleted flag "*" or not deleted " " All
x‐times contents of fields, fixed length, unterminated.
1…n 1… All
For n, see (2) byte 10…11
8.2.2 Pathloss.dbf File Contents
The DBF file provides information that is needed to check validity of each path loss matrix.

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
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
MODEL_SIG Text 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
Logical number referring to antenna pattern. Antennas with the same pattern will have
ANTENNA_SI Float
the same number.
Maximum path loss stated in 1/16 dB. This information is used, when no calculation
MAX_LOS Float
radius is set, to check the matrix validity.
84

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
Locking status
LOCKED Boolean 0: path loss matrix is not locked
1: path loss matrix is locked.
Atoll indicates if losses due to the antenna pattern are taken into account in the path
loss matrix.
INC_ANT Boolean
0: antenna losses not taken into account
1: antenna losses included
a. In order to benefit from the calculation sharing feature, users must retrieve the propagation models from the same
central database. This can be done using the Open from database command for a new document or the Refresh
command for an existing one. Otherwise, Atoll generates different model_ID (even if same parameters are applied on
the 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.
8.2.3 LOS File Format
The LOS (path loss results) files are binary files with a standard row‐column structure. Data are stored starting from the
southwest 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.
8.3 Path Loss Tuning File Format
Atoll can tune path losses calculated by propagation models using CW measurements or drive test Data. Path losses are tuned
by merging measurement data with propagation results on pixels corresponding to the measurement points and the pixels in
the 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 and
one 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.
8.3.1 Pathloss.dbf File Format
See "Pathloss.dbf File Format" on page 82.
8.3.2 Pathloss.dbf File Contents
The DBF file provides information about the measured transmitters involved in the tuning.

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
85
8.3.3 PTS File Format
The 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
• 4 bytes: Y
• 4 bytes: measurement value
• 4 bytes: incidence angle.
8.4 Interference Matrix File Formats
Interference matrices are used by GSM, LTE, and WiMAX AFPs (automatic frequency planning tools). Interference matrices
can 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 and
100%). When interference matrix files are imported, Atoll does not check their validity and imports interference probability
values for loaded transmitters only.
In the following format descriptions and samples, lines starting with the "#" are considered as comments.
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. For
subcells other than the BCCH, if the power offset of a subcell is X dB, then its
interference histogram will be shifted by X dB with respect to the BCCH interference
histogram.
• 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 number
depends on the probability variation between the fixed values). The C/I values have
0.5 dB accuracy and probability values are calculated and stored with an accuracy of
0.002 for probabilities between 1 and 0.05, and with an accuracy of 0.0001 for
probabilities lower than 0.05.
8.4.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 file
to import. Atoll looks for the associated DCT file in the same directory and uses it to decode transmitter identifiers. If no DCT
file is available, Atoll assumes that the transmitter identifiers are the transmitter names, and the columns 1 and 2 of the CLC
file must contain the names of the interfered and interfering transmitters instead of their identification numbers.
86
8.4.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 the
following lines:
# Calculation Results Data File.
# Version 1.1, Tab separated format. Commented lines start with #.
The second part details interference histogram of each interfered subcell‐interfering subcell pair. The lines after the header
are considered as comments if they start with "#". If not, they must have the following format:
<Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>
The 5 tab‐separated columns are defined in the table below:
Column Name Description

Identification number of the interfered transmitter. If the column is empty,
Column1 Interfered transmitter
its value is identical to the one of the line above.
Identification number of the interferer transmitter. If the column is null, its
Column2 Interfering transmitter
value is identical to the one of the line above.
Interfered subcell. If the column is null, its value is identical to the one of the
Column3 Interfered TRX type line above. 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.
Probability to have C/I the value specified in column 4 (C/I threshold). This
Column5 Probability C/I > Threshold
field must not be empty.
The columns 1, 2, and 3 must be defined only in the first line of each histogram.
Sample

# 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
87
17 0.752
22 0.316
25 0.292
1 2 BCCH,TCHa 8 1
9 0.944
10 .904
13 0.872
14 0.84
17 0.772
a. If the TCH and BCCH histograms are the same, they are not repeated. A single record indicates that the histograms
belong to TCH and BCCH both.
8.4.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 contain
the following lines:
# Calculation Results Dictionary File.

The second part provides information about transmitters taken into account in AFP. The lines after the header are considered
as comments if they start with "#". If not, they must have the following format:
<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
The last four columns describe the interference matrix scope. One transmitter per line is described separated with a tab
character.
Sample
# 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)
88
##---------------------------#
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
8.4.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 with
associated probabilities.
The .im0 file consists of two parts. The first part is a header used for format identification. It must start with and contain the
following lines:
The second part details interference histogram of each interfered subcell‐interferer subcell pair. The lines after the header
<Column1><tab><Column2><tab><Column3><tab><Column4><newline>
Column1 Interfered transmitter Name of the interfered transmitter.
Column2 Interfering transmitter Name of the interferer transmitter.
Interfered subcell. In order to save storage, all subcells with no power offset
Column3 Interfered TRX type
are not duplicated (e.g. BCCH, TCH).
C/I value and the probability associated to this value separated by a space
Column4 C/I probability
character. This entry cannot be null.
Sample

# Fields are:
#------------------------------------------------------------------------
#Transmitter Interferer TRX type {C/I Probability} values
#------------------------------------------------------------------------
#
#
# Margin is 5.
##---------------------------------------------------------------------#
89
#
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
8.4.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. The
histogram is a list of C/I values with associated probabilities.
The .im1 file consists of two parts. The first part is a header used for format identification. It must start with and contain the
following lines:

The second part details interference histogram of each interfered subcell‐interferer subcell pair. The lines after the header
<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.
Interfered subcell. In order to save storage, all subcells with no power offset
Column3 Interfered TRX type
are not duplicated (e.g. BCCH, TCH).
Column4 C/I threshold C/I value. This column cannot be null.
Probability to have C/I the value specified in column 4 (C/I threshold). This
Column5 Probability C/I > Threshold
field must not be empty.
Sample

# Fields are:
#------------------------------------------------------------------------
#Transmitter Interferer TRX type C/I Probability
#------------------------------------------------------------------------
#
#
90
# 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
...
8.4.4 IM2 Format (Co‐ and Adjacent‐channel Probabilities)
IM2 files contain co‐channel and adjacent‐channel interference probabilities for each interfered transmitter – interfering
transmitter pair. In GSM, there is only one set of values for all the subcells of the interfered transmitter. Each line must have
the following format:
<Column1><SEP><Column2><SEP><Column3><SEP><Column4><newline>
Where the separator (<SEP>) can either be a tab or a semicolon.
The four columns are defined in the table below:

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
Sample

# Fields are:
#------------------------------------------------------------------------
#Transmitter Interferer Co-channel Adjacent channel
#------------------------------------------------------------------------
#
#
# Margin is 5.
91

##---------------------------------------------------------------------#
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
The columns in the sample above are separated with a tab. These columns can also be separated with a semilcolon:
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
8.5 "Per Transmitter" Prediction File Format
When 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.
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 BIL
file (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 for
the 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 by
the cell’s name).
The format and the content of the DBF file is described here.
In both cases, an XML file describing the prediction is also created in the corresponding
’<doc_name>\{<GUID>}’ folder.
8.5.1 <per_transmitter_prediction>.dbf File Format
The format of ‘<per_transmitter_prediction>.dbf’ files is identical to the format described in "Pathloss.dbf File Format" on
page 82.
8.5.2 <per_transmitter_prediction>.dbf File Contents
The ‘<per_transmitter_prediction>.dbf’ files generated in specific ’{<GUID>}’ folders provide information that is needed to
check the validity of each "per transmitter" prediction> calculated by value intervals.

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
92

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
93
94
AT321_AM_E4 Chapter 9: Administration and Usage Recommendations
9 Administration and Usage Recommendations
This chapter lists various technical recommendations for optimising your work with Atoll.
9.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 the
users. 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 is
recommended 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 share
name of disk C.
Example:
Absolute Path C:\Program Files\Forsk\Geo Data\...
Relative Path \Program Files\Forsk\Geo Data\...
UNC Path \\Computer\C\Program Files\Forsk\Geo Data\...
If you define paths to geographic data files using the UNC, Atoll will be able to keep track of the linked files even if the
Atoll 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 to
optimise memory consumption, which enables it to perform efficiently with regional tiles (1 tile/file per region). In
Atoll, 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, BIL
files. Using compressed geographic data files, for example, compressed TIF or Erdas Imagine, can cause performance
reduction due to decompression of these files in real time. If you are using compressed geographic data files, it is
strongly recommended to:
• Either, hide the status bar that displays geographic data information in real time. You can hide the status bar from
the View menu.
• Or, disable the display of some of the information contained in the status bar, such as altitude, clutter class, and
clutter height using an option in the Atoll.ini file, see "Hiding Information Displayed in the Status Bar" on page 149.
• The following table shows the recommended file formats for different geographic data:
Geographic data type Recommended file format
Scanned maps ECW
Vectors SHP
95
Chapter 9: Administration and Usage Recommendations © Forsk 2014
9.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 are
accessed 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 administrators
and 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 are
invalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matrices
and uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whose
corresponding shared path loss matrices are valid. This can be useful for disk space management. For more
information, see "Synchronising Private and Shared Path Loss Matrices" on page 144.
Link or Embed
• Only embed path loss matrices in ATL files if you wish to make a portable document. In all other cases, it is
recommended 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 will
result in less fragmentation. Externalising path loss matrices does not reduce the performance of display and
calculations in Atoll.
• It is recommended to set the paths to the private and shared path loss matrices folders using the Universal Naming
Convention (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 share
name of disk C.
Example:
Absolute Path C:\Program Files\Forsk\PathLosses\...
Relative Path \Program Files\Forsk\PathLosses\...
UNC Path \\Computer\C\Program Files\Forsk\PathLosses\...
If you define paths to the private and shared path loss matrices folders using the UNC, Atoll will be able to keep track
of 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 of
each technology are calculated simultaneously using the same number of threads. For example, if 4 threads are used
to calculate path loss matrices, and there are 3 technologies (GSM, UMTS, and LTE), a total of 12 threads will be used
to 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‐RAT
documents, 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 calculation
using the RunPathloss function.
• Resource saturation during the calculation of path loss matrices for multi‐RAT
documents 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 does
not occur.
96
• Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices are
invalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matrices
and uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whose
corresponding shared path loss matrices are valid. This can be useful for disk space management. For more
information, see "Synchronising Private and Shared Path Loss Matrices" on page 144.
9.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 an
intermediate major version, you should upgrade your document twice in order to make it compatible with the new
version.
9.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 intermediate
major 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, you
must not create tables and fields with names longer than 20 characters. This is because Atoll adds some characters to
the table and field names for certain operations: creating associated triggers, creating project databases, etc. Limiting
the 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 have
priority over the internal predefined default values. If you define floating point default values, make sure that all the
users 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 update
your 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 Atoll
tables. Some requirements of the different user groups can be satisfied if a few general‐purpose user‐defined fields
are 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 and
Transmitters tables, users will be able to use these for sorting, filtering, grouping, or other purposes. This approach
can 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 and
transmitters’ names.
• To improve performance, unless absolutely necessary, do not add user‐defined fields of Text type. Rather, use
numeric field types, which allow sorting and other functions. If you must add Text fields, allocate them the appropriate
size that would suffice. For example, a 255‐character long Text type field would, for the most part, occupy disk space
for no purpose.
• To improve performance, you should avoid adding custom fields to the neighbour management tables.
97
9.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 a
multi‐user Citrix environment. The principal difference observed might be the inability to run multiple Atoll sessions on the
server without getting error messages, general application failures, or server crashes. Such problems can occur when the
number 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 can
exceed the Microsoft Windows’ (32‐bit editions) limit of 2 GB per process. This is especially the case with large Atoll
documents 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 avoid
memory and CPU overloading as follows:
• To reduce the impact of a large number of simultaneous path loss calculations, a Distributed Calculation Server should
be set up. Using the Distributed Calculation Server, path loss calculations can be performed outside Atoll. Using the
Distribution 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. A
server with four processors (eight threads with hyper‐threading) can accommodate four simultaneous path loss calculations
and use the other four threads for Atoll sessions. Atoll’s interface will also be more efficient and the overall processing time
for various tasks will be improved.
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 file
should be set made read‐only for end‐users.
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 Microsoft
Windows 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 global
memory when supporting more than 10 Atoll sessions simultaneously. This is different from the 2 GB per process
limit. 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 GB
to 3 GB as explained in "Process Memory" on page 99.
9.6 Atoll Administration Files
There is no specific order in which configuration and initialisation files should be created or installed on Atoll workstations
and servers. It is sufficient to have these files created and placed in the right locations before running Atoll to have the
predefined 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 to
their respective locations on the new server to have the exact configuration and set‐up as the first. If you do not copy these
98
files, or create them, you will not have the same configuration of the new server, but apart from that you will be able to work
with 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 your
Atoll documents.
• Separate configuration files created for your 2G and 3G projects, which would store their respective coverage
prediction 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, for
example, groups of users working on different regions, groups of users working on different technologies, groups
of 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 XML
studies file, make sure that this study template is aimed at serving a number of users. This means, avoid creating study
templates unless these will be needed for a long time by a number of users. You can use the configuration files to store
your created coverage prediction studies locally. And, you can also use the study duplicate feature to create copies of
existing coverage prediction studies.
9.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 the
following URL: http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx (/3GB section in “Memory
Support and Windows Operating Systems”).
The following link provides information on how you can setup your Windows Server 2003 systems to activate the 3 GB switch
at 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.
9.8 Printing
You should place different layers of geographic and radio data in a definite order when printing a project or a section of the
project. 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 recommended
to place vector layers on the top of coverage prediction plots. You can do this by transferring these vector layers to
the Data tab using the context menu. For performance reasons, it is advised to place vector layers on top of raster
layers before printing a project. Sites and Transmitters must be on the very top, above all other layers. You should
place 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.)
99
9.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 this
option and setting the Cell edge coverage probability to 50%.
• To improve memory consumption and optimise the calculation times, you should set the display resolutions of
coverage predictions according to the precision required. The following table lists the levels of precision that are
usually sufficient:
Size of the coverage prediction Display resolution
City Center 5 m
City 20 m
County 50 m
State 100 m
Country According to the size
9.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 displays
measurement points as small squares, it can have a significant impact on performance depending on the number of
measurement points in the Atoll document.
• When performing a CW measurements drive test campaign, please follow the recommended procedure described in
the Measurements and Model Calibration Guide.
9.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 would
in 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 the
file. You will have to replace the name of the pattern inside the file by the name of the pattern file itself, in order to
import these antennas correctly.
• A Planet Index file contains the path to and the name of each antenna file available. Creating such an Index file when
there are hundreds of antenna patterns available can be a difficult task. You can easily create the index file from the
Microsoft 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 antenna
pattern 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 antenna
pattern file names, with one name per line. The file will also contain a line with its own name, so, before importing
this 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 include
electrical tilt. Users should verify whether the antenna patterns of the antennas in their projects, do not already
include the effect of an electrical tilt.
9.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.
100
9.13 Atoll API
Correct functioning of Atoll when using Atoll through the API is guaranteed during interactive user sessions only. Atoll is an
application 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 is
not guaranteed. Unexpected errors can occur. Particularly, creating objects through CreateObject or CoCreateInstance might
fail.
Therefore, the correct functioning of Atoll requires an open user session on the computer.
9.14 Performance and Memory
Memory Refresh
• You can avoid memory fragmentation while working with Atoll documents by saving the Atoll document from time to
time, closing and restarting Atoll, and reopening the document.
This advice is applicable to any application running under Microsoft Windows because many common DLL files are
accessed 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. The
exact 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 working
on your existing ATL file for a long time, it might become unnecessarily large and might contain some useless remains
from your earlier operations, e.g., traces of records that no longer exist in the database, etc. You can completely
refresh 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, coverage
prediction parameters, neighbour allocation parameters, etc. For more information, refer to "Configuration Files"
on page 105.
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 less
space 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 separate
Atoll session rather than to open them all in the same Atoll window. Each Atoll session on the same computer has its
own memory space allocated by the operating system. Each computer consumes a single licence token independent
of 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 GB
to 3 GB as explained in "Process Memory" on page 99.
File Size
• Coverage predictions calculated over large areas require more memory. If you are working on an Atoll document
covering a large area, with coverage predictions calculated over the entire network, this document will require more
memory for loading all the coverage predictions. You can reduce memory consumption by making copies of your Atoll
document, and keeping a few coverage predictions in each copy. These ATL files will be faster to load and work with
compared 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 does
not become unnecessarily large.
Path Loss Calculation
• Before starting path loss calculation, verify that the calculation radii and resolutions assigned to the different types of
transmitters are consistent. For example, calculating path loss matrices of picocells over large calculation radii would
only waste memory and disk space.
101
• For calculating path loss matrices over large areas, you should use the dual resolution feature in Atoll. Define short
calculation radii and fine resolutions for the main path loss matrices, and large calculation radii and low resolutions
for extended path loss matrices. This approach decreases the calculation time significantly compared to calculating
just one matrix per transmitter using a fine resolution. The main path loss matrices should be calculated using the
same resolution as the resolution of the geographic data available. The extended path loss matrices can be calculated
using 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 the
data necessary for your working area. If you load a large network, Atoll will load a lot of data that might not be
necessary 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 the
AFP while working on large GSM networks. Large network projects are more susceptible to these problems. If the network is
large but homogeneous, these problems might only appear if the number of transmitters is over 15,000 or so. But, if there are
large city centres involved, with each pixel having many overlapping path loss matrices, then this size limit might decrease to
around 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 smaller
networks. This is because the process memory space (memory space allocated to Atoll by the operating system) becomes
fragmented.
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 not
be necessary all of the time. For example, in a typical large GSM network, you might have around 10,000 transmitter
records, 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 Matrices
folder in external files. Atoll loads interference matrices from the external files to the memory only when needed. You
will 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 correctly
associate calculation radii and resolutions to different types of cells. If you calculate path loss matrices for all types of
cells 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 be
ignored. The default value for this threshold (‐130 dBm), defined in the Predictions tab of the Predictions folder’s
Properties dialogue, means that the computations will take into account all the interferers. However, if you set it too
high, you might lose important interference information. The proper value for this threshold depends on the
Reception Thresholds and the C/I Thresholds defined in the Subcells table. The optimum value would be
Min AllSubcells  RT i – CIT i – M  . Which means the minimum value of the factor RT i – CIT i – M 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 is
important to have at least a 3‐dB margin for the interference energy aggregation in C/I studies. We recommend a
safety 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 certain
TRX 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 safety
margin in the AFP module’s Cost tab. The 12 dB and 9 dB default values already include safety margins. If you
increment 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 have
interferers and very few of them (not more than 20%) should have more than 70 interferers. If there are too many or
too 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 piecewise
manner.
This means that you can generate nation‐wide interference matrices with low resolutions based on the percentage of
interfered area (to improve computation time), with a cell edge coverage probability of 50% (which means no access
to clutter for reading standard deviation values), and an interference threshold of ‐112 dBm. This will provide rough
global 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 with
higher resolutions and reliabilities. Make sure that the computation zone in your project completely encompasses the
filtering zones that you define.
• If the memory‐critical task is the AFP session: Try to make the document lighter, e.g., remove coverage prediction
studies, exit and restart Atoll, and try to generate interference matrices with fewer entries.
102
• If the memory‐critical task is the traffic capture: You can use traffic load field of the Subcells table to provide traffic
loads 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 the
Average Simulation and Statistics". With this option Atoll uses much less memory because it only keeps limited
information in memory during the simulation process. Simulation results are detailed enough to be used in generating
coverage 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 documents
contain 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 consumes
more memory.
• Avoid loading neighbours and custom fields which are not required. This can be performed by creating views in the
database. For more information, see "Appendix 2: Setting Up Databases for Co‐planning" on page 56.
103
104
AT321_AM_E4 Chapter 10: Configuration Files
10 Configuration Files
Configuration files can be used to store parameter and display settings. These files are optional, not required for working with
Atoll, 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 user
configuration file containing the geographic data settings and other parameter settings can be saved with a CFG
extension.
User configuration files must be created using Atoll to ensure correct syntax and structure. It is possible to edit the
contents of these files in an XML editor and make changes if required (for example, to update the paths to geographic
data 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
• Projection and display coordinate systems are stored in the database, not in user
configuration files.
• Simulation settings are not stored in user configuration files.
For more information on the contents of user configuration files, see "Contents of User Configuration Files" on
page 106.
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" on
page 22 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 user
configuration 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 Configuration
Files" on page 129.
• Custom predictions file (UTF‐8 encoded XML files)
This file (one for all customised predictions) contains the list and parameter settings of customised coverage
predictions. 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 edit
the contents of this file in an XML editor and make changes if required. For more information on working with
customised predictions in Atoll, see the User Manual.
105
Chapter 10: Configuration Files © Forsk 2014
For more information on the contents of the custom predictions file, see "Content of the Custom Predictions File" on
page 133.
• 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 display
type (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>}".
10.1 Contents of User Configuration Files
The descriptions and examples provided below for each parameter set can help understand the format and function of the
user configuration files. The following details are available:
• "Geographic Data Set" on page 106
• "Map Centre and Zoom Level" on page 110
• "Zones" on page 109
• "Folder Configuration" on page 110
• "Coverage Predictions" on page 117
• "Automatic Neighbour Allocation Parameters" on page 119
• "Automatic Frequency Planning Parameters" on page 121
• "Automatic Scrambling Code Allocation Parameters" on page 122
• "Automatic PN Offset Allocation Parameters" on page 124
• "Microwave Radio Links Parameters" on page 126
• "Macros" on page 129.
10.1.1 Geographic Data Set
The 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> (same
as <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>, 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: <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:
• Displate type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (same
as <FieldSelector>) and <FieldTitle>, transparency level <Opacity>, visibility flag <visible>, and visibility range
between <minZoom> and <maxZoom>
• <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
106
• 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:
as <FieldSelector>) and <FieldTitle>, transparency level <opacity>, visibility flag <visible>, and visibility range
between <minZoom> and <maxZoom>
• <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>
107
</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"/>
108
<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>
10.1.2 Zones
The user configuration files store the coordinates of the vertices of the filtering, focus, computation, printing, and geographic
export 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.
109

<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>
10.1.3 Map Centre and Zoom Level
The following parameters are saved:
• <MapPosition>: X and Y coordinates of the centre of the map window and the zoom level.
Sample

<Atoll>
<MapPosition CenterX="609433" CenterY="5632019" Scale="250000"/>
</Atoll>
10.1.4 Folder Configuration
The following parameters are saved for the following folders:
• Sites folder:
• <Display>:
as <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>, background
• <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>, <Legend>, <MainColor>, <SecondaryColor>, <Symbol>,
and <SymbolSize>
• <DataTips>: List of <items> displayed in tip texts
• <Labels>: List of <items> displayed in labels
• <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
• Antennas folder:
110
• Transmitters, Multi‐Hops, and Point to Multipoint folders:
• <Display>:
• Displate type <Type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (same
as <FieldSelector>) <FieldTitle> and <FieldDBName>, visibility flag <Visible>, and visibility range between
• <LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour <Color>, label
• <Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>, <Symbol>,
and <SymbolSize>
• <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:
• <SecondNeighbourWeight>: Weight of the second order neighbour 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:
• <SecondNeighbourWeight>: Weight of the second order neighbour 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:
• <Display>: Contains visibility flag <visible>, and visibility range between <minZoom> and <maxZoom>
• <DefaultConfiguration>: The default configuration for the folder
• <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>, label
• <SiteDisplay> properties, such as:
• <Symbol>: Symbol used for microwave links
• <ShowText>: Caption for microwave links shown or not
• <RepeaterDisplay> properties, such as:
• CW Measurements folder:
• <Distance>: The minimum <Min> and maximum <Max> distance for measurement filtering
111
• <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
• <Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and
<SymbolSize>
• Drive Test Data folder:
• <Techno>: Name of the technology (if exported from a 3GPP Multi‐RAT document.
• <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
• <Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and
<SymbolSize>
• Propagation Models and Smart Antenna Models folders:
Sample

<Atoll>
<FoldersConfigurations>
<Sites>
<Name>Sites</Name>
<Display>
<Type>ByValues</Type>
<FieldDesc>
<FieldTitle>Vendor</FieldTitle>
112
</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>
113
<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>
114

<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>
115
<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>
116
<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>
10.1.5 Coverage Predictions
The list of coverage predictions available in the Predictions folder and the following parameters are saved:
• General tab:
• <Techno>: Name of the technology
• <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
117
• ...
• Display tab:
• 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>
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>
118
</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>
10.1.6 Automatic Neighbour Allocation Parameters
The following parameters are saved for intra‐technology (intra‐carrier and inter‐carrier) and inter‐technology automatic
neighbour 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. This
tag contains the name of the technology to which the parameters belong.
119
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>
120
<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>
10.1.7 Automatic Frequency Planning Parameters
The 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
121
Sample

<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>
10.1.8 Automatic Scrambling Code Allocation Parameters
The 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)
122
• <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
• <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>
123
<UseCloseNghbs>1</UseCloseNghbs>
<CloseDistance>80000.</CloseDistance>
<CloseImportance>3000.</CloseImportance>
<MaxCloseCost>100</MaxCloseCost>
</SCP_options>
</Atoll>
10.1.9 Automatic PN Offset Allocation Parameters
The 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
Sample

<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>
124
<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>
10.1.10 Automatic OFDM Resource Allocation Parameters
The 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

<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>
125
<RangeType>2</RangeType>
<ExcludedPis></ExcludedPis>
</OFDM_AFP_options>
</Atoll>
10.1.11 Microwave Radio Links Parameters
The 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

<Atoll>
<Microwave>
<QualityModel>6</QualityModel>
<QualityObjective0>3</QualityObjective0>
126
<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>
127
<ClutterDryCategory15>E</ClutterDryCategory15>
<ClutterDryCategory26>A</ClutterDryCategory26>
128
</Microwave>
</Atoll>
10.1.12 Macros
The 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

<Atoll>
<Macros>
<File>
<Path>C:\TestsAddin\testEvents.vbs</Path>
<Language>VBScript</Language>
<Timeout>3600</Timeout>
</File>
</Macros>
</Atoll>
10.2 Contents of Additional Configuration Files
Complete descriptions of the different additional configuration files are provided below.
10.2.1 Print Setup Configuration
The following parameters are saved for print setup:
• Page tab <Page>:
129
• 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 <Dimensions
width="" 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 <Dimensions
width="" 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>
130
<Footer>
<text></text>
</Footer>
</PrintConfiguration>
10.2.2 Table Import/Export Configuration
The 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

<TITRE>1</TITRE>
<FLD_SEPARATOR><tab></FLD_SEPARATOR>
<DEC_SEPARATOR>.</DEC_SEPARATOR>
<FIELDS>
Site
Transmitter
...
</FIELDS>
<CHOOSEN_FIELDS>
Site
Transmitter
...
</CHOOSEN_FIELDS>
10.2.3 Coverage Prediction Report Configuration
The 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

<ReportConfiguration>
<SelectedFields>
<Field>
<Title>Surface (km²)</Title>
</Field>
<Field>
<Title>% of Covered Area</Title>
</Field>
...
</SelectedFields>
</ReportConfiguration>
131
10.2.4 CW Measurement Import Configuration
More 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:
Type Index
Text 0
Integer 1
Real 2
Date 3
<Ignore> 4
Sample
[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
...
10.2.5 Drive Test Data Import Configuration
More 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)
132
• 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:
Type Index
Text 0
Integer 1
Long Integer 2
Single 3
Double 4
Date 5
<Ignore> 6
Sample
[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
...
10.3 Content of the Custom Predictions File
The content of the custom predictions file (by default, studies.XML in the installation 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 117.
133
10.4 Content of the "Value Intervals" Predictions Files
The content of the XML files for coverage predictions calculated by value intervals (by default, prediction_name>.XML in the
C:\<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 117.
134
AT321_AM_E4 Chapter 11: Initialisation Files
11 Initialisation Files
Initialisation files can be used to store operational and working environment settings. These files are optional, not required
for 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 135.
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 22 for
more information), or
b. Located in the Atoll installation folder. This file will be ignored if an initialisation file is loaded through the
command line parameter.
• You can open the Atoll.ini file in the Atoll installation folder for editing by pressing
CTRL+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 section
twice, only the first occurrence of the section will be read and loaded by Atoll.
• ACP initialisation file (ACP.ini)
This file contains calculation settings and other options for the Atoll ACP module. For more information on these
options, see "ACP Initialisation File" on page 185.
11.1 Atoll Initialisation File
The following main groups of options are available:
• "General Options" on page 135
• "GUI Options" on page 148
• "Distributed Calculation Server Options" on page 152
• "Licence Management Options" on page 153
• "Database Options" on page 154
• "Common Calculation Options" on page 157
• "GSM GPRS EDGE Options" on page 164
• "UMTS HSPA, CDMA2000, and TD‐SCDMA Options" on page 170
• "LTE, WiMAX, and Wi‐Fi Options" on page 175
• "3GPP Multi‐RAT Options" on page 181
• "Microwave Radio Links Options" on page 181
• "Measurement Options" on page 183
• "Specifying the Location of the ACP.ini File" on page 185
The Atoll initialisation file is a powerful tool. You should not modify any option until and
unless you are absolutely sure of what you are doing.
11.1.1 General Options
11.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:
[Site]
Prefix = <new_prefix>
Each new site will then be named “newprefixN” instead of “SiteN”, where N is the site number or index.
135
Chapter 11: Initialisation Files © Forsk 2014
For transmitters, you can define a prefix by adding these lines:
[Transmitter]
Prefix = <new_prefix>
Each new transmitter will be named “newprefixN” instead of Sitename_X (Sitename is the name of the site where the
transmitter 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 named
Sitename_X.
Furthermore, it is also possible to remove the underscore character "_" from the transmitter’s name, i.e., the transmitter can
be named SitenameX instead of Sitename_X. To do this, add the following line in the [Transmitter] section of the Atoll.ini file:
[Transmitter]
Underscore = 0 or 1
Setting this value to 0 means the underscore character will not be used when naming transmitters. The default value is 1. You
can also define whether the suffix X in the transmitter’s name should be a number or a letter. The following two lines define
this option in the Atoll.ini file:
[Transmitter]
SuffixIsNum = 0 or 1 #Default=1
FirstCharSuffix = <character> #if SuffixIsNum=0
When SuffixIsNum = 1, the suffix X in the transmitter name Sitename_X will be a number.
When SuffixIsNum = 0, this suffix will be a letter. The starting suffix in this case will be "A" by default but can be changed to
any other character in the 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 add
the following lines under the [Transmitter] section of the Atoll.ini file:
[Transmitter]
First = <number> #if SuffixIsNum=1
Where, X is a number.
11.1.1.2 Disabling Automatic Renaming of Transmitters and Cells
When the name of a site is modified, Atoll automatically renames the transmitters, cells, repeaters, and remote antennas
related to that site according to the new site name. By the same logic, when the name of a transmitter is modified, Atoll
automatically renames the cells, repeaters, and remote antennas related to that transmitter. Automatic renaming is enabled
by default. However, it can be disabled by adding the following lines in the Atoll.ini file:
[AutoRename]
Transmitters = 0
3GCells = 0
Repeaters = 0
• "Transmitters" refers to transmitter renaming when the site name is changed.
• "3Gcells" refers to cell renaming in 3G and 4G when the transmitter name is changed.
• "Repeaters" refers to repeater and remote antenna renaming when the transmitter name is changed.
11.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 represent
the background. You can export TIFF files with a palette containing the background colour at index 0 along with other colour
indices 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:
[TiffExport]
PaletteConvention = Gis
136
11.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 messages
displayed in the Event Viewer window to a log file. To do this, add the following lines to Atoll.ini:
[EventsObserver]
LogPath = FullPath\LogFile.log
The path should be the full path to the log file, which can be, for example, "\\Server\Drive\Root\Folder\Atoll\" or "C:\Program
Files\Forsk\Atoll\" (without quotation marks). "LogFile.log" will be created by Atoll as an ASCII text file, and can have any file
name and extension. Atoll will overwrite any already existing log file with the same name. If Atoll is unable to overwrite the
existing 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, or
by modifying the shortcut parameters. If you have a log file defined in the Atoll.ini file, and run Atoll with the ‐log option in
the 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 the
possibility to save the messages in the Event Viewer to a log file during an Atoll session (through the Event Viewer context
menu).
11.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 be
displayed in the Event Viewer. By defining an option in the Atoll.ini file, messages regarding insufficient permission will not be
displayed.
[EventsObserver]
ShowAddinAccessDeniedMsg=0 # 1 by default; insufficient permission messages are shown
11.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 memory
when printing. If you want Atoll to print your maps in a higher resolution than 150 dpi, you can add the following lines to the
Atoll.ini file:
[Print]
MaxDPI = 300
300 dpi is given as an example only.
11.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 the
linked path loss matrices folder corresponding to the created file and copies the existing linked path loss matrices from the
path loss matrices folder of the original document. There can be a large number of LOS files, and copying these files can take
a 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 the
following lines to the Atoll.ini file:
[Perfos]
StoreExternPrivLosFilesOnCopy = 0
StoreExternPrivLosFilesOnCopy is set to 1 by default, which means that Atoll makes copies of the linked path loss matrices on
Save As. If you set StoreExternPrivLosFilesOnCopy to 0, Atoll does not create the linked path loss matrices folder
corresponding to the created file, and the linked path loss matrices of the original Atoll document are used for the new Atoll
document 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 loss
matrices folder, the file open first will have access to the the path loss matrices. You will be able to open the second file, but
it will no longer point to any private path loss matrices folder. Therefore, if you have more than one file that points to the
same 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 whether
the user wants Atoll to make copies the linked path loss matrices or not. To add this confirmation step on Save As, add the
following lines in the Atoll.ini file:
[Perfos]
ConfirmStoreExternPrivLosFilesOnCopy = 1
137
ConfirmStoreExternPrivLosFilesOnCopy is set to 0 by default. This option is ignored when Atoll is run in non‐interactive mode,
for example using the API.
11.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 recalculating
a 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 coverage
predictions and transmitters, and/or high resolutions are used. if you have limited disk space, you can disable this feature by
adding the following lines in the Atoll.ini file:
[Studies]
NumericalResults = 0
NumericalResults is set to 1 by default, which means that Atoll will generate external results files and require more disk space.
Memory space is not impacted when NumericalResults is set to 1.
11.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 coverage
prediction in order to be able to distribute the live traffic data geographically. Atoll lets you select the best server coverage
prediction on which the traffic map will be based. In the list of available best server coverage predictions, Atoll lists all the best
server 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:
[Studies]
SelectNullMarginOnly = 1
SelectNullMarginOnly is set to 0 by default, which means that Atoll lists all the best server coverage predictions available.
11.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 details
cannot be copied or saved. If you want access to these details, or to a summary of these details, once the calculations have
finished, you can add the following lines in the Atoll.ini file:
[Pathlosses]
DisplayInvalidityCause = 1
DisplayIndividualSuccessOrFailure = 1
DisplayOverallSuccessOrFailure = 1
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 each
transmitter, and setting DisplayOverallSuccessOrFailure to 1 will display the total number of path loss matrices calculated, the
number 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.
11.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 the
header files of MapInfo (MIF) and ESRI (PRJ) vector files that you want to import. You can define a mapping between the two
coordinate systems by adding the following lines in the Atoll.ini file:
[MITAB]
Coordinate system definition in the header file = Coordinate system code in Atoll
In this way, Atoll is able to exactly detect the coordinate system used by the vector file being imported. In MIF files, the
CoordSys clause defines the coordinate systems, datum, unit, and other information. The coordinate system definition is
138
different in the PRJ files. The syntax used in Atoll.ini follows the syntax of the CoordSys clause in MIF files. Using the same
syntax for MIF and PRJ files, Atoll is able to read the detect the coordinate systems for both MapInfo and ESRI vector files.
The coordinate system codes in Atoll are stored in the CS files in the coordsystems folder. To access the coordinate system
codes through Atoll:
1. Select Tools > Options. The Options dialog box opens.
2. On the Coordinates tab, click the browse button (...) to the left of the Projection field. The Coordinate Systems dialog
box opens.
3. Select a coordinate system in the pane.
4. Click the Properties button. The Coordinate System properties dialog box opens.
The coordinate system code is available in the properties dialog box.
A few examples of such mapping are given below.
[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
11.1.1.12 Exporting Coverage Prediction Polygons in Text Format
You can export coverage predictions in the form of polygons to text format files.
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 exported
for coverage layers having more than one polygon.
You can enable this feature by adding the following lines in the Atoll.ini file:
[Studies]
EnableLBS = 1
Setting EnableLBS to 1 adds a new coverage prediction export format "LBS Polygon Files (*.txt)" to Atoll. The polygons are
exported in a comma separated values format.
11.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 servers
can be defined in the Atoll.ini file as follows:
[WMS]
S1 = Server1
S2 = Server2
...
SN = ServerN
You can define any number of servers by incrementing the index N. These servers will be available in the WMS data import
dialog box in Atoll.
139
11.1.1.14 Improving Point Analysis Performance
You can improve the performance, i.e. the calculation speed, of the Point Analysis tool by restricting the number of
transmitters for 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:
[Perfos]
PtAnalysisNbServersMax = X #Default=0 (i.e. no limit)
PtAnalysisMargin = Y #Default=30
PtAnalysisNbServersMax allows you to define the maximum number of servers (i.e. transmitters or cells) to consider when
calculating the received signal levels. X is the maximum number of servers.
PtAnalysisMargin allows you to define a margin with respect to the best server signal level. Atoll calculates the signal levels
from all servers within a Y dB margin from the best server signal level. The default value is 30 dB.
In addition to the above, you can also set the maximum number of servers displayed in the Point Analysis window and,
consequently, the maximum number of arrows displayed in the Map window (from the pointer location). To set this number,
add the following lines in the Atoll.ini file:
[Perfos]
PtAnalysisNbServersDisplayed = Z #Default=100
PtAnalysisNbServersDisplayed affects all tabs and reports of the Point Analysis tool in GSM, LTE, WiMAX, and WiFi.
Only the Reception tab is impacted in UMTS, CDMA2000, and TD‐SCDMA.
The following 2G/3G option is identical to PtAnalysisNbServersDisplayed. It is deprecated
and will no longer be available in future releases:
[ReceptionTab]
NumberOfTransmitterDisplayed = Z
11.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 can
dynamically load the data from SHP and TAB vector files when the following option is set in the Atoll.ini file:
[Import]
LoadVectors = 1
LoadVectors is set to 0 by default, which means that the data from imported vector files are loaded in memory. When you set
LoadVectors 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.
11.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. By
defining the following option in the Atoll.ini file, you can import KML and KMZ files without vectors:
[Import]
LoadKMLVectors = 0
LoadKMLVectors is set to 1 by default, which means that vectors are imported along with placemarks.
11.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 are
correctly aligned when:
• the horizontal pattern attenuation at 0° is the same as the vertical pattern attenuation at the pattern electrical tilt
angle, and
• the horizontal pattern attenuation at 180° is the same as the vertical pattern attenuation at the 180° less the pattern
electrical tilt angle.
By default, the option is inactive, i.e., the pattern attenuations are considered the same if they differ less than 100 dB. If you
want to change this default precision, add the following lines in the Atoll.ini file:
140
[Antenna]
PrecisionTimes10 = X
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
0,5  10 = 5 .
11.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 the
export is complete and open the XLS file created by the export in MS Excel. To enable this feature, add the following option
in the Atoll.ini file:
[Export]
AutoOpenWithExcel = 1
AutoOpenWithExcel is set to 0 by default.
11.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:
[GUIUserRights]
EnableNewDocFromTemplate = 0
EnableNewDocFromTemplate is set to 1 by default.
11.1.1.20 Blocking Access to Macros and Add‐ins
You can block access to the Add‐ins and Macros dialog box by adding the following lines in the Atoll.ini file:
[GUIUserRights]
EnableMacrosAddins = 0
EnableMacrosAddins is set to 1 by default.
11.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:
[GUIUserRights]
EnableZip = 0
EnableZip is set to 1 by default.
11.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 the
notification, add the following lines in the Atoll.ini file:
[Transmitter]
CheckImpactOnRepeaters = 1
CheckImpactOnRepeaters is set to 0 by default, which means that no notifications are displayed.
11.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 floating
point values include thresholds and power values in dBm. However, in case of documents connected to databases (other than
MS 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 dialog boxes and tables. For example, in order
to display two digits after the decimal point, you can add the following lines in the Atoll.ini file:
[Grids]
NbDecimals = 2
141
This option applies to all non‐formatted floating point parameters in Atoll, i.e., excluding geographic coordinates and
formatted floating point values.
NbDecimals is set to ‐1 by default. This corresponds to maximum precision, i.e., all the digits after the decimal point available
in the database are displayed.
11.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 dialog boxes of the file.
By default, the Find button in the Properties dialog box is available only for missing geographic data files, i.e., the linked files
that Atoll is unable to locate and load. However, you can enable the Find button even for available geographic data files by
[Geo]
FindGeoButtonAlwaysActive = 1 #default=0
This option can be useful when you have changed the location of a geographic data file, and you wish to change the path to
the new location.
When changing the path to a linked geographic data file, you must provide the new path
to the same file. This option does not allow linking to another file instead. In order to link
to another file, you must follow the normal file import procedure.
11.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 configuration
file (CFG) of the edited vector layer by adding the following lines in the Atoll.ini file. The exported display configuration file will
have the same file name and will be saved in the same directory as the exported vector‐format file.
[Geo]
VectorDisplayConfigurationCompanionFile = 1 #default=1
When you import vector data in an Atoll document, the same option enables you to simultaneously import the corresponding
display configuration file (CFG). The display configuration file will only be imported if it has the same file name and if it is
located in the same directory as the imported vector‐format file.
11.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 data
is visible on the map or not. You can change the default behaviour for population, traffic, and generic geographic data by
[Geo]
ReportObeysVisibility = 1 #default=0
11.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 default
respective World files (BPW or BMW for BMP, TFW for TIF, and PGW for PNG). If you want Atoll to export the georeference
information in a TAB file when you export in BMP, TIF, and PNG formats, add the following lines in the Atoll.ini file:
[RasterExport]
GeorefWithTAB = 1 #default=0
11.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:
[CoPlanning]
LinkSites = 1 #default=0
142
11.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 vertices
coordinates 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 of
import can take a long time. If you want to disable this normalisation when importing MIF and TAB vector files, add the
[MITAB]
DisableNormalization = 1 #default=0
11.1.1.30 Customising Performance Optimisation when Exporting Vector Files in
TAB Format
When you export vector files in TAB format, the performance is optimised by default , i.e. the export process is less time‐
consuming. If the resulting TAB files do not meet the quality level you were expecting, you can disable the performance
optimisation feature by adding the following lines in the Atoll.ini file :
[MITAB]
OptimizedTABExport = 0 #default=1
11.1.1.31 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 the
[Site]
AddToSiteListOnDuplicate = 1 #default=0
11.1.1.32 Real Altitude versus DTM Altitude in Sites’ Properties
11.1.1.32.1 Duplicate/Moved Sites
By default, when an existing site is duplicated/moved in the map (or when its coordinates are modified from its Properties
dialog box or from the Sites table) while a Real altitude is defined, the same Real altitude is inherited by the duplicate/moved
site. You can force Atoll to clear the duplicate/moved site’s Real field or to populate it with the duplicate/moved site’s own
DTM value by adding the following lines in the Atoll.ini file:
[Site]
ResetAltitude = 1 or 2 #default=0
In a nutshell, the following occurs to the duplicate/moved site according to the setting of ResetAltitude:
ResetAltitude Real field of duplicate/moved sites
0 The Real field of the duplicate/moved site inherits the original site’s Real altitude.
1 The Real field of the duplicate/moved site is cleared.
2 The Real field of the duplicate/moved site inherits the duplicate/moved site’s own DTM value.
If a site’s coordinate(s) and its real altitude are modified at the same time (from the site’s
Properties dialog box or from the Sites table), the new value in the Real field will be kept
even if ResetAltitude is set to 1 or 2.
11.1.1.32.2 New Sites
By default, when you create/drop a new site, repeater, remote antenna, or any type of link in the map, the Real field in the
sites’ Properties dialog boxes is cleared by default. You can force Atoll to populate it with the actual DTM value by setting
ResetAltitude to 2.
ResetAltitude Real field of new sites
1 The Real field of the new site is cleared.
2 The Real field of the new site inherits the site’ own DTM value.
143
11.1.1.33 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 coverage
predictions, whether the clutter classes are visible on the map or not. You can change the default behaviour by adding the
[Clutter]
OnlyVisibleClassesInInterferenceReport = 1 #default=0
The visibility of clutter classes on the map can be managed through the Display tab of the Properties dialog box of the Clutter
Classes folder. Using this option, you can exclude clutter classes which are not relevant in interference prediction reports, for
example, water.
11.1.1.34 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 area
of all the clutter classes covered by the prediction. If you want Atoll to display the percentages of covered clutter classes with
respect to the total surface area of all the clutter classes within the Focus Zone, add the following lines in the Atoll.ini file:
[Clutter]
PerClassPercentagesRelativeToCoverageInReport = 0 #default=1
11.1.1.35 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 total
surface area of all the environment traffic classes covered by the prediction. If you want Atoll to display the percentages of
covered environment traffic classes with respect to the total surface area of all the environment traffic classes within the
Focus Zone, add the following lines in the Atoll.ini file:
[Traffic]
PerClassPercentagesRelativeToCoverageInReport = 0 #default=1
11.1.1.36 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 loss
matrices are valid:
• Atoll deletes any corresponding invalid private path loss matrices and uses the valid shared ones for calculations if
Atoll.ini contains the following lines:
[Pathlosses]
FullResyncPrivShared = 0 #default=1
• Atoll deletes any corresponding valid and invalid private path loss matrices and uses the valid shared ones for
calculations if Atoll.ini contains the following lines:
[Pathlosses]
FullResyncPrivShared = 1 #default=1
If you have private path loss matrices tuned using measurement data, setting FullResyncPrivShared to 1 will make
Atoll automatically delete them when calculations are run. You should set FullResyncPrivShared to 0 when working
with tuned private path loss matrices.
11.1.1.37 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 "Print
Setup Configuration" on page 129). 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:
[Print]
LogoFooterChecked = 1 #default=0
11.1.1.38 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 some
common OFDMA coverage predictions can be available for both WiMAX and LTE. If you wish to filter the customised
predictions stored in the XML studies file by their technology, e.g., separate the WiMAX and LTE coverage predictions, and
144
only load the predictions specific to the technology of the current active Atoll document, add the following lines in the Atoll.ini
file:
[Studies]
CustomStudiesFilteredByTechno = 1 #default=0
This option is only relevant for reading the XML studies file. Atoll always writes the technology type in the XML studies file
when customised coverage predictions are saved in it.
11.1.1.39 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 the
[MITAB]
EnableMessages = 1 #default=0
Atoll does not display any messages related to MapInfo file import and export.
11.1.1.40 Setting the Resolution of Population Maps in Coverage Prediction Reports
Atoll uses the default resolution, defined in the Predictions folder’s Properties dialog box, for rasterisation of the population
maps. In order to use a different resolution for higher or lower precision, you can add the following lines in the Atoll.ini file:
[Population]
ReportResolution = X
Where X is the resolution for the conversion of population map vectors into raster.
If you set ReportResolution to a very precise (low) value, the performance (calculation
speed) can be considerably decreased depending on the size of the population maps in
the document. It is recommended to set this parameter to an optimum value, i.e., just
precise enough to get the required accuracy.
11.1.1.41 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 reports
by adding the following lines in the Atoll.ini file:
[Studies]
ReportDecimalPlacesAbsolute = X
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 reports
by adding the the following lines in the Atoll.ini file:
[Studies]
ReportDecimalPlacesPercent = X
Where X is the number of digits following the decimal.
11.1.1.42 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 these
ranges in coverage prediction reports by adding the following lines in the Atoll.ini file.
[Studies]
ShowIntervalsWithNoCoverageInReport = 1 # (Default=0)
11.1.1.43 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 of
145
hot spots covered by each coverage layer (display thresholds) with as reference the hot spot surface area, add the following
lines in the Atoll.ini file:
[Studies]
UseFullHotSpotSurfaceOnReport = 1 #default=1
11.1.1.44 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 coding
schemes, throughput, and CQI), you can export only the visible levels by adding the following lines in the Atoll.ini file:
[Studies]
ExportOnlyVisibleLevels = 1 #default=0
ExportOnlyVisibleLevels is set to 0 by default, which means that when any coverage prediction is exported, Atoll exports all
its levels, visible or not.
Atoll exports only visible coverage predictions. If a coverage prediction consists of only
one level, the visibility check box of that level also controls the visibility check box of the
prediction itself. This means that if the visibility check box of the only level of such a
prediction is cleared, the prediction will itself be hidden and will not be exported.
11.1.1.45 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 pixels
can 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:
[Studies]
NoOverlapOnBestServer = 1
By default, NoOverlapOnBestServer is set to 0. When NoOverlapOnBestServer is set to 1, Atoll arbitrarily selects one of the
best servers on such pixels. This option can be useful, for example, when calculating population statistics based on a best
server coverage prediction. When a pixel is covered by more than one best server, the population belonging to that pixel is
counted as many times as the number of best servers, which can give erroneous percentages of covered population.
11.1.1.46 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:
[Compression]
StartSizeInMB = X
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.
11.1.1.47 Loading, Activating, and Setting Add‐ins as Visible
Installed add‐ins are automatically loaded by Atoll and appear in the Add‐ins and Macros dialog box. You can change this
default 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 dialog box,
[Add-ins]
Add-in Name = 0
• If you want an add‐in to be loaded, activated, and accessible in the Add‐ins and Macros dialog box for activation/
deactivation, add the following lines in the Atoll.ini file:
[Add-ins]
Add-in Name = 1
• If you want an add‐in to be loaded and activated, but only shown in the Add‐ins and Macros dialog box for information
(impossible to deactivate), add the following lines in the Atoll.ini file:
146
[Add-ins]
Add-in Name = 2
• If you want to set an add‐in to be mandatory for Atoll, add the following lines in the Atoll.ini file:
[Add-ins]
Add-in Name = 3
Any add‐in set to option 3 will be loaded and activated, but only shown in the Add‐ins and Macros dialog box for
information (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 dialog box. Atoll fails to start if for some reason
it is unable to load an add‐in whose status is set to 3. The default status for add‐ins is 1.
11.1.1.48 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.ini
file as follows:
[OnlineMaps]
Name1 = City1
URL1 = http://...
Name2 = City2
URL2 = http://...
...
NameN = CityN
URLN = http://...
You can define any number of online map URLs by incrementing the index N. These URLs will be available in the online map
import dialog box in Atoll.
11.1.1.49 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. By
default, the location of this cache is "%TEMP%\OnlineMaps". You can change this location by adding the following lines in the
Atoll.ini file:
[OnlineMaps]
TilesCachePath = <new path>
11.1.1.50 Defining the Microsoft Bing Tile Server for Online Maps
If you want to define the Microsoft Bing Maps Server for online maps, you must request a Bing Maps key from Microsoft and
use it with the following option in the Atoll.ini file:
[OnlineMaps]
BingKey=<key> #Request your Bing <key> from Microsoft
When BingKey is specified with a valid key, "Bing" becomes available under Provider in the Add a Tile Server dialog box. A
Type and a Language must also be defined before you can validate.
• Type: available choices are "Aerial", "Road", and "Hybrid"
• Language: default languages are "English", "French", and "Japanese".
More languages can be selected if they are defined with the following options in the Atoll.ini file:
[OnlineMaps]
BingCulture<X>=<culture> #e.g. <X>=0, <culture>="ar-sa"
BingLanguage<X>=<language> #e.g. <X>=0, <language>="Arabic KSA" or any string
• <X>=0 is equivalent to 4th position in the Language list (after the 3 default languages)
• <culture> and <language> settings can be found in the Culture and Language columns
at the following URL: http://msdn.microsoft.com/en‐us/library/hh441729.aspx
147
11.1.1.51 Defining the Microsoft Bing Tile Server for Online Searches
By default, when you search for a point on the map by its full or partial postal address, Atoll returns specific search results. If
you want to force Atoll to return a list of results based on the Microsoft Bing Maps server, you must request a Bing Maps key
from Microsoft and use it with the following option in the Atoll.ini file:
[OnlineSearch]
BingKey=<key> #Request your Bing <key> from Microsoft
11.1.1.52 Managing Carriage Returns in Imported TXT/CSV Files
By default when you export the content of a table in TXT or CSV formats, the carriage returns (e.g. in a "Comments" frame)
are replaced by "\n" characters in the exported file. When you import this file in an Atoll document, these "\n" characters are
in turn replaced by carriage returns.
If you want, you can force Atoll to replace carriage returns by spaces instead of "\n" characters in the exported tables by
[Export]
NewLineEscapeSequence = " "
11.1.1.53 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 filtering
zone. If you wish to remove the filtering zone as well when removing filters from tables, add the following lines in the Atoll.ini
file:
[Settings]
KeepFilterZoneOnRemoveFilter=0 #Default=1
11.1.1.54 Disabling Automatic Restart of Atoll after a Crash
By default, Atoll restarts automatically after a crash. If you want, you can switch to manual restarts by adding the following
[System]
RestartOnImproperExit=0 #Default=1
11.1.2 GUI Options
11.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 can
define the parameters as follows:
[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
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 the
symbol, you can use the Windows’ Character Map tool. You can use the copy/paste features to set the symbol in the Atoll.ini
file.
Example:
[SitesSymbol]
FontName = Wingdings
Symbol = ¤
Size = 12
Color = 0
148
11.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:
[RemoteAntennas]
FrozenSymbol = 1
FrozenSymbol is set to 0 by default. When you set FrozenSymbol to 1, the remote antenna symbol will be fixed and no longer
linked with the transmitter symbol.
11.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. If
you want these transmitters to keep their original symbols, add the following lines in the Atoll.ini file:
[Transmitter]
ChangeSymbolOnSearch = 0
ChangeSymbolOnSearch is set to 1 by default.
11.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 to
display filled symbols for inactive transmitters, repeaters, and remote antennas on the map, add the following lines in the
Atoll.ini file:
[Transmitter]
EmptySymbolWhenInactive = 0
EmptySymbolWhenInactive is set to 1 by default.
11.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 by
[Transmitter]
AutoSynchronizeDisplay = 1
AutoSynchronizeDisplay is set to 0 by default.
11.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:
[StatusBar]
DisplayZ = 0
DisplayClutterClass = 0
DisplayClutterHeight = 0
DisplayZ, DisplayClutterClass and DisplayClutterHeight respectively refer to the display of altitude, clutter class, and clutter
height.
11.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 the
following lines to the Atoll.ini file:
[EventsObserver]
milliseconds = 1
date = 1
149
11.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 coverage
predictions available at a pixel up to 30 lines by default. You can change this default number of tool tip text lines through the
following option in the Atoll.ini file:
[Studies]
MultiplePlotsTipTextLines = X
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 large
value, however, the tool tip might not display correctly.
11.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 displayed
in two different ways. By default, these diagrams represent the average array correlation matrices and are symmetric about
the x‐axis (same on the front and back). If you want to display these diagrams taking into account the antenna pattern of the
single antenna element, add the following option in the Atoll.ini file:
[SAModel]
DrawSingleElementPattern = 1
H
DrawSingleElementPattern is set to 0 by default, in which case the displayed diagram is S  R Avg  S  . When you set
H
DrawSingleElementPattern to 1, the diagram displayed will represent g n     S   R Avg  S .
11.1.2.10 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 the
[Studies]
CommentsInLegend = 1
The comments are displayed between the name of the coverage prediction and the thresholds. CommentsInLegend is set to
0 by default.
11.1.2.11 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 tables
in UMTS, CDMA2000, and TD‐SCDMA. For example, cell identity "00678" is displayed as "678". If you want Atoll to display
leading zeros, you must set the minimun number of digits the CELL_IDENTITY field should contain by adding the following lines
[Display]
CellIDNbDigits = X
Where X is the number of digits that the CELL_IDENTITY field should contain. For example, CellIDNbDigits = 5 means that Atoll
will display at least five digits in the CELL_IDENTITY field by adding leading zeros where required. This means that Atoll will
display "00678" in the above example. However, if the CELL_IDENTITY field contains a number that has more than X digits, all
the digits will still be displayed. For example, all seven digits in "9376562" will still be displayed even if CellIDNbDigits is set to
5.
11.1.2.12 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:
[Antenna]
REDTDisplay = 1
REDTDisplay is set to 0 by default.
150
11.1.2.13 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 of
clutter classes with long names, by adding the following lines in the Atoll.ini file:
[StatusBar]
ClutterPaneWidth = X
ClutterPaneWidth is set to 100 by default, which means 100% of its default width. To increase the width to, for example, twice
the original width, set ClutterPaneWidth to 200.
11.1.2.14 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 the
technology names by adding the following lines in the Atoll.ini file:
[DocTitle]
UseTechnoName = 0
UseTechnoName is set to 1 by default.
11.1.2.15 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 the
Atoll.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 through
PaletteColor11) the next time you display objects by discrete values.
[Display]
PaletteColor0=141 211 199
You can also override user‐defined colours, if any, and force shading (from red to blue) by setting the following option in the
Atoll.ini file.
[Display]
DiscreteValueColoring=Shading
11.1.2.16 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 the
actual tilt in the geographic profile view of the Profile Analysis tool. You can configure this display mode by adding the
[GeoProfileDisplay]
Beamwidth=1
BeamwidthColor=128 128 128
Upper3dbColor=255 0 0
Lower3dbColor=196 0 196
151
The geographic profile displays clutter classes and the Fresnel ellipsoid by default. When the Beamwidth option is set to 1, the
option is enabled and three additional lines are added to the diagram:
• Thick upper and lower lines: These lines indicate the upper and lower ‐3 dB beamwidth limit in the vertical plane.
• Thick central 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).
You can specify the colors of the lines with the BeamWidthColor, Upper3dbColor, and Lower3dbColor options.
The vertical beamwidth is widest in the azimut axis of the antenna. If you move the position of the Point Analysis tool off of
the antenna azimut axis, the vertical beamwidth diminishes and disappears when the vertical beamwidth loss exceeds ‐3 dB.
11.1.2.17 Case‐insensitive Grouping
By default, the "Group by" feature is case‐sensitive, which means that items labelled "a" and items labelled "A" are grouped
into two different categories. You can make the feature case‐insensitive by adding the following lines in the Atoll.ini file:
[Display]
CaseInsensitiveGroups=1
CaseInsensitiveGroups is set to 0 by default.
11.1.3 Distributed Calculation Server Options
11.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 distributed
calculation server, can run up to 10 instances of Atollsvr, the distributed calculation application. The distributed calculation
server names can be listed in the Atoll.ini file in the following format:
[RemoteCalculation]
NumberedServers = Server1NameN; Server2NameN; ...
Here Server1Name and Server2Name refer to the names of the computers being used as calculation servers, and N is a number
from 0 to 9. This means, for example, that Server1 can run up to 10 instances of the distributed calculation application, and
all these instances can be listed in the NumberedServers option (Server1Name0; Server1Name1; Server1Name2; ...). Using
this 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 one
by one. It does not attempt creating more than one thread.
11.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 possible
to modify its priority, in both service and application modes, and set it higher or lower. You can do this by adding the following
[RemoteCalculation]
AtollSvrPriority = -1, 0, 1 or 2
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.
• The distributed calculation server (AtollSvr.exe) must be restarted in order to take
into account the new value for the AtollSvrPriority option.
• The Realtime priority mode has not been implemented for reasons of stability.
152
11.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. You
can increase this time‐out by adding the following lines to the Atoll.ini file:
[RemoteCalculation]
DetectTimeOut = 5000
In this example, the detection time‐out is set to 5000 ms.
11.1.4 Licence Management Options
11.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.ini
file should contain the following lines:
[License]
TimeBombNotice = X
X is the number of days prior to the temporary licence end date you want Atoll to warn you. When no information is given in
the Atoll.ini file, Atoll warns the user 30 days before the licence end.
11.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 and
distributes 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:
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
You can also block access to GSM, UMTS, or LTE radio access technologies in 3GPP Multi‐RAT documents using these options.
11.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 the
corresponding lines in the [License] section of the Atoll.ini file:
[License]
ACP_GSM = 0
ACP_UMTS = 0
ACP_LTE = 0
ACP_WiMAX = 0
GSM_AFP = 0
LTE_AFP = 0
WiMAX_AFP = 0
In order to carry out a combined GSM and UMTS optimisation using the ACP module, you must have access to both ACP
module licences, i.e., ACP_GSM and ACP_UMTS must both not be set to 0.
153
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 module
licence, i.e., WiMAX_AFP must not be set to 0.
11.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 floating
licences from a licence manager server reset this idle time parameter to its initial value every minute. If you are performing
time‐consuming calculations on Atoll connected to a floating licence server, and consuming a licence, it might occur that Atoll
does not get the chance to reset the idle time value to its initial value. In this case, a new Atoll session can steal the licence
actually allocated to an already running session. This might cause problems in the case where all the licences are used, the
Atoll session performing heavy calculations does not get the chance to initialise the idle time parameter for its licence, and a
new Atoll session is launched on another computer. In such a situation, the floating licence manager considers that the
already running session has been inactive or closed, and the licence allocated to the already running Atoll session is allocated
to 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 for
the idle time parameter, add the following lines to the Atoll.ini file:
[License]
IdleTime = X
Where X is the time in minutes. The idle time can be set to infinity by defining IdleTime = 0.
11.1.5 Database Options
11.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 was
recently upgraded to a new version, or when you refresh data in an Atoll document from the database. It is recommeded to
perform 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:
[Refresh]
ControlIntegrity = 0
ControlIntegrity is set to 1 by default.
11.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 from
a database. To turn this feature on, add the following lines in the Atoll.ini file:
[Database]
IntegrityChecker = 1
If this option is set to 1, Atoll performs SELECT filters in the database to guarantee data integrity. This feature enables selection
directly in the database in order to avoid integrity problems in the future.
11.1.5.3 Displaying Database Tables in the Event Viewer at Open
This option displays the database tables that are read as they are loaded when opening a document from a database. The
table names are displayed in the event viewer. To turn this feature on, add the following lines in the Atoll.ini file:
[Database]
DisplayTableNamesOnOpenFromDB = 1
11.1.5.4 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 of
connected documents. Failing to fill a non‐nullable custom field when you add a new record via a record template, a file
import, or table edition, will return a message in the form "’NameOfField’ column cannot be null". To avoid this, you can define
the custom field as nullable in the database, use a default value in the field definition, or create the field and fill it in the
relevant template.
154
As a last resort, you can force the previous behaviour of Atoll by adding the following lines in the Atoll.ini file:
[Database]
AllowNullRecordsForNonNullableCustomFields = 1 #default=0
11.1.5.5 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 data
from a database.
To automatically audit the consistency of redundant values in the transmitters, subcells, and TRXs tables without fixing any
problems found, add the following lines in the Atoll.ini file:
[Database]
SubCellAuditConsistency = 1
To automatically audit the consistency of redundant values in the transmitters, subcells, and TRXs tables and fix any problems
found, add the following lines in the Atoll.ini file:
[Database]
SubCellAuditConsistency = 2
To automatically audit the compatibility of the main subcell values without fixing any problems found, add the following lines
[Database]
SubCellAuditMainValues = 1
To automatically audit the compatibility of the main subcell values and fixi any problems found, add the following lines in the
Atoll.ini file:
[Database]
SubCellAuditMainValues = 2
SubCellAuditConsistency and SubCellAuditMainValues are set to 0 by default.
11.1.5.6 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. You
can change this default timeout value and set a higher value if you encounter problems, during execution of commands on
the database, which might be related to timeout. To change the value of the command timeout parameter of the ODBC driver,
[Database]
CommandTimeout = X
Where X is the timeout value in an integer number of seconds. After X seconds, the command is considered too long to
execute. If you set CommandTimeout = 0, there will be no time limit for the execution of the command.
11.1.5.7 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 case
sensitive by adding the following lines in the Atoll.ini file:
[PlanetImport]
SensitiveCase = 1
Case sensitive means that "Site0" will be considered different from "site0" during import.
11.1.5.8 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:
[PlanetImport]
155
ChangeKclutterSign = 1
ChangeKclutterSign is set to 0 by default.
11.1.5.9 Setting the Clutter No Data Value for When Importing Data From Planet
EV
Atoll automatically detects undefined clutter class data as No Data when importing data from Planet EV. No Data clutter is
considered transparent on the map and in calculations. You can instruct Atoll to use a specific value as the No Data value when
importing data from Planet EV by adding the following lines to the Atoll.ini file:
[PlanetImport]
ClutterNoData = X
Where X is the No Data value for clutter. ClutterNoData is set to ‐9999 by default.
11.1.5.10 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 user
to enter the username and password once per Atoll session, add the following lines in the Atoll.ini file:
[Database]
PromptOnArchive = 1
PromptOnArchive = 1 is the default setting used if this option is not provided in the Atoll.ini file. The user will be prompted for
password 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:
PromptOnArchive = 2
If you want to disable the prompt for password, set:
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.
11.1.5.11 Archiving Data to Databases Using Transactions
Atoll supports transactions for archiving data to databases. This approach ensures that users always get consistent data when
refreshing their documents with data from the database, even when another user is archiving his modifications at the same
time. By default, Atoll uses transactions for archiving data, however you can disable the transaction mode for Atoll by adding
the following lines to the Atoll.ini file:
[Database]
UseTransaction = 0
UseTransaction is set to 1 by default.
Before modifying this option, make sure that the database server is correctly configured
for transactions.
11.1.5.12 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 the
work and master projects to overwrite each other’s shared folder. From an operational standpoint, it is often preferable to
keep 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.
[Database]
156
OverwriteSharedFolderPath = 0 # "1" is default: path loss directory is overwritten
11.1.5.13 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 automatically
performs a full refresh, i.e., loads all the data from the database, when upgrading the document to the new version. If you
wish to enable partial refresh of data from the upgraded database (not recommended as it can cause data integrity problems),
[MajorVersionChange]
EnablePartialRefreshInMigration = 1
EnablePartialRefreshInMigration is set to 0 by default.
11.1.5.14 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:
[Database]
ExclusiveProvider = providername
Where providername can be "Access", "SQLServer", or "Oracle". When this option is set, Atoll uses the defined database type
and does not display the database selection dialog box that appears when creating a new document from an existing database
or when exporting a document to create a new database.
11.1.6 Common Calculation Options
11.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:
[Antenna]
Catalog Vertical Diagram Orientation = 90 or angle value
InterpolatePatternEvenIfOnlyOneDiagram = 0 or 1
InterpolatePatternIndB = 0 or 1
Catalog Vertical Diagram Orientation is a display option. It enables rotating the antenna’s vertical diagram to a user‐defined
angle. By default, Catalog Vertical Diagram Orientation is set to 90 meaning that the vertical diagram is displayed pointing to
the 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 attenuation
diagrammes for antennas with only one diagramme available, vertical or horizontal. With
InterpolatePatternEvenIfOnlyOneDiagram = 0 (default, new method), Atoll uses the only diagramme available for both
vertical and horizontal planes. With InterpolatePatternEvenIfOnlyOneDiagram = 1 (previous method), Atoll uses the
diagramme available for the plane to which it corresponds, vertical or horizontal, and an isotropic diagramme (a 0 dB circular
attenuation 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 any
value other than 0), interpolations are calculated in dB leading to stronger antenna pattern attenuation.
11.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 prediction
studies automatically, these lines have to be included in the Atoll.ini file:
[Studies]
AutoLock = 0
AutoLock is to 1 by default.
11.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 during
coverage predictions and other calculations such as point analysis, automatic neighbour allocation, automatic scrambling
157
code and PN offset allocation, and interference matrices calculation. This average value depends on the cell edge coverage
probability that you define for the calculation and the standard deviations defined per clutter class.
In the dialog boxes of all the above‐mentioned calculations, the Shadowing taken into account check box is not selected by
default. 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 dialog boxes, you
have to enter the following lines in the Atoll.ini file:
[Shadowing]
UseShadowing = 1
UseShadowing is set to 0 by default.
This option does not affect the shadowing margin calculation during Monte Carlo
simulations. Monte Carlo simulations do not use an average value of the shadowing
margin depending on the cell edge coverage probability. During Monte Carlo simulations,
random shadowing margin values are calculated based only on the standard deviations
defined per clutter class.
In UMTS HSPA and CDMA2000 documents, you can also deactivate the calculation and use of macro‐diversity gains. For more
information, see "Disabling Macro‐diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt" on page 170.
11.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 in
the Atoll.ini file, Atoll will consider the value of the cell edge coverage probability defined in the Atoll.ini file as the default
value, and will take it into account when performing point analysis, in the shadowing margins calculator, and will propose it
as the default value for coverage prediction studies.
[Shadowing]
Reliability = 60
Reliability = 60 means 60 % cell edge coverage probability.
The value of cell edge coverage probability used for automatic neighbour allocation and
interference matrices calculation is stored in user configuration files (CFG).
11.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 not
selected by default. If you want to select the check box by default in the properties dialog boxes of all the calculations, you
have to enter the following lines in the Atoll.ini file:
[ClutterParams]
IndoorActivity = 1
IndoorActivity is set to 0 by default.
11.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 calculation
resolution. These calculations can be time‐consuming if the geographic data is available with a very high resolution. You can
set the calculation resolution to a multiple of the resolution of the geographic data by adding the following lines in the Atoll.ini
file:
[LOSArea]
ResolutionMultFactor = X
Where X is an integer. Therefore, setting ResolutionMultFactor to 2 will double the calculation resolution and decrease the
time required for the calculation by half.
158
11.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 the
document and externalise the path loss matrices or if you would like to keep the path loss matrices embedded in the
document and save it later. You can suppress this message by adding the following lines in the Atoll.ini file:
[Pathlosses]
EmbeddedByDefault = 1
EmbeddedByDefault is set to 0 by default.
11.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 continues
performing the remaining calculations, and provides results even if they are not complete. If you want Atoll to stop the
calculations if there is an error, you can add the following lines in the Atoll.ini file:
[Studies]
ContinueOnError = 0
ContinueOnError = 1 by default. This means that by default Atoll does not stop the calculations on error.
11.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 you
modify the display options for coverage predictions. To deactivate this warning message, add the following lines in the Atoll.ini
file:
[Studies]
RecomputationWarning = 0
RecomputationWarning is set to 1 by default.
11.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 the
DTM for the site coordinates defined in the Sites table. However, transmitters can be located at certain distances from the
site 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 determining
the transmitter height, which will be read from the DTM at the exact transmitter coordinates, you must add the following lines
[Calculations]
UseSiteAltitude = 0
UseSiteAltitude is set to 1 by default, which means that the altitude used in calculations will be the one which is either read
from 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 exact
coordinates 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 for
the DX_A, DY_A, DX_B, and DY_B parameters.
With UseSiteAltitude = 0, if DX and DY are 0, i.e., for transmitters and microwave links
located at the site coordinates, Atoll will still use the altitudes defined per site, if any, or
the altitudes from the DTM otherwise
11.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 coverage
predictions that you create, in the Predictions tab of the Predictions folder’s Properties dialog box. If you create a new
coverage prediction, Atoll reads the default resolution from the Predictions folder’s Properties dialog box and sets that as the
display resolution for the new coverage prediction. Then, if you delete this resolution from the coverage prediction properties,
and do not enter any resolution, Atoll resets the resolution to the default value. In this way, each coverage prediction has a
159
display resolution defined. However, it is possible to manage a common display resolution for all coverage predictions, new
or existing, that do not have a resolution defined for them. You can switch to this option by adding the following lines in the
Atoll.ini file:
[Studies]
SpecifyResolutionAfterComputation = 0
Once SpecifyResolutionAfterComputation is set to 0, Atoll no longer resets the resolution to the default value for coverage
predictions that do not have a resolution defined. Atoll allows you to leave the field empty in the coverage prediction
properties, and directly reads the default resolution defined in the Predictions folder’s Properties dialog box. In this way,
when you create coverage predictions without defining resolutions for them, you can modify the default resolution in the
Predictions Properties dialog box and, therefore, change the display resolution for all the coverage predictions, new or
existing.
To return to the normal working, remove the lines from the Atoll.ini file or set SpecifyResolutionAfterComputation to 1.
11.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:
[RemoteCalculation]
Priority = 0, 1, or 2
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.
11.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:
[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
Maximum number of processors:
• NumberOfProcessors is the maximum number of processors that can be used for calculations. If you set this option to
0, Atoll will use the 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 by
default, 8 maximum)
• NumberOfThreadsSimulation is the maximum number of threads that can be used for Monte Carlo simulation
calculations (4 by default, 8 maximum)
• NumberOfThreadsStudy is the maximum number of threads that can be used for the calculation of coverage
predictions (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 (4
by default, 8 maximum)
All these options are upper limits per computer. Atoll supports a maximum of 64 parallel threads.
11.1.6.14 Parallel Calculation of Monte Carlo Simulations
In UMTS HSPA and CDMA2000 (1xRTT and 1xEV‐DO) documents, Atoll perform multi‐threaded calculations of Monte Carlo
simulations by default. To disable parallel calculations in these two technologies, add the following lines to the Atoll.ini file:
160
[CDMA]
ParallelSimulations=0 #Default=1
In GSM, Atoll can also perform multi‐threaded calculations of Monte Carlo simulations if you add these lines to Atoll.ini:
[GSM]
ParallelSimulations=1 #Default=0
The Generator Initialisation must be set to 0 in order for simulations to be calculated in
parallel.
Parallel calculation of Monte Carlo simulations is not available in TD‐SCDMA, WiMAX, LTE, and Wi‐Fi documents.
11.1.6.15 Performing Calculations in Read‐Only Documents
Parallel calculation of Monte Carlo simulations is not available in TD‐SCDMA, WiMAX,
LTE, and Wi‐Fi 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 calculations
in read‐only documents, add the following lines in the Atoll.ini file:
[Studies]
ComputeEvenIfReadOnly = 1
If you open a document that is already open in another Atoll session, Atoll lets you open the document as read‐only.
11.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 separate
coverage 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:
[Studies]
AerialStudy = 1
11.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, from
Atoll2.8.0 onwards, real values are rounded up or down to their nearest integer values. For example, using the previous
method, 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 the
previous method, add the following lines in the Atoll.ini file:
[Calculations]
RoundAltitudes = 0
RoundAltitudes is set to 1 by default.
11.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 Traffic
tab of the new simulation group dialog box. Estimated memory size within the green region means low consumption, within
the yellow region means medium consumption, within the orange region means high consumption, and within the red region
means very high consumption, in which case the simulations might generate an out of memory error and not complete.
This option is only available in the 32‐bit version of Atoll.
To activate the memory estimation feature, add the following lines in the Atoll.ini file:
[CDMA]
161
PredictSimuMemorySize = 1
PredictSimuMemorySize is set to 0 by default which means the feature is not active.
11.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 classes
files, add the following lines in the Atoll.ini file:
[FskPropagModels]
OptimOnNoData = 1
By default, OptimOnNoData is set to 0. This option only works with the propagation models available with Atoll by default.
11.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 unlocked
coverage 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 unlocked
coverage predictions in the Predictions folder of the current document, and not in the linked Predictions folder from another
document, add the following lines in the Atoll.ini file:
[CoPlanning]
ComputeLinkedPredictions = 0
ComputeLinkedPredictions is set to 1 by default.
11.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 the
Predictions folder of the current document and the linked Predictions folder from another document, add the following lines
[CoPlanning]
LinkedPredictionsComputationMode = Parallelized
LinkedPredictionsComputationMode is set to Serialized by default, which means the path loss matrices and unlocked
coverage 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 being
managed by a task list.
Calculations are carried out starting with the current document in the order of the coverage predictions in the Predictions
folder.
11.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 if
the 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 located
outside the Focus Zone. If you want Atoll to make only those neighbour relations symmetrical for which both transmitters in
the neighbour relation are located inside the Focus Zone, add the following lines in the Atoll.ini file:
[Neighbours]
ForceSymmetryInFocusZone = 1
ForceSymmetryInFocusZone is set to 0 by default.
11.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 small
variations 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:
[Simulation]
RandomTotalUsers = 0
162
By default, RandomTotalUsers is set to 1.
11.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 to
calculate the EIRP from the Max Power values when calculating signal level‐based coverage predictions, add the following
[Studies]
EIRPfromMaxPower = 1
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.
11.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 the
list of neighbours, add the following lines in the Atoll.ini file:
[Neighbours]
ExcludeFilteredCellsFromNeighbourLists = 0 (default)
By default, ExcludeFilteredCellsFromNeighbourLists is set to 0.
11.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 the
[Neighbours]
DistanceAzimutWeightingPercent = 0.3 (default)
If the value you set is too high (e.g. 0.7), the resulting inter‐transmitter distance can be
negative. In such a case, nothing will be displayed in the corresponding table cell.
11.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 the
donor sites only. If you want it to also consider repeaters and remote antennas, then add the following lines in the Atoll.ini file:
[Neighbours]
RepeaterInterSiteDistanceInAlloc = 1 #(default = 0)
11.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 higher
than 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 the
Atoll.ini file:
[Neighbours]
RealInterSiteDistanceCondition = 1 #(default = 0)
163
11.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 setting
for all neighbour candidates. As a consequence, there can be cases where the calculated importance is different when the
global Max inter‐site distance is modified.
You can avoid that by forcing Atoll to prioritise individual distances between reference transmitters/cells and their respective
neighbour candidates. To do that, add the following lines in the Atoll.ini file:
[Neighbours]
CandidatesMaxDistanceInImportanceCalculation = 1 #(default = 0)
11.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 reference
transmitter 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:
[Neighbours]
DoNotDeleteSymmetrics = 1 #(default = 0)
11.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 each
transmitter’s matrix separately. You can disable per‐site calculation of path loss matrices by adding the following lines in the
Atoll.ini file:
[RemoteCalculation]
DisablePathlossPerSiteCalculation = 1
DisablePathlossPerSiteCalculation is set to 0 by default for Atoll 64‐bit and to 1 for Atoll 32‐bit.
11.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 following
[Transmitter]
MaximumCalculationRadius = X
Where X is the maximum calculation radius in metres. By default, there is no limit for the path loss calculation radii. The limit
you set here is applied to values entered by the user in the Transmitters table or properties dialog box.
11.1.6.33 Preserving Loss and Noise Figures with no Assigned Equipment
By default, calculating and updating UL/DL loss and noise figures updates the parameters of the transmitter, even when no
equipment is assigned to the transmitter. This can cause problems in some environments.
You can force Atoll to preserve the existing transmitter values when no equipment is assigned, by adding the following lines
[Transmitter]
UpdateLossIfNoEquipment = 0
UpdateLossIfNoEquipment is set to 1 by default.
11.1.7 GSM GPRS EDGE Options
11.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‐technology
interference is taken into account by default. By adding the following option in the Atoll.ini file, you can add an Inter‐
164
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.
[GSM]
ExternalIncluded = 0
ExternalIncluded is set to 1 by default, i.e. inter‐technology interference is taken into account by default in GSM "Coverage by
C/I Level (DL)" predictions (the Inter‐technology check box does not appear in the list of Interference Sources) and in point
analyses’ "Interference" and "Details" views.
11.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 is
taken into account when the option "Best Server" is selected and a positive margin is defined. For interference matrices
calculation 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 in
the Atoll.ini file:
[Features]
IM_TRAFFIC_OVERLAP = 1
11.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:
[BsicFormat]
DefaultValue = 1 for Octal or 0 for Decimal format
DefaultValue enables you to change the default BSIC format (Octal by default) when you create a new Atoll document.
11.1.7.4 Checking Database Consistency Automatically
If you want Atoll to automatically perform a basic data consistency check to avoid incompatibility between redundant fields
in GSM GPRS EDGE documents, add the following lines to the Atoll.ini file:
[Refresh]
TRXIntegrity = 1
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 the
Transmitters folder’s Properties dialog box with the values from the TRGs and the TRXs tables respectively, when a document
is opened from a database or refreshed.
11.1.7.5 Disabling the Maximum Range Parameter
The maximum cell range parameter (System frame in the Network Settings folder’s Properties dialog box) in GSM GPRS EDGE
documents is used by default and set to 35 km. You can disable this option by adding the following lines in the Atoll.ini file:
[Perfos]
MaxRangeApplied = No
If you set this option to anything other than "No", Atoll will use the maximum range parameter and set it to the default value
of 35 km.
11.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 the
multi‐band modelling feature, add the following lines in the Atoll.ini file:
[Studies]
MultiBandManagement = 1
MultiBandManagement is set to 0 by default. Enabling multi‐band management allows the users to access the multi‐band
management features through the Frequency Band Propagation button under the Subcells section of the TRXs tab of a
165
transmitter’s Properties dialog box, and through the Subcells > Multi‐Band Propagation Parameters command in the context
menu of the Transmitters folder.
In the Multi‐Band Propagation Parameters table and in the database, Atoll uses the "@" character to identify the multi‐band
transmitters. Therefore, if you are working on a document with multi‐band transmitters, and you have the "@" character in
the names of repeaters, remote antennas, or subcells without a donor/main transmitter, Atoll deletes these records when
opening the document from a database. If you do not want Atoll to automatically delete such records when opening the
document from a database, you have to sett the following option in the Atoll.ini file:
[Studies]
RemoveBadMultiCells = 0
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 automatically
delete such records. If you want Atoll to automatically delete such records when opening the document from a database, you
have to sett the following option in the Atoll.ini file:
[Studies]
CleanMultiCellManagement = 1
CleanMultiCellManagement is set to 0 by default.
11.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
HCS
the serving transmitter must be higher than the minimum reception threshold ( T Rec ) 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 T HCS
Rec
HCS
is the highest. Where, T Rec 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:
[Studies]
UseThresholdForSameLayerPriorities = 0
UseThresholdForSameLayerPriorities is set to 1 by default.
11.1.7.8 Hiding AFP Advanced Parameters
You can hide advanced parameters in the Atoll AFP Properties dialog box by adding the following lines in the Atoll.ini file:
[AFP]
SimpleUserGUI = 1 #Default=0
When SimpleUserGUI is set to 1, the Interference Matrices, Finalisation, and Advanced tabs do not appear.
11.1.7.9 Hiding AFP Hopping Parameters
You can hide hopping parameters in the Atoll AFP Properties dialog box by adding the following lines in the Atoll.ini file:
[AFP]
HideHopping = 1 #Default=0
When HideHopping is set to 1, the HSN and MAL tabs as well as the MAIO frame on the Reuse tab do not appear.
166
11.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. This
importance can be evaluated during the automatic neighbour allocation, a specific calculation process or manually populated
in the neighbour tables. In the Allocation tab of the AFP results dialog box, no difference is made between high and low
importance neighbours in term of violation display. In other words, whatever the importance value is, any neighbour link in a
separation violation is systematically displayed in a specific colour. You can avoid displaying separation violations between
low importance neighbours in a specific colour by adding the following lines in the Atoll.ini file:
[GSM]
MinNeighbourImportanceInAFPResults = XX
Where XX is the minimum importance for a neighbour pair to be considered as potentially violated.
The value in the Atoll.ini file has to be between 0 and 100 whereas the importance value
in the neighbours tables is between 0 and 1.
11.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 be
identified over the entire duration of a GSM frame. As an example, when the synchronisation site, the HSN and the MAL length
of 2 MALs‐MAIOs are identical, it is always possible to identify if these are or not in separation violation. In case the
synchronisation site, the HSN and/or the MAL lengths or 2 MALs‐MAIOs are different, a certain probability of collision (and
consequently a separation violation) may occur.
You can avoid displaying separation violations between non‐synchronised MALs‐MAIOs in a specific colour by adding the
[GSM]
ShowNonSynchSFHViolationsInAFPResults = 0
ShowNonSynchSFHViolationsInAFPResults is set to 1 by default. Setting ShowNonSynchSFHViolationsInAFPResults to 0 does
not show non‐synchronised (MALs‐MAIOs) possibly in a separation violation case.
11.1.7.12 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 separation
constraint violation. You can modify the thresholds above which the important violations will be highlighted by adding the
[GSM]
CoRedColorThreshPercent = 12
AdjRedColorThreshPercent = 15
CoRedColorThreshPercent (for co‐channels) and AdjRedColorThreshPercent (for adjacent channels) are set to 12 and 15 by
default. 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 where
important and less important violations were both highlighted.
11.1.7.13 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.ini
file:
[AFP]
WorstCaseIM_FskAfp = 0 or 1
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 second
method.
• Worst Case Method: For each interference matrix relationship, the worst case value in all the active interference
matrices is taken into consideration.
167
• First Value Method: For each interference matrix relationship, the first value found in any active interference matrix
is taken into consideration. The order in which the interference matrices are scanned to find the first value is the order
of the interference matrices in the Interference Matrices folder in the Network tab, i.e. the first IM is the one at the
top.
The First Value method was the default method in earlier versions of Atoll which allowed multiple interference matrix import.
11.1.7.14 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 consideration
for each transmitter in order to ensure that performance is not degraded. In this example, the number is limited to 70:
[AFP]
GlobalDistanceMatrixDegreeUB = 70
11.1.7.15 Changing the Level of Intermodulation Products Checked by AFP in GSM
In GSM networks, you can force AFP to avoid allocating frequencies that generate intermodulation products up to the 9th
order (in case of 3 frequencies) by setting the following option:
[gAFP]
HighestOrderToCheck_with3frequencies = 9 #Default=5
11.1.7.16 Changing the Level of Intermodulation Products Checked by AFP in TETRA
In TETRAPOL and iDEN networks, you can force AFP to avoid allocating frequencies that generate intermodulation products
up to the 9th order (in case of 3 or 4 frequencies) by setting the following options:
[gAFP]
If you want, you can also force the AFP to consider only the intermodulation products in the uplink by setting the following
option:
[gAFP]
onlyUpLinkIntermodulationProducts = 1 #Default=0
11.1.7.17 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 table
might cause inconsistencies between the two tables in some cases. You can make these redundant fields uneditable in the
Transmitters table by adding the following lines in the Atoll.ini file:
[GSM]
CanEditTRXInfoAtTXLevel = 0
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.
11.1.7.18 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 the
Atoll.ini file:
[Studies]
2GTxDiversityGain = X
Where X is the value of the air‐combining gain in dB.
11.1.7.19 Deactivating Frequency Band Filtering in IM Calculation
When calculating interference matrices, Atoll filters potential interferers based on the frequency bands used by the interfered
and interfering subcells. For example, if the interfered subcell uses the GSM900 band and a potential interferer uses the
168
GSM1800 band, and the two bands do not overlap, then this potential interferer is ignored. This filtering helps improve the
calculation performance by ignoring the interfered‐interferer pairs that would have eventually resulted in no IM entry after
the calculation. Any interferer whose assigned frequency band overlaps with the frequency band assigned to the interfered
subcell is not filtered.
You can deactivate this filtering by adding the following lines in the Atoll.ini file:
[IM]
FilterByFrequencyBands = 0
FilterByFrequencyBands is set to 1 by default.
11.1.7.20 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 the
Atoll.ini file:
[GSM]
FirstTRXIndex = 1
FirstTRXIndex is set to 0 by default. Setting FirstTRXIndex to any other value has the same effect as setting it to 1.
11.1.7.21 Hiding the TRX Index
If you wish to hide the TRX index column, add the following lines in the Atoll.ini file:
[GSM]
TRXIndexHidden = 1
TRXIndexHidden is set to 0 by default.
11.1.7.22 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 the
[GSM]
WideRangeSubcellThresholds = 1
WideRangeSubcellThresholds is set to 0 by default, which corresponds to the default value ranges.
11.1.7.23 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:
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
If you wish to modify this default behaviour, add the following lines in the Atoll.ini file:
[GSM]
169
SubcellValueFixMethod = 1
SubcellValueFixMethod is set to 0 by default, which corresponds to the default behaviour described above.
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 the
default behaviour. Likewise, if it is greater than ‐50 dBm, it will be replaced by ‐50 dBm instead of ‐102 dBm.
11.1.8 UMTS HSPA, CDMA2000, and TD‐SCDMA Options
11.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 is
also the last carrier in the global parameters. To do this, add the following lines in the Atoll.ini file:
[3GCells]
NoSuffixIfUniqueCarrier = 0 or 1
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 only
one 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 the
transmitter names, SiteN_X.
11.1.8.2 Disabling Macro‐diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt
In UMTS HSPA and CDMA2000 documents, macro‐diversity gains are calculated by default for pilot Ec/Io, DL and UL Eb/Nt
based on their respective standard deviations.
You can deactivate the calculation and use of macro‐diversity gains for all of the above by adding this option in the Atoll.ini file:
[Shadowing]
WithSHOGain = 0 #Default=1
If you want, you can deactivate macro‐diversity gain calculations for pilot Ec/Io only by adding this option in the Atoll.ini file:
[CDMA]
AddPilotSHOGain = 0 #Default=1
11.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 HSDPA
throughputs per mobile, cell, and site in simulation results. To do this, you can add the following lines in the Atoll.ini file:
[CDMA]
HSDPAThroughputPeak = 0 or 1
• 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 on the MUG tab of the Proportional Fair properties. Inputs from this is 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 into
account the MUG corresponding to the current number of connected HSDPA users.
In Average Simulation results, the average HSDPA throughput per user can be calculated excluding the simulations where no
HSDPA users were served. To do this, add the following lines in the Atoll.ini file:
170
[CDMA]
HSDPAAvgSimuResults = 1
HSDPAAvgSimuResults = 0 by default.
11.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 instruct
Atoll to use maximum power in stead by adding the following lines in the Atoll.ini file:
[CDMA]
PmaxInIntraItf = 1
• 0: Intra‐cell interference calculation based on total power (Default)
• 1: Intra‐cell interference calculation based on maximum power
11.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 following
[CDMA]
UseStudyCnxProba = 1
MinUsersPerBin = X
This coverage prediction study is available in the list of prediction studies if UseStudyCnxProba is set to 1. Otherwise, it will
not be available. MinUsersPerBin is the minimum number of users per pixel required for that pixel to be taken into account
in the coverage prediction.
11.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 calculating
HS‐PDSCH CQI in Atoll by adding the following lines in the file:
[CDMA]
CQIDeltaWithPower = 0 or 1
CQIDeltaWithPower is set to 1 by default. In this case, the HS‐PDSCH CQI is calculated using the formula:
 CQI  HS – PDSCH =  CQI  pilot – P pilot + P HS – PDSCH
If you set CQIDeltaWithPower to 0, the HS‐PDSCH CQI will be calculated using the formula:
EC EC
 CQI  HS – PDSCH =  CQI  pilot –  ------- +  -------
 N T pilot  N T HS – PDSCH
Note that the default configuration (CQIDeltaWithPower set to 1) is relevant only when N T is calculated using the "Total
Noise" option.
The above equations are in dB. Refer to the Technical Reference Guide for more details.
11.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 the
CPICH physical channel only and models the loss of energy in the CPICH signal due to multipath. The Orthogonality Factor is
related 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
[CDMA]
OrthoInCPICH = 1
171
11.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.ini
file:
[CDMA]
MaxRejections = X
If a mobile is rejected X number of times, it will no longer be considered in the next iterations.
11.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 considered
permanently 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:
[CDMA]
HSDPAMaxRejections = X
Where X is the number of times an HSDPA mobile should be rejected to be considered permanently rejected for the
simulation.
11.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:
[CDMA]
CutOffSimu = X
Where, X is the offset value in dBs. During Monte Carlo simulations, calculations performed on each mobile only take into
account the cells whose received power, at the mobile location, is greater than the thermal noise minus this offset. You should
set CutOffSimu to 20 dB for optimum performance without losing a lot of interference.
11.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 a
distribution of users according to the traffic densities and the connection probabilities. The accuracy of this conversion from
vectors to raster is high enough for most, nearly all, cases. However, this accuracy might not be enough for highly precise
vector 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 and
the raster bin have the same traffic density in the following figure.
Figure 11.1: Rasterisation Process
The primitive libraries, which perform the conversion from vector to raster, deal in terms of float values for the x and y
coordinates 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 same
surface area as the vector polygons. If the coordinates of the vector polygons are not accurate, it is possible that the raster
pixel 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 since
the 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 following
172
[Rasterization]
Improve = 0 or 1
Precision = 1
SurfRatio = 20
MaximumSurf = 2500
The options are:
• Improve = 1 (by default) means that Atoll will use the accurate rasterisation method for small polygons. Improve = 0
means that the normal rasterisation method will be used for all polygons. Setting this option to 1 implies that this
algorithm 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 1
metre. You can set it to a higher value if you observe performance degradation. The step of rasterisation means the
size of the bin used to approximate the vector shape with bins.
If you set Precision = 1, the performance (calculation speed) can be considerably
decreased depending on the size of your network. It is recommended to set a higher
value for the Precision option.
• SurfRatio = 20 (by default) means that the accurate algorithm will be used only for polygons whose size is smaller than
20 times the size of the normal raster bin. The normal raster bin size in an Atoll document is the finest resolution
among the geographic data available in the document.
If your Atoll document contains two geographic data files, one with a 20 m resolution and
the other with a 5 m resolution, and you remove the 5 m one from your document, Atoll
will still keep 5 m as the normal raster bin size.
• MaximumSurf = 2500 (by default) means that a polygon will be considered small only if its surface area is less than or
equal 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 area
to 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.
11.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 this
option is 30. To modify the default value, enter the following lines in the Atoll.ini file:
[CDMA]
IterBeforeDown = X
Where X is the integer number of iterations.
11.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 the
Atoll.ini file:
[CDMA]
PFSchedulerCQIFactor = X
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.
11.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 server
for all the mobiles, connected or rejected. To display the Ec/I0 from the best server for the rejected mobiles, add the following
173
[CDMA]
DisplayEcIoOfRejected = 1
DisplayEcIoOfRejected is set to 0 by default.
11.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 carrier
within 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:
[CDMA]
MultiBandSimu = 0
MultiBandSimu is set to 1 by default.
11.1.8.16 Switching Back to the Old Radio Bearer Allocation Algorithm for Multi‐
carrier EVDO Rev.B
Before Atoll 3.2.1, radio bearer allocation for multi‐carrier EVDO Rev.B used to be performed by equally sharing the available
terminal power between the carriers.
To switch back to this radio bearer allocation method, add the following lines in the Atoll.ini file:
[CDMA]
SharingEquallyPower = 1
UsingPreviousIterationPowerWeight = 1
These two options are set to 0 by default.
11.1.8.17 Displaying Automatic Allocation Cost Values
You can display the cost values calculated by Atoll for different relations when allocating scrambling codes and PN offsets. To
display cost values, add the following lines in the Atoll.ini file:
[PSC]
DisplayCostValues = 1
DisplayCostValues is set to 0 by default.
11.1.8.18 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 strategies
that will be available to the user in the automatic allocation dialog box. To select the allocation strategies, add the following
[CDMA]
CodeStrategies = 1, 2, 3, 4
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
174
11.1.8.19 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 a
distributed strategy (Distributed per Cell or Distributed per Site). To apply the defined interval, add the following lines in the
Atoll.ini file:
[PSC]
ConstantStep = 1
ConstantStep is set to 0 by default.
11.1.8.20 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 equipment
does not support compressed mode, by adding the following lines in the Atoll.ini file:
[Neighbours]
CompressModeEval = 1
CompressModeEval is set to 0 by default.
11.1.8.21 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 coverage
prediction by adding the following lines in the Atoll.ini file:
[Studies]
SCActivesetMaxSize = X
Where X is the maximum number of transmitters in the active set. If you set SCActivesetMaxSize = 10, you will get the same
results in the coverage prediction as the SC Interference tab in the point analysis.
11.1.8.22 Displaying Uplink Total Losses in Coverage by Signal Level
In UMTS, CDMA, LTE, WiMAX, and Wi‐Fi technologies, you can activate the Uplink Total Losses and Minimum Uplink Total
Losses display options in the Coverage by Signal Level (DL) prediction by adding the following lines in the Atoll.ini file:
[Studies]
UplinkLosses = 1
UplinkLosses is set to 0 by default. Uplink total losses are calculated from the downlink total losses by replacing the downlink
transmitter losses by uplink transmitter losses. In GSM, the Uplink Total Losses display options is available in the Coverage by
Signal Level (UL) prediction.
11.1.8.23 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 per
HSUPA user. This can cause unnecessary rejection of some HSUPA users in very low traffic cases. You can set an upper limit
for the uplink reuse factor by adding the following lines in the Atoll.ini file:
[UMTSSimus]
MaxReuseFactor = X
MaxReuseFactor is set to 5 by default.
11.1.9 LTE, WiMAX, and Wi‐Fi Options
11.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,
175
[WiMAX]
ModifiableIEEEParams = 0
By default, ModifiableIEEEParams is set to 1, which means that all the parameters are modifiable. When you set
ModifiableIEEEParams 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 of
Subchannels per Channel.
• In the Permutation Zones table: Subchannel Groups (Segment 0), Subchannel Groups (Segment 1), and Subchannel
Groups (Segment 2) for FFT sizes < 1000.
In the Permutation Zones table, the first DL PUSC permutation zone cannot be
deactivated.
• In the Frame Configurations table and in the General tab of the frame configurations Properties dialog box:
Number of Preamble Subcarriers.
In the Frames Configurations table, the cells under Total Number of Subcarriers change
into combo boxes with the following five values: 128, 256, 512, 1024, 2048.
11.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,
[OFDM]
UseCommonBearersOnly = 1
UseCommonBearersOnly is set to 0 by default. When UseCommonBearersOnly is set to 1, Atoll only uses the bearers for
which selection thresholds are defined in both the terminal’s and the cell’s equipment for both downlink and uplink bearer
selection.
11.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 per
subcarrier. If desired, you can also use a point analysis to display SS & PBCH per subcarrier and PDCCH & PDSCH per subcarrier
[LTE]
DisplaySignalsPerSCInPtA = 1
DisplaySignalsPerSCInPtA is set to 0 by default. When the DisplaySignalsPerSCInPtA option is set to "0" or is absent, SS & PBCH
per subcarrier and PDCCH & PDSCH per subcarrier are not available options in a point analysis.
11.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 corresponding
to the cyclic prefix part of the total symbol duration. However, you can include the cyclic prefix energy in the useful signal level
calculation by adding the following lines in the Atoll.ini file:
[LTE]
ExcludeCPFromUsefulPower = 0
ExcludeCPFromUsefulPower is set to 1 by default.
Independant of the option, interference levels are calculated for the total symbol durations, including the energy useful
symbol duration and the cyclic prefix energy.
176
11.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 the
[WiMAX]
ExcludeCPFromUsefulPower = 1
ExcludeCPFromUsefulPower is set to 0 by default.
Independant of the option, interference levels are calculated for the total symbol durations, including the energy useful
symbol duration and the cyclic prefix energy.
11.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 indexes
assigned to neighbours of a cell. This means that Atoll tries to not allocate the same preamble index to two neighbours of a
cell. If you want to disable this constraint, i.e., allow Atoll to allocate the same preamble index to two neighbours of a cell,
[WiMAX]
InterNeighbourPICollisions = 0
InterNeighbourPICollisions is set to 1 by default.
The preamble index audit based on neighbours also takes this option into account. With InterNeighbourPICollisions = 1, the
audit lists the cell pairs that are neighbours of a cell and are allocated the same preamble index. When
InterNeighbourPICollisions = 0, the preamble index collision is not verified between neighbours of a cell.
11.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 assigned
to neighbours of a cell. This means that Atoll tries to not allocate the same physical cell ID to two neighbours of a cell. If you
want to disable this constraint, i.e., allow Atoll to allocate the same physical cell ID to two neighbours of a cell, add the
[LTE]
InterNeighbourIDCollisions = 0
InterNeighbourIDCollisions is set to 1 by default.
The physical cell ID audit based on neighbours also takes this option into account. With InterNeighbourIDCollisions = 1, the
audit lists the cell pairs that are neighbours of a cell and are allocated the same physical cell ID. When
InterNeighbourIDCollisions = 0, the physical cell ID collision is not verified between neighbours of a cell.
11.1.9.8 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 adding
the following lines in the Atoll.ini file:
[WiMAX]
ReplaceOPUSCwithPUSCUL = 1
ReplaceOPUSCwithPUSCUL is set to 0 by default.
11.1.9.9 Deactivating Uniform Distribution of Resources
By default, the basic automatic allocation of physical cell IDs and preamble indexes distributes the allocated resources
uniformly. If you wish to deactivate the uniform distribution of resources, add the following lines in the Atoll.ini file:
[OFDM]
UniformIDDistribution = 0
UniformIDDistribution is set to 1 by default.
177
11.1.9.10 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 order
neighbours into account when allocating preamble indexes and downlink and uplink zone permbases. If you want the AFP to
take both first and second order neighbours into account, add the following lines in the Atoll.ini file:
[OFDM]
SecondNeighbours = 1
SecondNeighbours is set to 0 by default.
11.1.9.11 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 of
adjacent channel overlap in resource allocation, add the following lines in the Atoll.ini file:
[OFDM_AFP]
AdjacentProtection = 0
AdjacentProtection is set to 1 by default.
11.1.9.12 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):
[LTE]
SameItf_PDSCH_RS_PDCCH = 0
Synchronised transmission and reception means that the OFDM symbols of the interfered and interfering frames
overlap 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:
[LTE]
This method is also used for calculating the interference received from LTE cells of an external network in co‐planning
mode, i.e., inter‐technology interference received from LTE cells calculated using the inter‐technology IRFs.
For more information, see the Technical Reference Guide.
11.1.9.13 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 the
interfering cells. If you wish to set the PDCCH to 100% loaded, i.e., only weight the interference from PDSCH by the downlink
traffic load and not the interference from the PDCCH, add the following lines in the Atoll.ini file:
[LTE]
ApplyDLLoadOnPDCCHInterf = 0
ApplyDLLoadOnPDCCHInterf is set to 1 by default. This option is only relevant when SameItf_PDSCH_RS_PDCCH is set to 1.
178
11.1.9.14 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 to
calculate the EIRP from the Reference Signal EPRE instead, add the following lines in the Atoll.ini file:
[LTE]
EIRPfromRSEPRE = 1
EIRPfromRSEPRE is set to 0 by default. This option applies to Coverage by Transmitter, Coverage by Signal Level, and
Overlapping Zones predictions in LTE.
11.1.9.15 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 to
calculate the average by directly using the noise rise values in dB, add the following lines in the Atoll.ini file:
[OFDM_SIMU]
MeanNRInDB = 1
MeanNRInDB is set to 0 by default.
11.1.9.16 Deactivating Service Max Throughput Demand Downgrading in LTE
Service maximum throughput demand downgrading is active by default in LTE Monte Carlo simulations, only for mobiles not
performing carrier aggregation. If you wish to deactivate this downgrading, add the following lines in the Atoll.ini file:
[LTE]
ServiceMBRDowngrading = 0
ServiceMBRDowngrading is set to 1 by default.
11.1.9.17 Displaying Pixels with Zero Throughput in Coverage Predictions
In throughput coverage predictions, pixels are coloured according to the defined throughput threshold colours if there are
bearers 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:
[OFDM]
DisplayThroughputZero = 1
DisplayThroughputZero is set to 0 by default.
11.1.9.18 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 part
of the simulation convergence criteria. For best effort noise rise control, you can modify the noise rise control margin through
Atoll.ini file by adding the following lines:
[LTE]
NR_CONTROL_MARGIN_MIN = X
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 rise
control method from best effort to strict by setting the following option in the Atoll.ini file:
[LTE]
ULNRControlMethod = 1
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 adding
the following lines:
[LTE]
ULNRControlPrecision = X
179
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.
11.1.9.19 Using the ABS Patterns on Cell‐edge Only
By default, ABS patterns are used throughout the cell, irrespective of the cell‐edge area and the cell‐edge traffic ratio. If you
wish to apply ABS patterns only on the cell‐edges, you can do so by adding the following lines in the Atoll.ini file:
[LTE]
UseABSonCellEdgeOnly = 1
By default, UseABSonCellEdgeOnly is set to 0. Applying the ABS patterns only on the cell‐edge means that all subframes are
considered non‐ABS subframes in the cell centre. This method enables you to include the cell‐edge traffic ratio in the
calculation of interference.
11.1.9.20 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 generate
certain amount of interference. The 3GPP defines further enhanced ICIC (FeICIC) as the possibility for some advanced
receivers to eliminate interference from reference signals on the ABS. If you wish to eliminate interference from reference
signals transmitted on the ABS, add the following lines in the Atoll.ini file:
[LTE]
eICICOnRS = 1
By default, eICICOnRS is set to 0.
11.1.9.21 Enabling Multi‐eNode‐B Carrier Aggregation
By default, Atoll supports intra‐eNode‐B carrier aggregation. This means that, Atoll only selects secondary serving cells from
within the same eNode‐B (belonging to the same site) as the selected primary serving cell of an LTE‐A user. If you wish to
switch to multi‐eNode‐B carrier aggregation, you can do so by adding the following lines in the Atoll.ini file:
[LTE]
CAWithinENB = 0
CAWithinENB is set to 1 by default.
11.1.9.22 Switching Between Carrier Aggregation Scheduling Methods
For their maximum throughput demands, LTE‐A users are scheduled separately on each of their serving cells, primary and
secondary. Each user’s remaining throughput demand (maximum – minimum) is distributed over each of its serving cells
proportionally to the resources available on each serving cell and to the user’s downlink effective RLC channel throughput or
uplink effective RLC allocated bandwidth throughput on each of its serving cell. Within each serving cell, resource allocation
for 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 cells
proportionally only to the resources available on each serving cell, add the following lines in the Atoll.ini file:
[LTE]
CASchedulingMethod = 1
CASchedulingMethod is set to 0 by default.
11.1.9.23 Displaying Grid‐of‐Beam Patterns in Logarithmic Scale
By default, Atoll displays the horizontal patterns of antennas selected as beams in the LTE grid‐of‐beams smart antenna model
properties using a linear scale. If you wish to display these patterns using the logarithmic scale, add the following lines in the
Atoll.ini file:
[GOB_MODEL]
DisplayLinearDiagram = 0
DisplayLinearDiagram is set to 1 by default.
180
11.1.10 3GPP Multi‐RAT Options
11.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 cells
that are neighbours of the same GSM transmitter or UMTS cell. If you wish to disable the inter‐technology neighbour
constraints in the automatic allocations of BSIC, SC, and PCI, add the following lines in the Atoll.ini file:
[MultiRAT]
AllCodesAllocWithInterRATNeighbours = 0
AllCodesAllocWithInterRATNeighbours is set to 1 by default.
11.1.10.2 Multi‐RAT Technology Selection Default Behaviour
When users open a Multi‐RAT Atoll document, the radio technology selection dialog box appears with all technologies
selected by default. In some cases, you might want to force users to explicitly select the technologies on which they want to
work by making the technologies appear as unselected by default.
If you want the radio technology selection dialog box to appear with no technologies selected by default, add the following
[MultiRAT]
UncheckTechnoChoices = 1
UncheckTechnoChoices is set to 0 by default.
11.1.11 Microwave Radio Links Options
11.1.11.1 Modifying the Default Format of Link Names
By default, Atoll automatically generates link names by using the format <Site A name>‐<Site B name>. In some cases, the site
names might contain characters that are undesirable for a link name (for example, spaces or underscores).
To specify characters that are forbidden when generating the link name, add the following lines in the Atoll.ini file:
[MWLinks]
AutoNameForbiddenChars = list of forbidden characters surrounded by quotes
For example, if AutoNameForbiddenChars is set to "_ ", any new link will be named "SiteName123‐SiteName345" instead of
"Site_Name 123‐Site_Name 345".
AutoNameForbiddenChars is set to "" by default, meaning that no characters are forbidden.
11.1.11.2 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 account
in the B>>A direction in real time. This produces inconsistent results in the 2 directions. If you want to make the profile update
real‐time in both directions, i.e., changes in one direction automatically updated in the other direction, add the following lines
[MWCalculations]
UpdateOppositeHop = 1
UpdateOppositeHop is set to 1 by default.
11.1.11.3 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, add
the following lines in the Atoll.ini file:
[MWCalculations]
ShieldingFactorOnWantedSignal = 0
181
ShieldingFactorOnWantedSignal is set to 1 by default, which means that the shielding factor is taken into account at the
receiver when calculating interference. On the transmitter side, the shielding factor is always taken into account when
calculating interference.
11.1.11.4 Considering XPIF value in Interference for Dual‐Polar Links
If you have dual‐polar links (i.e., a link with 2+0 XPIC configuration and a co‐channel allocation), you can consider XPIF in
interference calculation by adding the following lines to the Atoll.ini file:
[MWCalculations]
CCDP_XPIF = 1
CCDP_XPIF is set to 0 by default, which means that XPIF is considered in the decoupling calculation only. When the option is
set to 1, the XPIF value is considered in the decoupling and it is deducted from the interference level.
11.1.11.5 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 dialog box.
You can make this method available for availability and quality calculations by adding the following lines in the Atoll.ini file:
[MWCalculations]
HIDE_REC530_5 = 0
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 be
available even if HIDE_REC‐5 is set to 1 in the Atoll.ini file.
11.1.11.6 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, one
for 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 all
the 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:
[MWCalculations]
UseProfilesFiles = 0 # (default=1)
• Keep the ATL file on your machine instead of a server to significantly decrease the
calculation time of path profiles.
• This feature is more efficient when the DTM resolution is low, provided that the
calculation 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 not
be used either if they were created before an antenna has become remote.
11.1.11.7 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:
[Compatibility]
MWEquipment_CIMIN = 1
MWEquipment_CIMIN is set to 0 by default.
11.1.11.8 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 increasing
the tab value. To do that, add the following lines in the Atoll.ini file:
[MWReport]
tab = 2000 # Default value is 500
182
11.1.11.9 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:
[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
Where each of the above options corresponds to a specific Report Configuration dialog box:
• DesignSummaryCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button ( ) from the Design Summary view (MW Analysis window).
• LinkAnalysisCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button from the Analysis Report view (MW Analysis window).
• LinkInterferenceCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button from the Interference Report view (MW Analysis window).
• RequiredMarginCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button from the Required Margin view (MW Analysis window).
• LinksBudgetCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave Radio Links
> Links > Link Budgets > Configuration Report from the Network explorer.
• LinksInterferenceCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave Radio
Links > Links > Interference > Configuration Report from the Network explorer.
• MultihopAnalysisCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave Radio
Links > Multi‐Hops > [Multi‐Hop X] > Analysis from the Network explorer.
• ReflectionAnalysisCfg: corresponds to the Report Configuration dialog box 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).
11.1.11.10 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 the
Atoll.ini file:
[MWChannelArrangement]
DefaultConfiguration = path to the channel arrangement default configuration file
Where the above option corresponds to the Channel Arrangement dialog box displayed after selecting Microwave Radio
Links > Interference > Channel Arrangement > Display on Map from the Network explorer.
11.1.11.11 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.ini
file:
[MWReport]
DefaultTemplate = path to the default template for microwave links custom reports
11.1.12 Measurement Options
11.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)
183
You have to add the following lines in the Atoll.ini file to display this information:
[TestMobileData]
ShowCoupleInfo = 1
Setting ShowCoupleInfo to 0 hides this information.
11.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 neighbour
transmitters (or cells in CDMA documents) for drive test data paths. You can change the number of transmitters per drive test
data path by adding the following lines in the Atoll.ini file:
[TestMobileData]
NumberOfTestMobileTransmitters = X
Where X is the number of transmitters per drive test data path. The default value of NumberOfTestMobileTransmitters is 7.
11.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 following
[TestMobileData]
RecalcDist = 1 or 0
The default value of RecalcDist is 1, which means that Atoll will calculate the distance for each measurement point. The
nearest 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.
11.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 columns
should be imported as the BCCH column and which one as the BSIC column in Atoll, you can add the following lines in the
Atoll.ini file:
[TestMobileDataImportFmt]
BCCHColumn = Column1
BSICColumn = Column2
Where, Column1 and Column2 are the titles of the two columns in the .fmt file corresponding to the BCCH and the BSIC
columns respectively.
11.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 following
option in the Atoll.ini file:
[TestMobileData]
FloatingPointScramblingCodeSupport = 1
FloatingPointScramblingCodeSupport is set to 0 by default, and the scrambling codes are imported according to the numeric
data type selected for the scrambling code column in the import dialog box.
11.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 cell
identification method defined for the import. By default, Atoll takes all the transmitters and cells of the document into
account, whether they are active or inactive and filtered or not. If you want Atoll to take only active and filtered transmitters
and cells into account for drive test data import, add the following option in the Atoll.ini file:
[TestMobileData]
ImportForFilteredTransmittersOnly = 1
ImportForFilteredTransmittersOnly is set to 0 by default.
184
11.1.12.7 Specifying the Location of the ACP.ini File
For the most part, you can configure the ACP with its own initialisation file: the ACP.ini. However, there are a few options that
you can set in the Atoll.ini to configure the ACP.
By default, Atoll ACP uses the global ACP.ini file, located in the installation directory of Atoll. You can set an option in the
Atoll.ini file to define a different location for the ACP.ini file. This option is useful for assigning a different ACP initialisation for
a different group of users.
To use another location, add the following line to the Atoll.ini file:
[ACP]
iniFile = /path/to/the/ACP.ini
11.2 ACP Initialisation File
The ACP initialisation file is used to inform Atoll of the preferred settings when the ACP is used for automatic cell planning
during 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 ("#").
The ACP initialisation file is a powerful tool. You should not modify any option in the
acp.ini file until and unless you are absolutely sure of what you are doing.
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 185:
11.2.1 Managing ACP Preferences
Some of the settings provided in the acp.ini file can be modified directly using the ACP ‐ Automatic Cell Planning Properties
dialog box, under ACP Automatic Cell Planning on the Setup Template tab. ACP either embeds these settings directly in the
ATL document or in a user‐defined acp.ini file. These settings are referred as "local settings". Local settings are the settings
found in sections using the "Tpl" keyword, such as [ACPTplGeneralPage].
• The local settings, defined using the ACP ‐ Automatic Cell Planning Properties
dialog box, take precedence over the same settings defined in the global acp.ini
file. The settings in the acp.ini file are read when you start a new project to
initialise the settings of the ACP.
• When using the acp.ini file to define options, instead of using the ACP ‐
Automatic Cell Planning Properties dialog box, you can also define any other
settings even if they can not be set using the ACP ‐ Automatic Cell Planning
Properties dialog box. These settings redefined locally have precedence over the
global settings.
11.2.2 ACP GUI Options
In this section are the settings defining default values and certain aspects of the GUI configuration. These settings are local
and are usually defined using Setup Template tab of the ACP ‐ Automatic Cell Planning Properties dialog box, and stored
either in the Atoll project or a local acp.ini file.
11.2.2.1 Default Settings of the Optimisation Tab
The following options can be used to set default settings for the number of iterations and the resolution:
[ACPTplGeneralPage]
nbIteration=100
resolution=50
11.2.2.2 Default Settings of the Optimisation > Cost Control Tab
The following options can be used to define the default settings for the calculation of costs:
185
[ACPTplGeneralPage]
cost.type=0 # 0=off, 1=limt_to_max, 2=apply_cost_to_change_plan
cost.unit=<unit> # <unit>=$, yen, etc. (less than 4 characters recommended)
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
11.2.2.3 Default Settings of the Optimisation > Advanced Cost Control Tab
The following options can be used to define the default settings for advanced cost control. Advanced cost control options
allow you to define the maximum number of changes to be made (either as a value or a ratio) and to change the ranking of
the order of cost in the final implementation plan.
The option below allows you to display the Advanced label under Cost Control in the left‐hand pane of the Optimisation tab.
[ACPGeneralPage]
enableAdvancedCost=1 #Default=0
The following option enables you to define the importance of cost in the implementation plan:
[ACPTplGeneralPage]
cost.planCostWeighting=0,1,2 #0=low, 1=medium (default), 2=high
The following option enables you to specify the number of changes in the implementation plan:
[ACPTplGeneralPage]
cost.planLimitType=0,1,2 #0=unlimited, 1=max as absolute value, 2=max as ratio
• If cost.planLimitType is set to 0 (default), then the number of changes is unlimited.
• If cost.planLimitType is set to 1, then cost.planChangeMax must be specified to define the maximum number of
changes in the implementation plan as an absolute value:
[ACPTplGeneralPage]
cost.planLimitType=1
cost.planChangeMax=10
• If cost.planLimitType is set to 2, then cost.planChangePercent must be specified to define the maximum number of
changes in the implementation plan as a ratio of the number of antennas currently available in the computation zone:
[ACPTplGeneralPage]
cost.planLimitType=2
cost.planChangePercent=20
186
When cost.planLimitType is set to 2, you can also set cost.planChangeRefZone to 1 in the [ACPGeneralPage] section
to define the focus zone as the reference zone instead of the computation zone:
[ACPGeneralPage]
cost.planChangeRefZone=1 #0=computation zone (default), 1=focus zone
11.2.2.4 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 on
the 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:
[ACPGeneralPage]
zone.autobuildHotspot=1 # Automatically build hotspot from Atoll hotspot (default)
The following options can be used to automatically create ACP custom zones from one or more clutter classes or from a SHP
file:
[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.clutters=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)
zone.1.file=c:\path\to\file.shp # Absolute path to the SHP file.
11.2.2.5 Default Settings of the Objectives Tab
In the [ACPTplObjectivePage] section are the settings defining default settings of the Objectives tab.
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.):
[ACPTplObjectivePage]
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
187
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.cinr.isShadowing=no
param.lte.cinr.cellEdgeCov=0.75
param.lte.cinr.useFreqBand=1
param.lte.cinr.useICIC=1
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.cinr.autoPrediction=yes
param.wimax.cinr.isShadowing=no
param.wimax.cinr.cellEdgeCov=0.75
param.wimax.cinr.useFreqBand=1
param.wimax.cinr.useSegmentation=1
param.wifi.overlap.autoPrediction=yes
param.wifi.overlap.margin=5
param.wifi.overlap.minRxLevel=-105
param.wifi.coverage.autoPrediction=yes
param.wifi.coverage.isShadowing=no
param.wifi.coverage.cellEdgeCov=0.75
param.wifi.cinr.autoPrediction=yes
param.wifi.cinr.isShadowing=no
param.wifi.cinr.cellEdgeCov=0.75
The following options are used to define the default threshold for each objective rule:
[ACPTplObjectivePage]
quality.gsm.bcch.threshold=-85
quality.gsm.overlap.threshold=4
quality.gsm.distance.threshold=5000
quality.umts.rscp.threshold=-85
quality.umts.ecio.threshold=-13
quality.umts.overlap.threshold=4
quality.umts.distance.threshold=5000
quality.cdma.rscp.threshold=-85
quality.cdma.ecio.threshold=-13
quality.cdma.overlap.threshold=4
quality.cdma.distance.threshold=5000
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.rssi.threshold=-80
quality.lte.overlap.threshold=5
quality.lte.distance.threshold=5000
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.wimax.distance.threshold=5000
188
quality.wifi.coverage.threshold= -85
quality.wifi.c.threshold=-85
quality.wifi.cn.threshold=20
quality.wifi.cinr.threshold=10
quality.wifi.overlap.threshold=5
quality.wifi.distance.threshold=5000
The following option is used to remove the Capacity and Load Balancing features from the Objectives tab:
[ACPCapacityPage]
enable=0 (default=1 => capacity and load balancing enabled)
The following option is used to clear the Scale Traffic according to Zone Weighting check box on the Capacity page of the
Objectives tab:
[ACPTplCapacityPage]
useZoneWeight=0 (default=1 => zone weighting applied on capacity traffic)
The following options are used to define a capacity traffic map, either by a BIL file or by a comma‐separated list of traffic map
names:
traffic.file=c:\tmp\traffic.bil
traffic.maps=User density traffic map; environment map
traffic.resolution=50
The following options are used to define the default threshold for each quality (Objectives tab > Capacity page > Services
Definition frame):
quality.gsm.bcch.threshold=-85
quality.umts.rscp.threshold=-85
quality.umts.ecio.threshold=-13
quality.cdma.rscp.threshold=-85
quality.cdma.ecio.threshold=-13
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
quality.lte.rssi.threshold=-80
The following options are used to define the default quality used by each technology for traffic capture condition:
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
service.density=30
The following option is used to enable the load balancing feature by default:
189
loadBalancing.enable=1 (default setting is 0 => load balancing feature disabled)
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
loadBalancing.targetZoneIdx=-2
loadBalancing.target=80
loadBalancing.weight=1
11.2.2.6 Default Settings of the Reconfiguration page
In the [ACPTplReconfPage] section are the settings defining default settings of the Reconfiguration page.
The following options enable you to define the default reconfiguration that will be done: power, antenna, azimuth, or
mechanical tilt optimisation.
When the options in this section are set to 1, the default reconfiguration option is not
selected. 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.1xrtt.SyncSiteMultiCellPower=0
cdma.1xrtt.disablePilotPowerOptimisation=1
cdma.1xrtt.disableMaxPowerOptimisation=1
cdma.1xevdo.SyncMultiCellPower=1
cdma.1xevdo.SyncSiteMultiCellPower=0
cdma.1xevdo.disableMaxPowerOptimisation=1
cdma.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
gsm.disablePowerOptimisation=1
gsm.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
wimax.disablePreamblePowerOptimisation=1
wimax.SyncMultiCellPower=1
wimax.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
lte.disablePowerOptimisation=1
lte.SyncMultiCellPower=1
lte.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
The following options are used to define the default reconfiguration that will be done on transmitters and sites:
[ACPTplReconfPage]
disableAntennaOptimisation=1
disableETiltOptimisation=1
disableAzimuthOptimisation=1
disableMechTiltOptimisation=1
disableSiteSelection=1
The following options are used to specify default settings of the reconfiguration ranges:
190
[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.disablePilotPowerOptimisation=0
umts.disableMaxPowerOptimisation=0
The following option can be used to display an additional constraint on the Reconfiguration > Transmitters vertical tab that
will be applied to electrical tilt changes.
[ACPReconfPage]
tx.etilt.deltaLimitConstraint.show=1 #(default=0)
When tx.etilt.deltaLimitConstraint.show=1, the Variation + column appears under Electrical Tilt (deg).
You can enter a value next to the Variation + header or add the following lines in ACP.ini to define a default value:
[ACPTplReconfPage]
etilt.deltaLimitConstraint=1,2,... #(default=0)
• If etilt.deltaLimitConstraint=0, the variation constraint is disabled and the Variation + column is greyed.
• If etilt.deltaLimitConstraint=1,2,..., the constraint is enabled and the following appears under Variation +:
• A check box which must be selected in order for the constraint to be considered.
• A range determined by the value under Current and the value indicated next to the Variation + header.
The Variation + constraint determines one range and the specified Min. and Max. limits determine another range.
The final electrical tilt will fall within the intersection of the two ranges.
will be applied to mechanical tilt changes.
[ACPReconfPage]
tx.tilt.deltaLimitConstraint.show=1 #(Default=0)
When tx.tilt.deltaLimitConstraint.show=1, the Variation + column appears under Mechanical Tilt (deg).
[ACPTplReconfPage]
tilt.deltaLimitConstraint=1,2,... #(Default=0)
• If tilt.deltaLimitConstraint=0, the variation constraint is disabled and the Variation + column is greyed.
• If tilt.deltaLimitConstraint=1,2,..., the constraint is enabled and the following appears under Variation +:
• A range determined by the value under Current and the value indicated next to the Variation + header.
The final mechanical tilt will fall within the intersection of the two ranges.
will be applied to global tilt changes (electrical + mechanical).
191
[ACPReconfPage]
tx.etilt.tilt.sum.deltaLimitConstraint.show=1 #(Default=0)
When tx.etilt.tilt.sum.deltaLimitConstraint.show=1, ETilt + MTilt (deg) appears with Current and Variation + columns.
[ACPTplReconfPage]
etilt.tilt.sum.deltaLimitConstraint=1,2,... #(Default=0)
• If etilt.tilt.sum.deltaLimitConstraint=0, the variation constraint is disabled and the Variation + column is greyed.
• If etilt.tilt.sum.deltaLimitConstraint=1,2,..., the constraint is enabled and the following appears under Variation +:
• A range determined by the value under Current (sum of the values under Current for electrical and mechanical
tilts) and the value indicated next to the Variation + header.
The final gloabl tilt will fall within the intersection of the two ranges.
The following option allows you to reconfigure inter‐sector electrical tilts as asymetrics, i.e. it allows you to obtain different
tilts for sectors belonging to the same site. The value you specify (in degree) is a "minimum difference" constraint if tilts are
reconfigured. If they are not reconfigured, the constraint will not apply.
[ACPTplReconfPage]
etilt.asymetric=1 #(No default)
The following option can be used to automatically disable reconfiguration of all donors (possibly in cascade) of a repeater:
[ACPTplReconfPage]
autoLockDonor=0 #(Default=0)
Possible settings:
Value Description
0 No auto lock (default).
The Use check boxes for transmitter reconfiguration parameters are cleared (antenna, tilt,
1 azimuth, and height). Only the last repeater in a series of cascading repeaters is optimised; the rest
are cleared by default (but can be selected manually).
The Use check boxes for all reconfiguration parameters are cleared (antenna, tilt, azimuth, height,
2 and power). Only the last repeater in a series of cascading repeaters is optimised; the rest are
cleared by default (but can be selected manually).
5 Same as 1, except that the Use check boxes can not be selected in the user interface.
6 Same as 2, except that the Use check boxes can not be selected in the user interface.
11.2.2.7 Default Settings of the Reconfiguration > Sites vertical tab
In the [ACPTplReconfPage] section are the settings defining the default settings of the Reconfiguration> Sites vertical tab.
The following options enable you to define the reconfiguration options that are selected by default: site removeable, sector
removeable, antenna azimuth, and/or height. The settings of defaultSiteCellsRemoveable, defaultSiteRemoveable, and
defaultSiteHeightLocked also define the default settings in the Station Template Reconfiguration dialog box.
When these options are set to 1, the corresponding reconfiguration options in the user interface are selected by default.
[ACPTplReconfPage]
defaultSiteCellsRemoveable=1
defaultSiteRemoveable=1
defaultSiteAzimuthLocked=1 #Lock Sector/Azimuth
defaultSiteHeightLocked=1 #Lock Sector/height
defaultSiteReconfigurationLocked=1
192
The defaultSiteHeightLocked option is forced to false (0) for sites that have antennas at
different heights.
11.2.2.8 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 Reconfiguration > Sites vertical
tab:
[ACPReconfPage]
site.custom.count=x
site.custom.0.type=tabularDataColumn
site.custom.0.column=FOO
Where ’tabularDataColumn’ displays data issued from Atoll’s SITES table and identified by site.custom.0.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):
[ACPReconfPage]
site.custom.0.label=The Foo Label
11.2.2.9 Default Settings of the Reconfiguration > Transmitters Vertical Tab
In the [ACPReconfPage] section are the settings defining default settings for the display of mechanical and electrical tilts, and
for 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.
[ACPReconfPage]
tx.tilt.asRelative=1 (default=0)
tx.etilt.asRelative=1 (default=0)
The following option is used to display the minimum and maximum electrical tilts only once for each group of linked
transmitters, when the Advanced mode is selected for display.
[ACPReconfPage]
tx.etilt.groupMinMax=1 (default=1)
When tx.etilt.groupMinMax is set to 0, the min/max electrical tilts are displayed for each transmitter.
11.2.2.10 Custom Columns on the Reconfiguration > Transmitters/Remotes tabs
You can use this option to define the number of custom columns to display on the Reconfiguration > Transmitters vertical tab
and the Reconfiguration > Remotes vertical tab:
[ACPReconfPage]
tx.custom.count=2
You can then set the following options to specify the data you want to show under each custom column.
tx.custom.0.type=tabularDataColumn
tx.custom.0.column=FOO
tx.custom.0.label=The FOO label
tx.custom.1.type=elevation #site altitude + transmitter height
tx.custom.1.type=bandwidth #cell bandwidth (only for LTE, WiMAX, and Wi-Fi)
• tabularDataColumn shows data issued from Atoll TRANSMITTERS table, identified by
the required tx.custom.x.column setting.
• Atoll column names are case sensitive.
193
11.2.2.11 Default Settings of the Antenna > Patterns Vertical Tab
In the [ACPAntennaPage] section are the settings defining default settings for the display of additional constraints on
mechanical and electrical tilt values. The following options are used to display these additional constraints:
[ACPReconfPage]
enableMTilt=1 # (default=0)
enableETilt=1 # (default=0)
11.2.2.12 Default Settings of the Optimisation > EMF Exposure Tab
In the [ACPTplEMFPage] section are the settings defining default settings of the Optimisation > EMF Exposure tab.
The following option is used to enable the EMF exposure module:
[ACPTplEMFPage]
enable=1
The following option enables you to define the level of importance accorded to the optimisation of EMF exposure.
[ACPTplEMFPage]
weightLevel=1 #(normal, default)
Possible values:
Value Description
0 Low: EMF exposure is optimised only if does not worsen coverage quality.
1 Normal: There is a trade‐off between EMF exposure and coverage quality (default).
2 Critical: EMF exposure is optimised independently from the effect it may have on coverage quality.
The following options enable you to define the default resolution in metres in the X, Y, and Z planes:
[ACPTplEMFPage]
resolutionXY=5
resolutionZ=3
The following options define how EMF exposure will be measured in buildings: only on the facade or inside the building as
well:
[ACPTplEMFPage]
onlyFacade=1 #only on facade in building propagation classes. Default = 1 (yes)
buildingDeeping=10 #if onlyFacade is set to 0, the depth in the building measured.
The following option defines whether clutter classes and clutter heights are used to create a 3D representation of the terrain
or whether just vectors are to be used. The default is 1 (yes), but, given that vectors are always given priority where they exist,
this option can be disabled if vectors are available for the entire area of interest.
[ACPTplEMFPage]
useDhmFromClutter=1 # Default is 1 (yes)
The following option defines whether the 3D propagation model is using diffraction. When it is not, only positions with a direct
LOS to transmitters will register EMF exposure.
[ACPTplEMFPage]
useDiffraction=0
The following option defines whether the EMF module should use transparent mode. When transparent mode is used, no
obstacle or indoor loss is accounted for.
[ACPTplEMFPage]
isWorstCase=0 # Default is 0 (no)
The following option defines the calculation radius (in metres) around transmitters when calculating EMF exposure:
194
[ACPTplEMFPage]
calculationRadius=300
The following options define the default threshold and weight for the EMF exposure objective:
[ACPTplEMFPage]
defaultObjThreshold=0.6
defaultObjWeight=1
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.
[ACPTplEMFPage]
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
The following options enable you to map clutter classes to propagation classes. Each mapping is defined on two lines: the first
line defines the clutter class (by its code from the Description tab of the Clutter Classes Properties dialog box); the second
line defines the propagation class (by its ID under Propagation on the Optimisation tab of the ACP Setup dialog box). The
default propagation classes in the ACP are "Open" (ID "0"), "Vegetation" (ID "1"), and "Building" (ID "2"). Any additional
propagation classes will have an ID assigned when they are created.
[ACPTplEMFPage]
clutterMapping.count=3
clutterMapping.0.clutterCode=10
clutterMapping.0.classCode=0
In the [ACPEMFPage] section, you can specify whether or not users can define new propagation classes:
[ACPEMFPage]
isPropClassesExtendable=1 # 1 enables user to create propagation classes.
11.2.2.13 Controlling Antenna Pattern Smoothing
Crosswave version 4.0.4 has introduced the AntennaLossesThreshold option to control the smoothing performed on antenna
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:
[ACPGenericPM]
cw.antennaLossesThreshold = X
where X is a value between 0 and 500 specified by AntennaLossesThreshold in Crosswave.ini to increase the specific threshold
applied by Crosswave.
11.2.2.14 Default Settings of the Antenna Tab
The following options enable you to define default regex patterns that will be used to automatically create physical antennas
(from antenna patterns), merge physical antennas, and create antenna groups (from physical antennas):
195
[ACPAntennaPage]
autoGroupPattern=(.*)
autoGroupPattern_ant=(.*)
autoGroupPattern_group=(.*)
By setting the following option to 1 (default), ACP will automatically apply the default antenna configuration each time a new
setup is created (i.e., the configuration which have have been backed up by a user):
[ACPTplAntennaPage]
autoRestoreDefaultConfig=1
By setting the following option to 1, you enable the use of AEDT (additional electrical tilt) for managing different electrical tilt
on each antenna pattern:
[ACPAntennaPage]
enableAedt=1
By setting the following option, you can control the internal logic that ACP uses to assign different antenna patterns to
different frequency bands. ACP considers that an antenna pattern is allowed for a given frequency band if its base frequency
is within the allowed range (in MHz):
[ACPAntennaPage]
freqBandRange=99
11.2.2.15 Defining the Antenna Masking Model
In the [ACPAntMaskModelPage] section, you can find the options used to set the choices available under Antenna Masking
Method on the Setup Template tab of the ACP ‐ Automatic Cell Planning Properties dialog box.
You can use the advancedUI option to display a column called Delegate Calculation to Model. Using the Delegate Calculation
to Model column, you can define whether the ACP calculates the path loss matrices or angles of incidence used in antenna
masking or whether it delegates calculation to the propagation model (providing the propagation model implements the
appropriate methods of Atoll’s API). Delegating calculation to the propagation model provides more accurate results but
might take longer. Additionally, it will use disk space to store the calculation results.
[ACPAntMaskModelPage]
advancedUI=1 #Default=0 ("Delegate Calculation to Model" feature disabled)
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:
[ACPAntMaskModelPage]
nativeAllowFullPathLoss=1 #default=0 (disabled)
11.2.2.16 Defining Reconfiguration Values Using Custom Atoll Fields
In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields in the
relevant tables of the Atoll database. ACP will extract the values entered in the custom fields and use them as default
reconfiguration values when a new optimisation setup is created. The values extracted can be updated in the ACP setup, but
ACP will not update the Atoll tables with the new values.
• By default, ACP does not extract custom fields.
• If a value is undefined in a custom field, ACP will use the default value for that
parameter.
11.2.2.16.1 Defining Reconfiguration Values for Transmitters, Repeaters, and Secondary Antennas
Using Custom Atoll Fields
Transmitters, Repeaters, and Secondary Antennas tables of the Atoll database. This data will be used to initialise the
reconfiguration parameters of transmitters, repeaters, remote antennas, and secondary antennas in the corresponding
technology.
196
The custom columns in the Transmitters, Repeaters, Remotes, and Secondary Antennas tables of the Atoll platform must
match the column names defined in the ACP.ini file.
Some reconfiguration parameters such as height and azimuth can be defined either as
relative 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 value type (i.e., relative or absolute).
[ACPCustomFieldExtraction]
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.etilt.deltamin=acp_etilt_deltamin
tx.etilt.deltamax=acp_etilt_deltamax
tx.tilt.optimize=acp_tilt_use
tx.tilt.min=acp_tilt_min
tx.tilt.max=acp_tilt_max
tx.tilt.deltamin=acp_tilt_deltamin
tx.tilt.deltamax=acp_tilt_deltamax
tx.tilt.step=acp_tilt_step
tx.tilt.sum.optimize=acp_tilt_sum_use
tx.tilt.sum.delta=acp_tilt_sum_delta
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
The following options are NOT valid for the SecondaryAntennas table.
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
The following options are ONLY valid for the GSM Transmitters table.
In GSM, ACP extracts data from custom fields in the GSM Transmitters tables of the Atoll
database and displays it in ACP on the Reconfiguration > GSM Cells vertical tab.
tx.gsm.power.optimize=acp_gsmpower_use
tx.gsm.power.min=acp_gsmpower_min
tx.gsm.power.max=acp_gsmpower_max
197
tx.gsm.power.step=acp_gsmpower_step
The following options are ONLY valid for the Repeaters table.
repeater.gain.optimize=acp_gain_use
repeater.gain.min=acp_gain_min
repeater.gain.max=acp_gain_max
repeater.gain.step=acp_gain_step
11.2.2.16.2 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 in a
technology‐specific "Cells" table of the database. This data will be used to initialise the reconfiguration parameters for cells in
the corresponding technology.
In GSM, ACP extracts data from custom fields in the Transmitters table (not Cells) of the
Atoll database and displays it in ACP on the Reconfiguration > GSM Cells vertical tab. The
relevant options are described in "Defining Reconfiguration Values for Transmitters,
Repeaters, and Secondary Antennas Using Custom Atoll Fields" on page 196.
The following options can be used to extract data from custom fields in the "CDMA2000 cells" table of the database. The
custom columns in the CDMA2000 Cells table of the Atoll platform must match the column names defined in the ACP.ini file.
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
The following options can be used to extract data from custom fields in the "UMTS cells" table of the database. The custom
columns in the UMTS Cells table of the Atoll platform must match the column names defined in the ACP.ini file.
wcell.power.optimize=acp_power_use
wcell.power.min=acp_power_min
wcell.power.max=acp_power_max
wcell.power.step=acp_power_step
The following options can be used to extract data from custom fields in the "LTE cells" table of the database. The custom
columns in the LTE Cells table of the Atoll platform must match the column names defined in the ACP.ini file.
lcell.power.optimize=acp_power_use
lcell.power.min=acp_power_min
lcell.power.max=acp_power_max
lcell.power.step=acp_power_step
11.2.2.16.3 Defining Reconfiguration Values for Sites Using Custom Atoll Fields
"Sites" table of the database. The custom columns in the Sites table of the Atoll platform must match the column name
defined by the settings in the ACP.ini file:
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.
198
• All sites in the Sites table with the label set to the one defined by the site.status.candidate option will be automatically
set as candidate sites.
• Any site in the Sites table with a label other than the one defined by the site.status.candidate option will be considered
as an existing site.
• By default, all active sites are considered as existing sites.
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.
The following options can be used to define custom columns in the Sites table of the Atoll platform. These will be used for
default reconfiguration options for each 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
The following option can be used to manage the Inter Sector Lock check boxes (Height and Azimuth) in the Reconfiguration
column of the Reconfiguration > Sites vertical tab.
site.azimLocked=acp_site_azimLocked
site.heightLocked=acp_site_heightLocked
The following option can be used to manage the Disable check box in the Reconfiguration column of the Reconfiguration >
Sites vertical tab.
site.reconfLocked=acp_site_reconfLocked
11.2.2.16.4 Defining Reconfiguration Values for Antennas Using Custom Atoll Fields
Antennas table of the Atoll database. ACP can use the information in the custom fields to group antennas and to set default
reconfiguration values when a new optimisation setup is created . The custom column in the Antennas table must match the
column 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 groups
of physical antennas (i.e., all patterns related to the same physical antenna) and group the physical antennas at different
frequencies into radomes by using the antenna.model option. Using the antenna.model enables you to automatically form 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.
199
antenna.model=PHYSICAL_ANTENNA
If the physical antenna has been defined using the antenna.model option, the following option can be used to name the
custom column in the Antennas table that is used to define antenna groups. In the custom column in the Antennas table, all
antenna patterns corresponding to physical antenna belonging to the same group are identified with a unique string. The ACP
automatically groups all physical antenna into a new group with the name given by the string used in the column.
antenna.group.model=acp_group_model
The following options can be used to name the custom columns in the Antennas table to automatically define the mechanical
tilt options.
• 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_MIN
antenna.tilt.max=ACP_TILT_MAX
The following option can be used to name the custom column in the Antennas table to automatically link antenna elements
of a multi‐band physical antenna which have the same electrical tilt. In the ACP Setup dialog box, this is accomplished by
selecting 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 uses
same electrical tilt).
antenna.etilt.share=ACP_ETILT_SHARE
The following options can be used to name the custom columns in the Antennas table to automatically define the electrical
tilt options.
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
• The name of the custom columns in ANTENNA table of type 'string' or numeric, defining the allowed range for AEDT
and electrical tilt. Non‐valid values are treated as "forbidden":
antenna.etilt.min=ACP_ETILT_MIN
antenna.etilt.max=ACP_ETILT_MAX
11.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 automatically
appear in the ACP Setup dialog box and set options in the ACP.ini so that the ACP applies site classes based on optional data
in the Atoll database.
11.2.2.17.1 Defining Automatic Site Classes
The following option can be used to show or hide the site class feature and set the number of site classes defined:
200
[ACPGeneralPage]
cost.classes.showUI=1 # The default is 1; the site class feature is enabled.
The following option can be used to define the default settings when the site class option is available. These settings are local.
[ACPTplGeneralPage]
cost.classes.count=1 # Number of defined classes
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 sequential
number. 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.
[ACPTplGeneralPage]
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
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
11.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 that
identifies the site class of each site.
You must first create the corresponding custom column in the Sites table of the Atoll
database and assign a site class to each site in this column for this option to have effect.
201
site.costClass=[name of custom field in Site table]
The site class defined in the Sites table will be assigned automatically when an ACP optimisation is defined. For new candidate
sites which are located on an existing site, the site class is the same as the site on which the new candidate is located. For new
candidate 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 200, the cost structure is
automatically defined as well.
11.2.2.18 Defining the Appearance of a Running Optimisation Dialog Box
In the [ACPMapDefault] and [ACPMapPage] sections are the settings you can use to define the appearance of the
Optimisation dialog box during a run. Some options refer to the Quality tab and others to the Graphs tab.
11.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.
None of the options described in this section are available by default in the ACP.ini file. If
you want to use any of them, you must specify it manually in the ACP.ini file.
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.
[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)
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.
[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
These descriptions are used for default colormap and can easily be changed by the user. The settings are the same for the
various quality indicator in various technologies, where you replace:
• <techno> with: umts, gsm, lte, wimax, cdma
• <quality> with: sl, slgain (in GSM), ecio, ec, ecgain, eciogain, ecnt, ecntgain (in UMTS), sl, slC, slCN, rsrp, cinr, rsrq,
slgain, cinrgain, rssi (in LTE), sl, slC, slCN, cinr, slgain, cinrgain (in WiMAX)
202
[ACPMapDefault]
colormap.gsm.sl
colormap.gsm.slgain
colormap.umts.ec
colormap.umts.ecgain
colormap.umts.ecio
colormap.umts.eciogain
colormap.umts.ecnt
colormap.umts.ecntgain
colormap.lte.cinr
colormap.lte.cinrgain
colormap.lte.rsrp
colormap.lte.rsrq
colormap.lte.rssi
colormap.lte.sl
colormap.lte.slC
colormap.lte.slCN
colormap.lte.slgain
colormap.wimax.cinr
colormap.wimax.cinrgain
colormap.wimax.sl
colormap.wimax.slC
colormap.wimax.slCN
colormap.wimax.slgain
In addition, a number of other colormaps can be defined for other types of maps, e.g: overlap maps, objective status maps,
electrical tilt maps, mechanical tilt maps, combined electrical/mechanical tilt maps, change maps, emf maps, etc.
[ACPMapDefault]
colormap.bestcell.etilt
colormap.bestcell.objective
colormap.bestcell.sector
colormap.bestcell.tilt
colormap.bestcell.ttilt
colormap.bestcellHeight
colormap.capacity
colormap.capacitygain
colormap.change.azimuth
colormap.change.cost
colormap.change.etilt
colormap.change.impr
colormap.change.power.cdma
colormap.change.power.gsm
colormap.change.power.lte
colormap.change.power.umts
colormap.change.power.wimax
colormap.change.power2.cdma
colormap.change.power2.umts
colormap.change.selectionType
colormap.change.tilt
colormap.change.ttilt
colormap.change.type
colormap.changeHeight
colormap.diff
colormap.emf
colormap.emf.badSector
colormap.emf.gain
colormap.gain
colormap.imprCoverage
colormap.objective
colormap.objective.gain
colormap.objective.weighting
colormap.overlap
colormap.overlapgain
203
11.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:
[ACPMapPage]
config.foreground = 0 #default foreground colour setting (black)
config.background = 16777215 #default background colour code (white)
The RGB code for white is calculated as follows: 255 + 255  28 + 255  2 16 = 16777215 .

The following options define the size of the map title on the Quality tab:
[ACPMapPage]
config.titleHeight=16 # Title height in pixels
config.titleFontSize=16 # Size of title font in points
The following option defines the width of the margin on the Quality tab:
[ACPMapPage]
config.margin=2 # Margin width in pixels
The following options define the appearance of the map legend on the Quality tab:
[ACPMapPage]
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
The following option defines whether or not the axis will be displayed on the Quality tab:
[ACPMapPage]
config.showAxis=1
The following options define the appearance of the histogram on the Quality tab:
[ACPMapPage]
config.showHistogram=1 # Defines whether the histogram is displayed.
config.histogramHeight=60 # Defines the width of the histogram in pixels.
The following options define the appearance of the selected zone on the Quality tab:
[ACPMapPage]
config.showZoneSelection=1 # Defines whether the selected zone is displayed.
config.zoneLighterPercent=70 #Defines how much lighter selected zone is displayed.
11.2.2.19 Defining the Appearance of Predictions
The following option defines the transparency of predictions created from optimisation results:
[ACPMapDefault]
transparency=50
11.2.2.20 Defining New Predictions
In the [ACPNewPredictionDlg] section are options for displaying additional predictions that can be created from setups and
from the optimisation results.
Setting the following option allows you to create a prediction that displays the initial and final coverage by antenna.
[ACPNewPredictionDlg]
showBestServerAerialPrediction=1 #(Default=0)
204
Setting the following option allows you to create a prediction that displays the weight used for the traffic and for each zone.
showObjectiveWeightPrediction=1 #(Default=0)
Setting the following option allows you to create a prediction that displays the improvement in coverage.
showchangeImprovementPrediction=1 #(Default=0)
11.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 committed
on the Change Details tab (default). Setting allowUserChangeForCommit to "true" allows the user to edit the set of changes
on the Commit tab; this setting is not recommended.
[ACPCommitPage]
allowUserChangeForCommit=false
You can use the addCandidateComment option to create a comment in any site, transmitter, and cells automatically created
by ACP in Atoll as part of the candidate site selection. No comment is added if this option is left blank.
[ACPCommitPage]
addCandidateComment=Created from ACP candidate list
11.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 of
100 disables it.
[ACPOverlayDialog]
opacity=100
11.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 Optimisation
Properties dialog box. A value of 100 disables it.
[ACPGraphPage]
showTimeMarkers=1 # add time markers on the X axis. Default is 0 (OFF)
11.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 map
component. In the example below, the "MS UI Gothic" font used in Japanese systems is set as the default font.
[ACPUI]
DefaultFont=MS UI Gothic #font used by grid, graph component and map component
DefaultGridFontSize=0 #font size for grid only. 0 mean default size
11.2.2.25 Exporting Optimisation Results in XML
You can use the following options to define the contents and appearance of an XML report generated from the Statistics tab
of an optimisation’s Properties dialog box.
[ACPXmlReport]
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
205
defaultStylesheetName=.acpReport.xslt #name of the default stylesheet file. set it

empty to disable stylesheet processing instruction
11.2.3 ACP Core Engine Options
The settings in the [ACPCore] section are used to define how the ACP engine functions.
11.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):
[ACPCore]
generateLogFile=0 # The default is 0; no log file.
11.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 specified by the
computationThreadPoolSize option. The default setting for computationThreadPoolSize is ‐1 and means that ACP will use one
thread per processor core (CPU) available.
[ACPCore]
useComputationThreadPool=true
computationThreadPoolSize=-1
11.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 or
angles of incidence) are delegated to the propagation model. This can be useful, for example, to control the number of
licences taken by the ACP, without reducing the number of threads used by regular ACP calculations.
[ACPCore]
pathlossThreadPoolSize=-2 # Default. Same as computationThreadPoolSize.
Possible settings:
Value Description
The default value means that the propagation model will use the same number of threads as that
‐2
defined by the computationThreadPoolSize option.
‐1 Auto configuration; the propagation model will use one thread for each CPU core.
Entering a numerical value for pathlossThreadPoolSize indicates the number of threads the
Other
propagation model can use.
11.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 by
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 by
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 the
percentage 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, ACP displays
a message and the calculation is stopped. When using the option abortIfMemLimitReach, then ACP will not start if the
message indicating excessive memory use is displayed.
206
By default, excessive memory use is considered an estimate of 80% of the memory available to the process; ACP is not
prevented running even when 80% is exceeded.
When ACP estimates actual memory use (i.e., using either memLimitMemory or
memLimitUseableMemory), the memory estimate is only a rough estimate. Depending
on the project, actual memory usage can be quite different.
[ACPCore]
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
11.2.3.5 Macro Diversity Gains Calculation
The following option determines how ACP handles macro diversity gains.
[ACPCore]
addPilotSHOGain=1 #Default=1
For details on disabling macro‐diversity gains calculation, see "Disabling Macro‐diversity (SHO) Gains Calculation for Ec/Io and
Eb/Nt" on page 170.
Possible settings:
Value Description
ACP does not take macro diversity gains into account.
0 For consistency with the Atoll platform, the following option must be set in the Atoll.ini file:
[CDMA]
AddPilotSHOGain = 0
1 Default. ACP takes macro diversity gains into account.
ACP uses the same <value> as the one defined for the AddPilotSHOGain option in the Atoll.ini file:
2 [CDMA]
AddPilotSHOGain = <value>
11.2.3.6 Transmitter Altitude Calculation
The following option determines how ACP calculates the transmitter altitude from the DTM when no site altitude is defined
in Atoll.
[ACPCore]
useSiteAltitude=1 #Default=1
For details on reading altitudes from the DTM in Atoll, see "Reading Exact Altitudes From the DTM" on page 159.
Possible settings:
Value Description
During calculations, ACP will read the altitudes from the DTM at the exact coordinates of each
0
transmitter considering the values entered for the DX and DY parameters.
Default. This is the value used by the Atoll platform (which uses either the user‐defined site
1 altitudes from the Sites table or, if they are not defined, the site altitudes read from the DTM for
the site coordinates defined in the Sites table).
ACP uses the same <value> as the one defined for the useSiteAltitude option in the Atoll.ini file:
2 [Calculations]
useSiteAltitude = <value>
11.2.3.7 Automatic Candidate Positioning Options
The following option defines the default inter‐candidate site distance in metres.
[ACPAutoCandPosDlg]
interSiteDist=500
207
ACP normally places candidate sites in a strict hexagonal pattern. However, the ACP can search for a more appropriate site
within a search radius ratio according to the defined rules. The following option defines the default search radius ratio as a
percentage of the defined inter‐candidate site distance.
[ACPAutoCandPosDlg]
searchRadiusRatio=30
The following option defines the default minimum increase in altitude (in metres) that the ACP must find when placing a new
automatic candidate site.
[ACPAutoCandPosDlg]
hpHeightThres=10
11.2.3.8 Balancing Speed, Memory Use, and Accuracy in Calculations
On the User Preferences tab of the ACP ‐ Automatic Cell Planning Properties dialog box, ACP enables you to select a mode
of operation that balances balance speed, memory use, and accuracy. By defining the settings of the options in the acp.ini file
that 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 less
accurate.
• Default: When no changes are made to the acp.ini file, ACP uses the default settings. The default settings can be
overridden 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, calculating
the results will take the longest time and will use more memory.
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: defines the maximum number of cells monitored. This option affects memory use and accuracy. The
analogous options for the high speed mode and the high precision mode are maxMonitorCellSpeed and
maxMonitorCellPrec, respectively.
• threshLevelMonitorCell: defines the best server signal threshold (dB) in order to be monitored. 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:
[ACPCore]
maxMonitorCell=32
threshLevelMonitorCell = 35
The following options define the values ACP uses for high speed mode:
[ACPCore]
maxMonitorCellSpeed=30
threshLevelMonitorCellSpeed = 30
The following options define the values ACP uses for high precision mode:
[ACPCore]
maxMonitorCellPrec=35
threshLevelMonitorCellPrec = 40
Other options in the acp.ini file can be used to define additional offsets that will be used by the specific technology that ACP
is optimising:
[ACPCore]
threshLevelOffUmts=0
maxMonitorOffUmts=0
threshLevelOffGsm=0
maxMonitorOffGsm=0
threshLevelOffWimax=5
208
maxMonitorOffWimax=5
threshLevelOffLte=10
maxMonitorOffLte=10
11.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 main
document. ACP needs to access raster data and by default it accesses only the raster data specified in the main document. If
for some reason different raster data is used in the secondary document, you must set the ACP to access raster data for each
document separately using the following option:
[ACPCore]
gisDataTechnoShared=0
Atoll ACP loads raster data with block‐based processing to reduce memory usage. The maximum memory (in Mb) allowed for
this block processing in Mb is controlled with the following setting:
[ACPCore]
gisDataCacheMemMax=256
You can reduce this number if you experience issues with ACP failure due to memory allocation.
11.2.3.10 Filtering Clutter Class Layers
When using several layers of raster clutter classes, each with a different resolution, you can define which resolution (usually
the 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 (e.g. 20)
means that ACP will only use clutter classes with that resolution (in this case 20).
[ACPCore]
gisDataClutterOnlyRes=20 # ACP will only use clutter classes with this resolution
If you set the gisDataClutterOnlyRes option to filter out all clutter classes but those with the defined option, you should also
list the clutter classes that are not to be used in the zone.clutter.hiddenCodes in the [ACPGeneralPage] section to ensure that
the user will not create zones based on clutter classes that are not used. When you define the clutter classes that are not used,
they will not be displayed in the Zone Definition dialog box.
[ACPGeneralPage]
zone.clutter.hiddenCodes=0,1,2,12,13 # These clutter classes are not displayed
11.2.3.11 Multi‐antenna Interference Calculation (LTE)
This option has the possible values:
• 0: Interference independent of number of transmit antennas (old mode).
• 1: Interference multiplied by number of transmit antennas (new mode).
• 2: ACP automatically detects the version of Atoll used, and hence the value used by Atoll for this option. This is the
default value.
[ACPCore]
lteMultiAntennaInterference=2
11.2.3.12 Multi‐antenna Interference Calculation (WiMAX)
• 0: Interference independent of number of transmit antennas (old mode).
• 1: Interference multiplied by number of transmit antennas (old mode).
default value.
[ACPCore]
wimaxMultiAntennaInterference=2
209
11.2.3.13 Cyclic Prefix Energy in Signal Level Calculation (LTE)
Refer to "Including Cyclic Prefix Energy in LTE Signal Level Calculation" on page 176 for details.
• 0: Included.
• 1: Excluded.
default value.
[ACPCore]
lteExcludeCPFromUsefulPower=2
11.2.3.14 Cyclic Prefix Energy in Signal Level Calculation (WiMAX and Wi‐Fi)
Refer to "Excluding Cyclic Prefix Energy in WiMAX and Wi‐Fi Signal Level Calculation" on page 177 for details.
• 0: Included.
• 1: Excluded.
default value.
[ACPCore]
wimaxExcludeCPFromUsefulPower=2
11.2.3.15 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 to
stay constant. You can remove this constraint using the following option:
[ACPCore]
umtsPilotPowerRatioFixed=0
11.2.3.16 Showing Initial/Final Total Poweror 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 the
Sectors and Commit tabs of the Optimisation Properties dialog box, according to the DL load setting (Absolute or % Pmax,
resp.) in the Network Settings Properties dialog box.
Before you run an optimisation, make sure that Pilot Power is selected on the Reconfiguration > UMTS Cells vertical tab of
the Setup Properties dialog box and set the following option in ACP.ini:
[ACPResultSectorPage]
showDlLoad=1 # (default=0)
11.2.3.17 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, and
LTE), set the following option in ACP.ini:
[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
11.2.4 EMF Exposure Core Options
In the [ACPEMFCore] section there are several options controlling the EMF exposure calculation engine.
210
One set of options allows for the detection and auto correction of transmitter heights which are found to be indoors, just
below the roof. This is usually caused by inconsistencies between the vectors imported to create the 3D representation of the
terrain 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 imported
vectors used to create the 3D representation of the terrain) and DHM‐offset, then it is considered to be indoors, just below
the roof. The ACP automatically detects these transmitters and displays warnings in the Event Viewer. The default
distancebeneath the roof is 5 metres.
[ACPEMFCore]
detectTxIndoorOffset=5
The ACP can automatically adjust the height of transmitters that are below roof so that they are on top of the clutter height
using the defined offset (in metres).
[ACPEMFCore]
resetTxHeightWhenIndoor=0 # 0 is the default; height is not reset.
The following option defines the internal resolution in metres for terrain 3D representation when the ACP rasterises input
vectors:
[ACPEMFCore]
vectorRasterizationResolution=2 # 2 is the default.
The following option allows you decrease the displayed EMF exposure level when penetration loss is increased for buildings.
[ACPEMFCore]
flagPixelFacadeDist=<distance> #Distance in metres.
flagPixelFacadeDist defines the indoor distance from facade 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 (Propagation
page on the Optimisation tab).
11.2.5 Other Options
In the [ACPMisc] section are several additional ACP configuration options.
11.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 before
running an optimisation setup.
[ACPMisc]
autoCheckPredictionValidity=1 # 1 enables the automatic verification.
The following options can be used to enable other automatic verifications on the number of active transmitters, their pathloss
file size, and locked status in the Atoll document:
[ACPMisc]
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.
If autoCheckPredictionValidity is set to 1, thereby enabling the verification of the validity of coverage predictions, you can
have ACP automatically recalculate the invalid coverage predictions using the following option. If it is set to 0, ACP will not
automatically recalculate predictions.
[ACPMisc]
autoPathlossRecomputation=0
211
212
AT321_AM_E4 Index of Initialisation Options
Index of Initialisation Options
A cost.classes.0.azimuth.cost 201
acp.ini main options cost.classes.0.azimuth.isSiteVisit 201
cost.classes.0.etilt.cost 201
Calculation Thread Pool Settings
cost.classes.0.etilt.isSiteVisit 201
computationThreadPoolSize 206 cost.classes.0.height.cost 201
useComputationThreadPool 206 cost.classes.0.height.isSiteVisit 201
Custom columns on Transmitters and Remote tabs of Reconfigu‐ cost.classes.0.name 201
ration page cost.classes.0.newSiteCost 201
193 cost.classes.0.power.cost 201
tx.custom.x.column 193 cost.classes.0.power.isSiteVisit 201
tx.custom.x.label 193 cost.classes.0.removeSiteCost 201
tx.custom.x.type 193 cost.classes.0.siteVisitCost 201
Default Values on the Antennas Tab cost.classes.0.tilt.cost 201
cost.classes.0.tilt.isSiteVisit 201
enableAedt 196
cost.classes.0.upgradeSiteCost 201
Default Values on the Optimisation Tab cost.classes.count 201
cost.antenna.cost 186 Defining Reconfiguration Values for Sites Using Custom Atoll
cost.antenna.isSiteVisit 186 Fields
cost.azimuth.cost 186
site.gsm.status 199
cost.azimuth.isSiteVisit 186
site.lte.status 199
cost.etilt.cost 186
site.status 199
cost.etilt.isSiteVisit 186
site.status.candidate 199
cost.height.cost 186
site.umts.status 199
cost.height.isSiteVisit 186
cost.newSiteCost 186 Defining the Appearance of the Graph Tab
cost.power.cost 186 showTimeMarkers 205
cost.power.isSiteVisit 186 Defining the Functionality of the Commit Tab
cost.removeSiteCost 186 allowUserChangeForCommit 205
cost.siteVisitCost 186
Number of Threads Used for Propagation Model Calculations
cost.tilt.cost 186
cost.tilt.isSiteVisit 186 pathlossThreadPoolSize 206
cost.upgradeSiteCost 186 atoll.ini options listed by INI section
Default Values on the Patterns tab of the Antenna Tab 3GCells, NoSuffixIfUniqueCarrier 170
enableETilt 194 ACP, iniFile 185
enableMTilt 194 Add‐ins, ’Add‐in Name’ 146
Default Values on the Reconfiguration Tab AFP, GlobalDistanceMatrixDegreeUB 168
defaultTxAzimuthMinInterSector 191 AFP, HideHopping 166
defaultTxAzimuthStep 191 AFP, SimpleUserGUI 166
defaultTxAzimuthVariation 191 AFP, WorstCaseIM_FskAfp 167
defaultTxETiltMax 191
Antenna, CatalogVerticalDiagramOrientation 157
defaultTxETiltMin 191
defaultTxHeightMax 191 Antenna, InterpolatePatternEvenIfOnlyOneDiagram 157
defaultTxHeightMax.feet 191 Antenna, InterpolatePatternIndB 157
defaultTxHeightMin 191 Antenna, PrecisionTimes10 141
defaultTxHeightMin.feet 191 Antenna, REDTDisplay 150
defaultTxHeightStep 191
AutoRename, 3GCells 136
defaultTxHeightStep.feet 191
defaultTxTiltMax 191 AutoRename, Repeaters 136
defaultTxTiltMin 191 AutoRename, Transmitters 136
defaultTxTiltStep 191 BsicFormat, DefaultValue 165
tx.etilt.deltaLimitConstraint.show 191 Calculations, RoundAltitudes 161
tx.tilt.deltaLimitConstraint.show 191, 192 Calculations, UseSiteAltitude 159
Default Values on the Transmitters Tab of the Reconfiguration CDMA, AddPilotSHOGain 170
Tab
CDMA, CodeStrategies 174
tx.tilt.asRelative 193
CDMA, CQIDeltaWithPower 171
Defining Automatic Site Classes
CDMA, CutOffSimu 172
cost.classes.0.antenna.cost 201
CDMA, DisplayEcIoOfRejected 174
cost.classes.0.antenna.isSiteVisit 201
213
Index of Initialisation Options © Forsk
CDMA, HSDPAAvgSimuResults 171 GSM, 167

CDMA, HSDPAMaxRejections 172 GSM, CanEditTRXInfoAtTXLevel 168
CDMA, HSDPAThroughputPeak 170 GSM, ExternalIncluded 165
CDMA, IterBeforeDown 173 GSM, FirstTRXIndex 169
CDMA, MaxRejections 172 GSM, MinNeighbourImportanceInAFPResults 167
CDMA, MinUsersPerBin 171 GSM, ShowNonSynchSFHViolationsInAFPResults 167
CDMA, MultiBandSimu 174 GSM, SubcellValueFixMethod 170
CDMA, OrthoInCPICH 171 GSM, TRXIndexHidden 169
CDMA, ParallelSimulations 161 GSM, WideRangeSubcellThresholds 169
CDMA, PFSchedulerCQIFactor 173 GUIUserRights, EnableMacrosAddins 141
CDMA, PmaxInIntraItf 171 GUIUserRights, EnableNewDocFromTemplate 141
CDMA, PredictSimuMemorySize 162 GUIUserRights, EnableZip 141
CDMA, SharingEquallyPower 174 IM, FilterByFrequencyBands 169
CDMA, UseStudyCnxProba 171 Import, LoadKMLVectors 140
CDMA, UsingPreviousIterationPowerWeight 174 Import, LoadVectors 140
Clutter, OnlyVisibleClassesInInterferenceReport 144 License, ACP_GSM 153
Clutter, PerClassPercentagesRelativeToCoverageInReport 144 License, ACP_LTE 153
ClutterParams, IndoorActivity 158 License, ACP_UMTS 153
Compatibility, MWEquipment_CIMIN 182 License, ACP_WiMAX 153
Compression, StartSizeInMB 146 License, BH 153
CoPlanning, ComputeLinkedPredictions 162 License, CDMA 153
CoPlanning, LinkedPredictionsComputationMode 162 License, GSM 153
CoPlanning, LinkSites 142 License, GSM_AFP 153
Database, AllowNullRecordsForNotNullableCustomFields 155 License, IdleTime 154
Database, CommandTimeout 155 License, LTE 153
Database, DisplayTableNamesOnOpenFromDB 154 License, LTE_AFP 153
Database, ExclusiveProvider 157 License, Measures 153
Database, IntegrityChecker 154 License, MW 153
Database, OverwriteSharedFolderPath 157 License, TD‐SCDMA 153
Database, PromptOnArchive 156 License, TimeBombNotice 153
Database, SubCellAuditConsistency 155 License, UMTS 153
Database, SubCellAuditMainValues 155 License, WiMAX 153
Database, UseTransaction 156 License, WiMAX_AFP 153
Display, CaseInsensitiveGroups 152 LOSArea, ResolutionMultFactor 158
Display, CellIDNbDigits 150 LTE, ApplyDLLoadOnPDCCHInterf 178
Display, DiscreteValueColoring 151 LTE, DisplaySignalsPerSCInPtA 176
Display, PaletteColor0 151 LTE, eICIConRS 180
DocTitle, UseTechnoName 151 LTE, EIRPfromRSEPRE 179
EventsObserver, LogPath 137 LTE, ExcludeCPFromUsefulPower 176
EventsObserver, milliseconds 149 LTE, InterNeighbourIDCollisions 177
EventsObserver, ShowAddinAccessDeniedMsg 137 LTE, NR_CONTROL_MARGIN_MIN 179
EventsObserver,date 149 LTE, SameItf_PDSCH_RS_PDCCH 178
Export, AutoOpenWithExcel 141 LTE, ServiceMBRDowngrading 179
Export, NewLineEscapeSequence 148 LTE, ULNRControlMethod 179
Features, IM_TRAFFIC_OVERLAP 165 LTE, ULNRControlPrecision 179
FskPropagModels, OptimOnNoData 162 LTE, UseABSonCellEdgeOnly 180
gAFP, HighestOrderToCheck_with3frequencies 168 MajorVersionChange, EnablePartialRefreshInMigration 157
gAFP, HighestOrderToCheck_with4frequencies 168 MITAB, ’Coordinate system definition in the header file’ 138
gAFP, onlyUpLinkIntermodulationProducts 168 MITAB, DisableNormalization 143
Geo, FindGeoButtonAlwaysActive 142 MITAB, EnableMessages 145
Geo, ReportObeysVisibility 142 MITAB, OptimizedTABExport 143
Geo, VectorDisplayConfigurationCompanionFile 142 MultiRAT, AllCodesAllocWithInterRATNeighbours 181
GeoProfileDisplay, Beamwidth 151 MultiRAT, UncheckTechnoChoices 181
GeoProfileDisplay, BeamwidthColor 151 MWCalculations, CCDP_XPIF 182
GeoProfileDisplay, Lower3dbColor 151 MWCalculations, HIDE_REC530_5 182
GeoProfileDisplay, Upper3dbColor 151 MWCalculations, ShieldingFactorOnWantedSignal 181
Grids, NbDecimals 141 MWCalculations, UpdateOppositeHop 181
214
MWCalculations, UseProfilesFiles 182 Rasterization, SurfRatio 173

MWChannelArrangement, DefaultConfiguration 183 ReceptionTab, NumberOfTransmitterDisplayed 140
MWReport, DefaultTemplate 183 Refresh, ControlIntegrity 154
MWReport, DesignSummaryCfg 183 Refresh, TRXIntegrity 165
MWReport, LinkAnalysisCfg 183 RemoteAntennas, FrozenSymbol 149
MWReport, LinkInterferenceCfg 183 RemoteCalculation, AtollSvrPriority 152
MWReport, LinksBudgetCfg 183 RemoteCalculation, DetectTimeOut 153
MWReport, LinksInterferenceCfg 183 RemoteCalculation, DisablePathlossPerSiteCalculation 164
MWReport, MultihopAnalysisCfg 183 RemoteCalculation, NumberedServers 152
MWReport, ReflectionAnalysisCfg 183 RemoteCalculation, NumberOfProcessors 160
MWReport, RequiredMarginCfg 183 RemoteCalculation, NumberOfThreadsMicrowave 160
MWReport, tab 182 RemoteCalculation, NumberOfThreadsNeighbour 160
Neighbours, CandidatesMaxDistanceInImportanceCalculation RemoteCalculation, NumberOfThreadsPathloss 160
164 RemoteCalculation, NumberOfThreadsSimulation 160
Neighbours, CompressModeEval 175 RemoteCalculation, NumberOfThreadsStudy 160
Neighbours, DistanceAzimutWeightingPercent 163 RemoteCalculation, NumberOfThreadsStudyTile 160
Neighbours, DoNotDeleteSymmetrics 164 RemoteCalculation, Priority 160
Neighbours, ExcludeFilteredCellsFromNeighbourLists 163 SAMModel, DrawSingleElementPattern 150
Neighbours, ForceSymmetryInFocusZone 162 Settings, KeepFilterZoneOnRemoveFilter 148
Neighbours, RealInterSiteDistanceCondition 163 Shadowing, Reliability 158
Neighbours, RepeaterInterSiteDistanceInAlloc 163 Shadowing, UseShadowing 158
OFDM_AFP, AdjacentProtection 178 Shadowing, WithSHOGain 170
OFDM_SIMU, MeanNRInDB 179 Simulation, RandomTotalUsers 162
OFDM, DisplayThroughputZero 179 Site, AddToSiteListOnDuplicate 143
OFDM, SecondNeighbours 178 Site, Prefix 135, 181
OFDM, UniformIDDistribution 177 Site, ResetAltitude 143
OFDM, UseCommonBearersOnly 176 SitesSymbol, Color 148
OnlineMaps, BingCulture"X" 147 SitesSymbol, FontName 148
OnlineMaps, BingKey 147 SitesSymbol, Size 148
OnlineMaps, BingLanguage"X" 147 SitesSymbol, Symbol 148
OnlineMaps, Name 147 StatusBar, ClutterPaneWidth 151
OnlineMaps, TilesCachePath 147 StatusBar, DisplayClutterClass 149
OnlineMaps, URL 147 StatusBar, DisplayClutterHeight 149
OnlineSearch, BingKey 148 StatusBar, DisplayZ 149
Pathlosses, EmbeddedByDefault 159 Studies, 138
Pathlosses, FullResyncPrivShared 144 Studies, 2GTxDiversityGain 168
Pathlosses,DisplayIndividualSuccessOrFailure 138 Studies, AerialStudy 161
Pathlosses,DisplayInvalidityCause 138 Studies, AutoLock 157
Pathlosses,DisplayOverallSuccessOrFailure 138 Studies, CleanMultiCellManagement 166
Perfos, MaxRangeApplied 165 Studies, CommentsInLegend 150
Perfos, PtAnalysisMargin 140 Studies, ComputeEvenIfReadOnly 161
Perfos, PtAnalysisNbServersDisplayed 140 Studies, ContinueOnError 159
Perfos, PtAnalysisNbServersMax 140 Studies, CustomStudiesFilteredByTechno 145
Perfos,ConfirmStoreExternPrivLosFilesOnCopy 137 Studies, EIRPfromMaxPower 163
Perfos,StoreExternPrivLosFilesOnCopy 137 Studies, ExportOnlyVisibleLevels 146
PlanetImport, ChangeKclutterSign 156 Studies, MultiBandManagement 165
PlanetImport, ClutterNoData 156 Studies, MultiplePlotsTipTextLines 150
PlanetImport, SensitiveCase 155 Studies, NoOverlapOnBestServer 146
Population, ReportResolution 145 Studies, RecomputationWarning 159
Print, LogoFooterChecked 144 Studies, RemoveBadMultiCells 166
Print, MaxDPI 137 Studies, ReportDecimalPlacesAbsolute 145
PSC, ConstantStep 175 Studies, ReportDecimalPlacesPercent 145
PSC, DisplayCostValues 174 Studies, SCActivesetMaxSize 175
RasterExport, GeorefWithTAB 142 Studies, ShowIntervalsWithNoCoverageInReport 145
Rasterization, Improve 173 Studies, SpecifyResolutionAfterComputation 160
Rasterization, MaximumSurf 173 Studies, UplinkLosses 175
Rasterization, Precision 173 Studies, UseFullHotSpotSurfaceOnReport 146
215
Studies, UseThresholdForSameLayerPriorities 166 License, LTE_AFP 153

Studies,SelectNullMarginOnly 138 License, WiMAX_AFP 153
System, RestartOnImproperExit 148 Blocking Access to IEEE Parameters in WiMAX
TestMobileData, FloatingPointScramblingCodeSupport 184 WiMAX, ModifiableIEEEParams 176
TestMobileData, ImportForFilteredTransmittersOnly 184 Blocking Access to Macros and Add‐ins
TestMobileData, NumberOfTestMobileTransmitters 184 GUIUserRights, EnableMacrosAddins 141
TestMobileData, RecalcDist 184 Blocking Access to Technology Modules
TestMobileData, ShowCoupleInfo 184 License, BH 153
TestMobileDataImportFmt, BCCHColumn 184 License, CDMA 153
License, GSM 153
TestMobileDataImportFmt, BSICColumn 184
License, LTE 153
TiffExport, PaletteConvention 136 License, Measures 153
Traffic, PerClassPercentagesRelativeToCoverageInReport 144 License, MW 153
Transmitter, AutoSynchronizeDisplay 149 License, TD‐SCDMA 153
Transmitter, ChangeSymbolOnSearch 149 License, UMTS 153
License, WiMAX 153
Transmitter, CheckImpactOnRepeaters 141
BSIC, SC, and PCI Allocation in 3GPP with Inter‐technology Neigh‐
Transmitter, EmptySymbolWhenInactive 149
bour Constraints
Transmitter, First 136
MultiRAT, AllCodesAllocWithInterRATNeighbours 181
Transmitter, FirstCharSuffix 136
Calculating and Displaying Peak or Instantaneous HSDPA
Transmitter, MaximumCalculationRadius 164 Throughput
Transmitter, Prefix 136 CDMA, HSDPAAvgSimuResults 171
Transmitter, SuffixIsNum 136 CDMA, HSDPAThroughputPeak 170
Transmitter, Underscore 136 Calculating EIRP from Max Power in Signal Level Predictions
Transmitter, UpdateLossIfNoEquipment 164 Studies, EIRPfromMaxPower 163
UMTSSimus, MaxReuseFactor 175 Calculating EIRP from RS EPRE in LTE Signal Level Predictions
WiMAX, ExcludeCPFromUsefulPower 177 LTE, EIRPfromRSEPRE 179
WiMAX, InterNeighbourPICollisions 177 Changing Hot Spot Reference Surface in Prediction Reports
WiMAX, ModifiableIEEEParams 176 Studies, UseFullHotSpotSurfaceOnReport 146
WiMAX, ReplaceOPUSCwithPUSCUL 177 Changing the Default Cache Location for the Loaded Map Tiles
atoll.ini options listed by topic OnlineMaps, TilesCachePath 147
Adding the Duplicate Site to the Original Site’s Site List Changing the Display for Downlink Smart Antenna Results
Site, AddToSiteListOnDuplicate 143 SAModel, DrawSingleElementPattern 150
Adjusting the Working of the Proportional Fair Scheduler Changing the Level of Intermodulation Products Checked by AFP
CDMA, PFSchedulerCQIFactor 173 in GSM
Allowing Null Entries in Non‐nullable Custom Fields gAFP, HighestOrderToCheck_with3frequencies 168
Database, AllowNullRecordsForNotNullableCustomFields Changing the Level of Intermodulation Products Checked by AFP
155 in TETRA
Applying the ABS Collision Probability on Interference from RS gAFP, HighestOrderToCheck_with3frequencies 168
LTE, eICIConRS 180 gAFP, HighestOrderToCheck_with4frequencies 168
Archiving Data to Databases Using Transactions gAFP, onlyUpLinkIntermodulationProducts 168
Database, UseTransaction 156 Changing the NetHASP Licence Manager Idle Time Setting
Automatically Correcting Out‐of‐range Subcell Values License, IdleTime 154
GSM, SubcellValueFixMethod 170 Changing the Path to Linked Geo Data Files
Automatically Running a Database Integrity Check at Open or Geo, FindGeoButtonAlwaysActive 142
Refresh Changing the Rounding Method Used for Profile Extraction
Database, IntegrityChecker 154 Calculations, RoundAltitudes 161
Automatically Running GSM Subcell Audit at Open or Refresh Changing the Weighting Factor of the Effective Inter‐transmitter
Database, SubCellAuditConsistency 155 Distance
Database, SubCellAuditMainValues 155 Neighbours, DistanceAzimutWeightingPercent 163
Averaging the Uplink Noise Rise in dB Checking Data Integrity After Database Upgrade and Data
OFDM_SIMU, MeanNRInDB 179 Refresh
Avoiding Overlapping Pixels in Best Server Coverage Prediction Refresh, ControlIntegrity 154
Studies, NoOverlapOnBestServer 146 Checking Database Consistency Automatically
Blocking Access to ACP and AFP Modules Refresh, TRXIntegrity 165
License, ACP_GSM 153 Compressed Mode ‐ Restricting Inter‐carrier and Inter‐tech‐
License, ACP_LTE 153 nology Neighbour Allocation
License, ACP_UMTS 153 Neighbours, CompressModeEval 175
License, ACP_WiMAX 153 Considering Inter‐technology Interference in GSM
License, GSM_AFP 153
216
GSM, ExternalIncluded 165 Defining the Microsoft Bing Tile Server for Online Searches

Considering Overlapping Zones for IM Calculation Based on OnlineSearch, BingKey 148
Traffic Defining the Number of Iterations Before Downgrading
Features, IM_TRAFFIC_OVERLAP 165 CDMA, IterBeforeDown 173
Considering XPIF value in Interference for Dual‐Polar Links Defining the Parameters for the Default Sites Symbol
MWCalculations, CCDP_XPIF 182 SitesSymbol, Color 148
Co‐planning ‐ Calculating Predictions in Serial or in Parallel SitesSymbol, FontName 148
CoPlanning, LinkedPredictionsComputationMode 162 SitesSymbol, Size 148
Co‐planning ‐ Calculating Predictions in the Current Document SitesSymbol, Symbol 148
Only Defining Web Map Services Servers
CoPlanning, ComputeLinkedPredictions 162 WMS, ’Web map services servers’ 139
Creating an Event Viewer Log File Deleting the Filtering Zone on Removing Filters From Tables
EventsObserver, LogPath 137 Settings, KeepFilterZoneOnRemoveFilter 148
Customising Performance Optimisation when Exporting TAB Detecting and Listing Distributed Calculation Servers
Vector Files RemoteCalculation, NumberedServers 152
MITAB, OptimizedTABExport 143 Disabling Automatic Locking of Coverage Predictions
Deactivating Frequency Band Filtering in IM Calculation Studies, AutoLock 157
IM, FilterByFrequencyBands 169 Disabling Automatic Renaming of Transmitters and Cells
Deactivating Service Max Throughput Demand Downgrading in AutoRename, 3GCells 136
LTE AutoRename, Repeaters 136
LTE, ServiceMBRDowngrading 179 AutoRename, Transmitters 136
Deactivating Uniform Distribution of Resources Disabling Automatic Restart of Atoll after a Crash
OFDM, UniformIDDistribution 177 System, RestartOnImproperExit 148
Decreasing Calculation Time of Path Profiles Disabling Calculations Over NoData Values for DTM and Clutter
MWCalculations, UseProfilesFiles 182 Classes
Defining a Default Configuration File for the Channel Arrange‐ FskPropagModels, OptimOnNoData 162
ment Display Disabling External Storage of Numerical Results Files for Predic‐
MWChannelArrangement, DefaultConfiguration 183 tions
Defining a Default Template for Microwave Links Custom Studies, NumericalResults 138
Reports Disabling Macro‐diversity (SHO) Gains in Calculations
MWReport, DefaultTemplate 183 CDMA, AddPilotSHOGain 170
Defining a Fixed Interval Between Scrambling Codes Shadowing, WithSHOGain 170
PSC, ConstantStep 175 Disabling Normalisation of MIF/TAB Vector Files
Defining a Global Maximum Path Loss Calculation Radius MITAB, DisableNormalization 143
Transmitter, MaximumCalculationRadius 164 Disabling Parallel Calculation of Monte Carlo Simulations
Defining an Offset With Respect to The Thermal Noise CDMA, ParallelSimulations 161
CDMA, CutOffSimu 172 Disabling Saving and Opening ZIP Files
Defining Default Configuration Files for Link Budgets Reports GUIUserRights, EnableZip 141
MWReport, DesignSummaryCfg 183 Disabling Shielding Factor on Wanted Signal at Receiver
MWReport, LinkAnalysisCfg 183 MWCalculations, ShieldingFactorOnWantedSignal 181
MWReport, LinkInterferenceCfg 183 Disabling the Maximum Range Parameter
MWReport, LinksBudgetCfg 183 Perfos, MaxRangeApplied 165
MWReport, LinksInterferenceCfg 183 Disallowing Creation of New Documents from Templates
MWReport, MultihopAnalysisCfg 183
GUIUserRights, EnableNewDocFromTemplate 141
MWReport, ReflectionAnalysisCfg 183
MWReport, RequiredMarginCfg 183 Displaying % of Covered Clutter Classes with Respect to the
Focus Zone in Reports
Defining Online Map URLs
Clutter, PerClassPercentagesRelativeToCoverageInReport
OnlineMaps, Name 147
144
OnlineMaps, URL 147
Displaying % of Covered Traffic Classes with Respect to the Focus
Defining the BCCH and BSIC Columns for FMT Import
Zone in Reports
TestMobileDataImportFmt, BCCHColumn 184
Traffic, PerClassPercentagesRelativeToCoverageInReport
TestMobileDataImportFmt, BSICColumn 184
144
Defining the Maximum Number of Transmitters for Reuse
Displaying Additional Information in Drive Test Data
Distance
TestMobileData, ShowCoupleInfo 184
AFP, GlobalDistanceMatrixDegreeUB 168
Displaying Automatic Allocation Cost Values
Defining the Microsoft Bing Tile Server for Online Maps
PSC, DisplayCostValues 174
OnlineMaps, BingCulture"X" 147
OnlineMaps, BingKey 147 Displaying Coverage Prediction Comments in the Legend
OnlineMaps, BingLanguage"X" 147 Window
Studies, CommentsInLegend 150
217
Displaying Database Tables in the Event Viewer at Open Database, PromptOnArchive 156

Database, DisplayTableNamesOnOpenFromDB 154 Estimating Required and Used Memory Size for UMTS Simula‐
Displaying Date and Time in the Event Viewer tions
EventsObserver, date 149 CDMA, PredictSimuMemorySize 162
EventsObserver, milliseconds 149 EventsObserver, ShowAddinAccessDeniedMsg 137
Displaying Ec/I0 of Rejected Mobiles in Simulation Results Excluding Cyclic Prefix Energy in WiMAX and Wi‐Fi Signal Level
CDMA, DisplayEcIoOfRejected 174 Calculation
Displaying Filled Symbols for Inactive Transmitters on the Map WiMAX, ExcludeCPFromUsefulPower 177
Transmitter, EmptySymbolWhenInactive 149 Excluding Filtered Transmitters from the List of Neighbours
Displaying Leading Zeros in the CELL_IDENTITY Field Neighbours, ExcludeFilteredCellsFromNeighbourLists 163
Display, CellIDNbDigits 150 Excluding the Adjacent Channel Overlap from the AFP Cost Func‐
Displaying Objects’ Discrete Values with User‐defined Colours tions
Display, DiscreteValueColoring 151 OFDM_AFP, AdjacentProtection 178
Display, PaletteColor0 151 Excluding Vectors from Imported KML/KMZ Files
Displaying Path Loss Calculation Details in the Event Viewer Import, LoadKMLVectors 140
Pathlosses, DisplayIndividualSuccessOrFailure 138 Exporting BMP, TIF, and PNG Files with a TAB Reference File
Pathlosses, DisplayInvalidityCause 138 RasterExport, GeorefWithTAB 142
Pathlosses, DisplayOverallSuccessOrFailure 138 Exporting Coverage Prediction Polygons in Text Format
Displaying Pixels with Zero Throughput in Coverage Predictions Studies, EnableLBS 139
OFDM, DisplayThroughputZero 179 Exporting Only Visible Value Interval Layers of Coverage Predic‐
Displaying Uplink Total Losses in Coverage by Signal Level tions
Studies, UplinkLosses 175 Studies, ExportOnlyVisibleLevels 146
Displaying Vertical Beamwidth in Profile Analysis Exporting/Importing Vector Data with a Display Configuration
GeoProfileDisplay, Beamwidth 151, 152 File
GeoProfileDisplay, BeamwidthColor 151 Geo, VectorDisplayConfigurationCompanionFile 142
GeoProfileDisplay, Lower3dbColor 151 Extending the Allowed Value Range for C/I and Reception
GeoProfileDisplay, Upper3dbColor 151 Thresholds
Duplicating Linked Path Loss Matrices on Save As GSM, WideRangeSubcellThresholds 169
Perfos, ConfirmStoreExternPrivLosFilesOnCopy 137 Extending the Maximum Inter‐site Distance to Repeaters and
Perfos, StoreExternPrivLosFilesOnCopy 137 Remote Antennas
Embedding Path Losses in New Documents Neighbours, RepeaterInterSiteDistanceInAlloc 163
Pathlosses, EmbeddedByDefault 159 Filtering Predictions by Technology When Reading the XML
Enabling and Disabling Per‐site Path Loss Matrix Calculations Studies File
RemoteCalculation, DisablePathlossPerSiteCalculation 164 Studies, CustomStudiesFilteredByTechno 145
Enabling Coverage Predictions of Connection Probabilities Forcing Neighbour Symmetry Only Inside Focus Zone
CDMA, MinUsersPerBin 171 Neighbours, ForceSymmetryInFocusZone 162
CDMA, UseStudyCnxProba 171 Forcing the Real Inter‐site Distance Threshold
Enabling Display of Signals per Subcarrier Point Analysis in LTE Neighbours, RealInterSiteDistanceCondition 163
LTE, DisplaySignalsPerSCInPtA 176 Hiding AFP Advanced Parameters
Enabling Event Viewer Messages for MapInfo File Import/Export AFP, SimpleUserGUI 166
MITAB, EnableMessages 145 Hiding AFP Hopping Parameters
Enabling Indoor Coverage in Calculations AFP, HideHopping 166
ClutterParams, IndoorActivity 158 Hiding Information Displayed in the Status Bar
Enabling Notification for Donor Transmitter Parameter Modifica‐ StatusBar, DisplayClutterClass 149
tions StatusBar, DisplayClutterHeight 149
Transmitter, CheckImpactOnRepeaters 141 StatusBar, DisplayZ 149
Enabling Orthogonality Factor in Pilot EC/NT Calculation in Hiding the Rec. ITU‐R P.530‐5 Method
HSDPA MWCalculations, HIDE_REC530_5 182
CDMA, OrthoInCPICH 171 Hiding the Technology Name in the Title Bar
Enabling Partial Refresh from Recently Upgraded Databases DocTitle, UseTechnoName 151
MajorVersionChange, EnablePartialRefreshInMigration Hiding the TRX Index
157 GSM, TRXIndexHidden 169
Enabling Shadowing Margin in Calculations Hiding Violations Between Low Importance GSM Neighbours in
Shadowing, UseShadowing 158 AFP Results
Enabling the Support for Multi‐band Transmitters GSM, MinNeighbourImportanceInAFPResults 167
Studies, CleanMultiCellManagement 166 Hiding Violations Between Non‐Synchronised MALs‐MAIOs in
Studies, MultiBandManagement 165 AFP Results
Studies, RemoveBadMultiCells 166 GSM, ShowNonSynchSFHViolationsInAFPResults 167
Enabling/Disabling Password Prompt at Archive
218
Identifying Transmitter, Repeater, and Remote Antenna Modifying the Default Formats of Site and Transmitter Names
Coverage Areas Site, Prefix 135
Studies, AerialStudy 161 Transmitter, First 136
Ignoring Inter‐Neighbour Physical Cell ID Collision in LTE Transmitter, FirstCharSuffix 136
LTE, InterNeighbourIDCollisions 177 Transmitter, Prefix 136
Transmitter, SuffixIsNum 136
Ignoring Inter‐Neighbour Preamble Index Collision in WiMAX
Transmitter, Underscore 136
WiMAX, InterNeighbourPICollisions 177
Modifying the Resolution for the LOS Area Calculation Around a
Importing Drive Test Data for Active and Filtered Transmitters Site
Only
LOSArea, ResolutionMultFactor 158
TestMobileData, ImportForFilteredTransmittersOnly 184
Modifying the Threshold for Important Violations in AFP
Importing Drive Test Data with Scrambling Codes as Integers
GSM, AdjRedColorThreshPercent 167
TestMobileData, FloatingPointScramblingCodeSupport GSM, CoRedColorThreshPercent 167
184
Multi‐RAT Technology Selection Default Behaviour
Improving Point Analysis Performance
MultiRAT, UncheckTechnoChoices 181
Perfos, PtAnalysisMargin 140
Opening Exported XLS Files Automatically in MS Excel
Perfos, PtAnalysisNbServersDisplayed 140
Perfos, PtAnalysisNbServersMax 140 Export, AutoOpenWithExcel 141
ReceptionTab, NumberOfTransmitterDisplayed 140 Performing Calculations in Read‐Only Documents
Including Cyclic Prefix Energy in LTE Signal Level Calculation Studies, ComputeEvenIfReadOnly 161
LTE, ExcludeCPFromUsefulPower 176 Preserving Loss and Noise Figures with ni Assigned Equipment
Including Pixel‐free Ranges in Coverage Prediction Reports Transmitter, UpdateLossIfNoEquipment 164
Studies, ShowIntervalsWithNoCoverageInReport 145 Prioritising Individual Inter‐site Distances in Neighbour Impor‐
Increasing the Maximum Printing Resolution tance Calculation
Print, MaxDPI 137 Neighbours, CandidatesMaxDistanceInImportanceCalcula‐
tion 164
Increasing the Width of the Clutter Description Pane in the Status
Bar Reading Exact Altitudes From the DTM
StatusBar, ClutterPaneWidth 151 Calculations, UseSiteAltitude 159
Keeping Separate Work and Master Path Loss Directories Real Altitude Vs. DTM Altitude in a Duplicated Site’s Properties
Database, OverwriteSharedFolderPath 157 Site, 143
Keeping the Assigned Neighbours which are not Symmetrised Recalculating Distances of Points From There Serving Cells at
with the Reference Transmitter Import
Neighbours, DoNotDeleteSymmetrics 164 TestMobileData, RecalcDist 184
Keeping Transmitter Symbols From Changing on Search Refreshing the Display Automatically When a New Station is
Dropped
Transmitter, ChangeSymbolOnSearch 149
Transmitter, AutoSynchronizeDisplay 149
Linking the Sites Folder in Co‐planning
Renaming OPUSC Zone to PUSC UL in WiMAX
CoPlanning, LinkSites 142
WiMAX, ReplaceOPUSCwithPUSCUL 177
Loading Vector Files Dynamically
Restricting the List of Predictions for Creating Sector Traffic Maps
Import, LoadVectors 140
Studies, SelectNullMarginOnly 138
Loading, Activating, and Setting Add‐ins as Visible
Selecting SC and PN Offset Allocation Strategies Available in the
Add‐ins, ’Add‐in Name’ 146
GUI
Making Atoll Case‐Sensitive for Database Import From Planet
CDMA, CodeStrategies 174
PlanetImport, SensitiveCase 155
Selecting the Interference Matrices Used During the AFP
Making Redundant Fields in the Transmitters Table Read‐only
AFP, WorstCaseIM_FskAfp 167
GSM, CanEditTRXInfoAtTXLevel 168
Selecting the Logo 2 Check Box by Default in Print Setup
Making the Antenna Additional Electrical Downtilt Accessible
Print, LogoFooterChecked 144
Antenna, REDTDisplay 150
Setting a Common Display Resolution For All Coverage Predic‐
Managing Carriage Returns in Imported TXT and CSV Files tions
Export, NewLineEscapeSequence 148 Studies, SpecifyResolutionAfterComputation 160
Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Setting a Default Value for the Cell Edge Coverage Probability
Files
Shadowing, Reliability 158
MITAB, ’Coordinate system definition in the header file’
Setting an Alarm for the Licence End Date
138
License, TimeBombNotice 153
Modifying the Default Database Connection Time‐out
Setting PDCCH to 100% Loaded in LTE Interference Calculations
Database, CommandTimeout 155
LTE, ApplyDLLoadOnPDCCHInterf 178
Modifying the Default Detection Time‐out
Setting Precision of the Rasterisation Process
RemoteCalculation, DetectTimeOut 153
Rasterization, Improve 173
Modifying the Default Format of Link Names
Rasterization, MaximumSurf 173
MWLinks, AutoNameForbiddenChars 181 Rasterization, Precision 173
219
Rasterization, SurfRatio 173 PlanetImport, ChangeKclutterSign 156

Setting the Antenna Patterns Modelling Method Setting the TIFF Colour Convention
Antenna, CatalogVerticalDiagramOrientation 157 TiffExport, PaletteConvention 136
Antenna, InterpolatePatternEvenIfOnlyOneDiagram 157 Setting the Transmission Diversity Gain
Antenna, InterpolatePatternIndB 157 Studies, 2GTxDiversityGain 168
Setting the Best Server Calculation Method in Same Priority HCS Setting the Type of Database Being Used
Layers
Database, ExclusiveProvider 157
Studies, UseThresholdForSameLayerPriorities 166
Setting Uplink Noise Rise Control Parameters in LTE
Setting the Calculation Method for HS‐PDSCH CQI
LTE, NR_CONTROL_MARGIN_MIN 179
CDMA, CQIDeltaWithPower 171 LTE, ULNRControlMethod 179
Setting the Default BSIC Format LTE, ULNRControlPrecision 179
BsicFormat, DefaultValue 165 Solving Alignment Issue in Generated Reports
Setting the Display Precision of Floating Point Values MWReport, tab 182
Grids, NbDecimals 141 Specifying the Location of the Acp.ini File
Setting the Distributed Calculation Server Priority ACP, iniFile 185
RemoteCalculation, AtollSvrPriority 152 Starting TRX Indexes at 1
Setting the Maximum AS Size for SC Interference Prediction GSM, FirstTRXIndex 169
Studies, SCActivesetMaxSize 175 Stopping Calculations on Error
Setting the Maximum Number of Lines in Coverage Prediction Studies, ContinueOnError 159
Tool Tips Suppressing 3G Cell Name Carrier Suffixes
Studies, MultiplePlotsTipTextLines 150 3GCells, NoSuffixIfUniqueCarrier 170
Setting the Maximum Number of Rejections for HSDPA Mobiles Switching Back to the Old Best Server Determination Method
CDMA, HSDPAMaxRejections 172 CDMA, MultiBandSimu 174
Setting the Maximum Number of Rejections for Mobiles Switching Back to the Old Radio Bearer Allocation Algorithm for
CDMA, MaxRejections 172 Multi‐carrier EVDO Rev.B
Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise CDMA, SharingEquallyPower 174
Rise Estimation CDMA, UsingPreviousIterationPowerWeight 174
UMTSSimus, MaxReuseFactor 175 Switching Between Synchronised and Unsynchronised Interfer‐
Setting the Minimum ATL File Size Requiring Compression ence Calculation Methods
Compression, StartSizeInMB 146 LTE, SameItf_PDSCH_RS_PDCCH 178
Setting the No‐data Value for Clutter When Importing Data From Synchronising Private and Shared Path Loss Matrices
Planet EV Pathlosses, FullResyncPrivShared 144
PlanetImport, ClutterNoData 156 Taking Second Order Neighbours into Account in the AFP
Setting the Number of Parallel Processors and Threads OFDM, SecondNeighbours 178
RemoteCalculation, NumberOfProcessors 160 Updating A>>B and B>>A Profiles in Real‐time
RemoteCalculation, NumberOfThreadsMicrowave 160 MWCalculations, UpdateOppositeHop 181
RemoteCalculation, NumberOfThreadsNeighbour 160
Using a Unique Symbol for Remote Antennas
RemoteCalculation, NumberOfThreadsPathloss 160
RemoteCalculation, NumberOfThreadsSimulation 160 RemoteAntennas, FrozenSymbol 149
RemoteCalculation, NumberOfThreadsStudy 160 Using Old Min C/I Values
RemoteCalculation, NumberOfThreadsStudyTile 160 Compatibility, MWEquipment_CIMIN 182
Setting the Number of Transmitters per Drive Test Data Path Using Only Bearers Common Between the Terminal’s and Cell’s
TestMobileData, NumberOfTestMobileTransmitters 184 Equipment
Setting the Power to Use for Intra‐cell Interference in HSDPA OFDM, UseCommonBearersOnly 176
CDMA, PmaxInIntraItf 171 Using Only Visible Clutter Classes in Interference Prediction
Setting the Precision for the Antenna Pattern Verification at Reports
Import Clutter, OnlyVisibleClassesInInterferenceReport 144
Antenna, PrecisionTimes10 141 Using Only Visible Geo Data in Prediction Reports
Setting the Precision in Coverage Prediction Reports Geo, ReportObeysVisibility 142
Studies, ReportDecimalPlacesAbsolute 145 Using Poisson Distribution in Monte‐Carlo Simulations
Studies, ReportDecimalPlacesPercent 145 Simulation, RandomTotalUsers 162
Setting the Priorities for GUI and Calculations Using the ABS Patterns Throughout a Cell in LTE
RemoteCalculation, Priority 160 LTE, UseABSonCellEdgeOnly 180
Setting the Resolution of Population Maps in Coverage Predic‐ Warning About Prediction Validity When Display Options are
tion Reports Modified
Population, ReportResolution 145 Studies, RecomputationWarning 159
Setting the Sign for KClutter When Importing Data From Planet
EV
220
AT321_AM_E4 Atoll 3.2.1 Administrator Manual
221
• Head Office • US Office • China Office
7 rue des Briquetiers 200 South Wacker Drive – Suite 3100 Suite 302, 3/F, West Tower, Jiadu Commercial Building,
31700 Blagnac, France Chicago, IL 60606, USA No. 66 Jianzhong Road, Tianhe Hi‐Tech Industrial Zone,
Tel: +33 562 747 210 Tel: +1 312 674 4800 Guangzhou, 510665, P. R. of China
Fax: +33 562 747 211 Fax: +1 312 674 4847 Tel: +86 20 8553 8938 Fax: +86 20 8553 8285
AT321_AM_E4 www.forsk.com October 2014

Atoll 3.2.1 Administrator Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Atoll 3.2.1 Administrator Manual

Uploaded by

Copyright:

Available Formats

Version 3.2.

11.1.1.30 Customising Performance Optimisation when Exporting Vector Files in TAB Format . . . . . . . . . . . . . . . . . . . . . . . . . . 143

11.1.5.13 Enabling Partial Refresh from Recently Upgraded Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

11.1.8.7 Enabling Orthogonality Factor in Pilot EC/NT Calculation in HSDPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

11.2.2.1 Default Settings of the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

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

Provider Atoll version providername

Atoll Oracle Equivalent Microsoft SQL Server Equivalent Microsoft

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

Field Type Description

Field Type Description

Field Type Description

Field Type Description

Field Type Description

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

SQL > connect AtollADMINUMTS/ADMINUMTS@AtollDB;

SQL > commit;

SQL > alter table SITES add (POSTCODE number);

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

SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS;

SQL > commit;

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

Field Type Description

Field Type Description

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

32045 = "NAD27 / Vermont"; 2; 267; 6, -72.5, 42.5, 500000, 0, 0.9999643; "United

Code Cartographic Units Code Geographic Units

Code Datum Code Datum

Code Datum Code Datum

Code Projection Method Code Projection Method

Code Name Major Axis Minor Axis

Code Name Major Axis Minor Axis

Index Projection Parameter Index Projection Parameter

pixeltype Type of data read (in addition to the length)

UNSIGNDINT Undefined 8, 16, 24 or 32 bits

So, we have V = Vread  valuescale + valueoffset

nodatavalue Value corresponding to “NO DATA”

Byte Description Remarks

Byte Size Contents Description Applies to

Byte Size Contents Description Applies to

0 11 ASCI field name, 0x00 termin all

Size Type Description/Storage Applies to

Byte Size Description Applies to

Field Type Description

Field Type Description

Field Type Description

Column Name Description

# Calculation Results Data File.

# Calculation Results Dictionary File.

Column Name Type Description

# Calculation Results Dictionary File.

# Calculation Results Data File.

# Calculation Results Data File.

Column Name Description

# Calculation Results Data File.

Column Name Description

# Calculation Results Data File.

# Cell edge coverage probability 75%.

Field Type Description

Field Type Description

• Under <UMTS>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, ALPHA, FORTHO,

<?xml version="1.0" encoding="UTF-8"?>

<field length="50" type="text" name="NAME"/>